I don't have a framework. I have a sequence.
Four phases, run in order, on every engagement. Read the code and the numbers. Decide what to build, what to cut, what to leave alone. Document the path. Hand off the work in the format your team already executes in.
Why a sequence, not a framework.
A framework is a reusable grid somebody else built and you drop your problem into. That is not this. The sequence is the order the work happens in because it's the order that works — read before deciding, decide before documenting, document before handing off. Out of order, the work is slower and the plan is softer.
The sequence stays constant. What moves inside it is judgment — which vendors are live, which decisions are load-bearing, which risks belong on the first page of the plan and which belong in an appendix.
The outcome arrives because the sequence runs, not because someone attended a workshop.
The four phases.
- 1
Read
Week one. I read the code, talk to the team, and look at the numbers.
- Access to core systems and the three to five people who know where the bodies are buried.
- Enough context to stop guessing. Not enough to get precious.
- Written discovery notes, shared back inside the first week.
Principle The engagement clock starts when access is granted. The more context up front, the sharper the output.
- 2
Decide
Week two. The call goes in writing — what to build, what to cut, what to leave alone.
- One written call per load-bearing decision in scope.
- Reasoning on the page, not held back for a later reveal.
- Anything actionable surfaced early gets flagged the day I find it, not held for the final deliverable.
Principle Reframe free, resolve paid. If I can reframe the problem on a first call, I will. If resolving it takes real work, that's the engagement.
- 3
Document
Weeks three through six or seven. The path gets written in the format your team will execute from.
- Architecture specs where a decision is structural.
- Vendor scorecards where the market is the problem.
- A sequenced roadmap — prioritized by lift against revenue impact, so the highest-value, lowest-effort work ships first.
- Out-of-scope called out explicitly. The list of what I'm not doing is part of the plan.
- Weekly async status updates. No meeting tax.
Principle If the plan can't be picked up cold by the team that has to run it, it isn't done.
- 4
Hand off
Final week. A presentation of findings, the written plan delivered, and the work imported into the tracker your team already uses.
- Importable work items — Jira, Linear, GitHub Issues, whatever your team runs on.
- A formal walkthrough with the room that has to execute.
- Two paths surfaced at the close: hand off clean, or retain me for execution support.
Principle You do not have a deck. You have the decision in writing, the path documented, and the work in your tracker — ready on day one.
What you get, named.
The deliverable is the plan, written down. These are the named artifacts that tend to be in it, depending on scope.
- Written call on the load-bearing decision
- Root cause analysis
- Strategic remediation plan, sequenced by lift and impact
- Architecture specification where the decision is structural
- Vendor scorecard and selection memo where the market is the problem
- Integration design for downstream teams
- Risks named and rated
- Out-of-scope list, explicit
- Weekly async status updates across the engagement
- Importable work items — tickets ready to land in Jira, Linear, or GitHub Issues
- Presentation of findings and hand-off walkthrough
Not every engagement produces every artifact. The first working session names which of these matter for the problem in front of us.
What's out of scope, on purpose.
Workshops as standalone deliverables. Training programs. Anything that ends with "change management." Building and running software in production as the core deliverable — I can execute on a retainer after the plan lands, but the default offer is the plan.
These are named to be honest about where my expertise ends. If you need support in these areas, I can recommend specialists. A referral costs you nothing and makes the plan better once it lands.
What comes after.
At the close of Phase 1 the plan is yours. Two paths surface, scoped only at that point.
Hand off clean
Your team picks up the plan on day one. I step away. You own the outcome.
Execution support on retainer
A separate engagement for implementation oversight, vendor negotiations, and technical guidance during rollout. Scoped at close of Phase 1. Never pre-sold.
Bring me the stuck decision.
Limited engagements this quarter. Send the problem and you'll hear back inside two business days — with a scoped proposal or a referral to someone better suited.
jordan@cauley.co · 336-314-3314