Keep the shape. Win the edges.

Fifteen players. One ball. You may only pass it backwards.

Yet the team goes forward.

That is rugby’s quiet lesson. The ball goes back so the line can go forward. Every pass trusts that a mate is there in support. In Aotearoa New Zealand, many of us learnt this on a cold field long before we learnt it at work.

A team is a shape, not a list

An org chart lists people. A rugby team holds a shape.

Every player has a role. A prop, a halfback, a winger. Each is different. None is optional. A prop who tries to play wing leaves a hole at the scrum.

The shape holds when each player does their job and knows where their mates are. It breaks where the talking stops.

The game is won at the edges

A defence is weakest where its line runs out of players. An attack looks for the overlap: one more runner than the defence can cover.

Business works the same way. Threats and chances show up at the edges first. A leak in a building nobody visits. A cold store drifting warm at 3am. A customer about to leave. Spare capacity no one can see.

By the time the news reaches the centre, the gap has already opened.

Devices as players

Most sensors are spectators. They watch, and they send everything to the stand.

DePIN, decentralised physical infrastructure networks, points to something else. Sensors, hotspots and meters owned and run by many people, not one company, and rewarded for proving they do a useful job. Helium, for example, rewards hotspots for proving where they are and what coverage they give, and other hotspots in radio range witness the proof (Helium docs). Peers check the play.

Put devices like that on the edges as players, not spectators. A player does four things:

• Reads. The temperature is rising.
• Decides within its role. It is past the line we agreed.
• Acts. It closes the valve, or switches to backup.
• Passes. It tells the person who makes the bigger call, with what they need to act.

A good pass puts your mate into space. A bad one puts them into trouble. A device that floods a phone with alerts has thrown a bad pass.

Good governance plays advantage

Rugby has a law for this. When one side breaks the law, the referee can let play go on if the other side gains a clear and real advantage. If no advantage comes, the referee goes back to the original offence and applies the penalty (World Rugby, Law 7).

That is good governance in one law. Don’t stop the game for every mistake. Let the flow continue while it serves the team. Keep a clear point of return, and come back to it when it doesn’t.

Bad governance does one of two things. It blows the whistle for everything, or it never blows it at all.

There is a second line too: offside. You may only play from behind the ball. Speed doesn’t excuse it. A device or an agent acting outside its authority is offside, however quickly it moved. Safety and permission are lines to stay behind, not points to trade.

The laws are being rewritten

In rugby, the laws sit outside the game. In the economy now arriving, they are moving inside it.

Tokenization turns assets and bits into tokens that can move, be checked and be paid for, by people and by devices. Tokenomics decides who gets rewarded for what. Together they write the incentives into the field itself.

That changes how the game is played. A sensor can earn for proving its work. An agent can pay for the data it needs. A team that once shared a dressing room now shares a ledger.

Write those laws well and every player is paid to keep the shape. Write them badly and players chase the reward, not the result.

A phase of play

Rugby moves in phases. Each one is a small loop of coordination:

1. A shared intent: where are we going?
2. Each player takes a role.
3. They act within their authority.
4. They pass, or they support.
5. The result is checked.
6. The next phase starts better, or worse.

The same loop works for people, software agents and devices. That is the unit of teamwork worth watching. Not the player. The phase.

What we think now

Coordination isn’t everyone doing more. It is each player making their mate’s next move easier.

Play your role. Improve your mate’s options. Leave the next phase better than you found it.

For devices at the edge, the test is not how much data they send. It is whether the team acted sooner and better because they were there. A fast device whose alerts need a person to clean up is worse than a slower one the team can trust. Reward the check, not the noise. Pay the work, not the gate.

We are working on a teamwork index that scores the pass, not the player: alignment, role fit, handoffs, support, recovery, and whether the team can keep it up. It is a working idea, not yet tested.

What we’re unsure of

• How much should a device decide alone? Closing a valve is easy. Turning away a customer isn’t. Where does its role end?
• Can you score a pass without punishing the prop? Roles differ. One league table would reward the wrong players.
• Will device owners play for the team? When rewards come from tokens, people play for the reward. Is that the same as the outcome?
• Who referees when no one owns the field? Shared networks need shared laws, and someone trusted to blow the whistle.

What would change our mind

• A team that closed threats faster with more data alone, and no shared intent or roles.
• Evidence that central control beats cooperation at the edges, over time, where conditions change fast.
• A teamwork score that held up for years without being gamed.

Your turn

Pick one edge of your business, where trouble or opportunity shows up first. Ask four questions:

• Who, or what, is standing there?
• When they see something, who do they pass to, and does that pass put a mate into space?
• What may they do without asking?
• When something goes wrong, do you play advantage, or stop the game?

If nobody is standing at the edge, the other side already knows.

Read it with Tokenization: one word, three meanings, on what a token stands in for, and Tokenomics: pay the work, not the gate, on who a reward really pays.

Published 5 November 2026. A reflection on how teams are changing, not engineering or legal advice.