Mind mapping

Challenge

I work in the department of support for innovators through grants. Our goal is to ensure a transparent process for distributing grants to applicants. Our department employs 5 people who need to consider more than 200 applications in 45 days. Physically, we did not have time to process applications in manual mode, the employees were overloaded. As a result, the terms of consideration were violated. The solution to this problem was the development of an automated information system for processing applications. We will focus on trying to identify all business processes and identify where there might be gaps or failures.

Selection

I used the mind mapping tool to gain a general understanding of the innovation grant business processes before starting to develop the MVP version of the information system. I often use this approach when it comes to sequencing processes, scoping and assigning responsibilities in both my personal and professional life.

Application

I have used mind mapping techniques to allow developers and those who involved in the grant process to better understand the path from application acceptance to grant disbursement, to be able to identify pain points and opportunities for improvement or solutions. Our department began the development process by drawing a diagram on “Mindmeister”. In the center, a window for accepting applications was placed, then branches were launched on the sides, meaning the stages and who is involved at each stage. Each branch was also crushed and the procedure and terms were described in detail. So we could see the path/flow of the application at all stages of consideration and so that in the future we could see the status and progress of the application.

Next, we worked closely with the developers to clarify our goals and priorities. We divided the development of the system into sprints, where at each sprint we tested each stage. This tested our assumption that in the course of development gaps will be identified and we will continue to improve business processes.

Insight

Using the tool, our team identified our assumptions and developed a process map to test those assumptions. In addition, we have considered that the expected results may actually differ based on the deployment of processes. In the future, our team will review this understanding and include it in future stages of implementation.

Approach

The ease of using of this tool before starting a new project is that you start strategically thinking through the "skeleton" of your future project, and already before you launch it, you will have a clear plan of what to do about in the coming weeks and even months.


Mind mapping Challenge I work in the department of support for innovators through grants . Our goal is to ensure a transparent process for distributing grants to applicants . Our department employs 5 people who need to consider more than 200 applications in 45 days . Physically , we did not have time to process applications in manual mode , the employees were overloaded . As a result , the terms of consideration were violated . The solution to this problem was the development of an automated information system for processing applications . We will focus on trying to identify all business processes and identify where there might be gaps or failures . Selection I used the mind mapping tool to gain a general understanding of the innovation grant business processes before starting to develop the MVP version of the information system . I often use this approach when it comes to sequencing processes , scoping and assigning responsibilities in both my personal and professional life . Application I have used mind mapping techniques to allow developers and those who involved in the grant process to better understand the path from application acceptance to grant disbursement , to be able to identify pain points and opportunities for improvement or solutions . Our department began the development process by drawing a diagram on “ Mindmeister ” . In the center , a window for accepting applications was placed , then branches were launched on the sides , meaning the stages and who is involved at each stage . Each branch was also crushed and the procedure and terms were described in detail . So we could see the path / flow of the application at all stages of consideration and so that in the future we could see the status and progress of the application . Next , we worked closely with the developers to clarify our goals and priorities . We divided the development of the system into sprints , where at each sprint we tested each stage . This tested our assumption that in the course of development gaps will be identified and we will continue to improve business processes . Insight Using the tool , our team identified our assumptions and developed a process map to test those assumptions . In addition , we have considered that the expected results may actually differ based on the deployment of processes . In the future , our team will review this understanding and include it in future stages of implementation . Approach The ease of using of this tool before starting a new project is that you start strategically thinking through the " skeleton " of your future project , and already before you launch it , you will have a clear plan of what to do about in the coming weeks and even months .