The Pragmatic Marketing Framework, and how to actually use it

The Pragmatic Marketing Framework, now usually called the Pragmatic Framework, is a one page map of the activities that product management and product marketing teams are responsible for, published by Pragmatic Institute. It is not a process and not a methodology. It is a checklist of jobs arranged from market facing strategy on one side to execution and support on the other, and its purpose is to let a team see which of those jobs it is doing, which it is skipping, and who owns each one. Its central claim is that product decisions should come from evidence gathered in the market rather than from opinions formed inside the building, which is why the framework starts with market problems and not with features.

Teams adopt it for one of two reasons. Either nobody can say who owns pricing, win loss analysis or launch, and the framework settles it. Or the roadmap keeps filling with internal requests, and the framework gives a structured argument for going out and finding what the market actually wants instead.

The principle underneath it

Pragmatic Institute's best known line is that your opinion, although interesting, is irrelevant. Its companion idea is that nothing interesting happens in the office, meaning the information needed to make product decisions is held by buyers, users, prospects who said no, and the people who sell to them. Both lines sound blunt and both are doing the same work: they replace "the loudest voice decides" with "evidence decides".

Taken seriously, that principle produces specific habits:

• Regular conversations with buyers and users, on a schedule, by the people who decide the roadmap.
• Win and loss interviews after deals close, both ways, conducted by someone other than the salesperson.
• Market problems written down as problems, with evidence of who has them and what it costs them, before any solution is discussed.
• A roadmap that can be traced back to recorded market problems rather than to a meeting.

How to read the map

The diagram is a grid of boxes, each one an activity, grouped into sections that run roughly in this order:

• Understanding the market. Market problems, win and loss analysis, distinctive competence, competitive landscape, buyer and user personas, market sizing.
• Choosing where to play. Deciding which problems to solve, the business case, pricing, positioning, and the product portfolio view.
• Planning the work. Roadmap, requirements, release planning, and the handoff into building.
• Taking it to market. Launch planning, messaging, content and campaign programmes, channel and partner work.
• Enabling the people who sell and support. Sales tools, training, competitive guidance, support readiness, documentation.
• Running it afterwards. Performance against the business case, customer retention, sunsetting products that no longer earn their place.

Boxes on the market facing side are strategic and tend to belong to product management or product marketing; boxes further along are tactical and are often shared with marketing, sales enablement and support. Pragmatic Institute revises the diagram periodically and the box names change between versions, so take the current diagram from their own material when you adopt it rather than from a blog post.

Using it in practice: a gap assessment that takes an afternoon

1. Print the current framework and list every activity in a spreadsheet, one row each.
2. For each row, record three things: who does this today, when it last happened, and where the output lives. "Nobody", "never" and "nowhere" are legitimate answers and the useful ones.
3. Mark the rows where the answer is nobody and the rows where two functions both think they own it. Those two lists are your actual problem.
4. Pick three to fix this quarter, starting with the ones that block decisions: market problems, win loss, and pricing ownership are the usual culprits.
5. Assign a single owner per activity, with a cadence and an output. "Product marketing runs six win loss interviews a quarter and publishes a one page summary" is an assignment. "Product marketing owns win loss" is a wish.
6. Review the sheet each quarter. The value is in the repetition, not the first pass.

Where the framework helps most

Situation	What the framework contributes
Product management and product marketing keep colliding	A shared list of activities to split explicitly, instead of negotiating case by case
Roadmap driven by the biggest customer or the loudest executive	A defensible process that puts recorded market problems ahead of requests
Launches that surprise sales and support	Named readiness activities with owners, before the release date
Pricing nobody owns	Pricing as an explicit activity with a home
A new product team with no process	A ready made scope of responsibilities so the team does not invent one from scratch
Hiring product managers	A vocabulary for job descriptions, interviews and development plans

What to pair it with

The framework tells you which activities exist; it leaves the how to you. Teams get the most from it by pairing it with:

• A discovery practice for the market problem work: continuous customer interviews, jobs to be done style problem framing, and a written problem repository.
• A delivery process for the build side, whichever your engineering team already uses. The framework sits comfortably alongside agile delivery because it covers the market facing work rather than the sprint.
• Your own prioritisation method for deciding between validated problems, since the map does not rank them for you.
• Clear written artefacts. A persona document, a market problem record, a positioning statement, a launch plan and a win loss summary. Activities without artefacts quietly stop happening.

Pragmatic Institute sells training and certification built around the framework. The diagram itself is widely available and usable without the courses, which is worth knowing before a budget conversation. The courses add structured practice and a shared vocabulary across a larger team, which is where organisations tend to find the value.

Honest talk about adoption

Be careful with an adoption plan that starts by renaming everybody's job. The framework's value appears when one or two neglected activities start happening on a schedule, with an output somebody reads. Teams that announce a full framework rollout usually produce a wall chart and no behaviour change. Teams that start with six win loss interviews and a written market problem list get asked to do more.

This page covers what the Pragmatic Framework is and how to apply it to product management and product marketing responsibilities. For go to market execution in detail, such as positioning workshops, launch mechanics and campaign planning, each of those is a deeper subject in its own right.

The Pragmatic Marketing Framework questions worth an answer

Is the Pragmatic Marketing Framework the same as the Pragmatic Framework?

Yes. The name shortened when Pragmatic Marketing became Pragmatic Institute, and both names refer to the same one page map of product management and product marketing activities.

Do I need certification to use it?

No. The diagram is published and the gap assessment above can be run by any team. Certification and training add structured practice and a common language across a larger group, which is the usual reason organisations buy it.

Is it compatible with agile?

Yes, and they cover different ground. Agile practices govern how work gets built and released. The framework covers the market facing activities around that, including problem discovery, pricing, positioning, launch and sales readiness, which most delivery frameworks deliberately leave out.

Who owns the framework inside a company?

Usually the head of product or the head of product marketing, with each activity assigned to one named owner. The ownership mapping matters more than the title of the person holding the map.

What is the quickest win from adopting it?

Win and loss interviews, because they are cheap to start, they produce findings within weeks, and the findings change roadmap and messaging decisions immediately. Market problem documentation is a close second.

How does it compare with jobs to be done?

Jobs to be done is a way of framing and investigating customer needs. The framework is a map of organisational responsibilities. Most teams use a needs framing method inside the market problem activities the framework lists, so they fit together rather than compete.

A signal the framework does not list

The Pragmatic Marketing Framework starts from market problems, so it needs honest signals about how buyers describe those problems. Assistants now give one. Ask what product managers use to solve your problem and the reply sums up how the market's sources describe the category.

If that description differs from your positioning, you have found something to work on. Ask three assistants and compare. AI Knows Us runs that comparison and shows which pages shaped each reply.