Article

The Six Critical Skills Every Manager Needs

Founder of ManagerForge33+ years of management experience. 3,000+ interviews across his career, including 1,250+ at Amazon.

Published May 8, 2026·4 min read

Managers need to run useful 1:1s, hire well, set clear goals, guide projects, give timely feedback, and examine their own habits.

The six critical skills every manager needs

Managers need to run useful one-on-ones, hire well, set clear goals, guide projects, give timely feedback, and examine their own habits. Those six skills cover much of the day-to-day work of managing people. Software can help with pieces of each job, but the manager still has to connect the pieces.

The six skills

Run one-on-ones that surface real work. A useful one-on-one is not a status meeting with a different name. It gives the employee room to raise a problem, ask for help, talk through a decision, or share something they would not put in a project update. The manager's job is to listen, ask a question that moves the conversation forward, and follow through on what they agree to do.

Hire with a clear standard. Hiring means deciding what the role needs, asking questions that reveal relevant evidence, comparing candidates against the same expectations, and making a decision with incomplete information. A structured process helps managers avoid letting confidence, likability, or one memorable answer outweigh the evidence.

Set goals people can act on. A useful goal says what should change, how the team will recognize progress, and when they will check the result. "Improve communication" gives someone little to work with. A hypothetical goal might be, "Send the project status and the next decision needed by Thursday afternoon each week." The right goal depends on the job. The point is that both manager and employee can tell what action comes next.

Guide projects without hovering or disappearing. Delegation does not mean walking away. It also does not mean approving every small choice. Agree on the result, the limits, and the check-in points. Then let the person do the work. If the project starts to drift, talk about the work and the support needed before a missed deadline turns into a surprise.

Give feedback while the context is fresh. Feedback works best when it is close to the behavior and specific enough to act on. "You need to be more proactive" is difficult to use. "In yesterday's review, the risk came up after the deadline had moved. Bring that risk to our Monday check-in next time" gives the person something concrete to try. Save formal reviews for looking across a longer period, not for introducing feedback the employee has never heard.

Coach yourself. Managers have habits too. One person may avoid disagreement. Another may take over when a project gets tense. A manager can ask: What did I do when this got uncomfortable? What response did I get from the team? What would I try differently next time? If you only study your employees, you miss half of the management relationship.

Why tools do not do the managing

A company may use one product for hiring, another for performance reviews, a project tracker for delivery, and a shared document for goals. That can be a sensible way to organize work. The problem starts when a manager assumes that keeping each system current means the people are being managed well.

A project tracker can show an overdue task. It cannot tell you whether the owner is waiting on a decision, whether the scope changed, or whether they understand why the work matters. A review form can store feedback. It cannot make the feedback timely or fair. The manager still has to notice the situation, talk with the person, and decide what to do.

The work also crosses these systems. A goal affects a project. A project creates evidence for a one-on-one. Feedback may change how the employee approaches the next goal. If that information lives in separate places, the manager has to carry the connections in their own notes and memory.

That is a real load, but adding another dashboard does not automatically solve it. Start by deciding what each tool is for. Then make the handoffs clear. For example, after a one-on-one, record an agreed action in the project tracker if the team uses that tracker to follow the work. Do not copy every personal conversation into a system other people can read. Respect privacy and keep the employee's trust.

Start with the one-on-one

If you are trying to improve your management, start with the one-on-one. It gives you a regular place to hear what is happening before a review cycle, missed goal, or project escalation forces the conversation.

For your next meeting, ask the employee what is taking more effort than it should. Listen before you suggest a fix. Agree on one next step, name who owns it, and check back at the next meeting. That is a small practice, but it gives you information you can use when you set goals, guide work, and give feedback.

Then choose one of the other five skills to work on. If feedback is the issue, pick one recent example and say what you observed, what effect it had, and what you want to see next time. If project check-ins are the issue, agree on a date and a useful question before the work begins. Keep the change small enough to repeat.

The six skills are not a scorecard to fill out once. They are parts of a job that needs regular attention. Tools can help you remember the work. You still have to do it.

© 2026 David Liloia. Published under ManagerForge.

Become a better manager, starting today.

ManagerForge helps you track 1:1s, spot patterns, and grow as a leader.

Start your free account
ShareLinkedIn

Newsletter

Get new articles in your inbox.

Subscribe to the ManagerForge newsletter. No spam, just practical management content.

Related articles

Article

How to Tell a Good Employee They're Not Ready for Promotion

When a solid performer asks for a promotion they haven't earned yet, the way you handle that conversation will either accelerate their growth or quietly end their ambition. Here's how to get it right.

7 min read

Article

How to Deliver a Negative Performance Review Without Making It Worse

Delivering a "needs improvement" rating is hard enough. Doing it when you weren't direct enough along the way makes it harder. Here's how to walk into that room, say what needs to be said, and leave with a real path forward.

7 min read

Article

A Team Member Isn't Pulling Their Weight

One person on your team is consistently underdelivering and others are starting to notice. Ignoring it punishes your best people, but jumping to conclusions is just as dangerous. Here's how to be fair and firm at the same time.

7 min read

Article

Erratic Leadership Burns Cycle Time

The leader who turns every problem into an emergency thinks they're signaling urgency. Their team experiences something different: constant interruption, wrong fixes under pressure, and a calendar full of half-finished work.

8 min read

Article

Your Pond Size Is Your Resilience

The thing that separates people who adapt from people who freeze isn't intelligence or grit. It's the size of their reference library, and that library is built from variety, not tenure.

8 min read

Article

Adapt or Die

The ability to learn something new and adjust is worth more than any specific skill you'll ever develop. Specific skills go obsolete. Adaptability doesn't.

8 min read