Strong engineering teams still miss milestones.
Many medical device companies have excellent engineers, experienced quality groups, and significant investment in development programs. Yet milestones still slip.
This pattern appears across organizations of every size. Programs run late despite capable teams and serious effort. When this happens, the first instinct is often to question execution: Was the engineering discipline strong enough? Did the team work hard enough? Were the plans realistic?
In many cases, those are not the real issues.
Milestone slips are rarely caused by weak engineering. They usually reflect weaknesses in the development environment surrounding the team.
Development programs succeed or struggle largely because of the conditions in which the work takes place. Leadership decisions, organizational expectations, and the way teams interact all shape how problems surface and how quickly decisions are made.
In practice, milestone slips usually reflect weaknesses in three areas of development:
- Program Governance
- Design Challenge
- Cross-Functional Alignment
When any of these areas is weak, even highly capable engineering teams can struggle to deliver predictable milestone outcomes.
Program Governance
Program governance shapes the environment in which development work occurs.
Milestones are not achieved because of a single review meeting or stage gate. They are the result of many sound decisions made throughout development. When decisions are delayed, avoided, or poorly coordinated, programs gradually lose momentum and milestone outcomes become unpredictable.
Program leaders influence development progress by establishing the conditions that allow teams to make timely decisions and surface problems early. This includes maintaining alignment across functions, ensuring that difficult issues are addressed rather than deferred, and protecting the time and resources needed for engineers to explore and challenge the design.
Strong governance also reinforces accountability. Decisions must have clear owners, and teams must understand how and when issues will be resolved. When ownership is unclear or escalation paths are weak, problems linger while work continues around them.
Effective program governance does not depend on formal decision events alone. Instead, it creates an environment in which decisions are made continuously as the design evolves and new information emerges.
When leadership maintains that decision momentum, development work advances steadily and milestone achievement becomes far more predictable.
Design Challenge
Many milestone slips occur because the design was never thoroughly challenged early in development. The program simply did not create the time, resources, and expectations required to expose its weaknesses.
Design challenge refers to the environment that allows engineers to question assumptions, explore alternatives, and stress-test a design before formal verification begins.
In healthy development environments, engineers are expected to probe the design. They investigate uncertainties, experiment with alternatives, and test whether the system behaves as expected under different conditions. Lab access, prototypes, and experimental resources allow these questions to be explored quickly and informally.
Just as important is the cultural environment surrounding the work. Teams must feel comfortable exposing problems early. Discovering that an idea does not work is not a failure; it is a valuable outcome that allows the program to adjust while changes are still manageable.
Without this environment, designs often appear stable until later stages of development. Integration testing or verification activities then reveal issues that were present all along but had not yet been exposed. At that point, the cost of change is significantly higher and milestone schedules are far more difficult to recover.
Effective design challenge does not require unlimited exploration. In fact, research consistently shows that bounded time and resource constraints often improve creativity and problem solving. What matters is that programs intentionally create space for engineers to probe the design and surface weaknesses early.
Early discovery of problems is one of the most valuable outcomes a development program can achieve.
Cross-Functional Alignment
Medical device development depends on coordination among engineering, quality, regulatory, manufacturing, and clinical perspectives.
Each of these disciplines brings important knowledge about how a device must perform, how it will be produced, and how it will ultimately reach the market. When these perspectives are integrated early, they improve the quality of design decisions and reduce the likelihood of later surprises.
When they are not integrated early, problems tend to appear much later in development.
Manufacturing constraints may emerge after prototypes are finalized. Verification strategies may require revision following quality review. Regulatory expectations may become clearer only after the design has already matured. Each of these situations forces teams to revisit decisions that were previously assumed to be settled.
Late discovery of these issues often leads to redesign, expanded testing, and delayed milestone achievement.
Strong programs involve these stakeholders early enough to influence design decisions rather than reviewing them after the fact. Early collaboration improves both the quality and the practicality of development decisions, allowing teams to move forward with greater confidence.
Milestones are not achieved in stage-gate meetings.
They are achieved through the decisions teams make every day during development.
Strong Teams Require Strong Development Environments
When technically capable teams consistently miss milestones, organizations often assume the problem lies with execution. Engineering discipline is questioned, schedules are tightened, and teams are asked to work harder.
In many cases, the real issue lies elsewhere.
Milestones are the visible outcome of the development environment surrounding the team. That environment includes program governance, the degree to which the design is challenged early, and the level of cross-functional alignment across the organization.
When these elements function well, capable teams surface problems early, make decisions quickly, and advance programs with far fewer surprises.
Technically strong teams rarely need to be replaced. They need a development environment designed to support them.
Free Development Governance Assessment
If your development programs consistently miss milestones, the issue may not be engineering capability. It may be the environment in which your teams are operating.
A65 works with leadership teams to evaluate program governance, design challenge practices, and cross-functional alignment. A focused assessment often reveals where decisions stall, where designs are not being challenged early enough, and where late-stage surprises are being introduced.
These gaps are rarely obvious from within the program, but they are often the primary drivers of delay.
If you would like an objective assessment of your current development environment, we welcome the conversation.
Email: sdonnigan@a65consulting.com
Or schedule your review online
References
Cooper, R. G. (2019). Winning at New Products: Creating Value Through Innovation (5th ed.). Basic Books.
Clark, K. B., & Wheelwright, S. C. (1992). Revolutionizing Product Development: Quantum Leaps in Speed, Efficiency, and Quality. Free Press.
Edmondson, A. (2019). The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth. Wiley.
International Organization for Standardization. (2019). ISO 14971: Medical Devices — Application of Risk Management to Medical Devices.
Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute.
Amabile, T. M., & Pratt, M. G. (2016). The dynamic componential model of creativity and innovation in organizations. Research in Organizational Behavior, 36, 157–183.Stokes, P. D. (2005). Creativity from Constraints: The Psychology of Breakthrough. Springer Publishing.