name: onboarding-retrospective-runner description: > Executes the full Onboarding Retrospective SOP — reviewing the first 30 days of an engagement, extracting patterns from session notes, running a structured retrospective, and producing documented process improvements. Run 30 days after engagement kickoff. metadata: author: "Kathryn Brown, Practice Builders" version: "1.0.0" date: "2026-04-28" sop: "Onboarding Retrospective" category: "Client Onboarding" frequency: "Trigger-Based" estimated-time: "30 min" trigger: "30 days after engagement kickoff"

Onboarding Retrospective — Runner

You are executing the Onboarding Retrospective SOP for an independent consultant. Most onboarding problems become invisible by the time you're 60 days in — you've adapted, the client has adapted, and the friction just gets absorbed into the engagement. This runner captures the signal while it's still fresh and gives you the data to improve the next onboarding.

Do not skip steps. Do not ask questions across multiple turns — collect everything upfront.

What you'll have when this is done: A 30-day retrospective summary in your project system, 1-3 documented process improvements with specific action steps, and any systemic issues flagged for the Quarterly Practice Health Check SOP.

Step 1: Collect All Inputs

Gather the following from the user in a single prompt. Accept whatever detail level they provide. Flag gaps but keep moving.

Engagement context:

• Client name
• Engagement start date (kickoff date)
• Engagement type (retainer, project, sprint, advisory)
• Scope summary (1-2 sentences)

First 30 days — session notes:

• All session notes from the first 30 days (raw or summarized)
• Action item log (completed, in progress, overdue)
• Any session recaps already produced

Onboarding artifacts:

• Stakeholder map (from kickoff or updated since)
• Quick-win sprint log (what was attempted, what landed)
• Alignment check output (if the Stakeholder Alignment Check SOP was run)

Retrospective reflections (from the consultant's perspective):

• What worked well during onboarding? (processes, communication, deliverables)
• What didn't work? (friction points, miscommunications, delays)
• What was missing? (steps, information, tools you wished you'd had)
• Any surprises — things that went differently than expected?
• Have you seen similar issues in previous engagements? (pattern check)

Prerequisite confirmation:

• [ ] 30 days elapsed since engagement kickoff
• [ ] New Client Intake Process SOP complete
• [ ] Engagement Kickoff Prep SOP complete
• [ ] Quick-Win Sprint SOP complete
• [ ] Stakeholder Alignment Check SOP complete

Step 2: Run Session Recap Analysis (Session Recap Writer — Condensed)

Using the first 30 days of session notes, produce a consolidated recap analysis. This is not a single-session recap — it's a pattern extraction across all sessions.

2a. Decision Inventory

Review all session notes and extract every decision made during the first 30 days:

• Explicit agreements: "we decided," "let's go with," "agreed"
• Implicit agreements: topics where a direction was set and no one objected
• Non-decisions: topics discussed repeatedly but never resolved

Format: Numbered list. One decision per line. Flag any that were later reversed or modified.

2b. Action Item Audit

Extract the full action item history across all sessions:

Watch for: Action items that appeared in multiple consecutive recaps without completion. If the same task appears three sessions in a row, it's either blocked or deprioritized — flag it.

2c. Open Items Carried Forward

List anything discussed but not resolved across the 30 days:

• What the topic was
• How many sessions it appeared in
• Where the conversation currently stands

2d. Pattern Summary

From the decision inventory, action audit, and open items, identify:

• Recurring themes: Topics or concerns that surfaced repeatedly
• Structural gaps: Steps or processes that were missing from the onboarding
• Communication patterns: Where information flowed well vs. where it broke down
• Velocity indicators: Were action items completing on time? Was momentum building or stalling?

Session analysis rules:

• Every decision must be a clear statement, not a discussion topic.
• Every action item must name a specific person, not "we" or "the team."
• Separate client-side actions from consultant-side actions.
• Don't editorialize — document what happened, not what you think about it.
• If a decision feels ambiguous in the notes, include it with "[Confirm]" rather than omitting it.

Step 3: Run the Retrospective (Quarterly Reflection Debrief — Condensed and Adapted)

Using the session recap analysis from Step 2 and the consultant's reflections from Step 1, run a structured retrospective. This adapts the quarterly reflection framework to a 30-day onboarding window.

3a. What Worked (Keep Without Change)

Identify onboarding elements that functioned as intended:

For each, note whether it was a deliberate process or a happy accident. Happy accidents should be formalized into your onboarding SOP so they repeat.

3b. What Didn't Work (Document and Flag)

Identify friction points, breakdowns, or inefficiencies:

Be specific. Not "communication was rough" but "the client didn't respond to the SOW review email for 9 days because it went to their spam folder, delaying the kickoff by a week."

For preventable issues, draft the process change that would prevent recurrence.

3c. What Was Missing (Add to Onboarding SOP Backlog)

Identify steps, tools, or information that should have been part of the onboarding but weren't:

Rule: Proposed additions must be specific enough to act on. Not "improve intake" but "add a dedicated SOW review step before sending the questionnaire."

3d. Surprise Analysis

For each surprise — things that went differently than expected during the onboarding:

• The surprise: What happened that you didn't anticipate?
• Your original assumption: What did you expect instead?
• Why you were wrong: Bad assumption, missing information, or changed circumstances?
• Implication: What does this change about how you onboard the next client?

Format: Table with columns: Surprise, Original Assumption, Why Wrong, Forward Implication.

3e. Energy Check

Brief assessment of the onboarding's qualitative health:

• Your energy level at day 30: Energized, neutral, or depleted by this engagement?
• Client energy level at day 30: Engaged, neutral, or disengaging?
• Relationship trajectory: Strengthening, stable, or showing strain?

This matters because a technically successful onboarding that leaves both parties drained is a warning sign for the engagement ahead.

Retrospective rules:

• Separate what happened from what it means. The session recap covers the facts. The retrospective covers the judgment.
• State lessons as principles, not stories. "Clients respond faster when I send a specific question instead of an open-ended check-in" beats "I learned something about client communication."
• Be honest about what didn't work. A retrospective that only catalogs wins is a press release, not a reflection.
• If a lesson is recurring — you've seen this in previous engagements — escalate it. The problem isn't awareness, it's execution.

Step 4: Identify Process Improvements

From the retrospective findings, identify 1-3 specific process improvements for the next client onboarding.

For each improvement:

• What changes: The specific behavior, process, or step to add/modify/remove
• Traced to: Which retrospective finding drives this change (reference 3a, 3b, 3c, or 3d)
• How it's implemented: The concrete mechanism (new SOP step, checklist item, template update, timing change)
• How you'll verify it worked: The specific signal you'll check in the next onboarding retrospective
• First action: The exact next step to implement this change

Improvement rules:

• Maximum 3. If you try to change everything, you change nothing.
• Each must be structural (a process, a checklist item, an SOP update), not aspirational ("be more attentive").
• Each must trace to a specific finding from this retrospective.
• Each must be specific enough to act on without further clarification.

Step 5: Check for Systemic Patterns

Review the retrospective findings against the consultant's experience across engagements:

• Have any of these issues appeared in previous onboardings?
• Are there patterns that suggest a systemic problem rather than a one-off?

If systemic patterns are identified:

• Document the pattern with evidence across engagements
• Flag for the Quarterly Practice Health Check SOP
• Note whether the pattern is in your process, your client selection, or your scope definition

Step 6: Assemble Final Output

Present one unified document containing:

A. Retrospective Header

# Onboarding Retrospective: [Client Name]
**Date:** [Today's date] | **Engagement Start:** [Kickoff date] | **Day:** 30
**Engagement Type:** [Type] | **Scope:** [Summary]

B. Session Analysis Summary

The pattern summary from Step 2d — recurring themes, structural gaps, communication patterns, velocity indicators. Include the decision inventory count, action item completion rate, and open items carried forward.

C. What Worked

Table from Step 3a.

D. What Didn't Work

Table from Step 3b with root causes and preventability assessment.

E. What Was Missing

Table from Step 3c with proposed SOP additions.

F. Surprise Analysis

Table from Step 3d.

G. Energy Check

Brief assessment from Step 3e.

H. Process Improvements (1-3)

Numbered list from Step 4 with all five attributes per improvement.

I. Systemic Pattern Check

Findings from Step 5. If none identified, state: "No systemic patterns identified in this retrospective. Will reassess at the next onboarding retrospective or Quarterly Practice Health Check."

J. SOPs to Trigger

• [ ] Quarterly Practice Health Check — if systemic patterns were identified in Step 5
• [ ] Onboarding SOP Updates — implement process improvements from Section H before next client onboarding

Quality Check

Rules

1. Run at 30 days, not later. At 60 days, the onboarding experience has faded. The 30-day trigger exists because that's when the memory is still specific enough to be useful.
2. Collect all inputs in one pass. Do not scatter prompts across multiple turns. Ask once, flag gaps, keep moving.
3. This is a process audit, not a performance review. Focus on what the system should do differently, not what you should have done better. "The intake form didn't capture X" is useful. "I should have asked about X" is not.
4. State lessons as principles, not stories. "Clients need a dedicated SOW review step before the questionnaire ships" is actionable. "The SOW thing was a mess" is not.
5. Maximum 3 process improvements. Prioritization is the point. If everything changes, nothing gets implemented.
6. Every improvement must be structural. A new SOP step, a checklist addition, a template change, a timing adjustment. Not "try harder" or "be more thorough."
7. Every improvement must trace to a finding. No random improvement ideas. If it didn't surface in this retrospective, it doesn't belong here.
8. Check for systemic patterns. One-off issues get fixed in the onboarding SOP. Patterns that appear across engagements get escalated to the Quarterly Practice Health Check.
9. Include the energy check. A technically successful onboarding that depletes both parties is not a success — it's a warning.
10. Be honest about what didn't work. A retrospective that only catalogs wins produces no improvements. The value is in the friction.
11. Flag inferred details. If a root cause or pattern was inferred rather than stated, mark it [INFERRED — verify].
12. Escape dollar signs as \$ for Notion compatibility.

Copyright (c) 2026 Kathryn Brown, Practice Builders Licensed under the Practice Builders Skill License v1.0 See https://practicebuilders.ai/license for terms.

This skill is part of the Consulting Practice SOP Manual, a Practice Builders product. Redistribution, resale, or derivative use without written permission is prohibited.