Design an awesome experience! Part one.

-
The methodology behind designing service journeys provides you with great analytical tools that will fit almost any kind of experience. Working in the areas of design, development and project management this approach have been amongst my favorites for many years, but I’ve never taken the time to really document the way I use it.

Years ago, I attended a session demonstrating AT-ONEs Touch-point cards, and how simple images and text can be used to design a service or a service journey. I have kept my stack of cards and used them in every project I have worked on since.

The last few years I have dived into different methodologies and dragged more concepts into my work as I saw them fit. Now, time is overdue to tie some threads together and document my work. My next few blog posts are dedicated to this subject, and I hope that they can be helpful.
My context is based on designing web and intranet experiences, so naturally I will try to tie up this in my examples. Designing a SharePoint intranet for a medium sized company will be the case for the series.

Service design

Service design cross into most disciplines. The service itself forms the very base for the existence of each discipline in the first place. Why? Because each discipline in one way or another supports the service being provided. The point being, leaving service design solely to one person in the organization will not work so well.

However, let us not lose focus on the subject. :) How is this relevant to your company intranet?
The answer is really – what goes in your intranet? We define an intranet to be an arena for collaboration, sharing information and working with documents and workflows. The users find their tools for registering hours, sharing documents and for social interaction across the organization. All users will use a portal as their starting point, and will find their tools and content using search and navigation.

In order to design a coherent experience providing the users with content exceeding the native functionality of the intranet, we need input from the right people. Mapping different stakeholders and using them as resources for the design process helps collecting the input and set the requirements for the design.

So, here’s the case:
Sally from accounting want the company’s employees to register their hours using a new reporting system. Her requirement for the intranet is to provide a link to this system. The link must be visible and easy to find. Max, the sales manager, want to check in his hours when he is on the road, connecting via his phone. Pat from IT, requires that access to the intranet is secure so company confidential information do not get lost.


Only providing a simple service as this shows the necessity of the design properly thought through. 


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