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

Power Pages Manifest Explained related to Collaborative Development and ALM

-
In the Microsoft Power Pages, understanding the nuances of configuration files like the `manifest.yml` and environment-specific manifests (e.g., `dev.crm4.dynamics.com-manifest.yml`) is crucial. These files play a significant role in managing and deploying Power Pages sites, particularly in collaborative and ALM contexts. Understanding the Manifest.yml File First of all, always refer to the official documentation on how the power platform cli tool is supported. Creation and Usage Creation : The manifest.yml is generated through the pac powerpages download command. It serves as a snapshot of the Power Pages site's configuration, capturing details like page templates, form settings, and access permissions. Example: When you run this command, it creates a manifest.yml file that includes details of all the components such as web forms, entity lists, and site settings configured in the Power Pages site. Usage : The pac powerpages upload command utilizes the manifest.yml file to updat
Read more

Design an awesome experience! Part three.

-
Image
Chunk it up! Designing complex services requires that you fill in all the blanks in the service journey. Dividing the your design into a preface, main face and post face helps you focus on what happens before, during and after the user have interacted with the service. The preface is where the user encounters your service for the first time. You need to ask questions like; how will the user become aware of the service? What parts of the service does the user interface with and how are they presented? Does the service solve the right problems? What is the impression the user is left with after leaving the service and how likely is it that the user will return? Let us assume that we have interviewed our stakeholders. Sally from accounting have a need for registering correct hours before billing the company’s clients. Her need is to get the system implemented as soon as possible and getting the users to hand in their hours using the new system instead of handing it i
Read more