Consulting engagements usually end with a handover document and a final invoice. What they rarely end with is a disciplined look back at how the work itself went. A start-stop-continue review fills that gap. It asks both the consulting team and the client team to sort the engagement into three lists: practices to start, practices to stop and practices to continue. This guide sets out the method as eight steps, with an emphasis on using evidence from the engagement rather than impressions, because impressions fade fast and flatter whoever speaks first.
Step 1: Define the stretch of work under review
A review without boundaries produces vague output. Decide whether you are examining the whole engagement, a single phase such as the assessment, or a specific delivery such as a pipeline migration. Put the scope into a single line heading the page. A tight scope lets you compare like with like and keeps the discussion on what the two teams actually did.
Step 2: Gather evidence before the meeting
This is the step that separates an analytical review from a chat. Pull together artefacts that already exist: the ticket history, the change log, deployment records, meeting notes, the list of decisions that were reversed. Ask each participant to bring two or three observations, each tied to a specific artefact. “Handovers between the platform team and application teams were slow” becomes “three pull requests waited for a reviewer over several working days,” which gives the group something to examine.
Keep the pile small. A handful of concrete records beats a mountain of exported dashboards that nobody reads. Evidence exists to anchor opinions, not to bury them.
Step 3: Invite both sides and set the ground rules
In consulting, the review is only honest if the client voice is present. Include the people who lived with the changes: operations, security, product, and the sponsor. State the rules at the start: items describe practices, not individuals; every item should be actionable; and each list is capped at a small number of entries.
Step 4: Collect items silently, then group them
Give everyone ten minutes to write items on notes under the three headings. Silent writing prevents the loudest voice from setting the agenda. Then put the notes on a shared surface and cluster duplicates. Where two items contradict one another, such as one person saying to continue weekly steering meetings and another saying to stop them, mark the pair and discuss it explicitly, because the disagreement itself is information.
Step 5: Test each item against the evidence
For each cluster, ask: what record supports this? Where evidence is thin, label the item as a hypothesis rather than a finding. This keeps the final lists honest. A typical set of engagement-level items might look like this:
- Start: agree on a shared definition of “done” for infrastructure changes before the first sprint, so both teams judge completion the same way.
- Stop: stop holding status meetings that repeat what the board already shows; use the time for blockers only.
- Continue: continue pairing a consultant with a client engineer on each automation task, since knowledge transfer visibly improved on those tasks.
Each item points to something checkable, which is the standard to hold the whole list to.
Step 6: Reduce the start-stop-continue lists to a few commitments
Limit each list to two or three entries. Assign an owner and a review date to every item. If you leave the room with ten starts, you will complete none of them. The reduction is hard because it means leaving good ideas on the table, but a short list that gets done changes the next engagement, while a long list becomes a document.
For a consulting firm, the lists have a second life. The start and stop items shape how the next engagement is scoped, and the continue items become the habits that get written into proposals as standard practice. For a client, they become inputs to the internal playbook that remains after the consultants leave.
Step 7: Record the review where the next team will find it
Put the lists in the engagement folder or the client’s wiki, next to the handover material. Date them, name the scope, and link to the artefacts you examined. If you want a template for what the wider engagement should look like from assessment through enablement, a blueprint that traces an engagement from the opening assessment to the final enablement stage pairs well with the review. For teams whose engagements touch security, the guide to building security into DevOps pipelines can help you phrase start items that deal with scanning, secrets and approvals.
Step 8: Revisit at an agreed point
Return to the lists after a fixed interval, perhaps a month for a short engagement or a quarter for a long one. Mark each item as done, partly done, abandoned or overtaken by events. Where a stop item reappears, look at what makes the old habit attractive. Often it is solving a real need, such as the status meeting quietly covering for the lack of a shared board, and the stop will only stick once the underlying need has a better home.
A small illustration of evidence at work
Suppose a client felt the engagement had moved slowly in its middle weeks. In the meeting, instead of debating the feeling, the group opens the change log and notices that most delayed items shared one trait: each needed sign-off from a team that was not in the weekly meeting. That observation produces a start item (invite that team to a fifteen-minute slot each week), a stop item (stop sending approval requests by email and waiting) and a continue item (keep the written decision log that made the delay visible in the first place). The feeling became three actions in under an hour, and nobody had to be blamed for it.
That is the real advantage of working from records. Disagreements move from “I think” to “the log shows,” and the conversation shifts from defending the past to designing the next stretch of work.
What the evidence tends to show
In reviews like this, a few patterns recur. Start items cluster around clarity: agreeing definitions, naming owners, writing things down earlier. Stop items cluster around ceremony: meetings, reports and approvals that no longer earn their cost. Continue items cluster around people: pairing, open channels with the client, and honest escalation. None of this is surprising, but seeing it written on a page tied to the engagement’s own records makes it much harder to dismiss.
A note on borrowing sorting ideas from other fields
Consultants spend their working lives learning from other sectors. Take BestPilotsNow, an aviation discovery website that gives pilots, training schools, courses and reference material their own tabs, with discussion and articles alongside. Its habit of filing content by purpose has a twin in the review itself: sort what happened by what it asks you to do next, whether that is begin, drop or keep. Sorting by action, rather than by topic or by who said it, is what makes the lists usable.
Common pitfalls to avoid
- Running the review as a sales conversation. If the consultants are using it to justify a follow-on contract, the client will hold back.
- Letting the sponsor speak first. Seniority pulls the rest of the group toward agreement.
- Treating every item as equal. Rank by the cost of leaving it unchanged.
- Skipping the continue list. The practices that worked are the ones most likely to disappear after the consultants leave.
A compact checklist
- State the scope in a line.
- Collect a few records from the engagement.
- Invite both teams and agree the rules.
- Write silently, then cluster.
- Test each item against a record.
- Trim to two or three per list with owners.
- Store the lists with the handover.
- Revisit on a fixed date.
An engagement that ends with a clear, evidence-backed set of three lists leaves the client better prepared than one that ends with a longer slide deck, and it gives the consulting team a sharper starting point for the next piece of work.
Best Cardiac Hospitals Near You
Discover top heart hospitals, cardiology centers & cardiac care services by city.
Advanced Heart Care • Trusted Hospitals • Expert Teams
View Best Hospitals