Defining and Scoping a Regulation‑Ready MVP for a Next‑Gen Medical Practice Software

The Client: Medical Practice Software

Our client is a Berlin-based Healthtech scale-up, whose product is Medical Practice Software (MPS). They’ve created a cloud‑native Praxisverwaltungssystem (PVS) to replace the 30‑year‑old desktop tools still dominating German outpatient care.

‍

The Mission: Interim Product Manager

When we came aboard, Product, Tech, and Regulatory teams were staring at:

• 300+ scattered feature ideas in Airtable, Jira, Figma, and Slack
• Unclear ownership of Gematik certification and FHIR standards
• Conflicting assumptions about how patients, MFAs, and doctors actually move through a day
• A fast‑moving engineering cadence that left no time for “big‑picture” alignment

Our mandate was clear: define a launch‑ready MVP, translate regulations into code‑ready specs, and reboot discovery—without slowing a single sprint.

‍

Our Main Quest: From Feature Swamp to Crystal‑Clear MVP

We started by consolidating every requirement into one Notion database, mapping each item to a single Job‑To‑Be‑Done. Through a series of focused workshops—with founders, engineering leads, and regulatory experts—we whittled the list down to 74 must‑have features and stamped them with unambiguous acceptance criteria.

This new “single source of truth” lets every squad plan confidently, while a high‑level roadmap links the MVP to strategic goals and compliance gates.

‍

Explore and Conquer: Solved for the Client

Customer & Workflow Discovery

We audited legacy research, then launched a structured program of four surveys and four interview scripts targeting GPs, MFAs, and patients. Early conversations highlighted pain around check‑in, waiting‑room visibility, and data migration—fuel for the next backlog refinement.

Mapping the Patient‑MFA‑Doctor Flow

On‑site practice visits, plus interviews with internal SMEs, fed into a comprehensive Miro journey map. The visual revealed hidden hand‑offs (e.g., MFAs juggling room assignments) that became new acceptance criteria and UI checkpoints.

Competitive Intelligence

A 19‑vendor benchmark laid bare which “table-stakes” features MPS must match and where modern UX could differentiate. Pricing and module packaging insight also informed go‑to‑market planning.

Regulatory Deep Dive

Concise playbooks distilled Gematik’s roadmap, KBV‑specific FHIR deviations, and hardware/KIM connector obligations. We then baked 42 compliance criteria directly into the feature spec, turning a looming risk into a set of test cases.

‍

Discovery Mini Missions: Our Side Quests

• Pre‑built Components – Spike testing calendar and chat SDKs saved an estimated six sprints of custom build time.
• Handover Doc – A link‑packed handover page ensures future hires never hunt for information.
• Knowledge‑Sharing Sessions – Short, targeted trainings seeded user‑centric flow thinking across Design and QA.

‍

Mission Achievements: Delivered Outcomes

💡 MVP Scope Locked: 74 features, each tied to JTBD, owner, and acceptance criteria, signed by all stakeholders.

💡 Regulatory Confidence: Gematik and FHIR tasks are now concrete, testable, and traceable.

💡 Customer‑Insight Engine Live: Surveys deployed, interviews booked, evidence already shaping sprints.

💡 Competitive Positioning Sharpened: Data‑backed gaps and differentiators inform product and pricing.