The Job Map™: Deconstructing the Workflow to Find Hidden Friction
Type: media
Stage: Stage 1: Problem Proof
Difficulty: advanced
Stop looking at the user — look at the underlying process to find gaps that current software and manual tools miss.
Overview
Most founders research their users. Advanced founders research the workflow. The Job Map™ framework separates the person from the process — and reveals friction points that user interviews almost never surface. At this level, you're not asking 'what's painful?' — you're mapping exactly where in a sequence of steps pain is most expensive and least served.
The 8-step universal process
Every job a user tries to get done follows a natural sequence, regardless of the industry or the tool they're using:
• Define — clarify what needs to happen and what 'done' looks like
• Locate — gather the inputs, information, or resources needed
• Prepare — set up the environment, tools, or conditions
• Confirm — verify everything is in order before proceeding
• Execute — perform the core task
• Monitor — track progress and watch for problems
• Modify — adjust course when something goes wrong
• Conclude — wrap up, document, and hand off
This sequence is universal. A surgeon, a marketer, a warehouse manager, and a freelance designer all follow it — the specifics differ, but the structure doesn't. Mapping your user's job against all eight steps reveals far more than asking them to describe their pain.
Innovation in the margins
The most expensive friction rarely lives in the Execute step — that's where most tools focus. Advanced founders look for friction in the transitions between steps.
The Locate phase (gathering inputs before you can act) is consistently one of the most underserved. Users spend enormous time hunting for information, waiting for approvals, or reformatting data just to get to the actual task. The Modify phase (adjusting when things go wrong) is another — error recovery is almost universally painful and almost universally ignored by software.
Map each step and score it: how difficult is this step today? How long does it take? What breaks here most often? The steps with the highest friction scores are your highest-value targets.
Solution-free mapping
The critical discipline: draw the map without mentioning any specific product, tool, or technology.
This sounds obvious but is extremely difficult in practice. The moment you frame a step as 'they use Notion to...' or 'they export from Excel and then...,' you've anchored the map to existing solutions — and you'll miss the gaps that those solutions have normalized.
The map should describe what the user is trying to accomplish at each step, not how they currently accomplish it. 'Locate: find all client communications related to this project' — not 'they search their inbox and check the Slack channel.'
Why a job-defined market is more stable
Markets defined by technology shift constantly. Markets defined by user demographics narrow over time. Markets defined by a job stay stable for decades — because the underlying need doesn't change even when the tools do.
Fax machines, email, and Slack all served versions of the same job: communicate information to a specific person or group quickly. The job didn't change. The tools did.
If your market is defined by the job — not the current dominant tool — your research stays relevant even as technology evolves around you.
Putting the map to work
After building the Job Map for your target user, do this exercise for each of the 8 steps:
1. How does the user handle this step today?
2. How long does it take?
3. What goes wrong?
4. What would 'perfect' look like at this step?
The gaps between today's reality and the perfect state are your product opportunities, ranked by the friction score you assigned earlier. This is your roadmap — derived directly from the job, not from your assumptions.