We are rapidly delivering software without realising its impact on business before deployment. Our average success rate in Agile is merely 39% according to Standish Report. This is because processes and tools that we currently use only capture the functional and overlook emotional needs of the customer. Our user story capture and mapping process is fundamentally flawed and require complete rethink. It’s no surprise that we are on a mission to find better ways of product development to deliver value to customers. Design thinking offers a way forward for user-centric development.
Design thinking is one of emergent approaches that imagine the world differently than it currently is. The value of asking interesting questions is a central tenant of design thinking. It is an approach that is human-centred, possibility-driven, option-focused and iterative in nature that focuses on running experiments with the users instead of analysis of historic data to craft solutions. It is a way of approaching a challenge that offers another skillset that is complementary to other forms of thinking for product development such as Agile.
Mohinder’s talk is centred around demystify design thinking and how it is suited during the discovery phase of an agile development. It takes you through customer journey from touch points and moment of truth instead of activities and tasks that we are so used to in agile. Mohinder highlights crucial differences between customer journeys mapping in design thinking to user story mapping in agile that makes design thinking a better way of capturing customer needs. This is just one aspect of design thinking where it shines but there is more than meets the eye such as brainstorming with a difference, low fidelity prototyping, assumption testing and visualization. Mohinder emphasises kinds of problems where design thinking is best suited, misconceptions and pitfalls to avoid
You must be a Member to view this post and you are currently not logged in.
You can either log in below or sign up here.