Engagement setup

Engagement Setup

Take an engagement from "we just won this work" to "the project is running." This covers the opening weeks: preparing the kickoff, mapping stakeholders, designing discovery, and setting the operating rhythm. For standalone facilitated sessions later in the engagement (strategy offsites, innovation sprints), see workshop-facilitation.

The goal is shared understanding and momentum. Not a stack of templates. Every artifact here earns its place by driving alignment or unblocking work. If it does neither, cut it.

Ask the client for real inputs (names, dates, volumes, org data) before filling anything in. Where you sketch an example number to show the shape of an analysis, label it as illustrative and flag it for validation. Never invent stakeholder positions, benchmark figures, or dollar impacts.

Phase 1: Pre-Kickoff Preparation

Before anyone gets in a room, do the homework. The quality of the kickoff is set here, not on the day.

Stakeholder Identification

Build the inventory early. You need it for invitation lists, interview scheduling, and knowing who can actually make a decision versus who only talks like they can.

Internal stakeholders (client side):

Name/Role	Function	Relationship to Initiative	Current Stance
	C-suite / VP / Director / Manager	Sponsor / Decision-maker / Contributor / Affected	Champion / Supporter / Neutral / Skeptic / Opponent

External stakeholders (partners, regulators, vendors):

Name/Role	Organization	Relationship	Current Stance
		Client / Regulator / Partner / Vendor

Stakeholder groups (when individuals are too many to track):

Group	Size	Influence	Impact on Them	Priority
		High/Med/Low	High/Med/Low	1-5

Fill "Current Stance" from evidence, not optimism. If you have not spoken to someone or heard a credible read on them, mark them Unknown and make finding out a discovery task. A map full of "Supporter" guesses is worse than an honest map with gaps.

Influence-Interest Analysis

Plot everyone on the power-interest grid. The quadrant sets your engagement strategy for that person.

                    HIGH INTEREST
                         |
    +--------------------+--------------------+
    |                    |                    |
    |   KEEP SATISFIED   |   MANAGE CLOSELY   |
    |                    |                    |
    |   Regular updates  |   Active engagement|
    |   Address concerns |   Co-creation      |
    |                    |   Regular 1:1s     |
HIGH+--------------------+--------------------+
POWER                    |
    |                    |                    |
    |   MONITOR          |   KEEP INFORMED    |
    |                    |                    |
    |   Periodic check   |   Regular comms    |
    |   Watch for shifts |   Feedback loops   |
    |                    |   Town halls       |
    +--------------------+--------------------+
                    LOW INTEREST

Score each stakeholder and name the specific move, not the quadrant label:

Stakeholder	Power (1-5)	Interest (1-5)	Quadrant	Strategy
			Manage Closely / Keep Satisfied / Keep Informed / Monitor

The high-power, low-interest cell is where engagements die quietly. Those people can veto your work but will not spend attention on it until it threatens them. Give them a light, deliberate touch (a short monthly note, one early 1:1) so their first real look is not an ambush.

Alignment and Resistance Assessment

Get a read on where people stand versus where you need them. The gap is the work.

Stakeholder	Current Position	Desired Position	Gap	Difficulty
	Opponent / Skeptic / Neutral / Supporter / Champion		Size of shift needed	High/Med/Low

For anyone showing resistance, diagnose the type before you plan the response. The fix for each is different, and treating a political objection as if it were a rational one wastes everyone's time:

Stakeholder	Resistance Type	Root Cause	Severity	Mitigation
	Rational / Emotional / Political / Cultural	Why they resist	High/Med/Low	Approach

Rational resistance yields to evidence. Emotional resistance (fear of losing status, workload, or identity) yields to reassurance and involvement, and evidence alone will not move it. Political resistance is about who wins and loses, so trace the stake. Cultural resistance is the slowest to shift because it is collective, not individual.

Map the influence network. Formal reporting lines are a poor guide to who actually persuades whom:

Stakeholder	Influences	Influenced By	Coalition Opportunity
	Who they sway	Who sways them	Potential alliance

Kickoff Materials

Prepare and share 24-48 hours before kickoff so people arrive with context instead of consuming the meeting to catch up:

1. Agenda with time blocks and a stated objective for each section
2. Project charter template (completed collaboratively in the room, not presented as a done deal)
3. Stakeholder map (sanitized for the audience; the raw version never leaves the team)
4. Working arrangements draft for discussion
5. Expectations document covering what you need from the client
6. Initial communication plan

Phase 2: Kickoff Workshop

The kickoff is about alignment, not information transfer. If people leave with different understandings of the problem, the scope, or how you will work together, the kickoff failed no matter how polished the slides were.

Agenda Structure

Part 1: Introduction (15 min)
- Introductions: name, role, and the one thing each person cares about most
- Project purpose and background
- Meeting objectives

Part 2: Problem and Scope (30 min)
- Problem statement (get explicit agreement before moving on)
- Scope boundaries (in-scope and out-of-scope, both stated out loud)
- Success criteria
- Key constraints

Part 3: Approach and Plan (30 min)
- Methodology (how you will work; this is not a sales pitch)
- Phase structure and milestones
- Timeline overview
- Dependencies and assumptions

Part 4: Governance (20 min)
- Team roles and decision rights
- Steering committee composition
- Meeting cadence
- Escalation paths

Part 5: Working Arrangements (15 min)
- Communication protocols
- Document sharing and version control
- Access requirements
- Working styles and norms

Part 6: Next Steps (10 min)
- Action items with owners and dates
- Next meeting scheduled before anyone leaves
- Open questions parking lot

Facilitation Principles

• Set a collaborative tone from the first minute. You are working with them, not presenting to them.
• Align on the problem before you touch the approach. Skip this and you will re-litigate it later, at a worse time.
• Confirm scope boundaries out loud. A verbal assumption becomes a scope dispute the week before delivery.
• Trade expectations in both directions. Name what you need from the client (access, decisions, resources, availability) and what they can expect from you.
• Establish decision rights explicitly. Who approves scope changes? Who breaks a tie? Get names, not "the team."
• Build personal connection. Engagement outcomes track relationship quality more closely than methodology quality.
• Surface risks early. The kickoff is the safest moment in the whole engagement to say something uncomfortable.
• Get every decision-maker in the room or formally represented. If the sponsor does not show, that is your first finding, not a scheduling detail.

Project Charter

Complete this together during the kickoff. It is the contract between everyone on what you are doing and how. Fill each field with a real sentence. A charter of empty cells is a to-do list, not an agreement.

Use the fill-in template in references/project-charter-template.md, and complete every field live during the session.

Phase 3: Discovery Design

Discovery starts immediately after kickoff, often the same week. The goal is to understand the current state deeply enough to form hypotheses worth testing. This is where the real engagement judgment lives, so spend your preparation here.

Discovery Plan

Design the approach around what you need to learn, not around a standard menu of methods. Each method answers a different question:

Method	Purpose	Participants	Timing
Executive interviews	Strategic context, priorities, political landscape	C-suite, senior leaders	Week 1
Working sessions	Detailed requirements, process understanding	Middle management, subject matter experts	Week 1-2
Data review	Quantitative baseline, trend analysis	Analyst work	Week 1-2
Process observation	How work actually happens, versus how people describe it	Operations, front-line staff	Week 2
Survey	Broad feedback, validation of interview themes at scale	Organization-wide	Week 2

Sequence executives first so their framing shapes what you probe lower down, then use working sessions and observation to test whether the story from the top survives contact with the floor. The gap between the two is often the finding.

Interview Guides

Guides are a safety net, not a script. Ask the question, then follow the answer. One real thread pulled hard beats twelve questions read in order.

Executive Interviews (45 min)

Opening (5 min)

• Thank the participant, state the purpose in one sentence
• Confirm confidentiality: what will be attributed and what will not

Strategic Context (15 min)

1. What is your vision for [area] over the next [X] years?
2. What is the single biggest thing standing between you and that?
3. How does this initiative fit your strategic priorities right now?
4. What does success look like for you personally?

Current State (15 min) 5. How would you describe the current state of [area]? 6. What works well that we should be careful to preserve? 7. What are the most significant pain points? 8. What has been tried before, and why did it stick or fail?

Stakeholders and Organization (10 min) 9. Who are the key people we have to engage? 10. What organizational changes might this require? 11. What resistance should we anticipate, and from where? 12. What should we be asking that we have not? 13. Who else should we speak with? What should we read?

Process Interviews (45 min)

Process Overview

1. Walk me through how [process] works today, start to finish
2. What are the key steps and hand-offs?
3. Who touches it at each stage?

Pain Points 4. Where does the most time disappear? 5. Where do errors and rework cluster? 6. What are the real bottlenecks?

Requirements 7. What would the ideal process look like? 8. What is a must-have versus a nice-to-have? 9. Which systems or tools are load-bearing?

Volume and Metrics 10. How many [transactions/cases/units] per period? 11. What are the current cycle times? 12. What gets measured today, and which of those numbers actually changes behavior?

Data Request

Structure the ask precisely. A vague request produces a vague dataset three weeks late.

Category	Data Needed	Format	Owner	Due Date
Financial	Revenue by segment, cost breakdown	Spreadsheet	CFO office
Operational	Process volumes, cycle times, error rates	Spreadsheet	Ops lead
Organizational	Org chart, headcount by function, role descriptions	Any	HR
Technology	System inventory, integration map	Any	CTO office
External	Market data, competitive benchmarks	Report	Strategy team

If client data is messy or incomplete, send templates with the exact columns and grain you need. Do not assume they know your format. When you cite an external benchmark, record its source and context and present it as illustrative. A benchmark with no provenance is a liability, not evidence.

Synthesizing Discovery

Turn interviews and data into findings that drive the next phase. A finding needs a claim, the evidence behind it, and the implication. Anything missing one of the three is an observation, not a finding.

Discovery Summary: [Project Name]

EXECUTIVE SUMMARY
[2-3 paragraphs: what you learned, what it means, what to do next]

CURRENT STATE ASSESSMENT

Strengths (preserve these):
- [What works and should survive the engagement]

Pain Points (root cause, not symptom):
- [Pain point: its impact, then the underlying cause]

Opportunities:
- [Opportunity with an estimated impact; label the estimate as directional if it is not yet grounded in data]

KEY FINDINGS

Finding 1: [Title]
Evidence: [Interview quotes, data points]
Implication: [What this means for the engagement]

QUANTITATIVE HIGHLIGHTS

| Metric | Current | Benchmark | Gap |
|--------|---------|-----------|-----|
| | | Cite the source | |

INITIAL HYPOTHESES

Based on discovery:
1. [Hypothesis to test in the analysis phase]
2. [Hypothesis]
3. [Hypothesis]

RISKS IDENTIFIED

| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
| | H/M/L | H/M/L | |

RECOMMENDATIONS FOR NEXT PHASE
[Where to focus analysis and why]

Write real prose in the pain-point and finding sections: two or three sentences that connect the symptom to its cause and to the engagement's decision. A finding that reads as one word helps no one.

Phase 4: Standing Up the Engagement

Kickoff is done and discovery is underway. Now set the operating rhythm that carries the work. Do this in week one, before "we'll figure out the cadence later" hardens into no cadence at all.

Workstream Structure

For multi-workstream engagements, define each stream so the seams between them are explicit:

Workstream	Lead	Scope	Key Deliverables	Dependencies
		What this stream covers	What it produces	What it needs from other streams, and when

The Dependencies column is the one that prevents late-stage collisions. Fill it with specific hand-offs and dates, not "coordinate with the tech team."

Engagement Cadences

Set the recurring rhythms immediately:

Cadence	Purpose	Frequency	Attendees	Duration	Owner
Daily standup	Coordination, blockers	Daily	Working team	15 min	Engagement manager
Workstream sync	Progress, cross-cutting issues	Weekly	Workstream leads	30 min	Engagement manager
Client status	Progress, decisions needed	Weekly or bi-weekly	Core team + client lead	45 min	Engagement manager
Steering committee	Strategic decisions, escalations	Monthly or milestone-based	Sponsors, partners	60 min	Partner
Team retrospective	Working effectiveness	Bi-weekly or end of phase	Consulting team	30 min	Team lead

Working Arrangements

Capture the operational details that quietly prevent friction:

Communication:
- Primary channel: [Slack/Teams/Email]
- Expected response time: [X hours during business hours]
- Status updates: [Format and frequency]
- Escalation: [How, and to whom by name]

Document Sharing:
- Platform: [SharePoint/Google Drive/Box]
- Folder structure: [Link or description]
- Naming convention: [Convention]
- Version control: [Approach]

Meetings:
- Default time zone: [TZ]
- Recording policy: [Yes/No/Ask first]
- Notes responsibility: [Who, stored where]
- Decision log: [Where decisions are captured]

Access Requirements:
- [System/tool needed, who grants it]
- [Building/VPN access]
- [Data access permissions]

Engagement Strategy by Stakeholder

With the map built and the kickoff run, set the ongoing approach for each stakeholder who matters:

Stakeholder	Objective	Key Messages	Channel	Frequency	Owner
	What you need from them	Tailored to their actual concern	1:1 / Meeting / Email	Weekly / Biweekly / Monthly	Team member responsible

Coalition Building

Identify your champions and activate them early. Supporters mobilized before a fight are worth more than converts won during one:

Champion	Sphere of Influence	How to Engage	Support They Need
	Who they can mobilize	Activation approach	Resources / air cover / information

Plan quick wins that buy credibility:

Quick Win	Target Stakeholder	Expected Impact	Timeline
	Who benefits	Credibility / Trust / Proof of value

Escalation Triggers

Decide in advance what counts as trouble and what you do about it. Pre-committing to a response removes the hesitation that lets small problems grow:

Signal	What It Means	Response	Escalate To
Sponsor cancels two status meetings in a row	Engagement is losing priority	Request a 1:1 with the sponsor this week	Partner
Data requests unfulfilled after two weeks	Access or willingness problem	Escalate through the client lead	Engagement manager
A stakeholder actively undermines in meetings	Political resistance surfacing	1:1 to understand the real concern	Partner

Principles

These are the things that separate engagements that work from ones that stall.

On kickoffs:

• Kickoff is alignment, not information transfer. If you are presenting for 90 minutes, you are doing it wrong.
• Agree on the problem before discussing the approach. Skipping this is the most common and most expensive engagement mistake.
• State your expectations of the client explicitly: access, decision timelines, team availability. Do not be polite about it.
• Document every assumption. An undocumented assumption is a scope dispute you have not had yet.
• Schedule the next meeting before the room clears. Momentum dies in the gap.

On discovery:

• Discovery is for understanding, not for confirming what you already believe. If your findings perfectly match your opening hypothesis, you were not listening.
• Interview more people than feels necessary. Breadth catches what depth misses.
• Cross-validate. One person's view is an anecdote. Three independent people on the same theme is a finding.
• Follow the thread instead of firing questions. Genuine listening after one good question beats ten read off a guide.
• Chase root causes. Keep asking why until you are past the symptom. Recommendations built on symptoms do not stick.
• Flag data gaps the moment you see them. Discovering a missing dataset during analysis costs you a week you do not have.

On stakeholders:

• Informal influence usually outweighs formal authority. The org chart lies about who decides.
• Positions shift. Revisit the map on a schedule, not when a surprise forces you to.
• Build a coalition of supporters before you take on the resistors. Champions manufacture social proof.
• A private conversation moves a difficult stakeholder further than any group presentation.
• The stakeholder map is confidential. Handle it accordingly and keep the raw version off shared drives.
• Listen before you advocate. Understanding a concern is a precondition to answering it.
• Early engagement is cheaper than late resistance, every time.

On standing up the engagement:

• Set cadences in week one. "We'll find the rhythm as we go" means there is no rhythm.
• Working arrangements feel bureaucratic right up until the first miscommunication. Then they feel like the smartest hour you spent.
• A quick win in the first two weeks buys goodwill that carries you through the hard middle.