# Discovery Planning ## Overview In many public service contexts, teams jump into fieldwork without first aligning on why, how, and with whom research should be conducted. This often leads to fragmented efforts and missed insights. The Discovery Planning is designed to ensure your team has a shared, purposeful plan for conducting user-centred research. It helps you clarify your focus, select appropriate methods, and prepare for the logistical and ethical dimensions of fieldwork. {% embed url="" %} [Open in Google Slides](https://docs.google.com/presentation/d/1sPf3qWIPwvrHAGBdeIfqTp7EEgUrGXjlCW_Ngn7DVEE/edit?usp=sharing) {% endembed %} {% hint style="info" %} **⏱️ Time:** 60–90 minutes 👫 **Participants:** Core team (3–6 people) 🛠️ **Materials:** Printed canvas (A1 recommended), markers, sticky notes {% endhint %} ## Input Before completing this canvas, ensure you have completed the following steps: {% content-ref url="/pages/7afK8CiAQ1DpqChZLbb5" %} [Service Challenge](/publicservicebooster/design-steps/1-scope-what-challenge-are-we-addressing/service-challenge.md) {% endcontent-ref %} {% content-ref url="/pages/INg38Ka6W9AMTlzU6TdH" %} [Stakeholder Map](/publicservicebooster/design-steps/2-engage-who-are-we-designing-for/stakeholder-map.md) {% endcontent-ref %} ## Context Use this tool at the start of the research, after the challenge has been scoped but before interviews or observations begin. It is ideal for team sessions where alignment is needed on who to talk to, what to investigate, and how to go about it – especially when working across different departments or with external partners. ## Recipe {% stepper %} {% step %} #### Clarify the challenge Start by briefly noting the problem you’re exploring. This should reflect the framing done in the [scoping phase](/publicservicebooster/design-steps/1-scope-what-challenge-are-we-addressing/service-challenge.md), and remain open-ended – not solution-driven. {% endstep %} {% step %} #### Define who to engage Taking stock of the previous works on [stakeholder mapping](/publicservicebooster/design-steps/2-engage-who-are-we-designing-for/stakeholder-map.md) and [user characteristics](/publicservicebooster/design-steps/2-engage-who-are-we-designing-for/user-characteristics.md), identify your primary end-users and relevant stakeholders. Consider user characteristics (e.g. digital access, geography, literacy) and inclusion priorities. {% endstep %} {% step %} #### Draft research goals (at a high level) Clarify what your team needs to learn to understand the problem more deeply. Keep this broad for now – specific themes will be broken down in the Interview Objectives Sheet afterwards. {% endstep %} {% step %} #### Choose methods and tools Decide how to gather the insights you need – e.g. semi-structured interviews, in-context observations, journey mapping, process mapping. Each method reveals a different dimension of the current experience. Choose the one that best fits your **research goals**, the **type of insight** you’re looking for, and the **resources** you have. | Method | Best for… | Use when you want to… | Limitations | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- | | [**Interview**](/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/user-interview.md) (e.g. semi-structured) | Understanding user experiences, needs, motivations, and perceptions | Hear directly from users or staff about their thoughts, stories, or frustrations | Relies on what people say—not always what they do | | [**Observation**](/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/user-observation.md) (e.g. shadowing, fly-on-the-wall) | Seeing real behaviours in context | Understand how people actually interact with a service or system in practice | Can be time-intensive; requires trust and access | | [**Journey Mapping**](/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/todays-user-journey.md) (from user’s perspective) | Capturing the lived experience across time and touch-points | Visualise how a user moves through a service, including pain points and emotions | Based on reported experience or interpretation; may miss systemic factors | | [**Process Mapping**](/publicservicebooster/design-steps/3-understand-what-is-happening-now-and-why/todays-business-process.md) (from system/organisation’s view) | Clarifying internal steps, roles, and rules of the providers | Map how a service or process works behind the scenes; identify inefficiencies or blockers | May not reflect how users experience the process; needs insider knowledge | | {% endstep %} | | | | {% step %} #### Plan logistics Note where, when, and with whom the research will take place. Consider timeframes, access to users, ethics, translation needs, and internal capacity. {% endstep %} {% endstepper %} ## Results A shared plan that aligns the team on the purpose, scope, and logistics of research activities. Ready to begin recruitment and fieldwork. ## Tips * Make space for inclusion: who might be left out of your plan? * Avoid planning for “ideal” users only – seek out edge cases or those with the greatest barriers. * Don’t overcomplicate – start with a basic plan and adapt as you learn. * If you’re unsure how to reach a group, identify proxies or intermediaries. * Use this canvas collaboratively – diverse views strengthen your research framing. *** ### [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/3-understand-what-is-happening-now-and-why/discovery-planning.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.