Find the position you can actually defend
Leave with one positioning statement you can hold under questioning.
- Steps
- 7
- Time
- 16 min
- Level
- Foundational
Each guide takes one problem and works it end to end: the decision, the steps, the tradeoffs, and what to do when it does not go cleanly. Written to stay true a year from now, and to be usable the same afternoon you read it.
Pick the stage you are actually in rather than the one you would like to be in. Each track is a sequence, so the second guide assumes the first.
Nothing is public yet. The work is deciding what to be before spending on it.
Leave with one positioning statement you can hold under questioning.
One document that briefs a designer, a writer, or a freelancer identically.
A page list and a section order agreed before anything is drawn.
The decisions are made. Now they have to survive contact with a real audience.
A written exclusion list, so the offer stops being for everyone.
A palette with roles, not favourites, that still works in black and white.
A decision recorded with its tradeoffs, so the next person understands it.
It works. The problem is repeating it without the quality falling over.
Three cheap tests that tell you if the message lands before the build.
Rules short enough to be read, specific enough to be obeyed.
Contrast, focus, and order handled at the start instead of at audit.
Filter by the part of the business you are working on, then by how deep you want to go today.
Leave with one positioning statement you can hold under questioning.
One document that briefs a designer, a writer, or a freelancer identically.
A page list and a section order agreed before anything is drawn.
A dated plan you can run alone without missing the launch window.
A content boundary in writing, so the calendar stops being a guess.
A scope document that names the boundary before the work starts.
A sentence that survives being repeated by someone who does not work for you.
A pairing chosen against use, with the reasons written down beside it.
A homepage argument, section by section, written before layout.
A complete asset list, sized and named, ready before launch week.
A repeatable session that produces a month without draining a week.
A fit review that reaches yes or no without three unpaid meetings.
A written exclusion list, so the offer stops being for everyone.
A palette with roles, not favourites, that still works in black and white.
A decision recorded with its tradeoffs, so the next person understands it.
One message set that adapts to every channel without being rewritten.
A method for getting a month of material out of work you already did.
A schedule and a policy that stop you funding someone else's delay.
A defensible price built from the outcome, not from your hourly guilt.
A scored audit that separates what to keep from what to quietly retire.
The specific changes that move the numbers, in the order that pays first.
A day-by-day operating plan, including what you will not do.
A permission-safe structure, from the request email to the final page.
A package the client can still use a year later without calling you.
Three cheap tests that tell you if the message lands before the build.
Rules short enough to be read, specific enough to be obeyed.
Contrast, focus, and order handled at the start instead of at audit.
Templates and a triage rule so real conversations do not get buried.
A grammar of formats that reads as one voice across a quarter.
Three scripts for declining that leave the door open on purpose.
A sequenced migration plan, so the change does not read as a panic.
A method for new formats that does not require the original designer.
A small set of events that answer real questions, and nothing else.
A review that separates signal from relief, with decisions written down.
A pruning pass that improves the whole by removing part of it.
A working system with a buffer, a pipeline, and a stop rule.
The ground the other thirty-three stand on. Nothing here expires, and nothing here assumes you have read anything else first.
Leave with one positioning statement you can hold under questioning.
One document that briefs a designer, a writer, or a freelancer identically.
A page list and a section order agreed before anything is drawn.
Every guide here is written so you can run it without me. If you would rather not, that is exactly what the studio is for.