SVPG Product Operating Model — Crash Course | Novant Health Interview Prep | 2026-05-21
Mental Model: SVPG (Silicon Valley Product Group) is Marty Cagan's framework for building products the way the best tech companies do. The core insight: most organizations build features because someone asked for them (feature factories). SVPG-aligned teams own outcomes, not deliverables. They discover what to build AND deliver it — the team is empowered to make both decisions. Novant adopted this model for their Institute for Innovation and AI product teams. When the JD says "the AI Tech Lead owns the How, Execution of the How, and By When" — that is SVPG language for the Principal Engineer role on an empowered product team.
The 4 Big Risks (SVPG)
| Risk | Question It Answers |
|---|
| Value | Will users actually use this? |
| Viability | Can the business support this? |
| Feasibility | Can we actually build it? |
| Usability | Can users figure it out? |
The AI Tech Lead owns Feasibility — and informs Value and Usability from the technical side.
Key SVPG Roles
| Role | Owns |
|---|
| Product Manager | Value + Viability |
| Product Designer | Usability |
| Tech Lead / Architect | Feasibility — IS this role |
| Empowered Team | All 4 risks together |
In SVPG, the tech lead is NOT an order-taker. They co-discover the solution with PM and Designer.
Discovery vs. Delivery
| Mode | What Happens |
|---|
| Discovery | Rapid experiments to reduce risk before building. Prototypes, spikes, stakeholder tests. |
| Delivery | Engineering the solution at production quality. The tech lead guides this. |
Bishop's framing: "At Amgen I owned both discovery (400 SAFe stories) and delivery (MVP to enterprise program). That is exactly the SVPG tech lead model."
Key SVPG Vocabulary (Use These)
- Empowered team — Team owns the outcome, not just the sprint backlog
- Outcome-driven — Success = business result, not feature shipped
- Continuous discovery — Weekly touchpoints with customers/users to reduce uncertainty
- Product discovery — The phase where you test feasibility before committing to build
- Technical debt — SVPG expects tech leads to surface and manage it proactively
- North Star metric — The single metric the team is trying to move
- Feature factory — Anti-pattern. Outputs features on command. No outcome ownership.
- OKRs — Objectives and Key Results; SVPG teams are typically OKR-driven
- Tech lead as architect — Defines the architecture; coaches the team; removes blockers
How Bishop's Background Maps to SVPG
| SVPG Concept | Bishop Evidence |
|---|
| Feasibility ownership | Amgen: took GenAI from pilot → enterprise-approved. Owned the "can we build this?" answer. |
| Continuous discovery | Evernorth: 147 Epic reports — that was systematic discovery of what was blocking AI |
| Outcome-driven | Wolters Kluwer: 300+ hospitals, 96.3% accuracy — measured by outcome not features |
| Cross-functional partnership | Amgen: Regulatory Medical Writers + Engineering + PM; Street Grace: BBDO + clinicians |
| Technical leadership | NewsRx: sole architect and delivery owner of production GenAI platform |
Interview Language — Say These Naturally
"In a product operating model, the tech lead's job is to make sure discovery and delivery are never decoupled — I've worked that way at Amgen and Evernorth."
"The feasibility risk is mine to own. My value to the PM and Designer is knowing what's possible before we commit resources to delivery."
"I've operated in outcome-driven teams — at Wolters Kluwer success was measured by clinical outcomes at 300+ hospitals, not by features shipped."