Skills Open the Door. Competence Keeps You in the Room.

A young analyst once sent me his portfolio. Eleven dashboards, and I will admit they were good. Clean layouts, sensible colours, no clutter. He had clearly put in the hours.

So I asked him one question. I said, suppose a company tells you sales have fallen in three of their eleven regions and they want to understand why before the board meets on Thursday. What is the first thing you do?

He said he would build a dashboard.

That answer has stayed with me, because it was not a stupid answer. It was an honest one. It was the only answer his training had given him. Nobody had ever asked him to decide what question was worth answering. Nobody had asked him what data would settle it, or which of the assumptions in the brief were quietly wrong. He had been taught the tool, thoroughly, and then sent out to face a world that does not hand you problems in the shape of a tutorial.

I meet a version of him almost every month. And nearly every time, the person is convinced that his problem is that he needs to learn one more tool.

Three words that get treated as one

Part of what makes this so hard to see is that we use three different words as though they mean the same thing. Skills, competencies and experience. They do not mean the same thing, and confusing them is one of the quietest reasons careers stall.

A skill is narrow, and that is the point

A skill is a specific, observable ability used to perform a defined task. Writing a VLOOKUP. Building a bar chart. Writing a Python loop. Skills are narrow by design, and that narrowness is exactly what makes them teachable in a short course and testable in a short assessment. It is also what makes them easy to display, which is why so much of our professional energy flows towards them.

A competency is broader

A competency is what emerges when a skill is combined with real knowledge, sound judgement and appropriate workplace behaviour, and then applied to a live problem under real conditions. Scholars have argued about the precise definition for decades, but the reviews keep landing in the same place.

Competence is not a list of things you can do. It is the capacity to do the right thing, in the right way, in a situation nobody prepared you for.

Experience is the most misunderstood of the three

Experience is not the number of years on a CV. It is accumulated practical exposure that slowly builds contextual understanding and, eventually, judgement. It is why a senior colleague can glance at a report for ten seconds and say, “This number is wrong,” before she has checked anything at all. She has seen that shape of wrongness before.

Put them side by side and the relationship becomes clear. Skills help you get opportunities. Competence helps you perform consistently. Experience develops the judgement that no classroom can hand you. You cannot substitute a large quantity of one for the total absence of another, although a great many people are quietly trying.

The comfortable illusion

Because skills are the easiest of the three to acquire and the easiest to show, we optimise for them. Certificates are visible. Judgement is not. So people accumulate certificates and wait for the market to respond, and when it does not, they assume the problem is that they need another certificate.

The research keeps arriving at the same conclusion from very different directions. Students and graduates consistently rate their own technical ability higher than employers rate it, while underrating precisely the things employers complain about: communication, self-management, business awareness, the ability to take a vague problem and return with a sensible answer. A large European study comparing what students value with what companies value found the gap running in exactly that direction, with the vast majority of respondents reporting that the emphasis on these broader capabilities had risen sharply over the past decade.

The gap shows up closer to home too

A study of real estate employers across Lagos and Abuja found that employers rated qualities such as responsibility, listening, negotiation and work ethic very highly, then reported significant gaps in exactly those areas among the graduates they had hired. The graduates, for their part, believed they were doing fine.

That mismatch between self-assessment and employer assessment is not a Nigerian failing. It is a human one. But it costs Nigerian graduates jobs, and it is worth naming.

What I keep seeing in the training room

I have spent years now working as a data professional and as an accredited training consultant, and I will say this plainly, without any pleasure in saying it. Most aspiring analysts spend a great deal of time learning software and very little time learning how to think.

Many can recreate a dashboard. Many can follow a tutorial from start to finish without an error. Many can clean a dataset beautifully, provided somebody else has already decided what clean means for that dataset.

Then a real problem lands, and they discover that no part of it looks like a lesson. Nobody tells them what question is worth answering, as opposed to the question that was asked. Nobody tells them which data would actually settle the matter, and which data would merely look as though it had. Nobody tells them which analytical approach fits, which assumption in the brief is wrong, or how to say any of this to a busy executive in a way that produces a decision rather than a nod.

Not one item on that list is a software skill. This is where people who are genuinely good with tools freeze, and it is why I have stopped believing them when they tell me their problem is Python.

Their problem is not a shortage of software knowledge. It is a shortage of competence.

Competence is a compound, not an ingredient

Competence combines technical skill, domain knowledge, judgement, behaviour, professional attitude and repeated application. Remove any one of them and the others lose most of their value.

A skill supported by knowledge becomes useful

An analyst who understands how retail margins actually work will notice that a record revenue month came with collapsing profitability, because she knows where to look. An analyst who knows only the tool will build a beautiful chart of the record revenue and send it to the board.

A skill supported by good behaviour becomes trusted

The colleague who flags her own error before anyone else finds it, who asks a clarifying question on day one instead of guessing for three days, who says, “I do not know yet, but here is how I will find out,” is the one who gets handed the work that matters. Not because she is the most technically gifted person in the room. Because her work can be relied upon, and reliability is rarer than talent.

Behaviour is not the soft part of the job

Organisations do not hire people simply because they can operate a tool. They hire people who can apply what they know responsibly, work well with others, communicate clearly, keep learning, handle themselves under pressure, and leave the workplace better than they met it. The skill gets you the interview. The behaviour decides whether anybody wants to work with you again.

The behavioural competencies that matter are not mysterious. Communication. Emotional intelligence. Adaptability. Initiative. Collaboration. Accountability. Professionalism. Curiosity. Resilience. A real willingness to learn. What is interesting is how much evidence has quietly built up behind them while we were dismissing them as the soft stuff.

The evidence on emotional intelligence

Emotional intelligence, to take the most studied example, has a consistent positive relationship with job performance across large bodies of research, and it contributes something beyond cognitive ability and personality. The effect is moderate rather than overwhelming, and researchers still argue about how best to measure it. But the honest summary is simple enough. How you handle yourself and other people at work is not decoration. It shows up in performance data.

Are behavioural competencies harder to develop?

You often hear it said, quite confidently, that behavioural competencies are simply harder to develop than technical ones. The evidence does not support anything that firm. What it does support is more useful anyway. These capabilities can be developed, but they respond poorly to the way we usually try to teach them. They grow through practice, feedback, reflection and time spent inside real situations, not through a slide on the importance of teamwork. That is a different problem from being untrainable, and it calls for a different response.

What most technical training gets wrong

I say this with respect for people doing honest work in this space, and as someone who is part of it. A great many technical training programmes are, in practice, software operation courses wearing the clothes of professional education.

Learners are taught where to click. They are taught formulas, dashboards and syntax. What they are rarely taught is how to frame a problem, how to reason under uncertainty, how to structure a decision, or how to recognise when the answer they have produced is nonsense.

Does research support this concern?

Broadly, yes. The clearest and most repeated finding in the critical thinking literature is that thinking does not develop as a happy by-product of learning content. Instruction improves it, but only when the thinking itself is an explicit objective rather than an implicit hope. Left implicit, it largely does not happen.

The statistics education literature says something very similar, having found again and again that teaching centred on procedures and computation produces students who can calculate without being able to reason. And in the design literature, framing, which is the discipline of working out what the problem actually is before rushing to solve it, is treated as the core professional act. It is also the thing no tutorial has ever touched.

The good news is that the alternative works

When learners are made to wrestle with genuine, ill-defined problems instead of following prepared steps, their thinking measurably improves. Problem-based approaches have a solid and repeated effect on critical thinking in higher education. So we are not short of knowledge about what works. We are short of appetite, because teaching people where to click is faster, cheaper and produces happier feedback forms.

The tool is not the engine

This is the idea I most want you to leave with.

The software is not the engine. Knowledge is the engine. Problem-solving frameworks are the engine. The tool is only the gearbox. It transmits power. It has never produced any.

Statistical reasoning, computational thinking, systems thinking, design thinking, critical thinking. These generate the power.

A professional who knows how to break a problem into parts, spot the pattern, isolate the variables and test an assumption can pick up an unfamiliar tool in a few weeks, because the tool is only a new way of expressing thinking she already possesses. That is why some people drift from Excel to SQL to Python to whatever arrives next without any drama. Nothing fundamental changed for them.

Someone who knows only the tool stands on far more fragile ground. Change the software, change the industry, change the shape of the question, and the ground goes. They were never standing on the tool. They were standing in the tutorial.

Think of it as the difference between operating a steering wheel and knowing how to drive. Anyone can be shown how to hold a steering wheel in ten minutes. Driving across Third Mainland Bridge at six in the evening in the rain, with a danfo drifting into your lane and a pothole you cannot see until you are in it, is not a steering problem. It is a judgement problem. Professional expertise lives in the same place. Not in the operation, but in the judgement that decides what to do and when.

What experience actually gives you

We should be equally honest about experience, because it is oversold in job adverts and undersold in real life.

Years on a CV are a surprisingly weak signal

A large body of research on pre-hire experience found that the very measures employers rely on when screening candidates, such as years of experience or number of similar roles held, are poor predictors of how someone will actually perform. Broader work on experience and performance finds a real but modest relationship overall, and it is strongest when experience is measured by what a person has genuinely done rather than how long they were present.

That finding cuts in both directions, which is why I like it. If you are young and anxious that you have no experience, the market’s fixation on years is weaker than you fear. If you have fifteen years and assume they speak for themselves, they may be saying less than you think.

What experience really produces is tacit knowledge

This is the practical, hard-to-articulate know-how that separates people who have been present from people who have actually learnt. Research on professional learning shows that most of the knowledge governing skilled work is picked up informally, on the job, and that it operates through fast, intuitive reading of situations rather than conscious rule-following. Related work on practical intelligence found that this kind of knowledge predicts real-world performance and is largely independent of what formal tests measure. It is why two people can spend the same three years in the same role and come out as entirely different professionals.

The difference between them is almost always reflection. Experience that is never examined is just time passing.

Where to start

None of this is cause for despair. It is a matter of sequence. Here is what I would say to anyone who asked.

• Keep learning the tools, but stop treating them as the destination. Learn the software well enough to be dangerous, then move your energy to the thinking behind it.
• Learn one domain properly. Analytics without business understanding is typing. Choose an industry and learn how it makes money, where its costs hide, and what keeps its managers awake at night.
• Practise on problems, not on datasets. A tidy file with a stated objective teaches you almost nothing about competence. Go and find a messy, badly defined problem, ideally a real one belonging to a small business, an association or an NGO, and carry it from confusion all the way to a recommendation.
• Get explicit about your thinking. Decomposition, abstraction, hypothesis testing, problem framing, structured decision-making. Study them as deliberately as you once studied formulas. Name the framework you are using, and notice when it fails you.
• Treat communication as a technical skill, because it is one. An analysis nobody understands is an analysis nobody uses.
• Ask for the feedback you do not want, then act on it visibly. This single habit will do more for your behavioural competence than any course.
• Keep a decision journal. Write down what you decided, why, what you assumed and what you expected to happen. Return to it a month later. This is how time becomes judgement instead of simply evaporating.
• Build a portfolio of problems solved rather than tools used. “I built a dashboard” is a skill claim. “Stock-outs were costing them roughly two million naira a month, I traced it to a reordering rule that had never been updated, and here is what changed” is a competence claim. Only one of them gets you hired.

The question worth sitting with

Employers are not, in the end, paying for familiarity with tools. They are paying for problems to go away. The tools are simply the least interesting part of how that happens.

So by all means, finish the course and post the certificate. You earned it, and the discipline it took is real. But then sit with the harder question, because it is the one that decides what happens next.

If somebody handed you a problem tomorrow with no instructions, no template and no tutorial, would you know where to begin?

If the answer is not yet, that is not a failure. It is simply the next thing to learn. And unlike the software, it is the part that will still be worth something in ten years.

References

Abrami, P. C., Bernard, R. M., Borokhovski, E., Wade, A., Surkes, M. A., Tamim, R., & Zhang, D. (2008). Instructional interventions affecting critical thinking skills and dispositions: A stage 1 meta-analysis. Review of Educational Research, 78(4), 1102–1134. https://doi.org/10.3102/0034654308326084

Ayodele, T. O., Oladokun, T. T., & Kajimo-Shakantu, K. (2020). Employability skills of real estate graduates in Nigeria: A skill gap analysis. Journal of Facilities Management, 18(3), 297–323. https://doi.org/10.1108/JFM-04-2020-0027

Dorst, K. (2011). The core of ‘design thinking’ and its application. Design Studies, 32(6), 521–532. https://doi.org/10.1016/j.destud.2011.07.006

Eraut, M. (2000). Non-formal learning and tacit knowledge in professional work. British Journal of Educational Psychology, 70(1), 113–136. https://doi.org/10.1348/000709900158001

Liu, Y., & Pásztor, A. (2022). Effects of problem-based learning instructional intervention on critical thinking in higher education: A meta-analysis. Thinking Skills and Creativity, 45, 101069. https://doi.org/10.1016/j.tsc.2022.101069

O’Boyle, E. H., Jr., Humphrey, R. H., Pollack, J. M., Hawver, T. H., & Story, P. A. (2011). The relation between emotional intelligence and job performance: A meta-analysis. Journal of Organizational Behavior, 32(5), 788–818. https://doi.org/10.1002/job.714

Quiñones, M. A., Ford, J. K., & Teachout, M. S. (1995). The relationship between work experience and job performance: A conceptual and meta-analytic review. Personnel Psychology, 48(4), 887–910. https://doi.org/10.1111/j.1744-6570.1995.tb01785.x

Salman, M., Ganie, S. A., & Saleem, I. (2020). The concept of competence: A thematic review and discussion. European Journal of Training and Development, 44(6/7), 717–742. https://doi.org/10.1108/EJTD-10-2019-0171

Škrinjarić, B. (2022). Competence-based approaches in organizational and individual context. Humanities and Social Sciences Communications, 9, Article 28. https://doi.org/10.1057/s41599-022-01047-1

Succi, C., & Canovi, M. (2020). Soft skills to enhance graduate employability: Comparing students and employers’ perceptions. Studies in Higher Education, 45(9), 1834–1847. https://doi.org/10.1080/03075079.2019.1585420

Van Iddekinge, C. H., Arnold, J. D., Frieder, R. E., & Roth, P. L. (2019). A meta-analysis of the criterion-related validity of prehire work experience. Personnel Psychology, 72(4), 571–598. https://doi.org/10.1111/peps.12335

Wagner, R. K., & Sternberg, R. J. (1985). Practical intelligence in real-world pursuits: The role of tacit knowledge. Journal of Personality and Social Psychology, 49(2), 436–458. https://doi.org/10.1037/0022-3514.49.2.436