Skip navigation, go to main content
Contact

How we think

The Go approach in our work

A game of Go is rarely decided by a single blow. A player comes out ahead by choosing where to place each stone, holding the initiative, and letting go of what is no longer worth holding. The four principles below shape how we design solutions — and how we decline work.

The same nine points of territory: six stones enclose it in the corner, while eight in the centre still leave the wall open

Securing territory

A Go player does not win by capturing every enemy stone, but by enclosing more territory.

Applied to our work

You do not need to own everything. You need control of what decides the outcome — where the data sits, who operates it, and what it costs you to change supplier.

In practice

We build systems on open source, hosted in Viet Nam, and hand over the source code and configuration in full. Your organisation keeps control, including after our work together ends.

See infrastructure solutions →
Three stones already placed set the direction for the next two moves

Shape and influence

A good move is not only worth something where it lands; it creates influence for the moves that follow. Bad shape grows weaker the longer the game runs.

Applied to our work

A system built in a hurry runs today but closes off every later choice. The right architecture makes each next step cheaper than the last.

In practice

The data platforms we build separate storage from compute, keep table versions, and manage pipelines as code — so each later extension bolts on rather than forcing a rebuild.

See the data platform →
Black's last move leaves the white stone with a single liberty — White must answer before doing anything else

Sente

Holding sente means holding the initiative — forcing your opponent to answer your move, rather than having to answer theirs.

Applied to our work

Dealing with an incident only after it happens means the initiative is lost. Monitoring, recovery drills and regular patching are how it is taken back.

In practice

We run recovery drills with written records, review configurations on a schedule, and track changes to open source licences — dealing with them before they become a problem.

See backup and recovery →
Two black stones have one liberty left. Rather than save them, Black abandons them for a larger move in the lower corner

Knowing what to abandon

A strong player gives up stones that have lost their value in order to take more elsewhere. Clinging to them loses the position.

Applied to our work

Not every system is worth upgrading, and not every licence is worth replacing. Sometimes leaving things as they are is the right decision.

In practice

Our assessment report may conclude that you should not invest yet, or should choose an option that does not involve us — together with the reasoning behind it.

See consulting packages →
Why Go

Three things the board requires a player to accept

Not because Go is a better game than any other. Because its three constraints are the same constraints faced by anyone running infrastructure.

There is no killing blow

A game is scored on total territory at the end. No single move ends it on the spot. Winning by half a point is still winning.

Applied to our work No infrastructure project ends with the problem solved for good. There is only the sum of many sound decisions, accumulated over years.

The value of a move depends on where it is played

With the same number of stones, a corner holds far more territory than the centre. Go players sum this up as "gold in the corners, silver on the sides, grass in the middle".

Applied to our work Technology budgets work the same way: placing spend well matters more than spending more. We recommend starting with the item someone is actually waiting on.

No one can read out every variation

The board is too large to calculate exhaustively, even for a professional player. A player has to rely on shape and influence — that is, on principles.

Applied to our work We design systems on the same assumption: rather than trying to predict every situation, we choose an architecture that holds up under the ones nobody predicted.

Start with a small move

The first session is free of charge. We listen to the problem, establish the scope, and say clearly if an item falls outside our expertise.