Your operators are competent, but is your team?

Each operator has their skills validated, their authorizations up to date, and their level in the matrix. On paper, the team is solid. But when a production peak arrives or an absence disrupts the schedule, the reality is sometimes different: the individuals are competent, but the collective is not. The distinction between individual and collective competence explains this gap, and understanding it changes the way you manage your teams.

What is individual competence?

Individual competence is what an operator knows how to do and can prove. It is based on a triptych with which production managers are familiar: knowledge (theoretical knowledge), know-how (technical mastery in a given situation) and interpersonal skills (behavior at the workstation).

In production, this translates into very tangible elements. Electrical clearance is an individual skill, as is the ability to adjust a packaging machine after a format change, or to comply with HACCP protocols without supervision. These skills are measured, certified and recorded in a job sheet or matrix. They have a validity date, a level of mastery and sometimes a regulatory obligation. When an auditor asks «Who is authorized to work on this job?», it's the individual's skills that are being checked.

Where it gets tricky is when you think that all you have to do is assemble ten individually qualified operators to create a high-performance team. It's a bit like assembling eleven good players who've never played together: on paper, they look good, but on the pitch, the cohesion is lacking and the automatisms aren't there.

What is collective competence?

Collective competence is more difficult to grasp, precisely because it does not appear on any diploma, nor is it assessed in any annual appraisal. It refers to a team's ability to produce together a result that none of its members could achieve alone, and Guy Le Boterf, a French reference on the subject, gives a definition that sums up the idea: an organization's performance does not depend on the sum of individual skills, but on cooperation between competent professionals.

«Collective competence results from the quality of cooperative relationships implemented by a company's professionals.»

Guy Le Boterf, Building collective skills (Eyrolles)

In the field, this expertise can be seen in a number of ways.

First, there's the so-called synergy, These strong interactions mean that the downstream operator anticipates his colleague's needs without a word being exchanged.

There is also the operational solidarity, This is the group's ability to organize itself spontaneously when a temp arrives or a position becomes uncovered.

L'group learning comes into play when the team draws shared lessons from an incident or an audit, notably through «on-the-spot» feedback.

And finally, there is what management researchers call the joint representation The fact that everyone shares the same understanding of objectives, priorities and constraints, with a common vocabulary and shared reflexes.

When these dimensions work together, a production team absorbs hazards, adapts to load variations and maintains quality. When they don't, every absence or change of schedule becomes a source of disorganization, and the production manager spends more time putting out fires than managing his activity.

What really distinguishes the individual from the collective

As far as the individual is concerned, everything is relatively straightforward: skills can be assessed during an interview, validated by certification, and recorded in a file. A skilled operator can even move to another plant and take his know-how with him. Collective skills work differently: they are not measured in the same way, they are observed in action, when the team is faced with an unforeseen situation. Above all, it doesn't move around. It is linked to the group, to its history, to its work habits, to the extent that losing two key team members can shatter automatisms built up over years.

Another difference, less visible but just as important: where individual skills are formalized in reference frameworks and matrices, collective skills often remain in the shadows. Much of it is based on tacit skills, These unwritten skills account for up to 70 % of the skills actually used on the job. The gesture that no-one has documented but that everyone reproduces on the line, the way the morning shift anticipates the afternoon shift's needs: all this is part of the collective, and none of it appears in a file.

Herein lies the most common trap: believing that recruiting the best profiles is enough to build a high-performance team.

In reality, collective expertise cannot be added up, it has to be built., It requires time, stability and the right conditions for cooperation.

• Individual skills can be acquired through training, whereas collective skills are developed in the field, through shared action.
• Individual responsibility lies with each operator and his or her career path, while collective responsibility lies with work organization and management.
• The individual is visible and documented, but the collective is often the «unspoken» factor that makes the difference between two teams with similar profiles on paper.
• Losing an individual skill means having to manage a departure; losing a collective skill means sometimes losing months of performance.

How do individual skills feed the collective (and vice versa)?

The two are not mutually exclusive, but work in a virtuous loop, provided that the organization creates the conditions to make it work. The mechanism is fairly intuitive: each operator arrives with his or her individual know-how, which constitutes the raw material. When these skills cross-fertilize, complement each other and are passed on within the team, collective competence emerges, and in turn, the collective pulls each individual upwards.

We can see this clearly in the field. An experienced welder has been working alongside a temp for three weeks, and without any formal training, the temp has already integrated reflexes that the welder has never put down on paper: how to position the part to save time, what setting to adjust when the ambient temperature changes, when to alert maintenance. These are tacit skills passed on by the team, and the day this temporary worker is appointed, he will in turn enrich the group with his fresh eyes and his questions.

Several mechanisms activate this loop in production. The tutoring and job pairings accelerate the transfer of tacit skills, which is all the more important given that 25 % of the French working population is between 50 and 65 years of age: intergenerational transmission is no longer a distant subject, it's an operational emergency for many manufacturers. Visit job rotation, for its part, develops individual versatility while giving each operator a better understanding of the constraints upstream and downstream of his own position on the line. As for collective feedback (REX), especially those carried out «on the spot» after an incident or change, they transform individual experience into shared learning by bringing out a common language, a constructive critical stance and stronger team commitment.

The manager's role is central to this dynamic. It's the manager who organizes the pairings, plans the rotations, and protects the time for exchanges between operators. Without this framework, skills remain compartmentalized and cooperation does not develop on its own.

Moving from individual to team vision with the competency matrix

Many production managers keep track of skills, operator by operator. Every sheet is up to date, every clearance is traced. But when it comes to answering the question «Is my team capable of covering all the shifts this week?», things get a little fuzzy, because the individual vision says nothing about collective coverage.

This is precisely the role of skills matrix It bridges the gap between these two levels. By cross-referencing the skills of each operator with the requirements of each job, it enables us to see at a glance the strengths and vulnerabilities of a team, and to move from a logic of individual monitoring to one of true collective management.

The approach is structured in three stages: identifying the individual skills of each operator and their level of mastery, cross-referencing these skills with the real needs of each position or line, and then identifying collective gaps. Which jobs are covered by just one person? What critical skill is lost when an operator retires? The resulting team versatility score is an invaluable indicator, because it supplements the individual assessment with a collective reading, making it possible to anticipate weaknesses before they become production problems.

To find out more about how this approach fits into a global approach, see our guide to skills-based management.

Three actions to develop both in parallel

Articulating individual and collective skills does not require revolutionizing the organization. Three levers, activated gradually, produce visible results.

• Mapping for visibility. As long as know-how remains in the heads of managers or scattered in Excel files, it's impossible to have an overall vision. A structured mapping of individual skills is the foundation on which the versatility at work can be built, and the first step towards a collective reading of what the team can do.
• Organize peer-to-peer transmission. Classroom training is not enough to develop collective skills. It's job pairings, planned rotations and team debriefs that create the conditions for cooperation. Transmission integrated into the workflow is faster and more lasting than training disconnected from the field.
• Measuring team versatility, not just individual versatility. The indicator that changes the game is the collective coverage rate: how many shifts can my team cover in the event of absence? This managing versatility and industrial agility transforms planning into strategic leverage, because it makes visible what was previously in the head of the team leader.

Conclusion

Skills management that stops at the individual misses half the point. Each operator's know-how takes on its full value when it circulates, complements one another and ends up constituting a collective intelligence that the team mobilizes on a daily basis. The departure of a key employee then causes less damage, because reflexes have been shared and coverage of critical positions has been anticipated.