- If you follow a design thinking process,
it only takes a couple of weeks to show results.
You'll have clear project goals and the thing
you plan on building will already have been
prototyped and tested.
With technical team members involved from the beginning,
feasibility is less of an issue.
Costing will be clearer because you'll have a plan
with set phases and built in test points and metrics.
You've reduced the risk right from the first iteration.
There's still an opportunity to fail but you've reduced
the potential for that to happen.
As you move forward, you'll have multiple opportunities
to measure so multiple opportunities to change direction
and deliver the right product.
Communication is vital.
It will be hard to over communicate both among team members
and to the broader organization.
There more people who know what you're planning
on delivering, the more likely it is you'll find issues
or conflicts early enough to take evasive action.
The artifacts you create during the design
thinking process will make it much easier to communicate.
Each one from your initial experience map
summarizing the customer journey through to your paper
prototype showing your proposed solution.
There's people from outside the team understand
and more importantly contribute to your deliverables.
Of course, you might want to make prettier versions
of some of these artifacts so you can take them
to meetings and show them to people
but there's some real value in keeping the original
versions up on the wall in your team area.
It shows that you really did do all the messy work
to make this design happen and it's easier for anyone
from the team to just walk someone through
the story map, experience map, design straight output
or storyboards to help them understand
why the team's taking a particular direction.