Thinking
Leading an established business and creating one from nothing are two very different games. The experience that made you successful in one can quietly make you dangerous in the other.
Martin Dubreuil
August 26, 2026
Over the past few months, I've watched several experienced corporate leaders step into entrepreneurship.
Smart people.
Successful people.
People who have managed teams, budgets, departments and complicated businesses.
And then something strange happens.
They struggle.
Not because they've suddenly become less intelligent.
Not because they lack discipline.
And certainly not because twenty years of experience somehow disappeared the moment they left the office.
They struggle because they are playing a different game.
Leading a business is not the same as creating one.
And the experience that made you very good at the first can occasionally make you surprisingly bad at the second.
Let's get this out of the way before somebody from LinkedIn arrives carrying a pitchfork.
Building a successful corporate career is difficult.
You learn how to make decisions.
Manage people.
Navigate complexity.
Communicate.
Negotiate.
Lead.
Deal with pressure.
Allocate resources.
Understand politics.
Deliver results when several departments appear professionally committed to preventing them.
Those are real capabilities.
They don't disappear when you become an entrepreneur.
Many of them become enormous advantages.
The mistake is assuming the environment in which you learned to use those capabilities still exists.
It doesn't.
Even in a difficult corporate role, you usually arrive inside something that already exists.
There are customers.
Revenue.
Processes.
Systems.
Technology.
People.
Budgets.
Suppliers.
Policies.
Brand recognition.
Institutional knowledge.
Somebody knows how invoices get paid.
Somebody knows where customers come from.
Somebody knows what the company sells.
Hopefully.
You may be responsible for improving that machine.
Perhaps transforming it.
Perhaps fixing a dysfunctional piece of it.
Perhaps growing it significantly.
But there is a machine.
Entrepreneurship can begin with considerably less.
Sometimes it begins with:
"I have an idea."
Wonderful.
Now we have an assumption.
You don't inherit customers.
You have to discover them.
You don't inherit demand.
You have to find out whether it exists.
You don't inherit distribution.
You have to create it.
You don't inherit systems.
You build them when they're actually needed.
You don't have Finance, Marketing, IT, Legal and HR waiting three floors down.
You may have you.
And perhaps ChatGPT.
Congratulations on the new department.
This isn't simply a smaller version of corporate life.
The work itself changes.
Established organizations spend enormous amounts of energy improving things that already exist.
How do we increase margin?
Reduce cost?
Improve productivity?
Grow market share?
Increase conversion?
Make operations more efficient?
Improve the customer experience?
These are optimization questions.
Important ones.
But entrepreneurship often begins before optimization is useful.
Before asking how to improve the machine, you need to discover whether there should be a machine at all.
Who is the customer?
What do they care about?
What are they doing today?
Is there a sufficiently important problem?
Will they pay?
Can you reach them?
Can the economics work?
Those are discovery questions.
And discovery requires a very different relationship with uncertainty.
This is where successful people can get into trouble.
Experience creates patterns.
That's usually useful.
You've seen situations before.
You recognize problems.
You make decisions faster.
You know what tends to work.
But pattern recognition has a weakness.
Sometimes you recognize a pattern that isn't actually there.
A former executive sees a market and thinks:
I understand this industry.
Maybe.
But do you understand this customer?
This buying behaviour?
This price point?
This distribution model?
This tiny business with almost no resources?
This market in 2026 rather than the one you operated in ten years ago?
Experience should give you better questions.
It becomes dangerous when it gives you answers before reality has had a chance to speak.
This one can sting.
Inside a corporation, your title carries context.
Vice President.
Managing Director.
Chief Something Officer.
People answer your email.
Meetings appear.
Resources move.
Suppliers return calls.
Someone prepares the PowerPoint.
Then you leave.
Suddenly you're trying to convince your first customer to buy something from a company they've never heard of.
Nobody particularly cares what your old title was.
The market is wonderfully disrespectful that way.
It asks a simpler question:
Can you create value for me?
That's humbling.
It's also useful.
This may be the hardest transition.
The higher you've climbed, the less familiar it can feel to not know.
But early entrepreneurship is full of not knowing.
You don't know whether the idea works.
You don't know exactly who buys.
You don't know which message lands.
You don't know the right price.
You don't know which channel works.
You don't know whether Customer #1 represents a market or simply has unusually poor judgment.
You test.
Learn.
Adjust.
Then test again.
In corporate environments, uncertainty is often something we're expected to reduce before acting.
In entrepreneurship, you frequently act specifically because that's how uncertainty gets reduced.
Corporate careers can train people to avoid visible failure.
Understandably.
Failure can affect budgets, bonuses, promotions and reputations.
Entrepreneurship needs a slightly different interpretation.
A failed test can be useful.
A customer saying no can be useful.
A pricing assumption collapsing can be useful.
Discovering that your target market doesn't care can be extremely useful.
Preferably before you've spent $150,000 building for them.
Failure becomes dangerous when you learn nothing from it.
Evidence that changes your direction isn't failure.
It's information.
The answer isn't to pretend your corporate career taught you nothing.
That would be ridiculous.
Bring the strategic thinking.
Bring the leadership.
Bring the commercial judgment.
Bring the communication skills.
Bring the resilience.
Bring the ability to see systems and dependencies.
Bring your understanding of people.
Bring your network.
Bring your scars.
Just don't bring every assumption about how businesses are supposed to operate.
A startup doesn't need a miniature corporate structure.
It needs enough structure to discover what works.
This is why, before architecting a business, I increasingly want to understand the person building it.
What are you actually good at?
What did your corporate environment provide that you no longer have?
Where does your confidence come from?
Where might experience be creating blind spots?
What kind of business fits your life?
Your resources?
Your financial needs?
Your tolerance for uncertainty?
Your ambition?
Your personality?
Because we can design a perfectly reasonable business that is completely wrong for the person expected to run it.
That isn't good architecture.
The entrepreneur is part of the system.
I call this Founder Architecture. And before building a business, I want to understand whether the founder has actually created structural room for one to exist. If you've been saying you'll start when things calm down, I'd suggest reading about how your current life is likely designed to prevent exactly that.
Once we understand the builder, we can start working on what should be built.
Not by immediately ordering a logo.
Not by creating seventeen social accounts.
Not by hiring people because that's what a "real company" apparently does.
We work backwards.
What are you trying to create?
For whom?
What needs to be true?
What evidence do we have?
What needs testing?
How does money move?
How do customers arrive?
What capabilities actually need to exist?
What should happen first?
What should deliberately wait?
That's Business Architecture in an entrepreneurial context. And this is where understanding what a Business Architect actually does becomes useful.
It isn't about making the startup look like a company.
It's about discovering and designing the business that deserves to become one.
Your relationship with it might be.
Twenty years of corporate experience can be an extraordinary entrepreneurial advantage.
Or a very expensive collection of assumptions.
The difference is whether you're willing to examine which lessons still apply.
Corporate success teaches you how to operate inside systems.
Entrepreneurship asks you to discover what system should exist.
One is largely about operating and improving a machine.
The other begins with an empty floor and a question.
What the hell should we build here?
That's why the transition can feel harder than expected.
You're not inexperienced.
You're experienced in a different game.
Keep the experience.
Lose the certainty.
Become curious again.
And before you start building the enterprise, architect the entrepreneur who's going to have to make it work.
Share
Related Thinking
Most aspiring entrepreneurs don't have a motivation problem. They have a structural problem.
Most entrepreneurs don't build businesses in the wrong direction because they're lazy. It's because they start building before they've worked out what needs to exist.
How a Business Architect works from entrepreneur and idea through architecture and execution.
I've written about a lot of what goes into starting and building a business. The answer may already be here. If it isn't, challenge accepted.