<aside>
📋 Frequency: Trigger-Based | Time: 45 min | Trigger: During weeks 1-2 of new engagement
</aside>
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 — which is valuable to you but invisible to the client. Perceived momentum early is not a nice-to-have; it's what keeps the engagement from derailing by week four.
Prerequisites
- Engagement Kickoff Prep SOP complete
- Client record active in your project management system with engagement goals documented
- First working session complete — you have enough context to identify viable quick wins
Procedure
- Open your project management system and review the engagement goals and any early observations from the kickoff session.
- Run the Quick-Win Identifier skill with the client's primary constraint, available resources, and a 2-week time horizon as inputs. The skill outputs a ranked list of candidates — review and select 1-2 that are achievable within the sprint window.
- For each selected quick win, define the deliverable, the owner (you or client), and the completion criteria. Document this in your project management system.
- Run the Action Item Tracker skill with the sprint deliverables, owners, and deadlines as inputs. This produces the sprint tracking structure — add it to the client record.
- Share the sprint plan with the client. Frame it explicitly: these are the visible outcomes they'll have by the end of week 2.
- At the end of week 2, confirm completion against the defined criteria. If a quick win is incomplete, assess whether to extend or replace it — document the decision. If the sprint is on track, queue the Stakeholder Alignment Check SOP and the Client Session Cycle SOP.
Expected Outcome
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.
<aside>
⚠️ Common mistakes:
— Selecting quick wins based on what's easy for you — 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.
— Skipping documentation because it's "just the first two weeks" — the Action Item Tracker output becomes the baseline for the Stakeholder Alignment Check. Don't skip structure early or you'll rebuild it later.
</aside>