Skills & Self-Development Operational excellence is a system. People run it. Your skills are the engine.

Promotions used to follow tenure. Now they follow demonstrated skill. Hiring and internal mobility are going skills-first — what you can show you can do matters more than how long you have done it, and learning agility (how fast you pick up the next thing) is valued over years in a legacy system. That is good news: it means you can move faster than your years suggest, if you build the right skills on purpose.

Skills come in two kinds, and you need both:

• Hard skills are teachable and testable — Excel and Power Query, SAP, SQL, accounting, a specific process. You can name them, learn them, and prove them.
• Soft skills — increasingly called power skills — are how you operate: communication, problem-solving, collaboration, influence, judgment. Harder to measure, harder to fake, and harder to automate.

Here is the shift that matters: as AI takes over routine hard tasks, the price of the human skills goes up, not down. In AI-enabled roles, most of the top skills employers ask for are human ones. The technical skill gets you in the door; the power skills decide how far you go.

You cannot develop what you have not named. Two honest questions do most of the work: what does my role actually reward, and where am I against that?

Map what the role rewards. Read your role profile or the job description for the level above as a skills list, not a wish list. Watch your top performers — what do the people who get promoted out of this role do that you do not? And ask your manager the direct question: what separates a strong performer at the next level from an average one?

Find where you stand. Rate yourself honestly against that list. Then use two signals most people ignore:

• Energy. The tasks that energise you usually sit on top of a strength. The ones that drain you usually sit on a weakness. Notice the pattern over a couple of weeks.
• Outside feedback. Your own read is biased. Ask one person you trust where they think you are strongest and where you hold yourself back. One honest answer beats ten self-ratings.

Keep it simple — a short table is enough to start: the skill, whether your role rewards it, your honest level, and whether it gives or drains energy. That single page tells you where to aim before you spend a minute developing anything.

The old advice was to hunt down your weaknesses and grind on them. The better-evidenced model is the opposite. Decades of research point the same way: amplify the strengths you already have toward excellent, hold most weaknesses at good enough, and only hard-fix a weakness if it is actively derailing you.

The reason is simple. Effort spent on a weakness moves you from poor to average; it rarely reaches good, and almost never reaches exceptional. The same effort spent on a genuine strength can take you to a level few people in your function reach — and strengths-based development raises performance by roughly 8 to 18 percent on average, while people who use their strengths daily are far more engaged.

One caveat keeps this honest: if a weakness is a genuine flaw that derails you — the thing that makes people not want to work with you — fix that to safe. Everything else, manage to good-enough and move on.

Breadth keeps you useful. Depth makes you valuable. The professionals who stand out are T-shaped: a broad base of competence across the whole operation, plus one or two deep spikes where they are genuinely excellent. The base means you can work across the process and talk to anyone. The spike means there is a reason they call you.

Two things make the spike pay off:

• Depth over scatter. Being a little better at ten things is forgettable. Being clearly the best in your team at one or two is a reputation.
• Skill stacking. A rare combination beats a single skill. "Good with process" is common. "Good with process and can build the automation and can present it to leadership" is rare — and that combination is yours to build.

The fastest accelerator is not a course. It is proximity to people who are better than you. Actively seek out role models in your job, and find a mentor.

• Use the program if there is one. If your organization runs a mentoring program, use it — it removes the awkwardness of asking.
• If there is not, ask anyway. Most leaders are pleased to be asked. Ask someone you look up to, politely, with a clear proposal: how often you would meet, how long, and what you are hoping to get from it. Keep the commitment light so it is easy to say yes to.
• Own it, and come prepared. Take it seriously every time. Bring something to work on. You own this relationship — a mentor gives you their time, not your homework.
• Do not limit yourself to one. You can have two at once, and swap over time as your focus changes. Ideally, at least one is not your direct boss — you want a view from outside your own chain.
• Learn from peers — and from people more junior than you. Anyone can be excellent at one thing. Drop the pride and the hierarchy: the best person to learn a tool from might sit a level below you.

Done well, this compounds. Good mentors share what they know, inspire you to aim higher, and — when you have earned it — advocate for you in the rooms you are not in yet.