Pragmatic Institute Framework

What it is

Pragmatic Institute (formerly Pragmatic Marketing) codified a market-driven operating model spanning the full arc from understanding the market through building, launching, and supporting a product, organised as a grid of roughly 37 discrete activities across seven category columns (documented as "The Pragmatic Framework" at pragmaticinstitute.com/product/framework/) that run left to right across the product's life. Two of those column-groups fill a genuine gap in this knowledge base and are the sole focus of this entry: Enablement, covering the training curricula, certification, and channel or partner roll-out that a single competitive battlecard or one quarter's sales training session does not fully capture, and Business, covering the ongoing commercial health check of a product or portfolio after launch: revenue and margin performance tracked against the original business case, and a structured pricing health review distinct from a one-off pricing project. The remaining boxes (market definition, market research, competitive landscape, positioning, roadmap, launch sequencing) restate ground the existing 10-Step PMM Process and PMM Lifecycle Management Framework already cover in more depth, and are deliberately excluded here, per CLAUDE.md's rule against duplicate concepts under different names and the build condition attached to this entry.

When to use it

• Sales and channel partners have completed initial enablement training but there is no certification or ongoing curriculum, so skill decays within a quarter and no one can say with confidence who is actually competent to sell the current positioning.
• You are handing enablement to an indirect channel for the first time (resellers, systems integrators, technology partners), and the existing playbooks assume a direct rep with far more product context than a third party will have.
• Leadership asks whether a product or a tier is still commercially healthy 12 to 18 months after launch, and the honest answer is that no one has checked since the launch business case was approved.
• A pricing change or a competitor's move has likely shifted a product's health, but no standing review exists to catch it outside an ad hoc pricing project someone has to actively decide to start.
• You are building or refreshing a PMM operating model and want a checklist for the enablement and business-health boxes specifically, without re-litigating market research or launch process the knowledge base's other frameworks already own.

Ownership

The Head of PMM owns the scorecard itself, deciding which boxes are Yes, Partial, or No and prioritising gaps. Execution splits by group: a sales enablement manager builds and runs the certification and channel curricula in the Enablement boxes, while the Business boxes' revenue-and-margin review is jointly owned with Finance, typically a VP Finance or FP&A lead, since it compares actual results against the original business case. At a solo or founding-PMM stage, one person scores, builds, and reviews every box, looping in a finance counterpart only for the business-case numbers.

How to read it

Read the two box-groups as two ongoing health checks, not two one-off projects.

• Enablement boxes, read across a maturity axis: does a curriculum exist (not just a single onboarding session), is completion tracked and certified with a pass threshold, does the curriculum extend to indirect channels rather than only direct reps, and is content refreshed on a defined cadence rather than left to go stale after the quarter it was built.
• Business boxes, read across a commercial-health axis: is current revenue and margin tracked against the original business case, not just against last quarter's number; is a pricing health review scheduled independently of any active pricing project; and is a product- or portfolio-level win/loss pattern, not a single deal, reviewed on a set cadence. A "yes" across every box in a group signals that group is mature; a "no" identifies exactly which specific box needs attention, rather than a vague sense that "enablement isn't working."

How to apply it

1. Score the current state of each Enablement and Business box using the read above; mark each Yes, Partial, or No with one line of concrete evidence, not an opinion (for example, "certification: No, sales completes a slide-deck read-through with no assessment").
2. Prioritise the Nos and Partials by revenue risk. An uncertified indirect channel actively selling with outdated messaging typically outranks a stale internal FAQ no rep actually opens.
3. For each Enablement gap, build the specific missing layer: a certification quiz with a defined passing threshold, a channel-specific onboarding path shorter and more product-focused than the direct-rep curriculum, and a refresh cadence tied to the same schedule as the competitive battlecard's updates.
4. For each Business gap, stand up the specific missing check: a quarterly revenue-and-margin-versus-business-case review jointly owned by finance and PMM, and a standing, calendar-triggered pricing health review that runs independently of whether an active pricing project exists.
5. Assign an owner and a review cadence to every box that already scored a Yes, not only the gaps; a mature box left unowned tends to quietly decay back to Partial within a year once the person who built it moves on.
6. Report the box-by-box scorecard inside the knowledge base's existing operating cadence (Quarterly PMM Planning), rather than standing it up as a separate, competing planning ritual that asks leadership to attend yet another review meeting.