Growing teams rarely fail because they lack ideas.
They fail because they commit too early to a story about the product — and then protect that story longer than the evidence supports it.
Usually the story sounds smart.
It sounds differentiated.
It sounds like something you could put on a homepage.
Then real users show up, and the story quietly stops matching what they do.
Why this keeps happening
When nobody owns product design, the founder or CTO becomes the default keeper of the narrative.
That narrative starts as a hypothesis.
It hardens into a roadmap.
Engineering builds toward it.
Marketing learns to explain it.
And questioning it starts to feel like undoing progress.
The expensive part isn’t changing a headline.
It’s months of work aimed at the wrong job.
What we thought SePoso was
SePoso is a mobile-first Athens bus and trolley app that puts a daily commuter’s arrival on the home screen without repeating the official line-first search.
Early research made a compelling case for a different wedge: trust.
Live times jumped.
Vehicles disappeared.
People felt lied to when the app offered no explanation.
Competitors showed live ETAs, but few made uncertainty honest.
So the early positioning almost wrote itself:
“Help riders know what to believe while they wait.”
Trust states.
Live vs scheduled vs stale.
Never a blank screen with no explanation.
It felt like a product strategy, not a feature list.
That made it dangerous.
What soft launch taught us
Once SePoso was in people’s hands, a different pattern showed up.
Riders already trusted the official telematics enough to act on it.
Their daily pain wasn’t “the data lied.”
It was friction:
- Opening the app every morning
- Hunting the same line and stop again
- Paying too many taps for an answer they already knew they needed
The burning job was closer to:
“See when my bus arrives — without searching for it again.”
That sounds less dramatic than a trust thesis.
It was also more true.
The decision
We killed the sexy positioning.
Not because trust UX is worthless — honesty still matters when live data degrades.
But because leading with trust would have sent the team into the wrong build:
- Labels and states as the hero
- Commute memory as a secondary feature
- Activation work framed around “belief,” not speed to the answer
The corrected north star became simple:
Commute on screen at open.
If a daily commuter opens SePoso and still has to search for the bus they take every day, the product failed — regardless of how elegant the trust labels looked.
What to try next time
Before you defend a positioning statement, ask:
- Would a happy customer say this sentence to a friend? If only the team loves the framing, it’s still a hypothesis.
- Does this story change what we build next month? If flipping the thesis wouldn’t change the roadmap, it isn’t strategy — it’s branding.
- What evidence would force us to abandon it? If nothing could kill it, you’re protecting identity, not learning.
Strong product ownership isn’t loyalty to the first clever narrative.
It’s loyalty to the job users keep proving with their behavior.
If this sounds familiar
If your team is stuck shipping toward a story that no longer matches what users do, that’s usually an ownership problem — not a copy problem.
If this kind of product judgment is what you’re trying to install on your team, we’re happy to talk. And if you know someone else who should be in that conversation, we’d love an intro.
