Stop competing on features
Startups often compete by shipping more features, faster.
The problem?
Features are easy to copy.
A competitor can replicate your:
dashboard
onboarding flow
AI feature
pricing model
interface pattern
But it's much harder to replicate a deep understanding of why customers choose your product.
This is where Jobs to Be Done (JTBD) becomes a strategic advantage.
What is Jobs to Be Done?
Clayton Christensen's work, particularly Competing Against Luck, popularized Jobs to Be Done as a way to understand what customers are actually trying to accomplish.
A "job" isn't simply a task.
It's the progress someone is trying to make in a specific situation.
People don't necessarily "buy productivity software."
They might be hiring it to:
Feel in control of an increasingly complex workload.
That difference matters.
Because once you understand the job, you can design around the outcome, not just the feature.
Features compete. Jobs differentiate.
Imagine two startups building project-management software.
One asks:
"What features should our competitors have that we don't?"
The other asks:
"Why do teams hire a project-management tool in the first place?"
The first approach creates feature parity.
The second can reveal opportunities around:
reducing coordination overhead
creating confidence
making priorities visible
reducing uncertainty
helping teams make decisions
The product starts competing on user progress, not functionality.
JTBD can change your roadmap
A feature-driven roadmap asks:
What should we build next?
A job-driven roadmap asks:
What is preventing users from making progress?
That changes prioritization.
Instead of adding another feature, the highest-value opportunity might be:
removing friction
simplifying onboarding
improving an existing workflow
connecting two disconnected features
clarifying the product's value
This is where JTBD becomes more than a research method.
It becomes a product strategy lens.
Jobs improve product positioning
Understanding the job can also make marketing clearer.
Compare:
"Project management platform with powerful collaboration features."
with:
"Help your team know what matters next."
The second communicates the progress users are hiring the product to create.
This connection between product and positioning is particularly valuable for startups.
When the job, value proposition, product experience, and marketing narrative tell the same story, the product becomes easier to understand.
Design around the job
JTBD can influence the entire product experience.
Onboarding
Show users how the product helps them achieve their desired outcome.
Information architecture
Organize information around the user's goals rather than internal company structures.
Feature prioritization
Prioritize features that directly support important jobs.
Success metrics
Measure whether users are making progress, not simply whether they interacted with a feature.
UX writing
Explain value in terms of what the user is trying to accomplish.
This is where UX Design and Product Strategy start speaking the same language.
Ask better questions
Instead of asking:
"What features do you want?"
Ask:
What were you trying to accomplish?
What triggered you to look for a solution?
What did you try before?
What made that approach frustrating?
What does success look like?
What would make you switch?
These questions move the conversation from preferences to motivations.
And motivations are harder for competitors to copy.
The strategic advantage
Lenny Rachitsky's Lenny's Podcast frequently explores how startups find product-market fit, understand customers, and build products users actually want.
One recurring principle is simple:
Traction comes from solving a meaningful problem exceptionally well.
JTBD helps teams get closer to that problem.
It can create alignment between:
Customer need → Product strategy → Design → Marketing → Growth
Instead of every team interpreting the customer differently.
Takeaway
Jobs to Be Done isn't simply a user research technique.
It's a way to understand why your product exists in the customer's life.
Features can be copied.
Interfaces can be copied.
Technology can be copied.
But a deep understanding of the user's job can become a much stronger competitive advantage.
The best startup question isn't:
"What should we build next?"
It's:
"What progress are our customers trying to make, and what is stopping them?"
That's where better products begin.
