LEADERSHIP · IDEAS
A company can hire more people and still become less capable. It can also reduce a task through automation while strengthening the judgment needed to serve its customers. The headcount report will show the change in size. It may tell leaders very little about the change in strength.
That distinction matters for Latino founders building a business, executives allocating resources, and professionals deciding what to learn next. A job title describes a position. Capability describes what a person or organization can reliably do.
As Ai changes tasks, we need a better question than “How many employees do we have?” We need to ask what the organization can accomplish, under what conditions, and where that ability is vulnerable.
In Brief
- Headcount measures size; capability shows what the organization can deliver.
- Map enduring strengths, emerging skills, and deliberate backup coverage.
- Use that map to guide development and staffing decisions before adding or removing roles.
Look beyond the job description
Consider an illustrative customer service team introducing an automated response tool. Routine questions become faster to handle. Yet the remaining cases may require more interpretation, empathy, and authority to resolve an exception.
If leaders only count how many routine inquiries the software answers, they can miss the expertise the service still depends on. The team needs people who recognize a flawed response, understand the customer's circumstances, and know when to escalate.
A static job description can conceal that shift. The title stays the same while the contribution changes. Workforce planning should make that change visible.
The useful question is what your people can do together, and whether they can keep doing it when the work changes.
Map three kinds of capability
I think about capability architecture in three layers.
Core capabilities are the enduring strengths that make the business work: interpreting requirements, integrating systems, advising customers, or exercising sound professional judgment. These deserve attention even when they are difficult to count.
Adaptive capabilities help people respond to emerging work. They might include supervising Ai output, understanding data across departments, or coordinating an automated process. Buying a tool does not establish these skills. People need practice, feedback, and clear expectations.
Redundant capabilities provide deliberate overlap. A colleague can complete a critical process when its usual owner is unavailable. Another person understands why a decision was made. This is resilience through cross-training and knowledge transfer, with time allocated to both.
These layers overlap. An experienced employee may hold essential customer knowledge and need support learning a new system. A newer colleague may understand the technology and need supervised opportunities to develop judgment. A useful map reveals where they can learn from one another.
Make the map credible and fair
Start with work the organization must deliver. Identify the capabilities involved, who can demonstrate them, and where coverage depends on one person. Use evidence from completed work and observed practice, alongside the employee's own account of their experience.
A manager's impression alone is a weak foundation. Make the criteria visible, let people correct missing information, and review the map as work evolves. Otherwise, a new system can simply preserve familiar assumptions about who is ready for more responsibility.
For professionals seeking advancement, this creates a concrete development conversation: “Here is the capability I can demonstrate. Here is the assignment that would help me build the next one.” Leaders should make those assignments accessible rather than reserving them for an informal inner circle.
Plan around the gap
Before approving a hire, ask whether the gap requires another person, a different mix of skills, a better process, or development for the team already there. Before removing a role, identify the judgment and relationships that would leave with it.
Headcount still matters for budgets and coverage. A capability map adds the information needed to interpret it. It can reveal both an opportunity to redeploy talent and a risk hidden inside an apparently efficient staffing plan.
The Takeaway
Choose one critical service or process. List its core capabilities, the adaptive skills it now requires, and its backup coverage. Then select one gap to address through training, a supervised assignment, or a staffing change.
Give the action an owner and a review date. Count the people, but also understand the strength they bring—and the strength you need to build next.
About the Author
Jon Orozco, MBA, SHRM-SCP works at the intersection of strategy, people systems, operations, and Ai. He is the creator of the People Systems framework.
Adapted by the author for Latino Professionals Magazine from his article on LinkedIn. Examples in this essay are illustrative.
