I suspect that one of the major impacts to your roadmap is a budget change. And by change, I mean a reduction in available funds for product development. I suspect a lot of you dealt with this last year as you suffered through many rounds in workforce reduction. I am curious how you handled that.
Picture this scenario, late last fall you reviewed all your feature requests, dusted off the roadmap, the business case is shiny again and it is all aligned with your vision and the corporate vision. With your budget approved, you are ready for 2010. Enter January 2010 and due to slightly missing the Q4 numbers you are now forced to chop $75,000 from your budget. Basically the equivalent of one developer. What do you do?
- Band together with the other product lines and pray for Management to realize that chopping 75k is guaranteed to affect more than 75k in revenue this year?
- Offer to combine forces with another product to share revenue (knowing that you will likely never be able to undo this) in hopes that your new increased revenue will offset your requirement to reduce cost?
- Suck it up, chop the developer and leave the roadmap unchanged and modify the business case (i.e. budget) to reflect the reduced cost but leaving the revenue numbers unchanged? The more with less scenario or in this case same with less.
- Suck it up, chop the developer and scale back the roadmap and business case (i.e. budget) to reflect the reduced cost and revenue numbers?
I am less inclined to do anything that will affect revenue for future years. Depending on how many rounds of workforce reduction you have survived, I am less comfortable selling the same with less scenario. If you are in your first or second round, go with that. Teams generally perform better after the first and second cuts. I am not hopeful they will “see the light” and let you keep a full team in hopes of achieving your revenue targets. Although, this is probably the scenario I start with. Sell the vision, sell the facts and get buy-in on the business case. Failing that, cut, reduce and move forward.
I am hopeful someone will share a situation where a budget cut has affected their roadmap and how they responded.
I meant no offense to any development types by suggesting we cut you, it was a just a random example. We really hate cutting our roadmap in any scenario.
If you enjoyed this post, please leave a comment or subscribe to the feed to receive future updates. You can also follow me on Twitter. Tell other people about this post.
Related Posts:
