Time
30 min
People
2–5, core team

Overview

List everyone invested in or affected by the project, place them on a matrix of influence against interest and availability, then decide the engagement approach per quadrant. Its real job is to catch the person who can veto the work in week six but was never invited in week one.

Two things make the IFS version better than the textbook one. It puts availability alongside interest, which is the honest constraint — a director may care deeply and still have twenty minutes a month. And it does not stop at the map: the second half is agreeing how you will engage each group, which is the part usually skipped.

  • When to use it.

    Ahead of the framing workshops, before you finalise an invite list — and specifically when the product team is unsure who should be involved while filling in the Discovery brief’s steering committee section. Revisit it if the scope changes, because a wider scope usually pulls in a new decision-⁠maker.

  • Who to involve.

    Two to five from the core team. Include at least one person who understands the organisational politics, not only the org chart — that is who knows which director actually decides.

  • Effort.

    Low prepMedium engagement

    Fully facilitated; no prep beyond booking the room.

  • Outcomes.

    An invite plan for the framing workshops, named decision-makers for direction and for spend, and an agreed engagement method per group. It feeds the steering committee section of the Discovery brief directly.

  • Recommendations.

    Top left is the dangerous quadrant — high influence, low interest are the people to brief rather than invite, and the ones who cause the week-six surprise if you do neither. Name individuals, not just job titles: discoveries stall on people. And turn the quadrants into calendar entries, because “actively engaged” means nothing until there is a recurring slot in someone’s week.

How to run it

  1. List everyone

    5 minutes

    Individually and in silence, write down every person and team invested in the project or affected by its outcome, directly and indirectly — including people outside the product team: support, implementation, sales, compliance.

  2. Place them on the matrix

    15 minutes

    Influence up the side, interest and availability across. Discuss as you place rather than debating each name in isolation; moving stickies next to each other resolves disagreements faster than talking about them does.

  3. Agree the engagement approach

    10 minutes

    Work through the four quadrants and decide the method for each, not just the label.

QuadrantApproachWhat the board says about them
High influence, low interestKeep satisfiedHas a significant stake in the direction and will offer support as needed
High influence, high interestActively engagedRegularly provides input and helps move the project forward
Low influence, low interestMonitorOccasionally needs updates, and can provide context when required
Low influence, high interestKeep informedWants to stay informed, and will give feedback or input as needed
  1. Mark the decision-makers explicitly

    Ask the group directly: who signs off on direction, and who signs off on spend? Write their names next to the matrix — often two different people, and often neither is the loudest voice in the workshop.

Also on this board

An Ecosystem mapping exercise: a visual map of the people, organisations, systems and technologies a user touches during an experience, with the value or data exchanged noted on each connection. It runs later in the workshop and builds directly on the stakeholder list, so it is worth knowing it is there before you open a second board.