Positioning comes before product

Most founders don't have a product problem.

They have a clarity problem.

And they're trying to solve it by building.

#The default founder mistake

This is how most things get built:

• you have an idea
• you start building
• you add features
• you refine
• you launch

It feels like progress.

Because something exists.

But existence isn't value.

#The expensive truth

If you build before you're clear…

You don't build once.

You build twice.

First:

• you build what you think people need

Then:

• you rebuild what they actually need

And that second phase is where:

• time gets burned
• momentum drops
• reality finally shows up

[!warning] Building without clarity isn't shipping. It's expensive guessing dressed up as progress.

#The moment it became obvious

I learned this the hard way.

At one point, I launched a community app for Male Childcare & Teaching Jobs.

On paper, it made sense.

• a space for connection
• a place for discussion
• something to "bring the community together"

It looked good.

It worked.

It just didn't matter.

#Why it failed

Not because it was badly built.

Not because people didn't care.

But because it wasn't solving a real problem.

It was a nice-to-have.

Not a need-to-have.

People didn't wake up thinking:

"I need a community app for this."

So they didn't use it.

And without usage… it became irrelevant.

#The real problem

The issue wasn't execution.

It was positioning.

Because we didn't start with:

• what's the real friction?
• what's actually broken?
• what do people need?

We started with:

"Let's build this."

And that's where most founders go wrong.

[!tip] Positioning isn't what you say after you build. It's what determines what you should build in the first place.

#What this actually means

There are two ways to approach product:

#What this looked like with BookedIn

BookedIn could have easily stayed as:

"A platform to book CPD speakers, consultants, coaches, and training."

It's logical.

It makes sense.

But it's generic.

And generic doesn't convert.

#The turning point

The shift came when the problem became clearer.

Not:

"How do we help people find speakers?"

But:

"Why does booking CPD feel so manual, messy, and unreliable?"

That question changed everything.

Because now the product wasn't about access. It was about removing friction.

#What changed

Once the positioning became clear:

• features became more focused
• decisions became easier
• priorities became obvious

Because now there was a filter:

"Does this solve the real problem… or is it just another feature?"

#Where founders keep lying to themselves

They say:

• "We'll figure positioning out later"
• "Let's just build and iterate"
• "We'll adjust based on feedback"

What that actually means is:

"We're not clear, but we're building anyway."

#The mistake that costs the most

The most dangerous thing you can do is build the wrong thing well.

Because:

• it looks like progress
• it feels like progress
• it delays the real insight

Until you realise… nobody actually needs it.

#The practical sequence (do this instead)

If you want to avoid rebuilding twice, the order matters.

#The tension

Let's be honest.

Building feels productive.

Thinking feels slow.

So founders default to building.

But skipping clarity doesn't save time. It delays it.

#Why this matters now

We're entering a world where:

• building is easier than ever
• tools are faster than ever
• features can be shipped instantly

Which means it's easier than ever to build the wrong thing. And harder than ever to stand out.

#The shift that changes everything

Most founders don't need to move faster.

They need to think clearer.

Because speed without clarity just gets you to the wrong place faster.

#What I'm learning

You don't build great products by adding more.

You build them by being clear first.

Because positioning doesn't follow the product.

It defines it.