Level 2 - Product Maturity Driven Development (PMDD)
Maturity as a Test, Not a Verdict
Product Maturity Driven Development (PMDD) applies the core discipline of Test‑Driven Development (TDD) and Behavior‑Driven Development (BDD) to enterprise productization and governance.
First define what “good” looks like. Allow it to fail. Then evolve the system until it passes.
In PMDD, productization maturity criteria are the tests, and the enterprise platform is the system under test.
The Core Analogy (TDD → PMDD)
| TDD / BDD | Productization‑Driven Development |
|---|---|
| Write failing tests | Define productization maturity criteria (DPCH / AIPCH) |
| System initially fails | Enterprise/platform initially scores low or zero |
| Failures expose missing code | Failures expose missing platform capabilities |
| Implement code to pass tests | Build platform services to satisfy maturity criteria |
| Tests become regression guardrails | Maturity checks become continuous governance signals |
A 0% maturity score is not a failure of teams, on contrary, it is a truthful diagnosis of system readiness.
Why Start with a Failing Maturity Test?
Traditional governance typically asks:
“Why aren’t domains compliant?”
PMDD reframes the question:
“What capabilities does the enterprise not yet provide?”
When maturity is measured honestly:
- Missing APIs
- Missing policy engines
- Missing observability
- Missing cost attribution
…are exposed as platform gaps, not domain shortcomings.
This inversion is intentional.
The Role of the Product Maturity Evidence Product
Under PMDD, the Product Maturity Evidence Product acts as the test runner:
- It defines input ports (signals) that represent required platform capabilities
- It evaluates maturity criteria (DPCH / AIPCH)
- It produces a clear, explainable score and gap analysis
Crucially, the product can exist before all input signals exist.
If an input port has no backing service yet, the result is simple:
That characteristic scores 0%.
This is not an error, it is the test failing as designed.
Failing Scores as a Platform Backlog Generator
Each failing maturity characteristic directly maps to a capability gap:
- DPCH09 fails → Policy‑as‑Code capability missing
- DPCH08 fails → Observability & SLO platform incomplete
- DPCH14 fails → FinOps / chargeback not available
- AIPCH17 fails → Retraining pipelines not implemented
In this way, maturity assessment becomes:
- A diagnostic tool
- A prioritization mechanism
- A justification for platform investment
Rather than debating what to build next, the enterprise can simply ask:
“Which maturity tests are still failing?”
Why This Avoids Governance Anti‑Patterns
PMDD explicitly avoids common failure modes:
- ❌ Checklist‑driven compliance theater
- ❌ One‑off audits with no follow‑through
- ❌ Subjective maturity opinions
- ❌ Governance as policing
Instead it delivers:
- ✅ Objective, system‑derived signals
- ✅ Slow‑moving, meaningful indicators
- ✅ Clear ownership of capability gaps
- ✅ Governance as enablement
Snapshot‑Based by Design
Productization maturity is a structural property, not an operational metric.
Under PMDD:
- Maturity is evaluated as periodic snapshots (e.g. weekly)
- Scores are stable enough to support trend analysis
- Only true regressions (e.g. capability removal) warrant alerts
This preserves signal quality and avoids real‑time noise.
Manual First, Automated by Design
PMDD supports a natural evolution:
-
Phase 0 - Manual Self‑Assessment Domains use lightweight maturity checklists to establish a baseline.
-
Phase 1 - Assisted Assessment Evidence links point to emerging platform APIs.
-
Phase 2 - Automated Evaluation Maturity Evidence Product consumes authoritative signals.
-
Phase 3 - Continuous Governance Snapshots drive dashboards, alerts, and policy gates.
At every stage, the same maturity criteria apply.
Strategic Outcome
By adopting Productization‑Driven Development:
- Governance criteria are explicit before platforms are built
- Platform services converge toward a shared definition of done
- Domains are shielded from premature or unfair expectations
- Maturity evolves through capability pull, not compliance push
In short:
PMDD turns maturity from a judgement into a design instrument.
Aligned with: Base Product Specification (BPS 0.1) · Data Mesh Principles · HDIP Governance Model