A Lightweight Stakeholder Map for Small Team Choices. You do not need enterprise RACI. You need who can block you and who lives with the result.
Four lists on one sticky wall
Before a working session, write four lists: Decide, Do, Consult, Inform. Decide is who can say yes. Do is who builds. Consult is whose expertise could change the answer. Inform is who learns after the call, not during it. Ten minutes of mapping beats an hour of confused debate about who should have been invited.
Keep the map on one page. This is not a CRM, not a power analysis workshop, not a org chart redraw. It is a meeting design tool for one decision. Revisit when scope changes—a map for a pilot is wrong for a company-wide rollout.
Circle conflicts before the session: two names in Decide, or a Consult person who believes they Decide. Resolve ownership in a five-minute side chat instead of performing democracy in a twelve-person room.
Photograph the map or paste it into the invite description. Attendees arrive knowing whether they are deciding, building, consulting, or listening later. Surprises in role create defensive meetings; clarity creates shorter ones.
Decide versus Do: the conflict that stalls teams
Decide should be one person whenever possible. Two Deciders is deadlock risk wearing collaboration clothing. Do can be many people, but Do does not mean Decide by accumulation. Builders recommend; Deciders commit.
Common stall: the tech lead and product lead both believe they Decide. Fix by naming who owns tradeoffs for this decision only— not forever, not for all topics. “For vendor selection this month, Alex Decides; Sam Consults on integration” ends weeks of circular review.
Another stall: Decider is absent but Consult is full. That usually means the meeting is premature. Move builders to async spec review; schedule Decide time when the Decider is present. Consult without a Decider present often becomes speculative redesign.
Document the Decide name in the meeting notes header every time. Headers train behavior faster than verbal reminders that fade by the next sprint. When Decide changes mid-project, update the header and notify Do—the builders suffer most when ownership shifts silently.
Consult without inviting the whole company
Consult past four names is often campaigning, not listening. Pick experts whose input could change the answer—not everyone affected, not everyone senior, not everyone polite to invite. Affected people often belong in Inform after decide, not in Consult during design.
Give Consult a deadline and a question, not an open floor. “Can legal live with phrasing A or B by Thursday?” beats “What does everyone think?” Consult answers should arrive async when possible; reserve live time for unresolved forks only.
Politeness that doubles meeting size is still a cost. If someone moves from Consult to Inform, tell them why: their input is valuable after direction is set, not before. Most people prefer clarity to ambiguous attendance.
Inform after, not during
Inform is a short send once Decide happens: what changed, what starts, what they should stop doing. Inform people do not need live seats while options are debated. Keeping them out reduces performative alignment and speeds the working session.
Template for Inform notes:
- Decision in one sentence
- Effective date
- Action for Inform audience (if any)
- Link to decision log entry
After the change lands, note which conversations moved skeptical Inform recipients. Keep those conversation types. Drop meetings that only produced slides nobody opened. The map is a living note, not marble.
When scope jumps from pilot to rollout, redraw the map instead of assuming names carry over. Consult for a pilot might be Inform at rollout scale. Decide might move up a level. Ten minutes of redraw prevents forty minutes of wrong-room debate.
Workshop opening you can paste into the invite
Paste this into the meeting description: Before we debate options: Decide ___, Do ___, Consult ___, Inform ___. Working session starts only after Decide is present. That single block sets expectations better than a long policy doc nobody reads.
Open live with a sixty-second read of the four lists. Ask: Any conflicts on Decide? Resolve conflicts before option A versus option B. Option debates without Decide present are expensive drafts that may be thrown away.
Close live by naming who sends the Inform note and by when. Inform without a sender becomes “someone will communicate”—which means nobody will. Assign the sender in the room; put the send time on the calendar.
Maps fail when they become org charts. If your map has twenty names, you are listing stakeholders, not designing a meeting. Cut until the working session can fit on one screen and still leave room for builders to think.
After three uses, compare maps to meeting outcomes: Did Decide actually decide? Did Consult change the answer? If Consult never changes the answer, your Consult list is too large or too vague. Trim names until Consult hurts to cut—that is probably the right size.
Example map for a tool pilot: Decide—product lead; Do—two engineers; Consult—security and finance, async by Wednesday; Inform—customer success after Thursday decide. Working session: ninety minutes with Decide present. Without the map, customer success would have joined hour one and lengthened option debate by thirty minutes.
Save maps next to decision log entries. Six months later, you can see not only what you chose but who was in the room by design—not by accident. That history improves the next map faster than generic meeting training slides.
Map the next working session tonight
For one upcoming decision, write Decide, Do, Consult, Inform names before you send the invite—and trim Consult until it hurts slightly. Resolve Decide conflicts in a side chat, not in the big room. Practical teamwork guidance; not a substitute for your organization’s official governance rules.