“Understand what people are trying to get done, and you can design offers that fit real needs better.”

VPC stands for Value Proposition Canvas. It is a practical method used to understand how an offer fits the reality of the people it serves. One of its central ideas is Customer Jobs: the tasks, problems, needs, or aspirations a person is trying to address in a specific situation.

Customer Jobs help move the focus away from features and toward usefulness. Instead of asking only, “What can this solution do?”, the better question becomes, “What is the person actually trying to achieve?” This shift often improves relevance, adoption, and satisfaction.

What Customer Jobs means

Customer Jobs are the things a person wants to get done. They can be concrete, emotional, or social:

  • Functional jobs: complete a task, solve a problem, save time, reduce errors, organize work.
  • Emotional jobs: feel confident, reduce stress, gain peace of mind, avoid frustration.
  • Social jobs: appear competent, build credibility, collaborate well, meet expectations from others.

For example, a team member may not simply “need software.” They may be trying to coordinate work across departments, avoid missing deadlines, and feel in control during fast-changing situations. These are different layers of the same context.

Why it matters

When Customer Jobs are clearly identified, it becomes easier to:

  • prioritize what really creates value,
  • remove features that do not help enough,
  • improve messaging by using language closer to user reality,
  • identify hidden adoption barriers,
  • differentiate an offer beyond technical characteristics.

This approach is especially useful when a market is crowded or when teams are unsure why people do not fully adopt a solution that looks strong on paper.

How to think about Customer Jobs

A useful way to explore them is to look at the full situation:

  • Context: When does the need appear? Under what constraints?
  • Trigger: What event creates urgency?
  • Desired progress: What change is the person hoping to achieve?
  • Obstacles: What makes the task difficult today?
  • Success criteria: How does the person judge that the result is good enough?

This helps avoid shallow descriptions such as “the customer wants efficiency.” Efficiency for whom, in what situation, with what trade-offs, and for what purpose? Good analysis makes the answer specific.

Common mistake

A frequent mistake is confusing a solution with the job itself. “Use a dashboard” is not usually the real job. The deeper job may be “detect issues early enough to act before they impact delivery.” The tool is only one possible means.

Another mistake is treating all users as if they had the same priorities. Different roles may share a process but not the same jobs. A manager may seek visibility, while an operational user seeks speed and fewer repetitive actions.

Simple example

Imagine a professional preparing for weekly cross-team meetings. Their jobs may include:

  • collect updates quickly,
  • identify blockers before the meeting,
  • present reliable information,
  • avoid embarrassment caused by outdated data,
  • show that work is under control.

If an offer only provides reporting features but does not reduce preparation effort or improve confidence in the data, it may miss important parts of the real job.

How to identify Customer Jobs

  • Observe real behavior, not only stated preferences.
  • Interview people about specific recent situations.
  • Look for workarounds, manual steps, and repeated frustrations.
  • Separate what people ask for from what they are trying to accomplish.
  • Rank jobs by importance and current satisfaction.

Strong insights often come from concrete stories: what happened, what they tried, what failed, what mattered most, and what outcome they wanted.

Practical benefit

Customer Jobs provide a structured way to understand demand from the user’s point of view. That understanding helps teams make better choices about design, communication, priorities, and improvement. In many cases, the best opportunities come not from adding more, but from aligning better with what people are truly trying to get done.

References