FIELD MANUAL 001 · FREE TO USE
Seven days. One finished work.
Choose one useful result. Make it real.
Let the evidence decide what comes next.
POWER IS A PRACTICE.
A working method for independent builders.
THE STANDARD
A finished piece of work. A real attempt to use it. A record of what happened. This is the standard for the next seven days.
Choose a modest deliverable: a proposal, a checklist, a sample, a short lesson, or a working page. Define one person it could help. Keep the scope small enough to finish.
The protocol helps structure work and learn from it. It does not promise sales, income, or a particular outcome.
HOW TO USE THIS PAGE
Read one day at a time and answer its prompts in a notebook or your own document. To keep a paper copy, use your browser’s Print menu; on a phone, look for Print in the share menu. Your browser may also offer Save as PDF.
No account required. No form to submit. Keep your record with your work.
THE SEVEN DAYS
Use the lines as prompts.
Keep answers concrete.
DAY 01
Choose something another person can use. Reduce the work until a first version can be finished in seven days.
Write one sentence: By [deadline], I will finish [deliverable] for [person] so they can [useful action].
The person this is for
The one deliverable I will finish
The problem it should help them solve
My deadline: date and time
LEAVE WITHA deliverable, a specific audience, and a deadline.
DAY 02
Decide what would count as useful before the work can persuade you that it is finished.
Count an action, a completed task, or a specific response. A compliment alone is weak evidence.
The action someone should be able to complete
The evidence I will record
The minimum result that counts as useful
What I am deliberately leaving out
LEAVE WITHOne observable test and a clear boundary.
DAY 03
Build the smallest version that can be used from beginning to end. Make the important part work.
If time runs short, reduce the scope. Keep the useful action intact.
The rough version: title or file location
The essential action it already supports
The weakest part I can see
What must work before someone tries it
LEAVE WITHA complete rough version that can be tried.
DAY 04
Choose one person who faces the problem. Invite them to try the work. Ask these three questions without explaining the answer.
Record what happened. If there is no reply, write “no response” and keep that uncertainty visible.
1. What would you use this for?
2. Show me how you would use it. Where do you pause?
3. What is missing for you to complete the task?
Their actual words and actions, with the date
LEAVE WITHAn honest record of one attempt.
DAY 05
Choose the obstacle that most directly blocked the useful action. Make one revision that addresses it.
When feedback is unavailable, test the task yourself and label the result as a self-test.
The most important failure I observed
The change I made
Why that change should help
The version or file that contains the revision
LEAVE WITHOne revision tied to an observed problem.
DAY 06
Deliver the revision or run a private test. Use the test from Day 02 and record the result as it happened.
A failed test is useful evidence. Record it with the same precision as a successful one.
Where and when I delivered or tested it
What the person actually did
What met the Day 02 criterion
What failed, remained unclear, or went untested
LEAVE WITHA dated result with its limits stated.
DAY 07
Read the evidence. Decide whether to keep the work, revise it, or stop. Give the next move a reason.
Keep what works. Revise what has a specific repair. Stop when the next test is no longer worth the effort.
My decision: keep / revise / stop
The evidence that supports that decision
The one thing I still do not know
My next action and its deadline
LEAVE WITHA decision the record can support.
A WORKED EXAMPLE
HYPOTHETICAL EXAMPLE
No customer results are claimed.
A freelance designer wants to help other designers prepare clearer project quotes. The first deliverable is a one-page checklist.
01—03 · CHOOSE & BUILD
Result: one checklist covering scope, deliverables, revision limits, timing, and payment milestones. Deadline: Sunday, 18:00.
Proof: one designer uses it to review a sample quote and can identify any missing project terms. Record what they find and where they need help.
Exclude: contract language, pricing advice, branding, and a full proposal template. Make a plain first version.
04—06 · OBSERVE & REVISE
Ask a designer to review the sample quote with the checklist. Use the three Day 04 questions. Write down their actual response.
If they struggle with “revision limits,” a possible repair is a clearer prompt: “How many revision rounds are included, and what counts as an extra round?”
Have the revised checklist tried again. Record whether the task becomes clearer. Until that test happens, leave the result blank.
07 · DECIDE
Keep it if the record supports its usefulness. Revise it if a specific obstacle remains. Stop if the problem is not worth solving with this format. The evidence determines the next version.
BEGIN WITH DAY 01
Choose the result. Set the deadline.
Return with proof.