Challenge & Selection The tool I decided to use was Storytelling, to improve my understanding and use it in my  job. In my current role, I lead discussions with both technical and non-technical  stakeholders from both my employer and our customers, which are usually European  banks and utilities (mainly electrical infraestructure providers). I find the tool of storytelling  very useful to make business stakeholders relate to technical proposals and problems, and also to help technical teams understand non-technical requirements. This way, by  delimiting the context of the problem and hinting at possible technical solutions, I use  storytelling as the key part of the transition from business requirements to technical  specifications

Application I start the process by empathizing with our customer’s subject matter experts: after actively listening to them, I create a story summarizing how I understood the business problem.  This way, the stakeholders participate in the drafting of the context of the project. After  refining with them, the story is transmitted to the technical teams so we can elaborate the  technical specifications.

Insight The main insight I got by applying this tool was that contextualized stories are a better way to understand problems than simply handing out or writing specific requests. Although it  might seem slower at first, using Storytelling we are able to reduce the number of  meetings needed for a complete gathering of requirements or specifications.

Approach Depending on the client, I might use this same tool the same way, or try combining it with  Visual Thinking so as to immprove the shared understanding of the problem, its context  and implications.


Challenge & Selection The tool I decided to use was Storytelling , to improve my understanding and use it in my job . In my current role , I lead discussions with both technical and non - technical stakeholders from both my employer and our customers , which are usually European banks and utilities ( mainly electrical infraestructure providers ) . I find the tool of storytelling very useful to make business stakeholders relate to technical proposals and problems , and also to help technical teams understand non - technical requirements . This way , by delimiting the context of the problem and hinting at possible technical solutions , I use storytelling as the key part of the transition from business requirements to technical specifications Application I start the process by empathizing with our customer ’s subject matter experts : after actively listening to them , I create a story summarizing how I understood the business problem . This way , the stakeholders participate in the drafting of the context of the project . After refining with them , the story is transmitted to the technical teams so we can elaborate the technical specifications . Insight The main insight I got by applying this tool was that contextualized stories are a better way to understand problems than simply handing out or writing specific requests . Although it might seem slower at first , using Storytelling we are able to reduce the number of meetings needed for a complete gathering of requirements or specifications . Approach Depending on the client , I might use this same tool the same way , or try combining it with Visual Thinking so as to immprove the shared understanding of the problem , its context and implications .