# Free Intro to Stakeholder Engagement | ORBIT RRI > A free, self-paced 30-minute introduction to stakeholder engagement for research and innovation: mapping, listening, recording and returning findings. Source: https://orbit-rri.org/courses/introduction-to-stakeholder-engagement/ --- [Home](https://orbit-rri.org/index.html)/Free courses/Intro to Stakeholder Engagement # Introduction to *Stakeholder Engagement.* A free half-hour primer on stakeholder engagement for research and innovation. Who counts as a stakeholder, how to map them, how to plan a useful conversation, and how to feed what you hear back into the project. ## About this course **Format** Self-paced online **Time** Around 30 minutes **Level** Introductory **Prior knowledge** None needed **Cost** Free ## *Why* this course exists. Stakeholder engagement is one of the most cited and least practised parts of an RRI proposal. Researchers know they should talk to affected groups, then run out of time, then write the section the night before submission. The result is engagement on paper and not in the work. This thirty minute primer is designed to flip that. It is short, opinionated, and practical. It will not turn you into a community organiser, but it will leave you with a way of thinking about engagement that is realistic for the time and budget you actually have. ## *What* you will learn. By the end of the half hour you will be able to identify who counts as a stakeholder for a piece of research, sketch a basic stakeholder map, plan a useful engagement conversation, and decide how findings flow back into the project. - L1Who counts as a stakeholder - L2A simple two-axis stakeholder map - L3Planning a useful conversation - L4Recording what you heard, not what you wanted to hear - L5Returning findings to the project ## Who counts as *a stakeholder.* For the purposes of research and innovation, a stakeholder is anyone whose life is affected by the work you do, or who has a defensible interest in how it is done. That definition is broader than the common reading, and it is broader on purpose. It is worth being specific. Three useful cuts: - **Direct or indirect.** Direct stakeholders interact with your work or its outputs themselves. Indirect stakeholders feel the consequences without ever encountering the work. - **Affected or interested.** Affected stakeholders carry a real cost or benefit from the outcome. Interested stakeholders have a professional, regulatory or representational reason to follow the work. - **Voiced or under-voiced.** Some stakeholders already have a seat at every table. Others would not be invited unless someone deliberately invited them. The single most common mistake in stakeholder thinking is to list only the people who are already at the table. The whole point of the exercise is to surface the ones who are not. List the people whose lives are affected and the people who already have a voice. Pay particular attention to the difference between the two lists. ## A simple *two-axis map.* Once you have a list of stakeholders, the next move is to sort them. The two-axis map is the simplest tool that still produces decent decisions. The horizontal axis is **interest**: how much does this stakeholder care about what you decide? The vertical axis is **power**: how much can they actually shape what happens, either by funding, by approving, by adopting, or by blocking? Plot each stakeholder on the grid. Four quadrants fall out: - **High interest, high power.** Manage closely. These are the people the project succeeds or fails with. - **High interest, low power.** Keep informed. They care, but cannot move things on their own. They are often your best evidence base. - **Low interest, high power.** Keep satisfied. Quiet now, but able to derail a project later if they feel surprised. - **Low interest, low power.** Monitor. Light touch. This map is not the answer. It is a way of making the implicit explicit so a team can have a useful conversation about who they are actually planning to engage and who they are tacitly planning to ignore. Interest × power, four quadrants. The map is a conversation starter, not a delivery plan. ## Planning a *useful conversation.* Most stakeholder conversations fail because the team running them did not decide, in advance, what would count as a successful one. Five questions to settle before you walk in the room: 1. **Why this person, now?** A specific answer. "Because we are about to commit to X, and we have not heard from anyone who would carry the cost if X goes wrong." 2. **What do you want them to leave knowing?** Two sentences max. 3. **What do you want to leave knowing?** Three concrete questions, written down. 4. **What format suits them?** A patient advocate, a regulator, a clinician and a community group leader each prefer different formats. A coffee, a structured interview, a workshop, a written response. 5. **What changes if they push back?** Decide in advance which parts of the plan are negotiable. If nothing is, you are running an information campaign, not an engagement. A useful conversation is one where at least one of the five answers changes. Otherwise it was a briefing. Decide in advance what would count as a useful conversation. If nothing can change as a result, it is a briefing not an engagement. ## Record what you *heard, not what you wanted to hear.* Recording is where engagement projects most often go wrong. Two failures are common. **Selective listening.** The team writes up the parts of the conversation that confirm what they already thought, and leaves out the parts that do not. The remedy is to make the recording process less reliant on memory: capture quotes verbatim during the conversation, share the notes back to the person you spoke to within a week, and ask them to tell you what you missed or got wrong. **Premature distillation.** The team summarises a conversation into a single recommendation before the conversation is even over. The recommendation is then easier to argue with than the underlying evidence. The remedy is to keep the layered structure: what was said, what we think it means, what we propose to do, in three separate columns. Reviewers can challenge each layer separately. A good engagement record is one a future team member, reading it cold a year later, would describe accurately to a third party. That is the bar. Capture verbatim. Distil later. Share notes back to the person you spoke to as a sanity check. ## Returning findings *to the project.* Engagement is only worth doing if what comes out of it actually changes the work. That last step is the one that fails most often, usually because there is no agreed mechanism for findings to re-enter the project plan. Three habits that make this work: - **Engagement findings have a named owner** in the project team, the same way a risk has a named owner. Without that, no one's job is to act on them. - **Each finding is paired with a decision.** Either "we are changing X because of this", or "we are not changing X, for these specific reasons". Both count; a "noted" without either is the failure mode. - **The people you spoke to are told what changed.** A short note, a paragraph in a newsletter, a follow-up email. It costs almost nothing and is the only thing that builds trust for the next round. If a stakeholder you engaged once would speak to you again willingly, the engagement worked. That is the only test that matters. ## That's the intro *done.* Half an hour, five lessons, one practical habit: plan the conversation, capture it properly, send something back. If you are going to run engagement on a real project, the next move is either a stakeholder map for a current piece of work, or a tutor-led version of this material with role plays. ## Need to *actually plan* the engagement work? The free primer covers the thinking. The full course gives you a plan you can run with, plus a tutor to pressure-test it.