Mind mapping

Challenge When creating new software we often have to offer solutions to varying users. Each group of users  may work with a subset of the functionality that shall be offered and often does not see the complete value chain. It is usual that different user groups make use of some part of the data offered and input some new data or actions that will affect other user groups. If we design a system with to few users involved the risk is that the system will solve to small part  of the problem at hand. And it may feel unfamiliar to the users that was not involved in the process  from the start. Mind mapping involving enough variety of users help us get a good overview of the problem  domain.

Selection I have selected to use mind mapping to create a set of insights that is shared in the group before  taking on the what if part to create common ground in the group.  We do this to ensure that we have deep enough knowledge in the domain and all share a common  mind model of the system to be before starting on the what if phase. In this way we reduce the risk of creating a system that is not aligned with all user groups. We see this a as good tool to unleash creativity and intuition(as described in the video week 3 -  Mind Mapping). So we get new good ideas on the table to go forward with.

Application To start with we get hold of persons know the domain or that may be future users of the software  and make sure that we have some from all the departments involved.  Through interviews with each of them we get hold of statements, maps, charts and process  descriptions. This forms the basis for several posters. We spread the posters on the walls of a  conference room to form a gallery. We then get a group of people, around 10-15 to participate in a workshop. We group them in small  groups and give them green and yellow post-it notes. They are then allowed to move around individually studying the gallery that we made. As they gain  insight or new ideas they make a note of it on a green sticker and keep it on their clipboard. If there  is some information that is missing they make a yellow sticker with some additional information. Then all go back to their group and spend some minutes sorting through the stickers. Then the  group make a common overview where the familiar notes are clustered. Then the insight related to each cluster of notes is noted on new notes placed on top of the cluster. The clusters have some relationships between them that the participants identify. In the summary the insights on the clusters and the relationships between the clusters form the  design criteria we bring with us into the what if phase.

Insight Often we see that the user groups use different names for the same concepts and some times have  differing mental models of how it is supposed to behave. Bringing user groups together to form some aligned model before further design steps is essential to be able to present solutions that will fulfill all needs. This is also neccessary to avoid rejecting some users view - that will be a detriment to the implementation of the system.

Approach We have some times placed to little emphasis on the lonely notes, the outliers. So they have been  lost from the design criteria before starting the design phase. It have some times led to redesign of  parts due to over simplification of some areas.

In hindsight we could have saved quite soome time recognizing the importance of that information  at an earlier stage.


Mind mapping Challenge When creating new software we often have to offer solutions to varying users . Each group of users may work with a subset of the functionality that shall be offered and often does not see the complete value chain . It is usual that different user groups make use of some part of the data offered and input some new data or actions that will affect other user groups . If we design a system with to few users involved the risk is that the system will solve to small part of the problem at hand . And it may feel unfamiliar to the users that was not involved in the process from the start . Mind mapping involving enough variety of users help us get a good overview of the problem domain . Selection I have selected to use mind mapping to create a set of insights that is shared in the group before taking on the what if part to create common ground in the group . We do this to ensure that we have deep enough knowledge in the domain and all share a common mind model of the system to be before starting on the what if phase . In this way we reduce the risk of creating a system that is not aligned with all user groups . We see this a as good tool to unleash creativity and intuition(as described in the video week 3 - Mind Mapping ) . So we get new good ideas on the table to go forward with . Application To start with we get hold of persons know the domain or that may be future users of the software and make sure that we have some from all the departments involved . Through interviews with each of them we get hold of statements , maps , charts and process descriptions . This forms the basis for several posters . We spread the posters on the walls of a conference room to form a gallery . We then get a group of people , around 10 - 15 to participate in a workshop . We group them in small groups and give them green and yellow post - it notes . They are then allowed to move around individually studying the gallery that we made . As they gain insight or new ideas they make a note of it on a green sticker and keep it on their clipboard . If there is some information that is missing they make a yellow sticker with some additional information . Then all go back to their group and spend some minutes sorting through the stickers . Then the group make a common overview where the familiar notes are clustered . Then the insight related to each cluster of notes is noted on new notes placed on top of the cluster . The clusters have some relationships between them that the participants identify . In the summary the insights on the clusters and the relationships between the clusters form the design criteria we bring with us into the what if phase . Insight Often we see that the user groups use different names for the same concepts and some times have differing mental models of how it is supposed to behave . Bringing user groups together to form some aligned model before further design steps is essential to be able to present solutions that will fulfill all needs . This is also neccessary to avoid rejecting some users view - that will be a detriment to the implementation of the system . Approach We have some times placed to little emphasis on the lonely notes , the outliers . So they have been lost from the design criteria before starting the design phase . It have some times led to redesign of parts due to over simplification of some areas . In hindsight we could have saved quite soome time recognizing the importance of that information at an earlier stage .