Experience Implications in Design Thinking

Before you continue to build a productive solution or consider business value aspects, it is important to look at the implications of your future experience vision. These implications could be both dependencies and influences on other entities that may improve or diminish the overall value of the solution. Implications should be considered from the following three angles:

1. People. All connected or influenced stakeholders who are likely to be impacted by the solution.

2. Process. If the solution is part of a larger process, then which internal and related processes are likely to be impacted by the solution or will impact the implementation of the solution? This is primarily relevant for solutions that are suited for enterprises. However, it may also be relevant for personal/consumer solutions. For example, if your solution helps consumers with low credit get loans to buy used cars, your solution will be part of a larger car-buying process which includes searching for cars, checking creditworthiness, affordability calculations, car inspections,
car valuation, warranty, delivery, service, maintenance cost estimate and so on. Thinking of all these related processes will help you have a better idea of the value proposition and business model of your solution.

3. Technology. Finally, your solution is likely going to be leveraging technology. Thinking about various technology elements will help you have a better way to build and position your solution. As you think about the technology, think about the various systems, social and professional networks, data, algorithms and other tools that either you’ll be leveraging for your solution or must be thought about for implementation of your solution.

1. Experience Implications Template

This template is used to identify people, processes and technology implications for building a solution. It highlights obvious and latent needs and considerations early on.

User Implication Template
User Implication Template

Based on the future experience that you have envisioned and depicted in the storyboard, think about other dependencies in terms of expectations from other stakeholders. Also consider the impact on internal and external processes and the system and data dependencies.

2. Experience Implication Example

An example of how experience implication template could be filled is shown in the figure below:

3 Guidance

Session Lead
Draw the Experience Implications Template on the whiteboard and paste the scenes from the future experience vision on the top row. If you have three team members, assign each member to focus on specific implications: people, process and technology. It will be helpful to have the team members with capabilities in each area to be assigned to those areas. For example, the member focused on technology (a Chief Technology Officer in a start-up) should be focused on technology implications.

5-minute Self-brainstorm
Point out the first scene and ask each member to think about implications in their area and write the implications on sticky notes.

Team Brainstorm
Once the self-brainstorming session completes, each team member should paste their sticky notes at the appropriate swim lane/row and explain their ideas. Have an immersive discussion to ensure the whole team has a comprehensive understanding of the implications in all dimensions.
Move to the second scene and repeat the process. Continue moving through your experience vision and complete the entire Experience Implications Template.

3.1 Document Assumptions

After the session, the session lead should ask the team to write down all the assumptions made and record those assumptions in assumptions template in Stage 4.

3.2 Review Prior Steps

Review the prior steps and adjust as needed with the consensus of the team.