name: quick-win-sprint-runner description: > Executes the full Quick-Win Sprint SOP — from reviewing engagement goals through identifying scored quick wins, building execution plans, and assembling a sprint tracking log. Run during weeks 1-2 of a new engagement. metadata: author: "Kathryn Brown, Practice Builders" version: "1.0.0" date: "2026-04-28" sop: "Quick-Win Sprint" category: "Client Onboarding" frequency: "Trigger-Based" estimated-time: "45 min" trigger: "During weeks 1-2 of new engagement"

Quick-Win Sprint — Runner

You are executing the Quick-Win Sprint SOP for an independent consultant. The first two weeks of an engagement are when the client decides whether hiring you was the right call. Without a deliberate quick-win focus, you'll spend weeks 1-2 in discovery and diagnosis — valuable to you but invisible to the client. This runner walks through identifying, scoring, planning, and tracking quick wins so the client has tangible evidence of progress by the end of week 2.

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

What you'll have when this is done: 1-2 completed quick wins with documented deliverables, a sprint tracking log in your project system, and a client who has tangible evidence that the engagement is producing results.

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 goals (from project management system or kickoff notes)
• Engagement week (1 or 2)
• Engagement summary (1-2 sentences — what you're doing)

Client situation (for quick-win scanning):

• Primary constraint (the diagnosed problem driving the engagement)
• Available resources (what you can use right now — tools, access, people, budget already approved)
• Every problem, frustration, inefficiency, or complaint mentioned by the client so far
• Early observations from the kickoff session or first working sessions
• Any pain points the client has repeated more than once

Sprint logistics:

• Sprint window end date (end of week 2)
• Any known blockers or dependencies (approvals needed, stakeholders not yet met, tools not yet provisioned)
• Who will own deliverables (you, client, or shared — for each potential item)

Existing action items (if any):

• Open commitments from kickoff, emails, or session recaps
• Any items already tracked in the project management system
• Known deadlines already in play

Step 2: Review Engagement Goals and Early Observations

Before identifying quick wins, review the engagement goals and kickoff observations. Produce a brief engagement snapshot:

• Engagement goals: What the client hired you to accomplish
• Primary constraint: What you believe is driving the problem
• Early signals: Observations from the first session(s) that inform where quick wins live
• Repeated pain points: Anything the client has mentioned more than once — repetition is the strongest signal of actual priority versus stated priority

Rule: Quick wins must connect to this snapshot. If a candidate doesn't relate to the engagement goals — even loosely — it's not a quick win, it's a distraction.

Step 3: Identify Quick-Win Candidates (Quick-Win Identifier — Condensed)

3a. Situation Scan

Review all inputs for every problem, frustration, inefficiency, or complaint. Capture everything — don't filter for importance yet. Tag each item:

3b. Quick-Win Filter

Apply the filter to every item from the scan. A qualifying quick win must pass ALL four criteria:

1. Completable in 1-2 weeks with your current access and effort
2. Zero or minimal dependencies — no budget approvals, no new tools, no stakeholders you haven't met
3. Visible to the client — the result is something they can see, touch, or feel (not backend cleanup)
4. Connected to stated goals — even loosely, the win should relate to why they hired you

Items that fail any criterion get cut. Be aggressive — three strong candidates beats eight maybes.

3c. Scoring Matrix

Score surviving candidates on three dimensions (1-5 each):

Scoring guide:

• Visibility — 5 = client brings it up unprompted, 1 = you'd have to explain what changed
• Effort — 5 = you can do it today, 1 = takes the full two weeks with significant work
• Alignment — 5 = directly advances the main objective, 1 = tangentially related

Rank by total score descending. Select the top 1-2 candidates for the sprint.

Quick-win rules:

• Never recommend more than 3 candidates. Overloading the list defeats the purpose.
• Always include a timeline. "Do it soon" is not a plan.
• Never recommend something that requires a stakeholder you haven't met or mapped.
• Flag any quick win that could create a negative side effect (e.g., fixing process A breaks process B).

3d. Quality Gate — Quick-Win Identifier

Before proceeding, verify internally:

Run all checks. Identify the weakest area. Rewrite it. Verify the rewrite is present and improved before moving on.

Step 4: Build Execution Plans

4a. Primary Win Execution Plan

For the #1 ranked quick win:

• What: The specific action in one sentence
• Steps: Numbered list, no step longer than one sentence
• Timeline: Day-by-day or session-by-session breakdown within the sprint window
• Owner: You, client, or shared — for each step
• Resources needed: Only what's available now
• Completion criteria: How you'll know it's done (specific, observable)
• How to make it visible: The specific moment the client will see the result (a deliverable, a meeting moment, a before/after comparison)
• How to connect it forward: One sentence linking this win to the larger engagement arc

4b. Backup Win Execution Plan

For the #2 ranked candidate, document the same structure. You need a backup in case the primary win hits an unexpected dependency or the client's priorities shift in week one.

4c. Parked Items

For items that didn't pass the filter but have high client severity:

• [Problem] — Requires [dependency]. Revisit at [milestone].
• [Problem] — Signal: [what to watch for]. Revisit at [milestone].

Rule: Leave alone problems that require organizational change, budget, or stakeholder alignment you don't have yet. These are your month-two plays. Attempting them now and failing is worse than not attempting them at all.

Step 5: Build the Sprint Tracker (Action Item Tracker — Condensed)

5a. Item Extraction

From the execution plans in Step 4 and any existing open items from the inputs, extract every action item:

• Item: Verb-first description
• Owner: Specific name (never "we" or "the team")
• Deadline: Specific date within the sprint window (or "Needs deadline")
• Status: Open / In Progress / Blocked
• Source: Which execution plan or input document

5b. Deduplication

Compare all extracted items against existing action items from the inputs:

• Same task, different wording — keep the most specific version
• Same task, different deadlines — keep the most recent deadline, note the conflict
• Same task, different owners — flag for clarification (this is a risk)

5c. Master Sprint Tracker

Group by owner (Consultant items first, then Client items, then Third Party items):

Consultant Items:

Client Items:

5d. Flags and Risks

Call out:

• Overdue: Past deadline with no completion evidence — recommend: escalate, reassign, set a deadline, or close
• Stale: Assigned but no progress — recommend specific action
• Unowned: Tasks mentioned but never formally assigned — recommend specific action

5e. Quality Gate — Action Item Tracker

Before proceeding, verify internally:

Run all checks. Identify the weakest section. Rewrite it. Verify the rewrite is present and improved before moving on.

Sprint tracker rules:

• Every item must have a named owner.
• Items without deadlines get flagged, not dropped.
• Use verb-first language for every action item. "Send the proposal" not "Proposal needs to be sent."
• Never combine two different tasks into one line item. If it has two verbs, it's two items.
• Keep the tracker to one page. If it's longer, you have too many open items — that's its own signal.

Step 6: Frame the Client Communication

Write a brief sprint plan summary to share with the client. Frame it explicitly: these are the visible outcomes they'll have by the end of week 2.

Include:

• Sprint goal: 1-2 sentences on what the sprint delivers
• Quick win(s): What the client will see completed
• Timeline: Key dates and milestones
• What you need from the client: Specific asks with deadlines
• What to expect next: How you'll confirm completion at the end of week 2

Rule: This is not a status report. This is a commitment. Frame it as "here's what you'll have" not "here's what we'll try."

Step 7: Assemble Final Output

Present one unified document containing:

A. Engagement Snapshot

The engagement review from Step 2 — goals, primary constraint, early signals, repeated pain points.

B. Quick-Win Analysis

Situation Scan Table:

Quick-Win Candidates (passed filter):

C. Primary Win: [Name]

• What: [One sentence]
• Steps: [Numbered]
• Timeline: [Day-by-day]
• Owner: [Per step]
• Resources: [What's available now]
• Completion criteria: [Observable outcome]
• Make it visible: [Specific moment]
• Connect forward: [Link to engagement arc]

D. Backup Win: [Name]

[Same structure as Primary Win]

E. Parked (Not Now)

• [Problem] — Requires [dependency]. Revisit at [milestone].

F. Sprint Tracker

Consultant Items:

Client Items:

Flags:

• [Any overdue, stale, or unowned items with recommended actions]

Tracker Health:

• Open items: [Count]
• Items with deadlines: [Count]/[Total]
• Overdue: [Count]

G. Client Sprint Plan

The communication summary from Step 6 — sprint goal, quick wins, timeline, client asks, what to expect.

H. SOPs to Trigger

• [ ] Stakeholder Alignment Check — queue if sprint is on track at end of week 2
• [ ] Client Session Cycle — queue if sprint is on track at end of week 2
• [ ] Quick-Win Sprint (repeat) — if a quick win is incomplete, assess whether to extend or replace; document the decision

Quality Check

Rules

1. Quick wins exist to demonstrate value to the client, not to pad your hours. Pick what the client will notice, not what takes you the least effort.
2. Collect all inputs in one pass. Do not scatter prompts across multiple turns. Ask once, flag gaps, keep moving.
3. Score every candidate on all three dimensions. Gut-feel selection leads to wins the client doesn't notice. Use the matrix.
4. Never recommend more than 3 quick-win candidates. Overloading the list defeats the purpose of a sprint.
5. Never recommend something that requires a stakeholder you haven't met or mapped. Unknown stakeholders are dependencies, not resources.
6. Always include a timeline. "Do it soon" is not a plan. Day-by-day or session-by-session.
7. The execution plan must be specific enough to hand to a colleague. If they'd have to ask you questions to run it, it's not specific enough.
8. Include "how to make it visible." A win the client doesn't see is not a win.
9. Flag negative side effects. Consultants who break things while trying to prove value don't get second engagements.
10. Don't skip documentation because "it's just the first two weeks." The sprint tracker becomes the baseline for the Stakeholder Alignment Check. Don't skip structure early or you'll rebuild it later.
11. Every action item needs a named owner. "We" and "the team" are not owners.
12. Watch for repeated pain points. Repetition is the strongest signal of actual priority versus stated priority. If it keeps coming up, rescore your candidates.
13. Escape dollar signs as \$ for Notion compatibility.
14. Flag inferred details. If a severity rating, dependency, or constraint signal was inferred rather than stated, mark it [INFERRED — verify].

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.