Contrary to typical agile discovery, projects in high-stakes environments benefit from starting with extremely strict processes and documentation. This establishes a compliant foundation. Flexibility can be introduced later, once core requirements and constraints are fully mastered, rather than starting loose and adding rigor.
Related Insights
Before a major initiative, run a simple thought experiment: what are the best and worst possible news headlines? If the worst-case headline is indefensible from a process, intent, or PR perspective, the risk may be too high. This forces teams to confront potential negative outcomes early.
Counterintuitively, implementing formal processes like documented decision-making (e.g., a RAPID framework) early on increases a startup's velocity. It creates a clear, universally understood system for making decisions, preventing delays caused by ambiguity or passive-aggressive managers.
The conventional wisdom that you must sacrifice one of quality, price, or speed is flawed. High-performance teams reject this trade-off, understanding that improving quality is the primary lever. Higher quality reduces rework and defects, which naturally leads to lower long-term costs and faster delivery, creating a virtuous cycle.
A common mistake when systemizing a business is trying to document every single process, which is inefficient and overwhelming. Instead, identify the few critical processes that are absolutely vital to your value delivery and focus all documentation and systemization efforts on those mission-critical areas first.
In high-stakes fields like medtech, the "fail fast" startup mantra is irresponsible. The goal should be to "learn fast" instead—maximizing learning cycles internally through research and simulation to de-risk products before they have real-world consequences for patient safety.
Frame process management like a portfolio. Processes exist solely to lower 'beta' (volatility and unpredictability). The tradeoff is they also suppress 'alpha' (creativity and outperformance). The key is applying rigid processes where you need low beta (e.g., payroll) while allowing freedom where you need high alpha (e.g., new product discovery).
To make risk management tangible, build specific tests for Value, Usability, Feasibility, and Business Viability directly into each epic. This moves risk assessment from a separate, ignored artifact into the core development workflow, preventing it from becoming a waterfall-style gate.
The 'move fast and break things' mantra is often counterproductive to scalable growth. True innovation and experimentation require a structured framework with clear guardrails, standards, and measurable outcomes. Governance enables scale; chaos prevents it.
Instead of arguing for more time, product leaders should get stakeholder buy-in on a standardized decision-making process. The depth and rigor of each step can then be adjusted based on available time, from a two-day workshop to an eight-month study, without skipping agreed-upon stages.
The misconception that discovery slows down delivery is dangerous. Like stretching before a race prevents injury, proper, time-boxed discovery prevents building the wrong thing. This avoids costly code rewrites and iterative launches that miss the mark, ultimately speeding up the delivery of a successful product.
