Competency Iceberg Model: Visible Skills vs Hidden Traits

Turn this article into takeaways for your work.

Each assistant summarizes the article only for you and suggests best practices for your work.

The competency iceberg model says a person's competence has two layers. Knowledge and skills sit above the waterline, where you can see and test them. Self-concept, traits and motives sit below it, where they are harder to observe but shape how someone behaves under pressure. Lyle and Signe Spencer popularized the image in 1993, building on David McClelland's earlier research.

Where the Iceberg Model Comes From

Two sources matter here, and it helps to keep them apart.

The first is David McClelland. In 1973 he published "Testing for Competence Rather Than for Intelligence" in American Psychologist. His argument was that traditional intelligence tests had been validated almost entirely against school performance, and that the evidence they measure abilities needed for success in real life was weak. He suggested better measures could come from studying successful life outcomes, sampling the actual criterion behavior, and assessing communication skills. The paper is often treated as a starting point for the modern competency movement.

The second is Lyle M. Spencer and Signe M. Spencer, whose book Competence at Work: Models for Superior Performance (Wiley, 1993) turned that thinking into a working framework. According to the publisher's description, the book analyzes 650 jobs drawn from about 20 years of research using the McClelland/McBer job competence assessment method, including the Behavioral Event Interview.

The iceberg picture is the Spencers' figure. McClelland didn't draw an iceberg. He supplied the idea that you should measure what people actually do, and what drives them, rather than what a test says they know. That's the attribution to use when you cite this model.

The Five Layers of the Iceberg

The model describes five types of competency characteristics: knowledge, skill, social role and self-concept, traits, and motive. In a published application of the model, knowledge and skill are described as the visible characteristics that people can develop through training, while social role, self-concept, traits and motive are described as more hidden and deep, and as central to personality.

Above the waterline: knowledge and skill

Knowledge is what someone knows about a subject: tax rules, a programming language, contract law, how a CRM pipeline works.

Skill is the ability to perform a specific task: writing a clear report, running a discovery call, building a financial model.

These are easy to list on a résumé, easy to test, and relatively easy to teach. They're also the layers most hiring processes lean on.

At the waterline: social role and self-concept

Self-concept covers a person's attitudes, values and self-image. Someone who sees themselves as a problem solver will keep working a hard issue longer than someone who sees themselves as an executor of instructions. Social role is the image of how a person thinks they're expected to behave in a group, such as "the mentor" or "the one who keeps standards high."

Below the waterline: traits and motives

Traits are consistent ways of responding to situations and information, such as composure under stress or a habit of verifying facts before acting.

Motives are the things a person consistently wants or thinks about, the drives that direct behavior toward some goals and away from others. McClelland spent much of his career on achievement, affiliation and power motives, which is why his name sits next to this layer.

Threshold vs Differentiating Competencies

The iceberg also explains why two people with identical qualifications perform differently. Spencer and Spencer split competencies by what they predict. As one published summary puts it, threshold competencies are the characteristics a person needs to be minimally effective in a job, and they don't distinguish superior from average performers. Differentiating competencies, such as motive, trait or patterns of behavior, are the ones that do.

In practice, that means:

  • Threshold: the accountant knows revenue recognition rules. Everyone on the team does.
  • Differentiating: the accountant who chases down a discrepancy nobody asked about, because accuracy is part of how they see themselves.

Skills get you through the door. What's below the waterline tends to explain who pulls ahead. It's a useful frame for any core competencies framework, because it tells you which competencies to screen for and which to train.

Iceberg Model vs Other Competency Frameworks

The iceberg isn't the only way to describe capability. Each model answers a different question.

Framework What it describes Visible or hidden Best used for Main limit
Competency iceberg Five layers from knowledge to motive Both Deciding what to hire for and what to train Deep layers are hard to measure
KSA model (knowledge, skills, abilities) What a person must know and be able to do Mostly visible Job descriptions and role requirements Says little about drive or character
Four stages of competence How aware someone is of their own skill level Learning progress Coaching and onboarding conversations Describes a learner, not a role
T-shaped skills Depth in one area plus breadth across others Visible Team composition and career paths Ignores motives and traits
Competency framework (role-based) A named list of behaviors per level Observable behaviors Performance reviews and promotion criteria Can become a checklist

Think of the iceberg as the diagnostic and the others as tools you apply once you know which layer you're working on. A KSA list tells you what a role needs. The iceberg tells you which of those items you can train and which you have to select for.

Why the Hidden Layers Matter

Three practical reasons make the model worth the effort.

Training changes the top, not the bottom. In the published summary of the model, knowledge and skill are the competencies people can develop through training, while the core motive and trait competencies are more difficult to assess and develop. If a missing competency lives below the waterline, another course probably won't fix it. Selection and role design do more.

Deep layers drive behavior. The same source notes that motive, trait and self-concept competencies predict skill behavior, which in turn influences job performance. A skill without the drive to use it sits unused.

It keeps hiring honest. A résumé is nearly all above-water evidence. If your interview process only checks that layer, you're measuring the easy part.

How to Apply the Iceberg Model Step by Step

Step 1: Define what superior performance looks like

Start with the role, not the person. Describe what the best performers in that role do differently from the merely adequate ones. Be specific about outcomes: accounts retained, defects caught early, projects delivered without escalation.

Step 2: Separate threshold from differentiating requirements

List everything the role needs, then sort it. Anything every competent person in the role has goes in the threshold column. Anything that separates your best from your average goes in the differentiating column. Most job descriptions are mostly threshold items, which is part of why they all read alike.

Step 3: Map each requirement to an iceberg layer

For each differentiating item, ask which layer it lives in. "Reads financial statements" is a skill. "Takes responsibility for results even when the cause was outside their control" is closer to self-concept. "Needs to win the account, not just serve it" is a motive. This mapping decides how you'll assess it.

Step 4: Choose the right evidence for each layer

Different layers need different evidence.

  • Knowledge: tests, certifications, work samples.
  • Skill: job simulations, practical exercises, portfolio review.
  • Self-concept and social role: structured questions about how a candidate sees their role and what they'd do when a rule and a result conflict.
  • Traits and motives: behavioral interviews that ask for specific past situations. The Spencers' research method centered on the Behavioral Event Interview, which asks people to walk through real events in detail instead of describing themselves in general terms.

Step 5: Decide select-for or train-for

Apply the rule of thumb the model implies. Competencies near the top of the iceberg are cheap to build, so hire for potential and train. Competencies near the bottom are expensive to change, so select for them. A new hire who lacks a software tool can learn it in weeks. A new hire who lacks any interest in helping customers is a much harder problem.

Step 6: Build development plans around the layer

Match the intervention to the layer. Knowledge gaps call for courses and reading. Skill gaps call for practice with feedback, and structures like the 70-20-10 learning model help here. Self-concept and trait gaps call for coaching, stretch assignments and honest conversations. Building self-awareness and emotional intelligence is the path into the lower layers, because people can't change what they can't see.

Step 7: Review against outcomes

Feed the framework into your performance review framework. Check each year whether the competencies you selected for actually show up in the results of your top performers. If they don't, your model of superior performance was wrong, and that's useful to know.

Iceberg Assessment Template

Copy this table to profile a role. Fill the "Evidence" column before you open interviews.

Layer Role requirement Threshold or differentiating How to assess Train or select Rating (1-5)
Knowledge Train
Skill Train
Social role Either
Self-concept Select
Traits Select
Motive Select

A second table works for an existing employee and feeds a development conversation.

Layer Observed behavior (specific example) Gap versus top performers Development action Owner Check-in date
Knowledge
Skill
Self-concept
Traits
Motive

Keep the observed-behavior column factual. Write what the person did, not what you think they are.

Examples by Business Function

The examples below are illustrative sketches, not data from any study. They show how the same five layers translate into different roles.

Function Above the waterline Below the waterline Likely hiring focus
Sales Product knowledge, CRM use, negotiation technique Drive to win, resilience after rejection, belief that results are in their control Motive and self-concept
Customer support Product and policy knowledge, ticket tooling Patience, genuine concern for the customer's outcome Traits and motive
Finance Accounting standards, modeling skill Accuracy as part of identity, composure at close Self-concept and traits
Engineering Languages, system design Curiosity about root causes, ownership of quality Motive and self-concept
People and HR Employment rules, interviewing technique Fairness, discretion, interest in others' growth Traits and motive
Operations Process mapping, scheduling tools Preference for order, drive to remove friction Traits and motive
Leadership Strategy, budgeting, planning Self-confidence balanced with openness, desire to develop others Self-concept and motive

Read down the "Likely hiring focus" column and you'll see a pattern. Almost every function has a threshold of skills that candidates can learn, and a smaller set of deep characteristics that separates the people you'd hire again.

Where the Model Falls Short

The iceberg is a conceptual model, and it has limits worth stating.

  • The lower layers are hard to measure. The published summary of the model itself notes that core motive and trait competencies are more difficult to assess. Interview ratings of "drive" can easily become a mirror of the interviewer's own preferences.
  • It can slide into stereotyping. Treating traits as fixed can lead managers to label people early. Treat the lower layers as tendencies to understand, not verdicts.
  • Context matters. A motive that fits one team's culture can cause friction in another. Define superior performance for your own environment.
  • It is a map, not a test. The model tells you where to look. It doesn't hand you a validated instrument. Pair it with structured interviews and work samples.

Do's and Don'ts

Do Don't
Define superior performance from real outcomes before listing competencies Copy a generic competency list into the job description
Separate threshold requirements from differentiating ones Treat every listed skill as equally predictive
Use behavioral interview questions that ask for specific past events Rely on self-descriptions like "I'm a team player"
Train the top of the iceberg and select for the bottom Expect a course to change a motive
Give feedback on observed behavior Label people with trait words in reviews
Review the model against results each year Assume your first draft of the model is right
Keep language neutral and role-focused Screen on traits unrelated to the job, such as personality "fit"

Key Facts

  • Origin: David McClelland's 1973 paper argued for testing competence directly instead of relying on intelligence tests. The iceberg figure itself comes from Spencer and Spencer's 1993 book Competence at Work.
  • Five layers: knowledge, skill, social role and self-concept, traits, and motive.
  • Visible layers: knowledge and skill, which can be developed through training.
  • Hidden layers: self-concept, traits and motive, which are more central to personality and harder to assess and develop.
  • Threshold vs differentiating: threshold competencies are the minimum for effectiveness, while differentiating competencies separate superior from average performers.
  • Research base: the Spencers' book draws on analysis of 650 jobs over about 20 years, using the Behavioral Event Interview.
  • Best use: deciding what to select for versus what to train.

Frequently Asked Questions about the Competency Iceberg Model

What is the competency iceberg model?

It's a framework that sorts human capability into visible and hidden layers. Knowledge and skill sit above the waterline, while self-concept, traits and motives sit below. The point is that the hidden layers often explain performance differences that credentials can't.

Who created the competency iceberg model?

The iceberg figure comes from Lyle and Signe Spencer's 1993 book Competence at Work. It builds on David McClelland's 1973 paper arguing for measuring competence directly rather than through intelligence tests. McClelland supplied the foundation, and the Spencers supplied the picture.

What are the five competency characteristics in the iceberg model?

They are knowledge, skill, social role and self-concept, traits, and motive. Knowledge and skill are the visible, trainable layers. The other characteristics are described as deeper and more central to personality.

What is the difference between threshold and differentiating competencies?

Threshold competencies are what anyone needs to do a job at a minimum acceptable level, usually knowledge and basic skills. Differentiating competencies, such as motive and trait, are what separate superior performers from average ones.

How is the iceberg model different from the KSA model?

KSA lists the knowledge, skills and abilities a role requires, which are mostly observable. The iceberg adds the deeper layers of self-concept, traits and motive, so it also covers why someone uses their skills well.

Can you develop the hidden layers of the iceberg?

Slowly, and with different methods. Courses work for knowledge and skill. For self-concept, traits and motive, coaching, stretch assignments and self-reflection do more. Because these layers are harder to change, many teams select for them at hiring instead.

How do you assess traits and motives in an interview?

Ask for specific past events rather than general self-descriptions. Questions like "Tell me about a time a deadline was impossible, and what you did" reveal behavior. Score the answers against criteria you defined from your top performers.

Putting the Iceberg to Work

Start small. Pick one role you hire for often, profile it with the first template, and sort the requirements into threshold and differentiating. You'll likely find that the interview process tests knowledge well and the deeper layers barely at all. Fix that one gap, and your next few hires will tell you whether the model earns its place.

About the author

Kevin Kim

Kevin Kim

Senior Customer Retention Strategist

Kevin Kim is Senior Customer Retention Strategist at Rework, writing for HR leaders and people managers on growing their people. Kevin covers job descriptions and role design, employee competencies, and organizational competency frameworks: the building blocks for hiring the right people and developing them once they join.