| name | engagement-setup |
| description | Guide the first weeks of a consulting engagement from contract signature through a running project. Covers kickoff workshop design, discovery phase planning, stakeholder mapping, and standing up workstreams and cadences. Use when launching a new engagement, onboarding a new client, or resetting a stalled project. |
Engagement Setup
Take a consulting engagement from "we just won this work" to "the engagement is running." This covers the first weeks of a consulting engagement: planning the kickoff, mapping stakeholders, designing discovery, and establishing the operating rhythm. For designing 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 should earn its place by driving alignment or unblocking work.
Phase 1: Pre-Kickoff Preparation
Before anyone gets in a room, do the homework.
Stakeholder Identification
Build the stakeholder inventory early. You need it for kickoff invitation lists, interview scheduling, and knowing who can actually make decisions.
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 |
Influence-Interest Analysis
Map everyone on the power-interest grid. This determines your engagement strategy for each 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:
| Stakeholder | Power (1-5) | Interest (1-5) | Quadrant | Strategy |
|---|
| | | Manage Closely / Keep Satisfied / Keep Informed / Monitor | |
Alignment and Resistance Assessment
Before kickoff, get a read on where people actually stand versus where you need them.
| 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:
| Stakeholder | Resistance Type | Root Cause | Severity | Mitigation |
|---|
| Rational / Emotional / Political / Cultural | Why they resist | High/Med/Low | Approach |
Map influence networks. Who listens to whom? Where are the informal power centers?
| Stakeholder | Influences | Influenced By | Coalition Opportunity |
|---|
| Who they sway | Who sways them | Potential alliance |
Kickoff Materials
Prepare and share 24-48 hours before the kickoff:
- Agenda with time blocks and objectives for each section
- Project charter template (to be completed collaboratively, not presented as fait accompli)
- Stakeholder map (sanitized version appropriate for the audience)
- Working arrangements draft for discussion
- Expectations document covering what you need from the client
- Initial communication plan
Phase 2: Kickoff Workshop
The kickoff is about alignment, not information transfer. If people leave with different understandings of the problem, scope, or how you'll work together, the kickoff failed.
Agenda Structure
Part 1: Introduction (15 min)
- Introductions (not just names... roles, what each person cares about)
- Project purpose and background
- Meeting objectives
Part 2: Problem and Scope (30 min)
- Problem statement (get agreement before moving on)
- Scope boundaries (in-scope and out-of-scope, explicitly)
- Success criteria
- Key constraints
Part 3: Approach and Plan (30 min)
- Methodology (how you'll work, 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 start. You're working with them, not presenting to them.
- Align on the problem before jumping to approach. If you skip this, you'll pay for it later.
- Confirm scope boundaries explicitly. Verbal assumptions become scope disputes.
- Exchange expectations in both directions. What do you need from the client (access, decisions, resources, availability)? What can they expect from you?
- Establish decision rights clearly. Who can approve scope changes? Who resolves disagreements?
- Build personal connections. Engagement success tracks relationship quality more than methodology quality.
- Surface risks early. The kickoff is the safest time to name uncomfortable truths.
- Ensure all decision-makers are present or represented. If the sponsor doesn't show up, you have a problem.
Project Charter
Complete this collaboratively during the kickoff. It's the contract between the team on what you're doing and how.
Project Charter: [Project Name]
1. PROJECT OVERVIEW
Background:
[Why this project exists]
Problem Statement:
[What problem you're solving]
Objectives:
| Objective | Success Metric |
|-----------|----------------|
| | How you'll measure it |
2. SCOPE
In Scope:
- [Deliverable or activity]
Out of Scope:
- [Explicit exclusion]
3. TIMELINE
| Milestone | Target Date |
|-----------|-------------|
| Kickoff | |
| Discovery complete | |
| Analysis complete | |
| Recommendations | |
| Final delivery | |
4. GOVERNANCE
Core Team:
| Role | Name | Organization |
|------|------|--------------|
| Project Sponsor | | Client |
| Project Lead | | Client |
| Engagement Manager | | Firm |
Steering Committee:
| Member | Role | Responsibility |
|--------|------|----------------|
| | | Strategic decisions |
Meeting Cadence:
| Meeting | Frequency | Attendees |
|---------|-----------|-----------|
| Steering Committee | Monthly | Sponsor, Partner |
| Project Team | Weekly | Core team |
| Status Update | Bi-weekly | Extended team |
5. RISKS AND DEPENDENCIES
| Risk | Impact | Mitigation |
|------|--------|------------|
| | H/M/L | |
Dependencies:
- [Dependency]
6. COMMUNICATION PLAN
| Audience | What | How | When |
|----------|------|-----|------|
| Steering Committee | Status, decisions | Meeting + email | Monthly |
| Extended Team | Updates | Email | Weekly |
| Working Team | Day-to-day | Slack/Teams | Daily |
7. SIGN-OFF
| Role | Name | Date |
|------|------|------|
| Client Sponsor | | |
| Firm Partner | | |
| Engagement Manager | | |
Phase 3: Discovery Design
Discovery starts immediately after kickoff (often in the same week). The goal is understanding the current state deeply enough to form hypotheses worth testing.
Discovery Plan
Design the approach based on what you need to learn:
| 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 | N/A (analyst work) | Week 1-2 |
| Process observation | See how work actually happens (not how people describe it) | Operations, front-line staff | Week 2 |
| Survey | Broad feedback, validate interview themes at scale | Organization-wide | Week 2 |
Interview Guides
Executive Interviews (45 min)
Opening (5 min)
- Thank participant, explain purpose
- Confirm confidentiality (what will and won't be attributed)
Strategic Context (15 min)
- What is your vision for [area] over the next [X] years?
- What are the biggest challenges preventing you from achieving this?
- How does this initiative fit into your strategic priorities?
- 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 preserve?
7. What are the most significant pain points?
8. What has been tried before? What worked and what didn't?
Stakeholders and Organization (10 min)
9. Who are the key people we need to engage?
10. What organizational changes might be needed?
11. What concerns or resistance should we anticipate?
12. What questions should we be asking that we haven't?
13. Anyone else we should speak with? Documents we should review?
Process Interviews (45 min)
Process Overview
- Walk me through how [process] works today, start to finish
- What are the key steps and hand-offs?
- Who is involved at each stage?
Pain Points
4. Where does the most time get spent?
5. Where do errors or rework happen most often?
6. What constraints or bottlenecks exist?
Requirements
7. What would the ideal process look like?
8. What capabilities are must-haves versus nice-to-haves?
9. What systems or tools are critical?
Volume and Metrics
10. How many [transactions/cases/units] per period?
11. What are current cycle times?
12. What metrics are tracked today? Which ones actually drive behavior?
Data Request
Structure your ask clearly. Vague data requests produce vague data.
| 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, provide templates. Don't assume they'll know what format you need.
Synthesizing Discovery
After interviews and data collection, synthesize into findings that drive the next phase:
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 well]
Pain Points (with root causes, not just symptoms):
- [Pain point: impact and underlying cause]
Opportunities:
- [Opportunity with estimated impact]
KEY FINDINGS
Finding 1: [Title]
Evidence: [Interview quotes, data points]
Implication: [What this means for the engagement]
QUANTITATIVE HIGHLIGHTS
| Metric | Current | Benchmark | Gap |
|--------|---------|-----------|-----|
| | | | |
INITIAL HYPOTHESES
Based on discovery:
1. [Hypothesis to test in 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]
Phase 4: Standing Up the Engagement
With kickoff done and discovery underway, establish the operating rhythm that will carry the engagement.
Workstream Structure
For engagements with multiple workstreams, define clearly:
| Workstream | Lead | Scope | Key Deliverables | Dependencies |
|---|
| | What this workstream covers | What it produces | What it needs from other workstreams |
Engagement Cadences
Set up recurring rhythms immediately. Don't wait for "things to settle."
| 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 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]
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, where stored]
- Decision log: [Where decisions are captured]
Access Requirements:
- [System/tool needed, who to request from]
- [Building/VPN access]
- [Data access permissions]
Engagement Strategy by Stakeholder
Now that you've mapped stakeholders and run the kickoff, set the ongoing engagement approach:
| Stakeholder | Objective | Key Messages | Channel | Frequency | Owner |
|---|
| What you need from them | Tailored to their concerns | 1:1 / Meeting / Email | Weekly / Biweekly / Monthly | Team member responsible |
Coalition Building
Identify and activate your champions early:
| Champion | Sphere of Influence | How to Engage | Support They Need |
|---|
| Who they can mobilize | Activation approach | Resources / air cover / information |
Plan quick wins that build credibility:
| Quick Win | Target Stakeholder | Expected Impact | Timeline |
|---|
| Who benefits | Credibility / Trust / Proof of value | |
Escalation Triggers
Define what signals trouble and what to do about it:
| Signal | What It Means | Response | Escalate To |
|---|
| Client sponsor cancels two status meetings | Engagement losing priority | Request 1:1 with sponsor | Partner |
| Data requests unfulfilled after two weeks | Access or willingness problem | Escalate through client lead | Engagement manager |
| Stakeholder actively undermining in meetings | Political resistance | 1:1 conversation to understand concerns | Partner |
Principles
These aren't platitudes. They're the things that separate engagements that work from ones that don't.
On kickoffs:
- Kickoff is about alignment, not information transfer. If you're presenting for 90 minutes, you're doing it wrong.
- Get agreement on the problem before discussing the approach. Skipping this is the most common engagement mistake.
- Confirm your expectations of the client explicitly. Access, decision timelines, team availability. Don't be polite about this.
- Document assumptions. Every undocumented assumption is a future scope dispute.
- Schedule the next meeting before closing. Momentum dies in the gap.
On discovery:
- Discovery is about understanding, not validating what you already think. If your findings perfectly match your initial hypothesis, you weren't listening.
- Interview more people than you think you need to. Breadth catches what depth misses.
- Cross-validate everything. One person's perspective is an anecdote. Three perspectives with the same theme is a finding.
- Follow up, don't rapid-fire. One thoughtful question followed by genuine listening beats ten questions read from a guide.
- Focus on root causes. Ask "why" until you get past symptoms. Pain points without root causes produce recommendations that don't stick.
- Flag data gaps early. Don't wait until analysis to discover you're missing critical information.
On stakeholders:
- Informal influence often matters more than formal authority. The org chart lies.
- Stakeholder positions shift. Revisit the map regularly.
- Build coalitions of supporters before tackling resistors. Champions create social proof.
- One-on-one conversations move difficult stakeholders more than group presentations.
- Stakeholder mapping is confidential. Handle with care.
- Listen before you advocate. Understanding someone's concerns is a prerequisite to addressing them.
- Early engagement prevents late-stage resistance. The cost of inclusion is always lower than the cost of opposition.
On standing up the engagement:
- Set cadences immediately. "We'll figure out the rhythm as we go" means no rhythm.
- Working arrangements feel bureaucratic until the first miscommunication. Then they feel essential.
- Quick wins in the first two weeks buy goodwill that carries you through the hard middle of the engagement.
