Four operating modes of any system, and why your Russian team will not do what you ask

Picture a dashboard with four zones: green, yellow, blue and red. A car has one. You read engine revs from it and you know, without thinking, that an engine in the red is doing something different from an engine idling in the green. Every person, team and organisation carries a similar panel. Nobody can see it, and it does not show revs. It shows the functional mode: how mobilised the system is at this moment and what it is capable of doing while it stays there.

For a company that sells into Russia from abroad, that panel sits in three places at once. On the local team or partner who executes. On the customer who decides. On the market as a whole. Head office reads all three from a distance, usually assumes the zone it is in itself, and then asks for behaviour that the zone on the ground cannot produce. What comes back looks like resistance or passivity. It is neither. It is physics.

Four zones instead of one scale of “stressed or not”

The habit is to sort states into two boxes: calm and stressed. The functional model offers four ranges instead.

Green is comfort and low mobilisation. The system is not straining; it runs at minimum output. Yellow is playful exploration and rising activity. The system probes, searches, experiments; mobilisation grows, but there is no threat in it. Blue is structuring and control. The system pulls itself together, imposes order, acts on a clear plan; mobilisation is high and aimed at a target. Red is survival and deficit mobilisation. The system runs at its limit, and nothing is left over for anything except immediate rescue.

Each zone comes with three parameters. A threshold of sensitivity: how strong a signal has to be before the system notices it at all. A threshold of tolerance: how much the system can take before it breaks down. And dynamic competence: how flexibly the system can move between zones and come back.

Those three parameters are what a two-box model loses. “Stressed” covers both a team in blue, which is highly productive at a narrow kind of work, and a team in red, which can barely hold the line. Treating them the same way guarantees the wrong request to at least one of them.

Why you cannot demand the same thing in different zones

The mistake happens constantly: expecting a system in one zone to behave as if it were in another. From a person in the red zone, the survival zone, people expect the creative, playful behaviour of yellow. From a team in blue, the zone of hard structure, people expect the relaxed openness of green. Both expectations are doomed, because each zone physically limits the range of behaviour available.

A person in the red zone does not “refuse” to show flexibility and creativity. They cannot afford it. All the mobilisation they have is spent on getting through the here and now; there is no resource left for play. Demanding a creative approach from them at that moment is the same as demanding a smooth, economical cruise from an engine at the redline. The resource has already been redistributed to a different task.

This is where Western management and marketing habits collide with the ground in Russia. The playbooks that travel from the home market, and from Google’s own growth literature, assume yellow. Test and learn, fail fast, run the experiment, let the team find its own way. Every one of those instructions presumes a system with spare resource and a low threat level. Hand them to a system in blue and they land as noise. Hand them to a system in red and they land as an added threat.

Example: a team after a crisis

Take a team that has just come out of an acute crisis: a collapsed project, a conflict with a client, the loss of a key specialist. Formally the crisis is over. The team, though, stays in the blue zone for a while: hard structure, total control over process, minimal spontaneity. The manager, wanting to “bring back the fighting spirit”, starts demanding yellow-zone behaviour: playful search for new ideas, a readiness to take risks.

The demand does not work, and from the outside it looks like a lack of motivation or outright resistance. In fact the team’s dynamic competence has dropped after the crisis: the ability to switch between zones and return. It is not that one zone stands in the way of another. It is that the switch itself takes resource, and right now there is not enough of it.

Now put a border and a time zone between the manager and the team. The manager sits in a head office that is in yellow or green. The team is a Russian distributor’s sales unit, a hired local agency or a handful of remote people who have spent the last several years in an environment that kept pushing them into blue: re-routed supply, changed payment rails, rules that shifted mid-quarter. I am describing a pattern I see in practice, not a measured figure. The request from head office, “be bolder, try new channels, show us some creative tests”, arrives as a yellow-zone request to a blue-zone system. The reply, “send us the plan and we will execute it”, is read as Russian passivity. It is the blue zone describing its own capability accurately.

What the zones do to a customer

The same panel sits on the buyer, and the thresholds matter more there than the labels.

A customer in blue wants predictability. Delivery terms stated in full, a named person who answers, payment that works the first time, a warranty that reads like a rule rather than a promise. Brand communication built for yellow, with humour, open questions and an invitation to play, falls flat with that buyer. The usual explanation is that the humour did not translate. The more useful one is that the receiver is in a different mode and the message was built for the sender’s mode.

A customer in red has a raised threshold of sensitivity: only strong signals get through, so subtle brand cues go unregistered. The threshold of tolerance is low: a form that rejects a Russian phone number format, a payment method that fails, a delivery estimate that cannot be verified, and the buyer is gone. None of that is a conversion-rate problem in the ordinary sense. It is a system at its limit shedding anything that costs it effort.

This is why I do not trust a gut read of the Russian buyer made from another country, and why customer research comes before the campaign and not after it. Research is how you find out where the needle is. Everything else is an assumption about the zone, and the assumption usually mirrors the zone of the person making it.

What to do about it

The applied conclusion is short. Before demanding a particular behaviour from yourself, from another person or from a team, establish which of the four zones the system is in now. This is not observation for its own sake. It is the condition under which the demand has any chance of being met.

If the system is in red, the task is not to inspire it to creativity. The task is to lower the threat and bring it back at least to blue: give it structure, predictability, clear rules. If the system is in blue, the task is to lower the level of control gradually and allow it to try new things inside safe, limited frames, restoring the very ability to switch. Demanding the desired behaviour without doing this switching work is a reliable way to get either a breakdown or an imitation of the behaviour. Changing mode is separate work, and it needs resource.

For a company that sells into Russia from abroad, that translates into a sequence.

1. Read the zone of your local operation before you set targets. The signs are in how they handle ambiguity, how they respond to a task with no template, and how they talk about risk. A team that asks for the plan is telling you where the needle is.
2. Match the request to the zone you found. A blue-zone team gets a plan with checkpoints and a narrow, explicitly bounded sandbox for experiments. A red-zone team gets fewer fronts and an obvious next step. Neither gets “surprise us”.
3. Read the zone of your customers through research, not through assumption. Ask how they decide, what they verify, what makes them stop. Those answers show the sensitivity and tolerance thresholds, and the thresholds place the needle.
4. Budget resource for the switch itself. Moving a team from blue to yellow costs management attention and calendar time. Plan it as work with its own owner, not as a motivational call.
5. Re-read the needle at each planning cycle. The reading from the last period is not the reading for this one. This is also the reason a market entry plan written once and executed for two years tends to drift away from the market it was written for.

Zones are not a diagnosis, they are the position of a needle

None of the four zones is better or worse than another in itself, just as engine revs are never “wrong” if they match the task. Red is needed when there is a real threat. Blue is needed when order has to follow chaos. Yellow is needed when there is resource for experiment. Green is needed when the system simply has to recover.

This cuts both ways for a foreign company. Expecting yellow from a system in blue is one mistake. Deciding that “Russia is permanently in the red zone” and planning as if the needle were welded there is the same mistake pointed the other way. A label fixed on a market, a partner or a team stops you from reading the panel, and the panel is the only thing that tells you which request will work.

The problem is never the zone itself. It is the mismatch between the zone and the current task, or a system stuck in one zone longer than the situation requires. Before asking what is wrong with the person, the team or the Russian market, ask the simpler question: where is the needle right now, and is the conversation that is about to start actually heading there.

Frequently asked questions

Sources

• Russian version of this article on belokrylovo.ru: Четыре режима, в которых работает любая система