Reflections on mind mapping in design thinking

Challenge:

The challenge is to increase the efficiency in which development teams move their work out into  production environment/s, while meeting a long list of requirements that are prone to change  without warning and are poorly understood within the organization.

Selection:

The tool I used to target this problem was Mind Mapping (Week 3). This is when I get together with  different interested parties/customers and create maps about what people understand about their  current processes and what they see as key problems. This is laid out in a freeform flow chart  allowing the people to emphasize and clarify their understanding of the problems.

Application:

I sat down with a range of mainly self-selected development teams within the organization and  developed individual Mind Map’s on how the teams worked and the steps they need to take their  changes all the way to production along with identifying key challenges they face as a team.

I also worked with the regulatory teams to create Mind Maps focussing on what they need from the  development teams to meet the regulations.

Insight:

I discovered through this process is that current requirements make their teams feel unempowered  and their releases are held at the whims of other teams with inconsistently applied requirements.

The moving the changes through the process involved a lot of hand offs to these different teams,  costing the development team time and energy to drive the change into production.

Approach:

Using the insights learnt from the Mind Mapping My team created a series of tools and procedures  as proofs of the identified concepts then we are planning to do a series of Learning Launches  (Week 4) to demonstrate tools and processes my team have created. Then iterating on the tools  and procedures to improve the development teams lives.


Reflections on mind mapping in design thinking Challenge : The challenge is to increase the efficiency in which development teams move their work out into production environment / s , while meeting a long list of requirements that are prone to change without warning and are poorly understood within the organization . Selection : The tool I used to target this problem was Mind Mapping ( Week 3 ) . This is when I get together with different interested parties / customers and create maps about what people understand about their current processes and what they see as key problems . This is laid out in a freeform flow chart allowing the people to emphasize and clarify their understanding of the problems . Application : I sat down with a range of mainly self - selected development teams within the organization and developed individual Mind Map ’s on how the teams worked and the steps they need to take their changes all the way to production along with identifying key challenges they face as a team . I also worked with the regulatory teams to create Mind Maps focussing on what they need from the development teams to meet the regulations . Insight : I discovered through this process is that current requirements make their teams feel unempowered and their releases are held at the whims of other teams with inconsistently applied requirements . The moving the changes through the process involved a lot of hand offs to these different teams , costing the development team time and energy to drive the change into production . Approach : Using the insights learnt from the Mind Mapping My team created a series of tools and procedures as proofs of the identified concepts then we are planning to do a series of Learning Launches ( Week 4 ) to demonstrate tools and processes my team have created . Then iterating on the tools and procedures to improve the development teams lives .