PM Role Charter Example: Industrial
Role: Product Manager, NFA-500 controller (Northfield Automation), new to the company Why this example exists: in a matrix organization, plant operations, regional sales, and service all expect something from the PM. The charter defines the interfaces and the escalation.
**Role:** PM, NFA-500 · **Reports to:** Head of Controls Product · **Reviewed:** Nov 13 · **Next:** Feb
1. **Outcome:** Existing NFA-200 sites migrate to the NFA-500 in a shift, not a shutdown, and the launch reaches its business-case win rate through eight partners.
2. **Scope:** In: NFA-500 roadmap, migration path, launch plan, partner enablement content. Out: plant production, regional sales targets, service contracts, certification process.
3. **Decisions owned:** product requirements and trade-offs; the migration path design; launch readiness criteria (drafted by PM); what to publish as proof.
4. **Decisions shared:** launch go/no-go (**COO**); list price and partner margin (**Commercial director**); special engineering commitments (**Engineering director**); NFA-200 end of sale (**GM, Controls**).
5. **Interfaces:**
| With | PM provides | PM gets |
|---|---|---|
| Plant | Forecast, ramp priorities | Capacity, lead times |
| Regional sales | Narrative, battle cards, price file | Deal feedback, objections |
| Service | Migration guide, spares plan input | Field failure data |
| Compliance | Design changes | Certification lead times |
| Partners (via channel manager) | Training content, demo plan | Sell-through, objections |
6. **Success measures:**
| Measure | Type | Influence | Target |
|---|---|---|---|
| Migration quotes issued to NFA-200 sites | Leading | Narrative, partner enablement | `[NEEDS SOURCE]` |
| Units commissioned vs plan | Leading | Readiness, partner training | `[NEEDS SOURCE]` |
| Win rate on migration quotes | Lagging | Product, proof (not price, not coverage) | 35% (business case) |
| Early-life failure rate | Guardrail | Product quality, install guide | Escalate above 2x baseline |
**Gap:** win rate also depends on regional sales coverage, which the PM doesn't control. Head of Controls to confirm with sales leadership.
7. **Not this role:** regional sales management; production scheduling; service contract terms; project management (program office owns).
**Confirmed by:** Head of Controls ☑ · Commercial director ☑ · Plant manager ☐ (to review Dec 2)What to learn from this
- One confirmation is still open (plant manager) and the charter says so, instead of claiming agreement.
- A guardrail sits in the measures, so the PM can't be rewarded for volume that fails in the field.
- The interfaces table is the real content: it says what the PM gives and gets from each function.