September 27, 2023
What will it do?
When we start our businesses, we don’t really know.
We know what we want to do. More of the things we enjoy, less of the things we don’t, with no interference from the boss.
We have an inkling that left to ourselves, we can probably produce something much more in line with what the customer wants than we were able to as a small cog in a big machine.
Or we hope that having experienced a problem and found a new solution, there might be others who will welcome what we’ve discovered.
In truth, we don’t really know who they are, what they want, or how they want it.
That’s fine.
The job of a startup is to find that out. We need to be observant, flexible, opportunistic, open to a different who, a different what. A certain amount of thrashing is inevitable.
But once we do know who and what, thrashing no longer serves. Now we need to concentrate on how. Hand-crafting a consistent customer experience, ‘doing things that don’t scale’ until we’ve really hit the mark.
Until finally, we’ve answered the question “What will it do?”
You’re no longer a startup.
And the next challenge begins.
Because if you really have hit the mark for a significant number of people, the next question is “How can I do it like this for more people?”, “How do I replicate my actions through other people or through software so that I can reach more of the people who want what I can offer, in the way that I offer it?”
You don’t have to scale of course. You can stick with a handcrafted service and a select clientele. Just make sure they are paying you full value for that.
But if you want to reach more people, have an even bigger impact, you need to think about scaling up the system you’ve inadvertently designed.
Scaling up starts with treating it as a design, rather than a happy accident- soon to be overtaken by the next.
Which means starting by writing your design down. So there’s a reference point, a specification, an intention.
So that from now on, everyone knows what it has to do.
Otherwise how can you work how best to share the work? Or how best to automate it? Or whether the solutions you’ve chosen actually do the job? How do you know where to be flexible and where to stay firm? Or where you can leave it to the people on the ground to decide?
It doesn’t mean the design can’t change, it just means that every change is in service to what everyone knows it has to do.
And as we’re discovering with HS2, waiting until its half-built to decide exactly what it’s meant to do, is an expensive way to fail.
Discipline before you start building makes real Daring possible later.
Ask me how.
