Jobs-to-Be-Done: The Core Unit of Customer Understanding

The most durable way to understand customers is not to profile them — it is to understand what they are trying to accomplish. Jobs-to-Be-Done is the theoretical framework that makes this shift precise, and in journey management, it does something that personas and demographic segments cannot: it keeps the work inclusive, behavior-oriented, and grounded in intent rather than identity.

What a "Job" Actually Is

A job is the underlying goal a person is trying to achieve in a given context. Not who they are, but what they are trying to do.

"I need to buy new outdoor gear before a long hiking trip" is a job. "I need to assess whether my current gear is sufficient before committing to a route" is a job. "I need to understand the differences between two similar products without reading a technical spec sheet" is a job.

These jobs can be performed by a twenty-five-year-old first-time hiker and a fifty-year-old experienced alpine climber. The jobs are the same. The identities are different. Designing for the job produces an experience that works for both. Designing for the demographic produces an experience that favors one and frustrates the other.

"Jobs describe intent, not identity."

Why Jobs Beat Personas for Journey Mapping

The standard critique of personas is that they fossilize into caricatures — that the "beginner user" becomes a stereotype, that the demographic description starts carrying assumptions the research never supported. This is real and worth taking seriously.

But the deeper problem with personas in journey management is structural. A persona is a profile — it describes a type of person. A customer journey map needs to describe a sequence of needs, pains, and gains across a lifecycle. These two things do not map cleanly onto each other.

When a team tries to build a persona-driven journey map, they face a choice: either create separate maps for each persona (which multiplies the maintenance burden and creates inconsistencies) or create a composite map that averages across personas (which flattens the differences that made the personas useful in the first place).

Jobs solve this problem by anchoring each insight to what the customer is trying to accomplish rather than who the customer is. The map stays unified. Each insight is tagged with the relevant job or role, which provides enough segmentation for design purposes without requiring separate maps.

Jobs in B2B and B2C

The application differs slightly between contexts.

In B2C, the principle that good services should work for everyone applies directly. Designing for a job — "I need to make confident decisions about product quality without relying on in-store inspection" — produces a more inclusive solution than designing for a persona ("the research-driven millennial buyer"). The former accommodates anyone who has that job to do, regardless of age, income, or digital proficiency.

In B2B, a job is often shared across multiple roles. The job "validate that this solution meets our compliance requirements" might be performed by a legal counsel, a procurement officer, or a chief information security officer depending on the organization. Designing for the job rather than any of the specific titles produces an experience that serves all three.

B2B journey maps organized around jobs-to-be-done tend to be significantly more durable than those organized around role titles — because organizational structures change more often than the underlying jobs that people in those organizations need to accomplish.

Tagging for Jobs in Practice

The practical implementation is simple: tag each insight with the job it is connected to. On a collaboration board, this might look like #first-time-gear-buyer, #return-customer, #sustainability-focused, #B2B-procurement.

These tags allow teams to see which jobs cluster where in the journey without fragmenting the map into separate persona lanes. A product manager can filter by tag to focus on a specific audience. A designer can scan the full map to see which jobs appear most frequently. Leadership can assess which jobs are most poorly served.

The resulting map is unified, searchable, and dimensionally rich — without the maintenance burden of multiple parallel maps or the distortion risk of fixed persona profiles.