Design an awesome experience! Part four.

-

Let's get physical

Involved in a service of any kind there will be work that not necessarily is very visible. Visualizing progress or work behind the scenes or even giving the user some sort of price or token for using the service creates a more personal relationship or even feeling of ownership to the service. This boosts loyalty and the user is most likely to return time and again.

Getting physical would be far easier in a physical world. Now, in this context, the closest we get to getting physical would be by sending the user a price of sorts, but that would be expensive and not least – it would be very slow and taken out of context. What we need is something that would pamper the user and tie the price to the context, so the user experience some sort of reward for being loyal.

This is where we can draw advantage from social gaming, rewarding the user with points or badges for their activity. By ranking the users by their activities, or even by their contributions, we can easily achieve service awareness and loyalty.  

Therefore, in the context of designing an intranet, we use social gaming as a mean to boost usage and loyalty. In SharePoint, by creating lists that keep track of scores and workflows we can award contributions and other activities, and even keep the history from these events. We trigger activity by listing ranks and suggesting to the user how to improve his or hers ranking.

The figure above shows one example on how points, badges etc. can be used as rewards for contributions and service loyalty. The images is a screen dump from my profile at Stackoverflow.com

Comments

Post a Comment

Popular posts from this blog

Designing and programming - Part 2

-
This part of the series will handle the creative part of the cycle. You might loosely categorize the steps of the design process in three different stages. First is the creative methods - this stage contains methods that drives the design project forward adding new ideas and features to the design. However, systemizing the ideas and filtering them is also part of this stage. The next stage contains different methods of implementation. This is where the ideas meet the matter - where ideas become code and components. You get the idea:) The third and last stage is perhaps the most crucial one. This is where you test and evaluate your results. It is now that you have to decide whether the implementations meet with the requirements and visions of the design. The outcome of this stage will determent if the prototype is ready for some real world testing, also called a beta. Anyways, after clearing that up, the creative stage is what this part of the series will be all about. The Creati
Read more

Filtering Dropdown choices in a Power Pages form using Dataverse Relations

-
Image
Filter dropdowns Dropdown filters are a useful feature in form design, allowing users to filter options in one dropdown based on other selections in the form. In Power pages, leveraging the capabilities of Dataverse relations makes it possible to create these powerful filtering mechanisms. This is how it works. What you need to know first. Before we dive into the implementation details, ensure that you have a basic understanding of Power Pages forms and Dataverse relations.  How is´t made Create two tables in your Dataverse environment: "Type" and "Category." These tables will hold the relevant data for the dropdowns. Establish a Lookup Relationship between the "Category" and "Type" tables. Create a lookup column in the "Category" table that references the "Type" table. This lookup column will allow us to filter the categories based on the selected type. Now, create a third table called "Request." This table will ser
Read more

Exploring the Power of Variables in Liquid and Power Pages

-
Covering the basics - Variables As a templating language, Liquid offers a rich collection of possibilities for web developers and designers, bringing Dynamics business data to the web. Variables in Liquid enable us to display dynamic content and enable us to implement a certain level of custom logic as well. We'll have a look at some examples on how to work with variables. Variable Assignment In Liquid, variables can be assigned values using the {% assign %} tag. For example, let's assign the value "Hello, Nerd!" to the variable greeting: {% assign greeting = 'Hello, Nerd!' %} Variable Output Once a variable is assigned a value, it can be outputted using the {{ }} syntax. To display the value of greeting, we can use: {{ greeting }} Assigning Site Settings Liquid is powerfull enough to allow you to assign values from site settings to variables. For example, if you need the site setting for inactivity for
Read more