The Build Method · based on Google's Design Sprint
The Build Method
Four phases, run on your team's own workflows. Understand opens on what your team does by hand. Decide closes on what is worth building. Prototype opens on a working build. Validate closes on your own testers accepting it. Nicole led dozens of Design Sprints at Google. This is the version a firm can run in about four weeks per build.
The shape
The double diamond
The first diamond is about the problem. It opens wide on every workflow your teams do by hand and closes on the ones worth building. The second diamond is about the solution. It opens on a build and closes when your own people have tested it and signed.
Phase by phase
The four phases
1 · Opens the first diamond
Understand
- Who is in the room
- Per team: the people who have already built skills, the heaviest Claude users, and whoever knows the team's common workflows and procedures. Up to two hours of intakes per team, in 30-minute conversations. A team of one or two gets one or two.
- What happens
- Each intake asks for the one repeated job that takes longest, the files it uses, who judges a good output, and what the person has already built. Then the Role-Specific Workshop, where the team works hands-on on its own workflows and names the one it would turn into a firm Skill.
- What comes out
- Every workflow in the team's own words, with the files it uses and the person who judges a good output.
2 · Closes the first diamond
Decide
- Who is in the room
- The people who run the workflows. Planned at 25, never the whole firm.
- What happens
- Ninety minutes at a shared whiteboard. Every workflow goes up as a card. The room walks each one: does everyone do it the same way, with the same inputs, to the same output, and where does it break. Missing ones get added. Three dots each.
- What comes out
- The build plan, ranked by the vote and checked against the data and access each build needs before it works. The vote ranks. The readiness check decides.
3 · Opens the second diamond
Prototype
- Who is in the room
- Elevate, with one named champion on your side who decides what right looks like.
- What happens
- An output spec agreed in writing before anything is built: what it does, what it will not do, what you give it, how each standard is checked. Then the build, on our own test seat, on synthetic or closed-deal material. About four weeks per build.
- What comes out
- A versioned build, with the version line in every output it produces.
4 · Closes the second diamond
Validate
- Who is in the room
- The champion and two or three testers who do this work every week.
- What happens
- A build review where the golden cases run live in front of the room, then two rounds of testing by your own people against a fixed set of cases, inside ten business days.
- What comes out
- Acceptance signed by your champion, then release at organization level so everyone runs one version and nobody keeps an old copy.
What your sponsor reads
Where each skill stands
Every skill is on one rung at a time, and the label matches something a person can check in the Claude admin console. Only a release uses the word Live.
- NominatedSomeone asked for it. A one-line request and a named owner.
- QualifiedThe output spec is agreed and one champion has said yes.
- In buildElevate is building it on the test seat.
- ClearedYour compliance approver has signed off on the data it touches and where a person reviews the output.
- In testingYour testers are running the test pack.
- LiveInstalled for everyone, on the current version, and a second person has run it.
- RetiredThe owner took it down because it stopped earning its place.
What accepted means
- The output spec was agreed in writing before anything was built: what it does, what it will not do, what you give it.
- The test cases were fixed from that spec and run more than once, because a skill does not give the same answer twice.
- Your own testers ran them, in your environment, on the surfaces you use.
- Your champion signed. A build with an open wrong result is never accepted; a build with open suggestions is, and they go into the next version.
A skill that lives in one person's account is shared and unsupported, whatever it looks like from the inside. At one firm we counted ten skills in the admin inventory and four switched on for everyone. The gap between those two numbers is what this method closes.
Where it runs
The engagements that use it
One build
The Build Sprint
All four phases, once. You usually arrive past Decide, so Understand is the written brief.
Three builds
The Build Series
Understand and Decide once at the start, then Prototype and Validate for each build, with training after each acceptance.
The full install
The 90-Day Rollout
All four phases for its one Firm Build. The 60-Day runs Understand and Decide to produce the roadmap.
Frequently asked questions
It is four of its six phases, run on a firm's own workflows. Google's kit runs Understand, Define, Sketch, Decide, Prototype and Validate over five days with one team. We run Understand, Decide, Prototype and Validate over about four weeks per build, because the client is buying a working build and the sketching is the output spec we write with their champion. Nicole led dozens of Design Sprints at Google before founding Elevate.
The people who run the workflows on the wall, up to 25 of them. It is never the whole firm. A deal team's comps workflow in front of 60 people gets no honest answers. The session runs on a shared whiteboard, so the room adds cards and moves them, and the board stays up after the engagement.
A skill does not give the same output twice, so acceptance is measured over a fixed set of cases run more than once. The things that have to hold every time are enforced by a script or a template and checked on every run. The things the spec says it should do are checked by hand across all the runs. Then your champion answers one question per case: would you start your next real piece of work from this output. Criteria are frozen when the test pack is signed, so a new idea during testing goes into the next version instead of moving the bar.
The vote ranks. It says what the room feels most. Before a workflow is built it still has to pass the readiness check: a champion named and agreed, the inputs landed, and the surfaces it runs on proven to work. The most-voted card with no clean data behind it waits.
Every Firm Build. The Build Sprint runs it once. The Build Series runs Understand and Decide at the start, then Prototype and Validate three times. The 90-Day Rollout runs all four for its one Firm Build, and the 60-Day runs Understand and Decide to produce the roadmap. The Custom Program is a different method: your team builds in the room and keeps the capability.
Put your team's workflows on the wall
A 30-minute discovery call is where we work out which workflows belong in the first diamond and which engagement fits.