§00 / Method

Scoped, then staffed.

The approach is deliberately plain. Work starts with a scoping conversation, becomes a written scope document, and is controlled through a decision log, delivery cadence, handover documentation and post-engagement review.

§01Scoping conversation
§02Written scope
§03Decision log
§04Delivery cadence
§05Handover and review

Initial scoping conversation

Produced: a short note on the problem, constraints, known stakeholders and open questions. Signed off by the client sponsor as an accurate basis for drafting scope. If the problem is not ready to scope, the work stops there.

Written scope document

Produced: objectives, exclusions, deliverables, decision owners, working language and handover expectations. Signed off by the sponsor and the trailhatchix engagement lead. If scope needs to change mid-engagement, a variation note states the change before the work continues.

Decision log

Produced: a decision, dated, with options considered, owner, rationale and consequences. Signed off by the person with authority to make that decision. The log prevents old questions being reopened without acknowledging the cost of doing so.

Delivery cadence

Produced: agreed checkpoints, work-in-progress review and escalation route. Signed off through attendance and written acceptance of checkpoint notes. If a new dependency appears, it is logged as a risk, blocker or variation.

Handover documentation

Produced: final documents, open decisions, assumptions, owners and next-step recommendations. Signed off by the sponsor or named receiving owner. Work is handed over, not handed off; the receiving owner must know what they are accepting.

Post-engagement review

Produced: a close-out note covering what was delivered, what changed, what remains unresolved and what should not be continued. Signed off by both sides as a record, not as a claim of guaranteed outcome.

Before we start

We ask for a named sponsor, a practical reason for the work, access to relevant documents, a list of decision makers, known constraints, and a clear statement of who owns this inside the organisation. We do not need a perfect brief. We do need permission to write down ambiguity instead of pretending it is already solved.