The problem
The product is a cross-platform technology that lets developers share code across mobile and backend instead of rebuilding the same logic per platform. It's free, so success isn't revenue — it's developer satisfaction.
The team was stuck building everything for everyone. The backlog was enormous and nothing could be prioritized, because there was no principle for deciding what mattered. Against established cross-platform competitors, the differentiator was fuzzy. And classic demographic segmentation — company type, team size — produced no usable signal. Knowing a team's headcount said nothing about what they needed the tool to do.
Two jobs that reordered the roadmap
Reframing around the job to be done surfaced two distinct, concrete reasons developers reached for the technology:
- Eliminate bugs in complex shared business logic. When the same intricate rules — think the pricing math in a ride-hailing app — had to behave identically on every platform, reimplementing them separately was a bug factory. Sharing that code once removed an entire class of errors.
- Keep a highly customized, fully native-looking UI on each platform. A second group cared most about platform-perfect interfaces and did not want a shared UI layer that flattened the native feel.
These weren't slogans — they were opposite needs that demanded opposite priorities, and naming them finally gave the team a way to choose.
What changed
- They stopped building "a product for everyone." The two jobs became the lens for every roadmap call.
- The backlog and marketing were rebuilt around the segments' actual tasks, leading with the outcome each job cared about rather than a flat feature list.
- Sequencing followed the jobs. Work on a shared UI framework was deliberately deferred so the team could first win the large segment that explicitly didn't want one — capturing real users before spreading effort thin.
The results
- The technology climbed into the top three in its category among cross-platform options — up from a fuzzy, undifferentiated position a few years earlier.
- Developer satisfaction rose about 20%, the metric that actually defines success for a free tool, as the roadmap finally matched what developers were trying to get done.