Our company is debating whether to create a centralized Resource Management Office (RMO) or keep the power with the functional managers. Team leads argue they know their people best, but the PMO argues they see the "big picture" of company priorities. Which model have you seen work best for a mid-sized software company that is scaling rapidly?
3 answers
For a scaling company, a "Hybrid" model is usually the most successful. We found that a purely centralized RMO felt too much like "people as widgets," and a decentralized model led to resource hoarding. Now, our PMO handles the high-level capacity planning and strategic prioritization, while the Team Leads handle the specific task assignments and day-to-day management. The RMO provides the data and the "source of truth" for availability, but the Team Leads have the final say on who is the best fit for a specific technical challenge. This balance maintains culture while ensuring efficiency.
How do you handle conflicts when two different Team Leads both claim they need the same "Star Performer" for their respective projects?
Centralization is the only way to ensure that "bench time" is minimized across the whole organization, especially during quiet periods.
I agree. Without a central view, you end up with one team working weekends while another team has nothing to do. Visibility is key.
Christopher, that is where the RMO earns its keep. When a conflict arises, we look at the Project Tiering. If Project A is a "must-win" for a major client and Project B is an internal optimization, Project A gets the resource. If both are equal, we look at "Resource Sharing"—can the person spend 50% on each for two weeks? If no agreement is reached, it gets escalated to the VP of Delivery. Having a neutral RMO makes these conversations data-driven rather than emotional.