Page 95 - Transforming an Idea Into a Business with Design Thinking

74 ◾ Transforming an Idea Into a Business with Design Thinking

4.5.3.2 Review Prior Steps

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

4.6 Step 12: Experience Implications

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 credit worthiness, 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 bet-
ter idea of the value proposition and business model of your solution.

3. Technology. Finally, your solution is likely going to be leveraging tech-
nology. 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 leverag-
ing for your solution or must be thought about for implementation of
your solution.

4.6.1 Template (Figure 4.9)

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