Member-only story
A Lightweight Product Roadmapping Process
Works with your team’s natural rhythm, and give the organization what it needs to succeed
Building roadmaps is hard. Keeping them up to date is even harder.
Any business with multiple cross-functional teams and growing discipline functions understand this.
As organizational units expand, cultures and processes morph to the needs of the smaller units. This works until the complexity of dependencies creeps in.
Dependencies sneak up on you like a crouching tiger. Just when you think you have things figured out and running smoothly, the dependency tiger pounces and your release gets delayed or worse your features don’t function in front of the customer.
Keeping up with all product work across teams and avoiding the jaws of the tiger takes artful navigation. Teams communicate and work at different cadences. You can try to execute standardize frameworks like SAFe or DAD, but the reality is that synchronizing value delivery alignment perfectly causes undue stress on your product teams.
In general, the larger the organization, the more structure required, but it is possible to implement a lightweight structure, even in large organizations.
