PAPER NO. 03
Build Something
You Can Actually Deliver.
The first product is not everything you can imagine. It is the thing you can actually deliver.
How to turn a real problem into a focused first product, protect the wider vision, and avoid trying to build everything at once.
FROM CLUSTER TO SCOPE
Ambition is what you defer,
not what you launch with.
The second paper ended with a cluster. A real, connected, lived problem mapped by the person closest to it.
This paper is about what happens next, which is one of the most underrated disciplines in building anything.
Cutting.
Founders often fail here in a specific way. They look at the complete problem they have mapped, see everything that could be fixed, and decide the first product should fix all of it.
The result is predictable. Development takes longer. Complexity grows. Costs increase. Focus gets divided. And eventually something ships that represents a compromised version of a much larger vision.
The fix is not to lower your ambition.
The fix is to change where ambition lives.
Ambition belongs in the system you are building over time. The first thing you ship has a narrower job.
It has to work.
The first product is not what you can build.
It is what you can deliver.
Build is a low bar.
Build means something exists.
Deliver means the product can actually reach the customer at the standard you promised, supported by the manufacturing, information, setup, service and infrastructure required for them to use it.
Most ideas become much harder somewhere between those two words.
The discipline of scope is closing that gap.
What ONE Blades
had to become first.
ONE Blades has never suffered from a shortage of ideas.
That is not necessarily an advantage.
Once you understand a category deeply enough, you can see problems everywhere. Products you could make. Education you could build. Services you could offer. Systems that could connect all of it.
The temptation is to treat seeing the opportunity as permission to pursue it immediately.
It is not.
The question I eventually had to answer was much simpler: what should ONE Blades actually deliver first?
The answer became the EDGE™ | Inline Figure Skating System.
Not because it represented every problem I could see in skating. It did not.
It represented the problem I understood deeply enough to build against, explain clearly, manufacture, support and put into the hands of skaters.
That distinction matters.
A company can have a large mission while still having a very small first focus.
Why the cut
has to be made.
More product can look like more progress.
Often it is the opposite.
Every additional product introduces another set of decisions. More development. More manufacturing. More inventory. More documentation. More customer questions. More things that can go wrong.
It also divides the story.
A new company already has to earn attention and trust. Asking customers to understand several new things at once makes that job harder.
But there is a more important reason to focus.
Your first product is not just a product.
It is evidence that your system can deliver.
Until you have shipped something, you do not fully understand your manufacturing process, fulfillment, customer support, education, communication or what actually breaks when the product leaves your hands and reaches a real person.
Those things cannot all be learned in design.
They are learned through delivery.
The first product proves more than the product.
It proves the company can deliver.
Three questions
the cut has to answer.
Cutting should not be random.
Do not simply pick the easiest idea or abandon whatever feels difficult.
Run each candidate through three questions.
Which one do I understand most deeply?
Your strongest starting point should sit where your accumulated experience gives you a real advantage.
You should understand the skater, the problem and the context from inside the category, not simply from research conducted after deciding to enter it.
Which one can I deliver without compromising the promise?
Build is not the test.
Can you manufacture it at the standard you want? Can you support it? Can customers understand it? Can you get it into their hands and stand behind what arrives?
If your plan depends on knowingly shipping something you would not stand behind, the scope is wrong.
Which one creates the strongest foundation?
The first product does not need to complete the mission.
It needs to strengthen your ability to continue it.
A strong first product teaches you how the company operates, creates customer relationships, generates evidence and gives you better information for every decision that follows.
Inside the chosen product,
cut again.
Choosing one product is only the first cut.
Now you have to make the same decision inside the product.
Every product accumulates features, options, configurations and ideas during development.
Many of them will be good.
Good is not enough.
For every part of the product, ask whether it has to exist for the product to deliver its core promise.
If removing it breaks the promise, it belongs.
If removing it merely makes the product less impressive in your own head, question it.
EDGE needed the structural decisions that make it an inline figure skating system rather than simply another inline frame.
Four wheels create three balance zones. The rocker axle system allows the skating setup to be adjusted. The EDGE pick is part of the skating geometry. Frame sizing has to work across the intended boot range.
These are not decorative additions.
They are part of the answer to the problem.
Other ideas can wait.
If removing it breaks the promise, keep it.
If it only makes the launch bigger, question it.
Deferring is
not abandoning.
This is where founders can make bad decisions emotionally.
An idea moves to Later and it feels as though something has been lost.
Nothing has been lost.
Killing an idea means deciding it should not exist.
Deferring an idea means deciding that now is not the moment to build it.
Those are completely different decisions.
In fact, deferral can be a form of protection.
A good idea launched too early competes for resources, receives partial attention and risks being defined publicly by a compromised first version.
The same idea held until the company has the resources, knowledge and focus to execute it can remain intact.
How to spot that
you are over-scoped.
Most people discover excessive scope too late.
There are warning signs much earlier.
You cannot explain the first product in one clear sentence.
Complexity in the explanation is often revealing complexity in the product.
The schedule keeps moving because more things have to be finished.
A moving date can be a resource problem. It can also be the product telling you that you are trying to ship too much at once.
You spend more time deciding what to add than what to remove.
Early product development naturally produces possibilities. Scope requires deciding which possibilities do not belong yet.
You knowingly plan to fix important weaknesses after launch.
There is always more work after launch.
But knowingly shipping something that fails the core promise is not iteration. It is unfinished scope.
Too many unfinished parts depend on each other.
Interdependence creates fragility.
If nothing can finish until everything finishes, look for another cut.
None of these signs mean the wider vision is wrong.
They mean the current scope may be carrying too much of it.
Protect the vision by reducing what has to happen now.
The next paper in this series, One Person, Full Stack, looks at what happens after the scope is clear.
You know what you are building. Now somebody has to actually build the company around it.
DO THIS NOW
Make the cut,
in writing.
Take the cluster you mapped in Paper No. 02.
This is the bridge between understanding the problem and deciding what you will actually deliver first.
List every product idea you currently carry.
Write down every distinct product, service or offering you are imagining inside the territory.
Separate products from features. Be honest about how many different things you are actually trying to carry.
Run each through the three questions.
Which do you understand most deeply?
Which can you deliver without compromising its core promise?
Which creates the strongest foundation for what comes next?
Choose what ships first.
Put the strongest candidate at the top of a clean page.
Write beneath it: this is what I am shipping first.
Everything else moves to a separate list called Later.
Cut inside the chosen product.
List every feature, option and addition you currently expect the first product to contain.
Ask whether each one is required for the product to deliver its core promise.
Keep what is essential. Move the rest to Later.
Write the one-sentence promise.
Describe what the scoped first product delivers and who it serves in one clean sentence.
If you cannot make the sentence clear without adding explanations, inspect the scope again.
THE BUILD SERIES · PAPER NO. 03
The first product is not
what you can build.
It is what you can deliver.
PAPER NO. 04