Cognitians, Not Technicians

Rugby does not need better technicians.

It needs cognitians.

A technician executes correctly. A cognitian solves correctly.

The distinction is simple, but it changes almost everything when it comes to how we think about player development.

The technician is the player who does things right. They pass with clean mechanics. They tackle with excellent technique. They clean out with a strong shape. They execute the movement the coach has asked for.

The cognitian does the right thing.

They read the situation, recognise what matters, choose the appropriate response, adjust that response to the context, and then execute. They may still need excellent technique. But their technique is attached to a better problem.

That distinction matters because rugby does not reward technical execution in the abstract. It rewards the right action, at the right moment, in response to the right information.

A technically perfect action can still be the wrong action.

A player can throw a beautiful pass slightly off-target, or worse, to the wrong receiver. They can set up for a textbook tackle and miss by inches because they solved the carrier too late. They can clean out with excellent body position when the breakdown did not need them. They can kick with perfect connection into the wrong space.

In each case, the technique may be excellent.

The rugby action is still poor.

This is why the technician model is not enough.

This is the old Peter Drucker distinction, applied to rugby: efficiency is doing things right; effectiveness is doing the right things.

Rugby coaching often confuses the two.

We become efficient at producing cleaner actions, sharper movements, tidier drills, and better-looking repetitions. But if those actions are not attached to the right reads, the right timing, and the right decisions, the programme may only be getting better at producing the wrong thing.

A player can become more technically efficient without becoming more effective as a rugby player.

That is the trap.

Technical mastery is not the ceiling in rugby.

It is the entry fee.

A player still needs the physical skill to pass, tackle, kick, carry, clean out, and compete. The best read in the world is useless if the player cannot execute the action the situation requires. But those abilities only become rugby skills when they are attached to the right problem.

There are sports where the technician model is at its strongest.

In some sports, performance is measured in centimetres, grams, or seconds. These are often called CGS sports. The athlete lifts more weight, runs faster, jumps higher, throws further, or completes the task in less time. The output is measured against a relatively fixed standard.

In weightlifting, the bar is there. The movement is known. The environment is stable. There is no defender to read, no space opening and closing, no opponent manipulating the picture, no decision about whether a different action has become more useful. The lift is a technical problem. A coach who produces technically excellent lifters has done the main job.

The same logic applies, in different ways, to many events in athletics, and partly to sports like diving and gymnastics where performance is judged against a technical standard. Better execution usually means better performance. A technical improvement might add a kilogram, save a hundredth of a second, increase a distance by a centimetre, or reduce a deduction.

In those sports, doing things right sits very close to doing the right thing.

Rugby is different.

The environment is unstable. The picture changes on every phase. The same space can be available, closed, and available again in the space of seconds. Opponents are not passive obstacles. They are acting, adjusting, disguising, and disrupting. Teammates are also moving, changing the options available to the ball carrier or support player.

Of course, rugby is not the only sport with perception, decision-making, and opponents. Football, basketball, hockey, league, and other invasion games all demand cognition.

But rugby adds something unusually severe: contact, breakdowns, set piece, territory, and constant transitions between structured and unstructured phases. The game does not just change pictures. It changes the type of problem the player is solving.

That means rugby skills are rarely just skills.

They are responses to situations.

A pass is not just a pass. It follows a read of defender position, support line, space, timing, pressure, and risk. The player is not merely asking, "Can I pass?" They are asking whether this pass, to this player, at this speed, at this moment, is the right solution to the picture in front of them.

A tackle is not just tackle technique. It follows a read of the carrier's line, speed, footwork, body position, support, and threat. The useful tackle shape depends on the situation as it unfolds. The correct action is not floating above the game waiting to be performed. It is produced by the relationship between the tackler, the carrier, the support, and the space around them.

A kick is not just striking the ball cleanly. It follows a read of backfield space, chase capacity, pressure, score, field position, weather, and the likely next contest. The technical act matters, but the value of the kick is decided before the foot reaches the ball.

This is one of the central claims of Rugbyology:

In rugby, every technical execution is preceded by, or coupled with, a decision process.

Not some technical executions. Not only the obvious "decision-making" moments. Every technical execution.

The pass, tackle, kick, carry, clean-out, reload, support line, and defensive adjustment all sit inside a process of reading, selecting, judging, calibrating, and acting. Sometimes that process is conscious. More often it is fast, embodied, and unfolding as the player moves. But it is there.

That is the point coaching too often misses.

The visible action is the final thing we see, so it becomes the thing we coach. The pass misses the target, so we correct passing mechanics. The tackle fails, so we correct tackle technique. The clean-out is poor, so we correct body height.

Sometimes that is right. Sometimes the technical execution really was the problem.

But often the technical error is downstream of a reading error, a timing error, a selection error, or a judgment error.

The player did not just pass badly. They passed late because they read the defender late.

They did not just tackle badly. They chose the wrong shoulder because they misread the carrier's angle.

They did not just clean out badly. They entered a contest that did not require them, selected the wrong threat, or arrived with a technique suited to a picture that had already changed.

If the coach only sees the visible execution, the correction will be aimed at the wrong problem.

The simplest way to understand the cognitian is this:

Read. Pick. Tune. Do.

The player reads the situation. They pick the response. They tune the action to the specific context. Then they do it.

Those stages are not neatly separate. Rugby does not give players time to finish thinking and then begin executing. The process is nested and continuous. The player is reading while moving, picking while pressure changes, tuning while the defender adjusts, and executing while the original picture is already becoming a new one.

This process is not something elite players add on top of technique.

It is running underneath every action in the game.

The question is not whether the process exists. It does. The question is whether coaching sees it, develops it, and designs practice around it.

This is why technique cannot be treated as an isolated object in rugby. Technique is often the visible end of a deeper process.

The breakdown makes this obvious.

A clean-out can look like a contact skill. From the sideline, the obvious coaching points are body height, shoulder placement, entry angle, footwork, and leg drive.

Those things matter.

But the clean-out does not begin at contact.

Before the player arrives, they must decide whether they need to enter the breakdown at all. Is this ball actually under threat? Is their contribution needed, or would they only add another body? Are they close enough to affect the contest? Is someone else already better placed?

If there is a threat, they must identify it. Not every body near the ball is a threat. Some players are present but harmless. Others are in the process of becoming dangerous.

The support player is not just reading what is there now. They are projecting what will be there by the time they arrive.

Then they must decide how to solve the contact problem. A player arriving in one second is not choosing a technique for the picture that exists now. They are choosing a technique for the body position, ball presentation, and threat that will exist when they get there.

That requires anticipation.

It requires cue recognition.

It requires judgment under incomplete information.

Only then does the technique appear.

So the clean-out is not just a contact technique.

It is a decision that ends in contact.

This is the difference between technicians and cognitians.

The technician can be trained to win a shape. The cognitian has to know whether the shape is needed, who it is needed against, when it is needed, and how it must change as the situation changes.

This does not make technique less important.

It makes technique more contextual.

The best players are not vague thinkers who somehow get by without execution. They can execute. But they execute actions that fit the situation. Their skill is not only in the movement. It is in the coupling between information, decision, calibration, and action.

That is what coaching has to build.

The problem is that technicians are easier to coach.

Technical execution is visible. A coach can watch a pass and see the hands, hips, follow-through, and ball flight. They can watch a tackle and see body height, foot placement, shoulder contact, and leg drive. They can watch a clean-out and see whether the player won the collision.

Decision quality is harder.

If a player throws a poor pass, was the technique wrong, or was the read late? Was the option wrong, or was the option right but the execution poor? Did the player miss the defender, misread the support line, fail to adjust their timing, or simply lack the skill to deliver the pass the situation required?

The same visible mistake can come from different failures.

In Rugbyology terms, the failure may sit at a different level of the action: the read, the selection, the timing, the calibration, or the execution.

That is why coaching defaults to the visible level.

It is not because coaches do not value game intelligence. Most coaches talk about awareness, vision, feel, and decision-making constantly. The issue is that technique is easier to see, easier to correct, and easier to feel productive about.

So programmes drift toward producing technicians.

Players repeat movements. They refine mechanics. They rehearse patterns. They improve the visible parts of performance.

Some of that work is useful.

But it can also become seductive, because it produces visible progress.

Passes look cleaner. Tackles look sharper. Clean-outs look more powerful. The session looks better. The standards appear higher. Completion rates rise. Contact quality improves.

Those improvements can be real.

They can also be improvements inside the wrong frame.

A programme can become very efficient at producing execution detached from the problem that gives execution its value. It can produce players who look better in practice without becoming better at solving rugby problems.

That creates a specific kind of player.

The player who looks excellent in drills but ordinary in games.

The player who has beautiful technique but poor timing.

The player who can pass, tackle, clean out, and kick, but cannot reliably identify when, where, why, or how those actions are required.

The player who does things right, but not often enough does the right thing.

This is not a small distinction.

It changes what coaching is for.

If the goal is to produce technicians, then the coach's job is to improve execution quality. Break the game apart, isolate the movements, correct the errors, and rebuild from the pieces.

This is the Cartesian temptation in coaching: the assumption that if we improve the parts, the whole will take care of itself.

It produces a powerful illusion of progress. The smaller we make the problem, the easier it becomes to show improvement. But improvement in the fragment does not guarantee improvement in the game.

The cleaner the movement, the better the work appears.

If the goal is to produce cognitians, then the coach's job is different.

The coach must design activities that preserve the decision process attached to the execution. They must ask what the player is reading, what options they are choosing between, what uncertainty remains, and how the technique is being calibrated to the situation.

The question is not only:

Can the player execute the skill?

The question is:

What decision process is this execution attached to?

A passing drill that removes all meaningful information may still improve mechanics. That may be useful for a limited purpose. But it is not developing the player who can read the defender, time the support line, choose the pass, and execute the right ball under pressure.

A tackle drill that removes the carrier's real movement may still improve contact confidence. That may be useful for a limited purpose. But it is not developing the player who can read the carrier, adjust late, and solve the collision as it changes.

A clean-out drill that removes the question of whether the clean-out is needed may still improve body position. That may be useful for a limited purpose. But it is not developing the player who can decide whether to enter, who to remove, and what contact solution the unfolding breakdown requires.

A lot of rugby practice produces compliance and calls it learning.

The player learns the coach’s rule, the drill’s rhythm, or the artificial governing constraint. But they do not necessarily learn the rugby problem. They become better at the activity, not better at the game.

The mistake is assuming that once the technique is good enough, the decision-making will take care of itself.

It will not.

A player can pass cleanly for years without learning when the pass is on, because the activity has never required them to read the defender.

A player can tackle with good shape for years without learning how to solve the carrier, because the activity has removed the very information the tackle depends on: movement, timing, deception, and threat.

The player gets better at the action, but not the problem that makes the action rugby.

Perception and decision-making do not emerge automatically from technical competence.

They develop in environments that demand perception and decision-making.

This is the coaching implication.

Do not just train the action.

Train the problem that makes the action rugby.

That does not mean every activity must be fully live, chaotic, or game-like. It means the coach must ask the question at the heart of my activity classification system:

What is the cognitive demand of the activity?

Not what skill does it contain. Not what phase of the game does it resemble. Not whether it has a ball, defenders, cones, contact, or chaos.

What is the player actually being asked to solve?

Is it mechanical repetition, heuristic attunement, selection around one salient constraint, judgment across multiple interacting constraints, or sense-making, where the player must first work out what kind of problem they are in?

A drill is not defined by the rugby action it contains. It is defined by the cognition it demands.

That is the difference between looking like rugby and acting like rugby.

An activity looks like rugby when it contains rugby’s surface features: a ball, opponents, contact, space, and familiar language.

It acts like rugby when it preserves the cognitive demand of the game.

Those distinctions matter because rugby performance lives in the coupling.

Without that distinction, the development of cognitians becomes accidental. A player improves because the game happened to expose the right problem often enough, not because the programme deliberately built the capacity.

Accidental development is not a programme.

It is luck wearing the clothing of coaching.

Technique without the right read is fragile.

Decision-making without execution is useless.

The cognitian is not the opposite of the technician. The cognitian contains the technician, but adds the thing rugby actually demands: the ability to solve before and while executing.

That is why rugby needs cognitians, not technicians.

Not players who merely do things right.

Players who do the right thing, then do it well.