Most resource management tools treat people like robots with a list of "tags" (e.g., Python, SQL). But some people are better at client-facing roles, and others prefer deep focus work. If we keep assigning people to tasks they hate just because they have the "skill tag," we lose them to turnover. How are you incorporating "soft skills" and "career goals" into your resource planning?
3 answers
Doesn't this make the job of a Resource Manager much more difficult when they have to juggle personal feelings alongside project deadlines?
We use a 'Shadowing' system where people can spend 10% of their time on a project they are interested in, even if it's not their primary assignment.
This is a fantastic way to handle it. It allows for "low-stakes" exposure to new skills and keeps the team's morale high without impacting the main project.
We’ve started using "Social Contracts" within our Resource Management tool. Every six months, employees update their "Passion Projects" and "Growth Areas." If we have a project that requires a Senior Dev but a Mid-level Dev has expressed a strong desire to learn that specific tech stack, we try to pair them up. We also tag resources with "Work Styles" like "Collaborator" or "Individual Contributor." It takes a bit more effort to manage, but our retention rates have skyrocketed because people feel their assignments are helping them grow, not just checking a box for the PMO.
William, it definitely adds a layer of complexity, but the cost of replacing a skilled employee is much higher than the cost of spending an extra hour on a thoughtful resource plan. We view it as "Sustainable Resource Management." If you burn someone out on a task they hate, you lose that resource entirely. A happy resource is a productive one. We treat employee preference as a "secondary constraint" in our scheduling logic—deadlines come first, but interest is a very close second.