What Should Banks and Financial Services Firms Put on the Roadmap First? A Jobs-to-Be-Done Approach

Direct answer: Prioritize the roadmap item that resolves the highest-frequency, highest-friction job your customers are already trying to get done — not the feature your competitors just shipped. In banking and financial services, that usually means the point where a customer "hires" your product to make money move, reduce anxiety about a decision, or prove compliance. Jobs to Be Done (JTBD) forces you to rank roadmap candidates by the progress a customer is trying to make, which is a far more stable prioritization signal than feature parity or internal politics.

(Disclosure: this article is published by Percision, a strategic intelligence platform. We use JTBD as one method among many, and we'll be honest below about when you don't need us to run it.)

Why "feature parity" is the wrong roadmap default in financial services

Banks and financial firms tend to build roadmaps from three weak inputs: what the competitor across the street launched, what the loudest internal stakeholder wants, and what the regulator just mandated. The first two produce sprawling roadmaps that satisfy no one deeply. The third is non-negotiable but shouldn't crowd out everything else.

Jobs to Be Done reframes the question. A customer doesn't "want a mobile check-deposit feature." They have a job: "When I receive a paper check on a weekend, I want to deposit it without visiting a branch, so I can access the funds before Monday and stop worrying about losing it." The feature is just one way to serve that job. Once you see the job clearly, you can evaluate whether your roadmap candidate actually advances it — or just adds surface area.

This matters more in financial services than in most industries because the "jobs" are emotionally loaded (fear of loss, fear of missing out, fear of getting audited) and functionally regulated. The right roadmap item usually reduces both functional friction and emotional anxiety at the same moment.

A concrete JTBD walkthrough for a bank or fintech roadmap

Here's how to run it on a real prioritization decision. Suppose you're a commercial bank deciding between: (a) a treasury cash-flow forecasting tool, (b) faster onboarding for new business accounts, or (c) an embedded payments API.

Step 1 — Write the jobs as job statements. Use the structure: When [situation], I want to [motivation], so I can [expected outcome].

• "When I'm a new business trying to open an account, I want to be operational the same day, so I can start collecting revenue immediately."
• "When I'm a CFO managing a lumpy cash position, I want to see next 90 days of liquidity, so I can decide whether to draw on my line."

Step 2 — Interview for the switch, not the wish list. Ask customers about the last time they hired or fired a solution for this job. What triggered the switch? What did they try first? What made them abandon it? These stories reveal the real friction, which surveys and feature-request logs hide.

Step 3 — Score each job on frequency, severity, and current satisfaction. A job that occurs weekly, causes real pain, and is poorly served today outranks a rare job served adequately by a workaround. In our example, if onboarding friction is causing lost accounts at the top of the funnel, it likely outranks a forecasting tool that only power users touch monthly.

Step 4 — Map the job to a competitive gap. Good roadmap candidates sit where the job is important, poorly satisfied, and aligned with a capability you can defend (deposits, risk data, licensing).

What "good" looks like: a ranked shortlist of 3–5 roadmap candidates, each tied to a specific job statement, each with evidence from switch interviews, and each scored on importance and satisfaction. That single artifact usually ends the "whose feature wins" argument in the room.

Where Percision fits — and where it doesn't

Once you have the raw job research, you still have to turn it into a defensible, board-ready roadmap: which item first, what it's worth, what it costs to delay, and how it changes your financial trajectory.

That's the translation layer Percision is built for. You feed in your business context, and the platform runs it through structured reasoning steps across specialist models — applying JTBD alongside financial frameworks — to produce a prioritized recommendation, scenario analysis, and a board-ready deck with the underlying model exported to Excel. For a financial-services team choosing between roadmap bets, that means pairing the qualitative job ranking with a DCF or scenario view of what each bet does to revenue and risk. It's a co-pilot: it structures the analysis in minutes, but your leadership team makes the call.

When you don't need Percision: If you've already run strong switch interviews and the winner is obvious, don't over-engineer it — build it. If your decision is a small feature tweak, a spreadsheet and a product manager are enough. And if the roadmap question is deeply entangled with regulatory interpretation or a bespoke risk model, a specialist consultant or your compliance counsel should lead, with any tool playing a supporting role. JTBD tells you what job to serve; it doesn't replace domain judgment on how to serve it legally.

The honest framing: Percision compresses the analysis-and-packaging timeline from weeks to minutes and keeps an audit trail. It does not replace customer conversations, and it does not remove accountability from the humans signing off.

FAQ

Q: How many customer interviews do we need before ranking the roadmap? There's no magic number, but switch stories tend to saturate quickly — you often hear the same triggers and workarounds after 8–12 focused conversations per job. Stop when new interviews stop surprising you.

Q: Can JTBD handle regulatory-driven roadmap items? Partly. Mandatory compliance items sit outside prioritization — you must do them. JTBD helps you decide the order and design of everything else, and sometimes reveals that a compliance requirement also serves a real customer job (e.g., fraud alerts reducing anxiety).

Q: Does Percision run the customer interviews for us? No. Percision structures and prioritizes the analysis and produces the board deck and financial model. The primary research — talking to customers about the jobs — is still your team's work, and it's the part that makes the output trustworthy.

Want to pressure-test your roadmap ranking with structured JTBD and financial scenario analysis? You can explore how it works at percision.app.