Rugby's Surface Complexity Is a Coaching Trap

Add bodies, movement, defenders, contact, and a ball, and an activity quickly starts to feel like the game. It looks alive. It looks contested. It looks representative.

That is the trap.

Looking like rugby is not the same as demanding what rugby demands.

An activity can borrow rugby's surface without preserving rugby's problem.

Surface form is what the activity looks like. Actual demand is what the player has to solve.

Those two things can diverge.

A drill can look simple while preserving an important piece of the game. A drill can look rich while removing it. A drill can include defenders without creating a meaningful decision. It can include contact without preserving the information that makes contact difficult. It can include shape, width, and support lines while removing the uncertainty that makes those structures worth reading.

Rugby makes this problem worse because rugby looks like rugby too easily.

Take small-sided games.

A small-sided game can produce high volumes of action. Players get touches. They compete. They communicate. They attack space, fold around, defend, transition, and solve problems under pressure. From a coaching perspective, it can feel like a strong answer to the limitations of isolated drills.

Sometimes it is.

But the fact that an activity is a game does not mean it preserves the game. A small-sided game can remove the spatial and tactical structures that make rugby decisions meaningful. It can shrink the field in ways that simplify the problem. It can create repeated versions of one obvious decision rather than the more ambiguous decisions players face in competition.

The activity looks live. It may be live. But live is not the same as representative.

If the game gives players one clear answer again and again, it may be training recognition or even compliance rather than judgment. If the space, numbers, and defensive picture have stripped away the competing pressures of the match, the activity may be less demanding than it appears. The player is making decisions, but not necessarily the decisions the coach thinks they are training.

Contact work creates the same trap, and nowhere does compliance masquerade as learning more easily.

The sensation of collision is easy to reproduce. Players can hit pads, wrestle, clean out, tackle, jackal, fight for body position, and leave the drill physically taxed. The session looks like contact training because there is contact everywhere.

But real contact in rugby is not just collision.

The moment before contact is full of information. The ball carrier's line matters. Their speed matters. Their body position matters. Their support matters. The defender's angle matters. The arriving threat matters. The timing of the contest matters. In a match, the player is not just performing contact technique. They are reading the conditions that make a particular technique useful.

A scripted contact circuit can remove most of that information while preserving the feeling of work.

The body learns to collide. It may not learn what to read before collision. It may not learn when contact is worth entering, when to adjust body position, when to change the target, when to leave the contest, or when the technique that looked correct in the drill is wrong for the actual situation.

The surface is contact. The demand may be compliance.

Phase play is even more deceptive because it sits so close to the game in appearance.

The width is there. The depth is there. The attacking shape is there. The support lines are there. There is a defensive line to move against. The language sounds right: launch, shape, edge, connection, fold, reload, speed.

But phase play can quietly remove the thing that makes phase play hard.

If the pattern is predetermined, the defensive picture is predictable, and the outcome is largely known, players may not be reading the field. They may be executing a sequence against a vaguely resistant backdrop. The activity looks tactical. It looks organised. It looks like preparation for the game.

But the player may not be solving the same problem they will face on Saturday.

In each case, the activity keeps rugby's visible features while quietly removing part of the problem that gives those features meaning.

This is why rugby-shaped is not the same as representative.

A drill is not representative because it contains pieces of the game. It is representative when it preserves the relationship between information, decision, timing, and action that exists in the game.

That relationship is fragile.

Change the space and you change the information. Remove a defender and you change the decision. Script the opposition and you change the timing. Take away contact and you change the attacking choice. Add a rule to force a behaviour and you may get the behaviour while removing the reason for it.

The mistake is not simplification—it is confusing the simplified activity with the game problem it no longer contains.

This is the distinction my MACS framework tries to preserve: the difference between what an activity looks like and what it actually demands.

This is the practical cost.

A coach believes they trained decision-making because defenders were present.

But the defender may have created only one obvious answer.

A coach believes they trained contact because players collided.

But the activity may have removed the reading that makes contact a rugby problem.

A coach believes they trained game preparation because the session looked like the game.

But the uncertainty may have been taken out.

The result is familiar. Feedback gets aimed at the wrong problem. Players are praised for solving a thinner task than the coach believes they solved. Sessions look complete because all the visual categories have been covered: passing, contact, defence, phase play, game-based work. But the real demands may still be missing.

That is why this kind of error persists. The session creates the impression that something important was trained when the real demand may have been barely touched. It does not just fail quietly. It produces false confidence.

This is why a classification framework becomes necessary. The starting point of MACS is not surface appearance, but actual demand: not what the activity looks like, but what the player is actually being asked to solve.

The question is not whether the activity looks like rugby.

The question is: what part of rugby's real problem does this activity preserve?

What information does the player have to read?

What uncertainty remains?

What decision is being made?

What timing problem exists?

What has been removed to make the drill cleaner, safer, faster, or easier to coach?

Those questions do not condemn any activity. They sharpen it. They help a coach see the drill for what it is, not for what it resembles.

The surface of rugby is rich enough to hide the absence of depth.

The useful question is not whether the activity looks like the game. It is what the player is actually being asked to solve.