Decreasing Product Development Lead Time

Product development team collaborating around a table

A global pharmaceutical manufacturer was losing time and money in its own product development process, not because the science was failing but because the team structure around it had broken down. A multi-layered organisation of core teams and functional sub-teams had created overlapping responsibilities, priority conflicts, and decisions made in isolation. Product teams found out about changes after the fact; functional departments executed without consulting the people accountable for the product. The result was rework, frustration, and slipping lead times.

Working with a cross-functional group drawn from across the organisation, we went back to first principles: what does a Product Team Lead actually need to own, and where does that responsibility end? We redesigned the team structure to eliminate the overlaps, clarified the role of the Portfolio Governance Committee in resolving cross-functional conflicts, and wrote a new playbook that gave teams a shared language for how good collaboration looks in practice. The new structure was simpler, with shorter, cleaner lines of accountability.

Lead times came down, and the organisation found itself able to make and execute development decisions with considerably less friction. What the engagement reinforced for us is that the Product Team Lead role is one of the most underinvested positions in drug development. These individuals must be leaders, negotiators, and advocates all at once. Placing the right people there — and then supporting them — is as important as any structural fix.

All perspectives Start a conversation