# Storytelling ## Overview This is the final step of the project. After weeks of research, idea development, and testing, your team now needs to **make your work visible and understandable to others**. This tool supports you in building a clear narrative of your process—from your initial scope and insights to the concept you developed and what you are asking for now.\ It also helps you clarify how you will explain your proposal to others, and what kind of feedback or support you need to move it forward. By making your thinking transparent, you open the door to collaboration, feedback, and real-world implementation. {% embed url="" %} [Open in Google Slides](https://docs.google.com/presentation/d/1cuWWLvVJ83HX2rm8WWilr5WEXP8BBaHv_jkbEMUKBV8/edit?usp=sharing) {% endembed %} {% hint style="info" %} **⏱️ Time:** 60–90 minutes 👫 **Participants:** Whole team (especially those presenting or leading discussions) 🛠️ **Materials:** Storytelling canvas, outputs from all previous tools, any visuals {% endhint %} ## Input Before completing this canvas, ensure you have completed the following steps: {% content-ref url="/pages/dgtue9jVBZNLfGZAHuRa" %} [Re-Framing](/publicservicebooster/design-steps/4-re-frame-what-is-the-real-challenge-we-need-to-solve/re-framing.md) {% endcontent-ref %} {% content-ref url="/pages/UCNPTpLQZVD4FdAEW3bm" %} [Service Concept](/publicservicebooster/design-steps/5-design-what-ideas-could-address-the-challenge/service-concept.md) {% endcontent-ref %} {% content-ref url="/pages/MV4ET5F9HNZ1So9Nu8XW" %} [Testing Plan](/publicservicebooster/design-steps/6-test-would-the-idea-really-work-in-the-real-world/testing-plan.md) {% endcontent-ref %} ## Context Use this tool at the **final stage of the project**, when preparing to present your idea internally or externally. It is especially useful before pitching your proposal to leadership, user groups, partner organisations, or other stakeholders. This is not just about documentation—it’s a tool to align your team and activate others. ## Recipe {% stepper %} {% step %} #### Tell the story of your process Use the first part of the canvas to reflect on your project journey: * What was the [original scope](/publicservicebooster/design-steps/1-scope-what-challenge-are-we-addressing/service-challenge.md) or focus? * Who did you engage with, and how did you conduct your research? * What did you **learn** from the research—[interview](/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/user-interview.md), [observation](/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/user-observation.md), [journey map](/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/todays-user-journey.md), [business process map](/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/todays-business-process.md)? What did you learn about your users, your service and your organisation? What were the key insights and surprises from your work? * Based on that, what [question or challenge](/publicservicebooster/design-steps/4-re-frame-what-is-the-real-challenge-we-need-to-solve/re-framing.md) did you decide to address? * What [ideas](/publicservicebooster/design-steps/5-design-what-ideas-could-address-the-challenge/crazy-8.md) did you generate, and which one did you select? Why? {% endstep %} {% step %} #### Present your proposal In the second part of the canvas, showcase: * The [concept](/publicservicebooster/design-steps/5-design-what-ideas-could-address-the-challenge/service-concept.md) you have developed * A visual of the [future journey](/publicservicebooster/design-steps/5-design-what-ideas-could-address-the-challenge/tomorrows-user-journey.md), [process](/publicservicebooster/design-steps/5-design-what-ideas-could-address-the-challenge/tomorrows-business-process.md), and/or [prototype](/publicservicebooster/design-steps/6-test-would-the-idea-really-work-in-the-real-world/testing-plan.md) * Your [testing result](/publicservicebooster/design-steps/6-test-would-the-idea-really-work-in-the-real-world/testing-plan.md): how you got user feedback and what you have learnt {% endstep %} {% step %} #### Define your ask Think about your audience: what kind of support do you need from them? * Feedback on feasibility * Resources (for piloting, coordination, communication) * Help expanding or scaling the initiative * Endorsement or political buy-in * Involvement from other stakeholders Be clear and concrete about what you’re asking, and why. {% endstep %} {% endstepper %} ## Results A ready-to-share storyline that connects your process, insights, and proposal—plus a clear call to action for those you want to involve next. ## Tips * Be honest about what you know and what’s still uncertain—it is not just about convincing, but also to learn through feedback * Use tangible visuals (e.g. journey maps, sketches, prototypes) to help explain * Practice telling the story out loud—does it flow logically? * Tailor your message depending on your audience * Focus on why this matters to real users, not just your team *** ### [Share Your Experience](https://padlet.com/opsi/innovation-booster-collaboration-lmuadp5wornnbo86) We'd love to hear how you're using this tool! Please share your examples and feedback to inspire others and help improve the Booster. Submit your example today and be part of our community. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://oecd-public-service-innovation-b.gitbook.io/publicservicebooster/design-steps/7-communicate-how-do-we-gain-support-for-the-new-solution/storytelling.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.