What Actually Matters When You Are Managing People
Most organisations compile a list of managerial skills and call it a day. They print it out, put it on an intranet page, and expect it to change how anyone does their job. It doesn't. The list itself is inert. What separates a functional management framework from wall decoration is whether people actually use it when something goes wrong. I found this out the hard way about four years ago when we were promoting someone internally into a team lead role. Their technical skills were solid. Their listed competencies checked every box on our Organisational Managerial Skills List. The team fell apart within six weeks because nobody had asked how they handled conflict escalation in practice. Start by identifying the decisions managers in your organisation actually make. Not the theoretical decisions from a textbook. The real ones. Who do they hire? Who do they fire? How do they allocate budget when there isn't enough for everyone? How do they handle a senior person who underperforms but has institutional knowledge that would be expensive to lose? Map the skill requirements to those decisions, not to job titles. A team lead managing ten people has different skill demands than a director managing eight team leads. Your list should reflect that distinction. Then separate skills into three categories: core, specialized, and developmental. Core skills are things every manager needs regardless of level or function. Communication, basic financial literacy, feedback delivery, conflict resolution, prioritisation. Specialized skills depend on the domain. A engineering manager needs technical estimation ability. A marketing manager needs campaign analytics fluency. Developmental skills are what high performers need to reach the next level. Strategic thinking, cross-functional influence, change management. This structure prevents you from requiring things that aren't actually necessary for the role at hand.
I have seen lists that required strategic thinking competencies for first-time managers. That is backwards. First-time managers need operational competence and people management basics. Strategic thinking comes after they have proven they can run a team without constant intervention. Putting it on the initial list creates a filtering problem where you either skip it or hire people who talk a good game but have never managed anyone before.
The Skills That Actually Move the Needle
Communication is always on every list, which is why it is almost never useful on its own. Specify what kind of communication matters. Status reporting to stakeholders is one skill. Delivering difficult feedback to a direct report is another. Presenting a project setback to leadership without sounding defensive is a third. These are different competencies with different training paths. Grouping them all under "communication" makes it impossible to assess or develop any of them properly. Delegation is another skill that gets listed without definition. Most managers struggle with it because they confuse delegation with dumping work. Real delegation involves handing off decision-making authority alongside the task. If someone is executing but cannot make any choices about how to do it, you have not delegated. You have assigned. I spent three months fixing a pattern where my own managers were assigning instead of delegating because our review process only checked whether tasks got completed, not whether the people doing them were developing judgment. Changing the review criteria to require evidence of decision-making handoffs fixed it in about eight weeks. Prioritisation is where most management frameworks break down. Managers are expected to prioritise constantly but are rarely given clear criteria for what takes priority over what. Is it revenue impact? Customer satisfaction? Risk mitigation? Employee development? The answer changes depending on the situation, and good managers know which framework to apply when. Train people to recognise which logic applies in different contexts rather than giving them a single prioritisation matrix and expecting it to work everywhere.
Get the Full Details
Assessment Methods That Don't Waste Time
Self-assessment alone is unreliable. Managers consistently rate themselves higher than their peers and direct reports do. I stopped relying on self-assessments for promotion decisions about five years ago. They are useful for identifying blind spots when someone rates themselves low in areas where others rate them high, but on their own they add noise rather than signal. 360-degree feedback is better but only if you protect anonymity properly and give respondents specific behavioural anchors rather than vague rating scales. "Rate their communication skills from 1 to 5" produces garbage data. "Rate whether this person provides feedback in a way that helps you improve versus making you defensive" produces something you can actually act on. The difference between those two questions is the difference between a useful assessment and paperwork. Work samples and simulated scenarios are the most predictive method I have encountered. Give managers a realistic problem and watch how they handle it. A budget reallocation request from another department. A performance conversation with an employee who claims unfair treatment. A project that is two weeks behind schedule with a key stakeholder breathing down your neck. These reveal more about actual capability than any questionnaire. The downside is that designing good simulations takes time and requires people who understand both management theory and your specific organisational context. A poorly designed scenario tests test-taking ability rather than management ability.
Common Pitfalls in Management Skill Frameworks
The biggest mistake I see is treating management skills as fixed traits rather than learnable competencies. This creates a hiring problem where organisations look for managers who already have all the skills instead of building people who can develop them. It also creates a development problem where managers who don't naturally score high on certain competencies are written off rather than given targeted support. Leadership potential and current capability are not the same thing, and conflating them wastes good people. A second pitfall is creating lists that are too long. I have seen frameworks with forty or fifty competencies. Nobody can focus on improving forty things at once. Pick the twelve to fifteen that matter most for your organisation's current stage and strategy. Everything else can wait. A focused list gets used. A comprehensive list gets ignored after the initial rollout excitement fades. There is also the cultural assumption problem. Many widely cited management skill frameworks originate from American corporate culture and assume individual autonomy, direct communication, and competitive performance metrics. These assumptions don't translate cleanly into organisations with different cultural norms around hierarchy, consensus-building, or relationship-first working styles. Adapt the framework to your context rather than forcing your context to fit the framework.
Keeping the Framework Alive
Lists rot if nobody updates them. I review our managerial skills framework annually and remove anything that hasn't shown practical relevance in the past year while adding whatever new capabilities the business environment has made necessary. During the pandemic shift to remote work, we added digital facilitation and async communication management to the core skills list. Those didn't exist on our framework two years earlier. They became table stakes within six months of widespread remote adoption. Link the skills list to actual decisions. When someone is considered for promotion, reference specific competencies from the list and provide evidence against each one. When someone is placed on a development plan, tie it to gaps in the framework rather than generic improvement goals. When you hire for a management role, use the list to structure interview questions. This creates consistency and makes the framework feel relevant to the people who need to use it most. The framework is never complete. Management is a moving target because the work itself changes. What worked for managing a team of twenty people in a stable industry won't necessarily work for managing a team of five through a restructuring. Treat the Organisational Managerial Skills List as a working document that gets revised whenever the organisation's management challenges shift in a meaningful way, not as a static artifact that gets created once and filed away.
