# Project Management

> Comprehensive project management guidance for management consulting engagements, covering planning, tracking, risk management, and client communication Use when user asks to "manage a consulting project", "project plan", "workstream tracking", or mentions project governance, milestone tracking, or engagement management.

- Skill: `lauraflorentin/project-management` (Agent Skill)
- Install (CLI): `npx skillmds@latest add lauraflorentin/project-management`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lauraflorentin/project-management/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: lauraflorentin (https://skillmd.com/u/lauraflorentin)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lauraflorentin/project-management

---


# Project Management for Consulting Engagements

## Engagement Planning

### Work Breakdown Structure (WBS)
- Define all deliverables from business objective down to discrete work packages
- Structure by workstream or phase to enable parallel workstreams
- Assign ownership and effort estimates (days/weeks) to each package
- Ensure no overlapping scope and complete coverage

### Workstream Definition
- Group related activities by functional area (e.g., Finance, Operations, Technology)
- Define workstream lead, core team, and governance
- Establish workstream-specific milestones and success criteria
- Map dependencies between workstreams to sequence activities

### Milestone Planning
- Identify 5-8 major milestones spanning the engagement duration
- Milestones should align with project phases and deliverable completion
- Include buffer for synthesis, client review, and refinement cycles
- Communicate milestones to all stakeholders at project kickoff

### Resource Allocation
- Match team composition to workstream needs (consulting, client, subject matter experts)
- Define roles, responsibilities, and FTE commitments
- Plan for ramp-up and ramp-down periods
- Account for client resource constraints and availability

## Status Reporting

### Weekly Status Update Template
- **Accomplishments**: Completed deliverables, completed activities, decisions made
- **Next Steps**: Planned activities for following week with owners and target dates
- **Risks/Issues**: New risks identified, issues blocking progress, mitigation status
- **Decisions Needed**: Client decisions required, escalations, steering committee input
- **KPIs**: Milestone variance, effort burn rate, quality metrics

### Steering Committee Deck Format
- One-page executive summary with RAG status and key decisions
- Milestone progress with variance commentary (schedule and budget)
- Top 3 risks and mitigation status
- Next period priorities and decision items
- Attendance: Project Sponsor, Steering Committee members, PMO

### RAG Status Methodology
- **Red**: Schedule behind >2 weeks or budget overrun >10% or critical risk unmitigated
- **Amber**: Schedule behind 1-2 weeks or budget overrun 5-10% or emerging risks
- **Green**: On schedule, on budget, risks managed and mitigated
- Update RAG status weekly; escalate Red immediately to Sponsor

## RAID Log Management

### Risk Identification & Tracking
- Identify risks in kickoff and continuously throughout engagement
- Record: Description, category, owner, probability (H/M/L), impact (H/M/L), mitigation action
- Update RAID log weekly; review during risk management meetings
- Use probability x impact scoring to prioritize risk response

### Action Item Tracking
- Capture all action items from meetings with owner, target date, and status
- Track both internal (consulting team) and client (steering committee, functional leads) actions
- Close-out when deliverable is completed or decision is made
- Escalate overdue items weekly to project manager

### Issue Management
- Log issues when risks materialize or blockers emerge
- Define issue: Impact if unresolved, required resolution, owner, target resolution date
- Assign resolution to appropriate workstream lead or project manager
- Track through resolution and document lessons learned

### Decisions & Approvals
- Log all material decisions (go/no-go, approach/design choices, priority trade-offs)
- Record decision, rationale, approver, date approved, and next steps
- Decisions provide audit trail and prevent scope creep or rework
- Revisit decisions if assumptions change materially

## Workplan Structure

### Project Phases
1. **Mobilize** (weeks 1-3): Kickoff, team establishment, detailed planning, baseline data collection
2. **Discover** (weeks 2-6): Current state assessment, stakeholder interviews, root cause analysis
3. **Analyze** (weeks 5-10): Deep-dive analysis, benchmarking, opportunity quantification
4. **Design** (weeks 9-14): Solution design, business case development, implementation roadmap
5. **Implement** (weeks 12-20): Change management, pilots, training, full rollout
6. **Transition** (weeks 18-22): Handoff to operations, knowledge transfer, sustained support

### Typical Durations & Dependencies
- Most consulting engagements span 12-24 weeks
- Phases overlap 1-2 weeks to maintain momentum
- Analyze cannot end until Discover is substantially complete
- Design requires sufficient analysis; delays compound downstream
- Implement readiness depends on Design quality and stakeholder alignment

## Risk Management

### Risk Identification Techniques
- Facilitated workshops with full project team and key stakeholders
- Template-based approach by phase (mobilize, discover, analyze, etc.)
- Lessons learned from similar engagements
- Stakeholder interviews to surface concerns and organizational risks

### Probability/Impact Matrix
- **High Probability, High Impact**: Mitigate aggressively or escalate sponsor
- **High Probability, Low Impact**: Mitigate or accept based on effort
- **Low Probability, High Impact**: Develop contingency plans
- **Low Probability, Low Impact**: Monitor and document

### Mitigation Strategies
- **Avoid**: Eliminate the risk through different approach
- **Mitigate**: Reduce probability or impact through proactive action
- **Accept**: Acknowledge and budget contingency time/budget
- **Escalate**: Sponsor or steering committee assumes responsibility

### Risk Appetite Alignment
- Clarify at kickoff: organizational tolerance for change, schedule, budget, quality trade-offs
- Align risk strategy with client's broader transformation program
- Document sponsor's willingness to make difficult decisions
- Review risk appetite quarterly as business context evolves

## Milestone Tracking

### Earned Value Concepts (Simplified)
- Planned Value: Budgeted effort for completed work packages to date
- Actual Cost: Actual effort and expense spend to date
- Earned Value: Credit for completed work based on % completion
- Variance: Earned Value minus Planned Value (schedule), Actual Cost (budget)

### Percent Complete Methodology
- Define completion criteria for each deliverable (draft, quality review, approved)
- Use 0%-100% scale: 0% until started, 50% at internal review, 100% at client approval
- Avoid "almost done" syndrome: enforce clear completion gates
- Roll-up % complete to workstream and project level weekly

### Variance from Plan
- Schedule Variance: If milestone is behind >1 week, activate mitigation
- Budget Variance: If effort burn exceeds plan >10%, adjust staffing or scope
- Quality Variance: Track rework and defect rates; adjust process if needed
- Communicate variance impact on downstream phases to sponsor

## Client Communication Cadence

### Communication Plan
- **Project Sponsor**: Weekly 1:1 (status, decisions, escalations), monthly steering committee
- **Steering Committee**: Monthly half-day (executive summary, approvals, risk review)
- **Workstream Leads**: Bi-weekly status, weekly working sessions
- **Full Working Team**: Weekly kickoff (15 min), daily stand-ups (optional), weekly close-out

### Content Tailoring
- **Executives**: Context, impact, decisions, risks, business outcomes
- **Workstream Leads**: Progress, blockers, upcoming milestones, resource needs
- **Team**: Priorities, dependencies, quality standards, celebration of wins

## Change Management Integration

### Alignment with Organizational Change
- Project milestones coincide with change readiness gates (awareness, adoption, capability)
- Workplan includes change activities: communication, training, reinforcement
- Project risks include adoption/resistance; track in RAID log
- Design phase integrates organizational design; implement phase executes change roadmap

### Stakeholder Engagement
- Map stakeholders by workstream and phase (impact, influence, readiness)
- Engagement activities: awareness sessions, design workshops, training, reinforcement
- Project manager coordinates with change lead; escalate adoption barriers early

## Meeting Management

### Kickoff Meeting (4-6 hours)
- Agenda: Vision, objectives, scope, timeline, workstreams, team, governance, success criteria
- Outputs: Signed project charter, RACI, detailed workplan, risk register baseline
- Participants: Full team, steering committee, sponsors, key stakeholders

### Weekly Status Meeting (1 hour)
- Agenda: Accomplishments, next steps, blockers, decisions needed
- Format: One slide per workstream (owner present), red items discussed first
- Outputs: Updated RAID log, action items, decisions recorded

### Steering Committee Meeting (2 hours, monthly)
- Agenda: Executive summary, milestone progress, top 3 risks, decisions/approvals, Q&A
- Presentation: 1 page summary, milestone dashboard, risk heat map, decision log
- Outcomes: Approvals, resource commitments, escalation resolution

### Working Sessions (2-4 hours)
- Deep-dive workshops to drive analysis, design decisions, or validation
- Participants: Consulting team, workstream leads, subject matter experts
- Outputs: Detailed findings, recommendations, designs, or approved approach

## Workflow Overview

1. **Plan Engagement**: Define WBS, workstreams, milestones, resource plan, risk baseline
2. **Track Progress**: Update RAID log weekly, % complete by workstream, effort burn, schedule variance
3. **Report Status**: Weekly updates to sponsor, monthly steering committee, consistent cadence
4. **Manage Risks**: Weekly risk review, mitigation action tracking, escalate Red items immediately
5. **Close Engagement**: Final report, lessons learned, knowledge transfer, team recognition, wind-down

## Scope Change Management

Scope changes during engagement are inevitable. Manage them systematically to protect profitability and client relationship without appearing inflexible.

### When to Say Yes vs. No to Scope Changes

Before evaluating a scope change request, understand the client's motivation and quantify the impact.

**Ask clarifying questions:**
- "What is driving this request? Is this a new business need, or did we miss it in scoping?"
- "How critical is this to your success criteria for the engagement?"
- "Are you requesting to add scope or expand an existing deliverable?"

**Framework for evaluation:**

**Say YES if:**
- Change is small (≤5% project effort) and client relationship is strategic.
- Change supports the core engagement objective. Example: Adding 2 interviews when you learn of a missing stakeholder is wise; adding a full new workstream is not.
- Client will pay for expansion via change order or you can absorb 5-10% of margin without jeopardizing engagement economics.
- Change addresses a genuine miss in your initial scoping, not a moving target.

**Say NO (offer alternative) if:**
- Change expands scope >10% without proportional budget increase.
- Change shifts focus away from original engagement objective.
- Change requires expertise outside your team's capability.
- Change compresses timeline materially (would require weekend/overtime work).

**When saying no:** Frame positively. "We can't add that to this engagement without impacting quality. Here's what I recommend: We complete Phase 1 as scoped, and we propose Phase 2 to address [new scope] separately. That keeps this engagement focused and high-quality."

### Quantifying Scope Change Impact

When a client requests a change, you need to answer: "What does this cost in time, effort, and timeline?"

**Impact assessment template:**
1. **Effort impact:** "Adding 5 customer interviews requires 40 hours of analyst time + 10 hours of senior consultant review = 50 hours."
2. **Resource impact:** "This pulls our Analyst from [other workstream]. Do we delay the Analyst's current deliverable or add resources?"
3. **Timeline impact:** "This adds 2 weeks to the Discover phase, pushing the Analyze phase start from [date] to [date]. Does this push the overall engagement end date?"
4. **Cost impact:** "At our blended rate of $200/hour, this is an additional $10k. Or, we can reprioritize within scope and absorb it if you forego [something else]."

**Present as options:**
- "Option A: Add 5 new interviews as additional deliverable. Cost: $10k, extends timeline 2 weeks."
- "Option B: Add 5 interviews but reduce current stakeholder group interviews from 20 to 15 to compensate. Cost: $0, timeline unchanged."
- "Option C: Include initial 5 interviews now; schedule deeper follow-up interviews as Phase 2 follow-on engagement."

Let the client choose, and document their decision in the change order.

### Scope Change Request Template

Formalize every scope change in writing to prevent misunderstandings. Use this template:

```
SCOPE CHANGE REQUEST #[#]
Project: [Project Name]
Date Submitted: [Date]
Submitted By: [Client Name/Role]
Approved By: [Project Sponsor Signature]

DESCRIPTION OF CHANGE:
[Specific request; what is being added/removed/modified]

BUSINESS RATIONALE:
[Why the client needs this change; what problem it solves]

CURRENT SCOPE (what was in original SOW):
[Reference specific deliverable/phase being modified]

PROPOSED SCOPE (what will be added):
[Specific description of new work]

EFFORT IMPACT:
[Estimated additional hours by consultant level]

TIMELINE IMPACT:
[Does this extend engagement end date? By how much?]

COST IMPACT:
[Additional fee required, or scope to be eliminated to offset]

RESOURCE IMPACT:
[Does this require different team composition or external resources?]

APPROVAL:
[Client Sponsor signature line]
[Project Manager signature line]

EFFECTIVE DATE:
[When does this change go into effect?]
```

Make it clear that work does not proceed on the change until both parties sign the change order.

### Escalation Paths for Contested Changes

Disagreements arise: Client insists scope change is "minor" but your estimate is 80 hours; or Client demands free work claiming it "should have been in original scope."

**Escalation approach:**
1. **First level:** Project manager and client project lead discuss. Is this a misunderstanding that can be resolved?
2. **Second level:** Consulting engagement lead and client sponsor discuss. Can the scope be reframed or prioritized differently?
3. **Final level:** Consulting firm leadership and client C-level executive discuss. At this point, you may decide to absorb cost to preserve relationship or hold firm on the scope boundary.

**Language for delicate conversations:** "We want to make sure you're successful. Let's talk about what's most important. If we can't fit [X] in the current timeline without sacrificing quality, what are your priorities? Can we sequence this differently?"

---

## Client Relationship Health

Dissatisfaction often builds silently. Monitor for warning signs and intervene proactively before client frustration leads to escalation.

### Signals of Dissatisfaction

Watch for these behavioral and verbal cues indicating the client is unhappy:

**Early warning signs:**
- Delayed feedback on deliverables (was 5 days, now 3 weeks). Signals disengagement or decision-making conflict.
- Reduced meeting attendance. Sponsor attends fewer steering committee meetings; key stakeholders stop showing up.
- Repeated questions about what you're doing. Client asks same question twice (signals they didn't absorb your answer; or you didn't answer it clearly).
- Tone shift in communications. Emails become terse or formal. Casual rapport disappears.
- Increased "other priorities" comments. Client cancels meetings repeatedly or sends junior substitutes.
- Unsolicited budget discussions. Client suddenly asking "Are we on track to spend the budgeted amount?" or "Can you discount the remaining invoices?" Signals budget pressure or value doubts.

**Serious warning signs:**
- Sponsor requests private conversation with firm leader. This is a precursor to escalation.
- Client explicitly states dissatisfaction: "We're concerned about progress" or "We're not sure this is working."
- Requests for additional team members or "more senior resources." Signals confidence issue.
- Threats to terminate or withhold payment.

### Proactive Check-In Techniques

Don't wait for problems to fester. Use structured check-ins to gauge satisfaction and catch issues early.

**Weekly one-on-one with sponsor (30 min):**
- Ask directly: "How are we doing? What's working? What could we do better?"
- Don't just report status; listen actively.
- Take notes and act on feedback within 48 hours.

**Monthly temperature check (via survey or conversation):**
- Satisfaction scale (1-5): How satisfied are you with progress to date?
- Pace: Is the engagement moving at the right speed?
- Team dynamic: Is our consulting team working well with your team?
- Value perception: Do you feel you're getting value for the investment?
- Open feedback: What would make this engagement better?

**Quarterly "partnership review":**
- Retrospective: What's working? What could we improve?
- Forward-looking: Are original objectives still relevant? Any adjustments needed?
- Relationship health: Are there any concerns blocking success?

**Act immediately on feedback.** If client says "We need more senior time," increase senior consultant presence next week, not in 2 weeks. If client says "We're drowning in data," reduce the amount of analysis output and focus on key insights. Speed of response to feedback is a leading indicator of client satisfaction.

### Recovery Playbook When Things Go Wrong

If you detect serious dissatisfaction, move to recovery mode immediately.

**Step 1: Acknowledge (within 24 hours)**
Sponsor calls or visits client to acknowledge concern: "We've sensed some frustration, and we want to understand what's not working. Let's talk openly."

**Step 2: Diagnose (within 48 hours)**
Conduct a working session with sponsor and key stakeholders to understand root cause:
- Is it about the work quality or approach?
- Is it about team dynamics or communication?
- Is it about cost or perceived value?
- Is it about progress or timeline?

Document findings from this conversation.

**Step 3: Develop a recovery plan (within 1 week)**
Based on diagnosis, propose specific actions:
- **If quality concern:** "We'll conduct a full quality review of our findings to date. We'll meet in [X] days with our leadership review findings."
- **If team concern:** "We're deploying our engagement lead to be on-site 3 days per week to increase senior presence and ensure alignment."
- **If value concern:** "We're refocusing the engagement on [specific high-impact objective]. We'll pivot to deliver sooner on that vs. completing all original scope."
- **If timeline concern:** "We're adding a second work stream to accelerate and will deliver key findings 2 weeks earlier than planned."

**Step 4: Demonstrate quick wins (within 2-3 weeks)**
Show visible progress on the recovery plan:
- Deliver a quick finding or recommendation.
- Share new team members or increased seniority.
- Produce a revised project schedule showing accelerated timeline.

The goal is to rebuild confidence through action, not words.

**Step 5: Recommend course correction**
If fundamental issues can't be resolved:
- Reduce scope to focus on highest-value work, completing this narrower engagement excellently.
- Propose a pause and restart with modified approach.
- Recommend the engagement end, if truly unworkable, without acrimony.

Better to exit gracefully than drag through a miserable engagement.

---

## Knowledge Transfer & Close-Out

How you wrap an engagement determines whether client can sustain your recommendations and whether they'll hire you again.

### Knowledge Transfer Sessions

Plan 2-3 dedicated sessions (each 4-6 hours) to hand off capability and institutional knowledge.

**Session 1: Findings & Rationale**
- Walk client team through all key findings, the evidence supporting them, and the reasoning behind recommendations.
- Focus on "why we believe this" not just "what we found."
- Client team asks questions and validates their understanding.
- Deliverable: Recorded session (video or transcript) so absent team members can catch up.

**Session 2: Implementation Approach**
- Step through the implementation roadmap, decision gates, timeline, and resource requirements.
- Walk through sample project plans and governance structures.
- Discuss lessons learned from similar implementations and what to watch out for.
- Deliverable: Detailed implementation playbook client can hand to project team.

**Session 3: Tools, Models & Data**
- Review all Excel models, dashboards, decision tools client will inherit.
- Walk through calculation logic and assumptions.
- Show how to update and refresh the models as business context evolves.
- Provide documentation on how to interpret outputs and test scenarios.
- Deliverable: Commented model files with user guides.

**Attendance:** Core implementation team, operational leads, CFO/Finance (if financial models involved). Document attendee list for record.

### Documentation Handoff

Prepare a complete "consulting binder" the client can reference during implementation.

**Contents:**
1. **Executive summary** of engagement findings and recommendations
2. **Full analysis** with methodology and supporting data
3. **Implementation roadmap** with phasing, milestones, and sequencing
4. **Detailed playbooks** for each major recommendation (step-by-step how-to guide)
5. **All models, tools, and templates** used (Excel, project schedules, org charts)
6. **Training materials** if you created them (presentation slides, reference guides, video walkthroughs)
7. **Stakeholder lists** with contact info and roles
8. **Glossary** of terms and acronyms used
9. **Bibliography** of sources, analyst reports, and reference materials
10. **Contact information** for post-engagement support (if included in SOW)

**Format:** Digital PDF manual + editable working files. Make it searchable and index-friendly. Client should be able to find what they need within 60 seconds.

### Lessons Learned Facilitation

Within 2 weeks of engagement end, conduct a 2-hour lessons learned session with the consulting team. This is different from client debrief—it's internal.

**Discussion agenda:**
- What went better than expected?
- What challenges did we encounter?
- If we did this engagement again, what would we do differently?
- What insights can we apply to other client engagements?

**Participants:** Full consulting team, including junior staff. Project manager facilitates; client does not attend.

**Outputs:** One-page lessons learned document filed in project records. Key insights get shared in firm's project learning database.

This prevents losing institutional knowledge and accelerates learning across projects.

### Transition to Business As Usual (BAU)

Clarify the moment when the client "owns" the work and consulting team steps back.

**Define BAU transition explicitly:**
- **On [date], the engagement is complete.** Deliverables have been accepted.
- **For 30 days post-engagement, we provide** (if included in SOW): Email support for questions on implementation, one call-in available if stakeholder meeting goes sideways, quick fixes to any models or materials.
- **After 30 days:** Any support or follow-up becomes a new engagement billed separately.

Document this in the final status update. Prevents open-ended assumptions that consulting team will help forever.

### Follow-On Opportunity Identification

Before closing, identify natural follow-on work for the relationship.

**Questions to ask in final steering committee meeting:**
- "After you've had 90 days to implement Phase 1 recommendations, we'd recommend a checkpoint session to assess what's working and what adjustments are needed. Would you be interested in a Phase 1b engagement?"
- "Based on what we've learned, we see an opportunity in [related area]. Should we discuss a separate proposal for Phase 2?"
- "We can provide ongoing advisory support on [metric/area] if you'd like to retain us on a retainer basis."

**Don't be aggressive.** Make the case for follow-on work based on genuine client need, not consulting firm revenue target. Best repeat business comes from excellent execution on the first engagement, not premature upselling.