The Best Product Tools Act As a Lens, Not a Framework

Most teams adopt JTBD as a framework. They learn the steps. They run the interviews. They produce the artifacts. They follow the process.

And then they wonder why the decisions didn't change.

The problem is what happens when you treat any tool as a framework — a set of steps to follow, artifacts to produce, and ceremonies to perform. Frameworks are comfortable. They have a beginning, a middle, and an end. You can point to the output and say "we did the thing."

But the best product tools don't work that way. They work as lenses — ways of seeing that change what you notice, which is what changes what you do. A framework tells you what to do next regardless of context. A lens makes it hard to un-see something that was always there.

When you treat JTBD as a framework, you get process. When you treat it as a lens, you get better decisions.

What framework mode looks like

Framework mode is seductive because it's manageable. You can put it on a slide. You can tie it to a training plan. You can audit adherence. You can tell leadership "we've adopted JTBD" and point to artifacts as proof.

In framework mode, JTBD looks like a big organizational commitment. "We will adopt JTBD across the organization." "All epics must be written as job stories." "We will train everyone on the jobs interview method." You can do all of that and still ship a roadmap that's basically stakeholder requests with jobs stickers on top.

You get teams that run usability tests because "we should be doing more research now," not because anyone has a real question. Teams that fill out canvases because "we're a JTBD organization now," not because anyone is confused about the job. Teams that add jobs language to stories because "that's the format," not because it clarifies what success looks like.

On paper, you adopted the framework. In reality, nothing important changed. The same ideas win. The same bets get made. The same blind spots persist. The tools didn't change what you noticed or how you argued. They just added overhead.

What lens mode looks like

A good lens is modest in scope and ruthless in effect.

A jobs lens doesn't tell you "now you must write job stories." It makes it hard to un-see that three tickets in the backlog are all the same job, and two others are jobs you probably shouldn't be doing at all.

A four forces lens which looks at the four things that shape every switching decision – frustration with the current way, attraction to something new, comfort of existing habits, and anxiety about change — doesn't tell you "run this exercise every quarter." It makes you notice that you're optimizing onboarding for curiosity when the only people who stick around are desperate.

A JTBDUX lens — which evaluates user experiences through a set of questions tied to the job, like whether the experience speaks the user's language, shows progress, and reduces anxiety at the moments it peaks — doesn't tell you "always use pattern X." It makes you uneasy when a flow clearly serves "browse" while your retention depends on "execute under pressure."

Lenses change the questions that feel natural to ask. And then the decisions change even if the mechanics of your process don't.

In lens mode, JTBD is much simpler and much harder to ignore:

• Before you green-light an epic, someone has to be able to answer: for what job, in what situation, for whom, is this actually important?
• Before you call retention "good," you have to be able to say: rehired for which job, under what conditions?
• Before you redesign a flow, you have to ask: are we designing for browsing or execution? Hands-on control or hands-off delegation? Relief or exploration?

No new process. No new artifacts. Just a small set of questions that, if taken seriously, make certain moves feel obviously wrong.

The distinction shows up in what happens when the team gathers around real work.

A team using JTBD as a framework presents a roadmap where every item has a job label. "This serves the coordination job." "This serves the visibility job." The labels are there. The process was followed.

But if you ask "did the jobs research change what's on this roadmap, or did the roadmap stay the same and get labeled after the fact?" — the room goes silent. The answer is usually the second one. The jobs work produced vocabulary, not decisions.

A team using JTBD as a lens might not have a single job label on the roadmap. But when someone proposes a feature, the first question is "How does this help them make progress in the Job they hired us to do?" When retention dips, the first question is "Which job did we stop serving well?" When a competitor ships something, the question isn't "Should we match it?" but "Does their version serve a job our users are hiring us for?"

The lens team might never say the word "JTBD" in a meeting. The decisions are still shaped by it because the lens changes what they notice, which changes what they argue about, which changes what gets built. The framework team says the word constantly. The decisions aren't shaped by it at all.

How to stay in lens mode

If you don't want your tools to calcify into frameworks, a few habits help.

Stop saying "we're a JTBD org." The moment a tool becomes an identity, the social pressure shifts from "is this helping us see better?" to "are we being faithful to it?"

Insist on a before/after test. After any exercise — a jobs workshop, a four forces analysis, a research sprint — ask one question: "What would we have done without this lens, and what are we going to do differently now?" If you can't answer that in a sentence, you didn't use the tool. You performed it.

Let lenses lose. Some decisions are genuinely constraint-driven or supply-side. Some problems really are about performance, cost, or compliance more than about underlying jobs. Forcing everything through a single lens is just a different kind of blindness. A lens earns its place by being useful, not by being mandatory.

The question to ask of any product tool — JTBD, JTBDUX, Agile, OKRs, whatever — isn't "are we using the framework?" It's: what does this make us see that we were previously blind to? What questions feel natural now that didn't before? What kinds of bad decisions get harder to make?

If you don't have a clear answer, you don't need another framework. You need a sharper lens — or you need to put the old one down.