What to expect in the first 30 days of a fractional engagement

The reasonable worry about any consulting engagement is that you spend a month paying for someone to learn your business, receive a document, and see nothing change. It is a fair worry, and it happens often enough to be a legitimate objection.

A well-run delivery engagement should produce something usable within the first fortnight and measurable change by day 30. Here is what that looks like, and what to hold an engagement to.

Week 1 — Observe, do not change

The first week is diagnosis. Sitting in existing ceremonies without redesigning them, reading the backlog, tracing recently shipped work backwards from production to origin, and talking to engineers individually.

Changing process in week one is a mistake. Every team has reasons for how it works, and some of those reasons are good ones that are not visible from outside. Someone who arrives and immediately reorganises your board is guessing.

Expected output: a written diagnosis identifying the primary constraint, with the evidence behind it. It should tell you at least one thing you did not already know.

Week 2 — Stop the bleeding

The narrowest set of changes that improve predictability, applied to the current cycle. Typically: a cleaned backlog with an explicit priority order, acceptance criteria on anything about to be worked on, and one named owner per in-flight dependency.

This is deliberately unambitious. The goal is not the ideal process — it is removing the two or three things causing most of the unpredictability.

Expected output: a backlog you could hand to a new engineer, and a shared definition of done.

Week 3 — Make it measurable

You cannot demonstrate improvement without a baseline, so this week establishes one: committed versus delivered, cycle time, rework rate. If those were never tracked, the first readings will be uncomfortable. That is the point.

Reporting also starts here — one page, weekly, saying what shipped, what slipped, what is at risk, and what changed. Written for someone who was not in the room.

Expected output: a delivery baseline and the first weekly report.

Week 4 — Forecast and hand back

With three weeks of measured data, forecasting stops being guesswork. By the end of week four you should be able to give an external commitment — to a board, a customer, an investor — with reasoning behind it rather than optimism.

This is also where handover begins. Which parts your team now runs themselves, which still need support, what happens if the engagement stopped tomorrow.

What should be true at day 30

• You can state what your team will ship in the next month, and defend the estimate.
• The backlog is ordered, and someone owns that order.
• Nothing enters a sprint without acceptance criteria.
• "Done" means the same thing to everyone.
• You receive a weekly written report you did not have to chase.
• You know the primary constraint on your delivery, with evidence.

What should not have happened

Equally worth checking, because these are the signs of an engagement optimising for its own continuation:

• A wholesale methodology change in month one. Nobody has enough information for that in four weeks.
• New tooling purchased. Tools rarely fix process problems and often disguise them.
• Reporting that requires the consultant to explain it.
• Increased dependency on the consultant rather than less.

A month is a fair trial. If delivery predictability has not visibly improved by day 30, the engagement is not working — and that is worth saying out loud rather than waiting for a quarterly review.