Write what done looks like before the work starts, and name the thing that proves it.
We got this wrong ourselves. On a six-location software conversion, the plan showed the insurance module complete at the first office to go live. The plans would not open for editing, so the front desk was estimating coverage by hand. Nobody had written down what done would look like.
Every task on our boards now carries four columns before anyone begins: the task, one sentence a third person could test, the artifact that proves it, and a second person who opens that artifact in the weekly meeting. The meeting reads the scorecard first and the task list second, because a task can be closed while its number sits flat. At a four-office group, the scorecard showed thirty-nine calls in one month that the AI phone agent failed to hand to a person.
Two pages went up since the last note. How do I know the work was actually done and not just checked off? has the four columns and five questions to ask whoever runs your boards today. One-time build and hand off, or build and stay month to month? lays the two shapes side by side and says what moves the quote, so a partner can read it before we talk.
A question from a discovery call this fortnight with a nine-location group: do we bring the implementation partner in before or after we pick the software?
Either, and the work changes with the timing. Before you pick, the job is an audit of what you already pay for: which systems overlap, which ones nobody opens, and what the new purchase has to do that the current stack cannot. After you pick, the job is the rollout: the workflows configured before go-live, the few features your team will use picked and measured, the technical setup finished inside about 30 days. Either way, write the success and failure lines for the pilot before it starts and judge it 60 to 90 days after setup. A lift under 15 percent may not justify the cost.
If any of this describes your group, book 30 minutes: calendar.app.google/YCunxshZzSg56HME7. You walk me through your locations and the list. I tell you which shape fits and what the first 30 days would look like.
Craig
Where the proof on this page comes from
Every number and named process above traces to a row in our proof library. Each row names its source and the date we last checked it.
- P-024 Conversion lesson: after one office went live, insurance plans could not be edited or deleted, so the front desk estimated coverage by hand until the vendor fixed it. New CBCT scans did not transfer and needed a manual upload.
- P-028 39 calls failed to transfer from the AI phone agent to a person in one month at that group.
- P-044 Rollout rule Craig gives on calls: finish the technical setup of a system of action inside about 30 days, then track training, adoption and the agreed success measures.
- P-043 Pilot rule Craig gives on calls: set success and failure criteria before the pilot starts, judge it 60 to 90 days after setup, and a lift under 15 percent may not justify the cost.
- P-041 The 30-minute call: no pitch deck; by the end of it you know whether ASC is the right fit and what we would do first.