The craft · product The system behind manual 06 Published craft page

Product · active

The Four-Artifact Project Pack: scope it like a firm would, before you spend a dollar running it.

Your internal project is not going to fail in execution. It is going to fail right now, at scoping, the way most of them do: a vague goal, no agreed definition of done, and a budget that quietly doubles because no one wrote down what they were actually buying. This pack gives you the four documents a serious consulting team builds before anyone touches the work, so your project finishes on time instead of sprawling into next quarter.

UseWork the tool now
Your timeAbout one week of scoping
FormatFour templates + review and closeout
Apply for advisory Read the manual it comes from
The four scoping artifacts laid out before a project starts.

The problem you actually have

Your project did not fail because the team was bad. It failed before the team started.

You greenlit it on a sentence: "we need to fix onboarding," "we should rebuild the reporting," "let's stand up the new function." Everyone nodded. Three months later the project is over budget, nobody agrees on what done looks like, and the scope has quietly tripled because every meeting added one more reasonable-sounding thing. The team worked hard. The project still drifted, because the drift was baked in at scoping, before anyone wrote a line of work down.

This is exactly the failure a good consulting firm charges you to prevent. Most of what their fee buys, in the first phase, is four documents that force the hard questions before the spending starts. You can build those documents yourself in about a week, and skip the firm entirely on the projects that never needed one.

A project with no written definition of done is not a project. It is a standing invitation to spend.

The pack gives you those four artifacts, plus the weekly review and the closeout that keep the project honest from kickoff to the day you can prove it is finished. It does not slow the project down. It stops the version of the project that never ends.

Who it is for, and who it is not

For the sponsor who keeps greenlighting projects that sprawl.

This is for you if

You sponsor or lead internal projects with real budget and real stakes. You have watched one drift past its deadline with no clean way to say it was done. You would rather scope it tight yourself than pay a firm to impose the discipline, on the projects that do not actually need the firm.

It is not for you if
  • You want someone to run the project for you. This scopes it; you still execute.
  • You will not spend a week scoping before you spend a quarter building.
  • The project genuinely needs a specialist firm's expertise, not just discipline.
  • You are fine greenlighting on a sentence and finding out later.

Why this, and not a project plan template

A project plan tracks the work. These four artifacts decide whether the work was worth starting.

The templates you find online are execution tools: Gantt charts, task lists, status trackers. They are good at managing a project that was already scoped well and useless on a project that was not, because they happily track a doomed project right up to the day it dies on schedule. They answer "are we on track" and never "on track to what, and how will we know we got there."

This pack lives entirely upstream of that, in the part that decides the outcome.

Difference 01

It forces a written test-of-done.

One artifact is nothing but the conditions that, if met, mean the project is finished. Written before kickoff, agreed by the sponsor. Without it, "done" is whatever everyone is too tired to argue about, and scope creep has no wall to hit. This single document kills most of it.

Difference 02

It separates the brief from the workplan.

Most internal projects fuse why and how into one fuzzy doc. The pack splits them: the brief is the problem and the outcome, the workplan is the path. Keeping them apart is what lets you change the how without quietly drifting the why, which is where scope creep actually hides.

Difference 03

It runs the weekly review against the brief, not the to-do list.

Every week you check progress against the original brief and test-of-done, not against last week's tasks. That is the firm's discipline: measure the work against the goal it was supposed to serve, so a busy week of the wrong work gets caught instead of celebrated.

What is inside

Four artifacts up front, a weekly review, and a closeout that proves it is done.

One folder per project. Four documents you write before kickoff, a short weekly review note, and a closeout you hold against the test-of-done at the end. You write them in order, because each one constrains the next, which is the whole point.

project/
  brief           # the problem and the outcome. why this project exists
  workplan        # the path. phases, owners, dates. the how, kept separate from the why
  deliverable-spec # exactly what gets produced, in what shape, to what standard
  test-of-done    # the conditions that mean finished. agreed before kickoff
  weekly-review   # short note, measured against the brief, not the task list
  closeout        # held against the test-of-done. proves done, or names the gap

Four written before a dollar is spent. Two that keep it honest until the test-of-done is met.

  1. 01

    The brief.

    The problem in plain language and the outcome that would mean it is solved. No solution yet. If the brief cannot be written without naming the fix, you do not understand the problem well enough to start, and that is the cheapest finding the pack will ever give you.

  2. 02

    The workplan.

    The path from here to the outcome: phases, owners, dates, the fully-loaded cost. Separate from the brief on purpose, so when the plan changes, and it will, you can see whether the change still serves the original problem or has quietly become a different project.

  3. 03

    The deliverable spec.

    Exactly what the project produces, in what form, to what standard. The thing you can hold at the end and check. Vague deliverables are how a project ends with everyone busy and nothing finished. The spec makes "produced" mean something specific.

  4. 04

    The test-of-done.

    The conditions under which the project is over, agreed by the sponsor before kickoff. This is the wall scope creep hits. Anything that does not move you toward the test-of-done is not part of this project, no matter how reasonable it sounds in the moment.

  5. 05

    The weekly review against the brief.

    Thirty minutes, against the brief and the test-of-done, not last week's tasks. The question is not "did we do things," it is "are we closer to done." A week of hard work on the wrong thing gets caught here instead of at the deadline.

  6. 06

    The closeout against the test-of-done.

    At the end, you hold the result against the test-of-done you wrote at the start. Either the conditions are met and the project is provably finished, or they are not and you have named the exact gap. No more projects that just quietly stop.

A real project with it running

Here is how one week of scoping saves a quarter of drift.

Say the project is "fix onboarding," greenlit in a meeting because new hires keep ramping slowly. Walk it through the pack.

  1. 1

    The brief exposes a fuzzy problem.

    Writing the brief, you cannot state the outcome without admitting you do not know whether slow ramp is a training problem, a hiring problem, or a manager problem. That is the project's real first task, and you almost spent three months building training for a hiring problem.

  2. 2

    The test-of-done forces a number.

    You define done as "new hires reach defined productivity in 45 days, down from 90, measured for two cohorts." Suddenly the project has a finish line. Before, "fix onboarding" could have run forever, because nothing was ever quite fixed enough.

  3. 3

    The weekly review catches the drift.

    In week four someone proposes also rebuilding the onboarding portal. Held against the brief, it does not move the 45-day number, so it is a different project. You park it instead of absorbing it. That one catch is the whole quarter saved.

  4. 4

    The closeout proves it.

    At the end, two cohorts hit 45 days. The test-of-done is met, the project is provably finished, and the team is freed instead of drifting into a vague phase two. You can point to the result, not just the effort.

Without the pack: three months of training built for the wrong cause, a portal rebuild nobody asked for, and a project that never officially ended. With it: one week of scoping and a finished project you can prove.

What you walk away with

Four payoffs, and none of them is a prettier status deck.

The compounding effect

Every project you scope this way makes the next one cheaper to run.

The biggest return is organizational. After a few projects run on the pack, your team learns to expect a brief and a test-of-done before work starts, scope creep stops being the default, and you stop reaching for an expensive firm to impose discipline you now have in-house. The cost of running good projects drops, and the cost of the firm you used to need drops with it.

  • Projects finish on a defined line instead of drifting to a stop.
  • Scope creep hits a written wall every single week.
  • You stop paying a firm for discipline you can run yourself.

Payoff 02

You catch the wrong project before you fund it.

The brief regularly reveals that the named problem is not the real one. Finding that in week one, on paper, is the cheapest save in the whole pack.

Payoff 03

Done means something specific.

The test-of-done turns "are we finished" from an argument into a checklist. Projects end cleanly and the team gets freed instead of lingering.

Payoff 04

If you do hire a firm, you brief them sharply.

Scoped artifacts make you a far better client. You hand a firm a real brief instead of a sentence, and you get better proposals and a better price.

How you grow it

Start with two artifacts on your next project. Add the rest as it proves out.

Next project

Write just the brief and the test-of-done.

Do not adopt the whole pack at once. On your next project, write only the brief and the test-of-done before kickoff. Those two alone prevent most of the drift, and they are the ones that change how the project feels immediately.

Project after

Add the workplan, the spec, and the weekly review.

Once the first two earn their place, run the full four plus the weekly review measured against the brief. By now the team expects the discipline and the review takes thirty honest minutes.

Across the org

Make the brief the price of a greenlight.

Set the rule that no project gets funded without a brief and a test-of-done. Now the discipline is structural, not personal, and the sprawling-project problem stops being a recurring tax.

When you outgrow it

Turn the artifacts into an RFP.

When a project genuinely needs a firm, your scoped artifacts become a sharp RFP that gets better proposals at a better price. That is the next product, and your pack is its input.

Use it now

The page is open for operators who need the tool before the work gets expensive.

The pack goes out once the six templates have carried two real internal projects start to finish without needing to change, because a scoping template that is still moving teaches the wrong discipline to the team that adopts it today.

The four artifacts and the review-and-closeout cadence are in use. What is still settling is the test-of-done template, written so it forces a measurable condition instead of a vague one, and the weekly-review format that keeps the check on the brief instead of sliding back to the task list.

If you have a project to scope now and want the working version, apply. Advisory clients run the live pack inside the engagement, and the standalone version goes to that list first.

What this is not

The pack scopes the project. It does not run it, and it does not pick the right project.

Running it firm-style does not give you a firm.

The pack gives you a consulting team's scoping discipline. It does not give you their specialist expertise, their hands to execute, or the outside judgment on whether this is even the right project to run. When the project needs deep domain skill you do not have, or when you are not sure the project should exist at all, that is where a firm or an outside read earns the engagement. The manual names that line, and the advisory is where the is-this-the-right-project question gets pressure-tested.

Back to the manual →
Bring in a firm or a read when
  • The brief keeps coming out wrong and you cannot see why.
  • The project needs expertise the team genuinely does not have.
  • You suspect the project is the wrong project entirely.
  • The test-of-done cannot be met and no one will say so.

When the work is live

Apply, and you run the live pack on your next project now.
The standalone version reaches that list first.

Application-gated. Personal reply within 48 hours. Advisory clients run the working scoping pack inside the engagement before it ships to anyone else.

Apply for advisory

Tier 01 Outside Read: Monthly $2,500/mo · Tier 02 from $4,500/mo · All three tiers