Culture eats strategy: style is a management layer

One person on the team likes a project laid out on a grid: stages, deadlines, owners, a table that fills the screen. Another works in bursts and answers the question of what happens next with “bring me a vision”. Formally they share one goal, one department, one strategy. Six months later the first one resigns because “it is impossible to work here”, and nobody can properly say why. The strategy was right. The goals matched. The style did not.

That is the level at which an organisation stops being only a process, only an organism, only an information system, and turns out to be a culture.

Style is a management layer, not a decoration

Culture is a set of rules and limits that hold on a given territory. Inside a company it appears as symbols, artefacts, rituals and behaviour, all of them soaked in style. Style is the operative word. The same artefact, a meeting, a report, an email to a client, can be coloured in completely different ways: said quietly or said loudly, worked into a narrative or squeezed into two lines. That colouring is not ornament laid over content. It is a management layer of its own, and it decides whether even a correct strategy takes root.

Hence the formula. Culture eats strategy for breakfast. It does not cancel the strategy openly. It passes the goals, the mental pictures and the motivation through the medium, and what the medium cannot carry is quietly left out. If the style of that medium does not support reaching the goal, the strategy sinks into everyday behaviour while everyone formally agrees with it.

Culture grows upward before anyone announces it downward

Culture does not arrive from above as an order. It forms from the bottom up. Conditions in the environment produce a functional demand, for example the need to react fast to situations nobody wrote a procedure for. An organ self-organises around that demand: a specific group of people who start handling those situations in their own particular way. Out of the organ comes a set of people with a shared behavioural style. Only then does it harden into a trait of the company as a whole, and the ascending process meets the descending one. What was born below as an answer to reality becomes the norm transmitted from above as “the way things are done here”.

This is where the internal and external environment, information and the symbolic function lock into a single loop. Culture is, in effect, a frozen style, the style in which an organisation has learned to process information and respond to its surroundings.

The most expensive conflict gets read as a personality clash

A clash of styles is the most common and the most underestimated source of loss inside teams. The person who needs structure and the person who works as a spontaneous flow can both be genuinely good at their part of the job. If nobody in the company understands that what they are looking at is a difference of cultural styles rather than a difference of characters, the conflict is read as personal incompatibility or as a lack of professionalism. The outcome is predictable. A good employee leaves, and the reason was never the tasks. The reason was that the tasks came wrapped in a style of delivery they could not work inside.

The cost of that mistake is paid twice: once in the departure, once in the confident wrong conclusion about why it happened. The next hire is then selected against a criterion that had nothing to do with it.

What a head office ships to Russia without noticing

For a company selling into Russia from somewhere else, this stops being an abstraction on the day the first local people are hired or the first local partner starts acting on your behalf. The strategy crosses the border as a document. The style crosses with it as an unexamined assumption.

A head office usually recognises written evidence of work. A documented process, a ticket with a history, a filled CRM, a weekly report in English, a decision recorded in the tool where decisions are supposed to live. A team formed in Russian practice frequently carries the same knowledge in a different form: verbally, through the person who holds it, in a chat thread, in a call that produces a result and no artefact. Escalation goes to whoever can decide rather than to whoever formally owns the queue.

Neither form is better in general. The trouble starts when the absence of a familiar artefact is read as the absence of work. The head office concludes that the local team is disorganised. The local team concludes that head office cares about paperwork more than results. Both are describing a style difference in the vocabulary of competence, which is exactly the misreading that empties good teams.

There is a second version of the same trap running in the other direction. A local team that has learned what head office likes to see will produce the artefact and keep the real work in the channel where it always lived. Then the reporting layer becomes a performance, the dashboards stay green, and the first honest signal about the market arrives a quarter late.

Google, Yandex and the style built into the tools

The difference has a very concrete face in marketing work, and it is worth naming because it is usually mistaken for a skill gap.

A practice built around Google grew up on self-serve documentation. English help pages, a large indexed community, public certification, an expectation that the answer to an operational question exists in writing and that the professional move is to find it. Practice built around Yandex leans more on an assigned manager and on knowledge that travels between people. A great deal of current operational detail circulates in professional chats and in conversation rather than in indexed manuals, and much of what is written exists in Russian first.

So a specialist who answers your question with a screenshot from a chat instead of a link to a manual is using the channel their market actually runs on. A head office that insists on a documented source for every claim will get slower answers and, worse, will filter out the people who know the most. The workable arrangement is to accept the channel and add one requirement on top: whatever came out of the chat gets written down once, in your language, in the place your company keeps decisions.

The same applies to the rhythm of communication. Expect more of the real coordination to happen in messengers, and expect a request phrased as a short direct instruction to land as normal rather than as rudeness. A message written in the softened, heavily hedged register that reads as polite at home can read as evasive, or as a sign that nothing has actually been decided. Directness here is a dialect, and reading it as aggression is the same error as reading a missing ticket as laziness. This is one of the points where an outside view helps, and it is the reason market entry work has to describe the local operating style as well as the channel plan.

Making style something people say out loud

What follows for anyone responsible for a team, or even for their own patch of work? First, the habit of separating the content of a request from its style. When a colleague frames a task in a way you find alien, too dry, too abstract, too emotional, the first reaction is often to file it as incompetence. Worth stopping there and asking whether this is about content at all, or whether you are simply speaking different stylistic languages inside one culture.

A manager at this level is neither the architect of the process nor a motivator nor a coach. They manage style: they notice where style supports the goal and where it quietly sabotages it, and they can translate a message from one stylistic dialect into another before it turns into a clash of personalities. This is also where a meaningful logo and an internal tone of communication come from, as an explicit statement of what used to live implicitly and therefore caused misunderstanding.

The practical step is to make the style of the company a subject of conversation rather than a default assumption. Ask it directly. Do we break things into points here, or do we move by intuition? Do we say things plainly, or do we prefer half-tones? Where does a decision become real, in the call or in the document? These questions are rarely answered out loud, and every new employee is left to guess the answers through trial and stress.

Match the answers to what the company is trying to do. A company pursuing product differentiation often needs a culture built like a rainforest: varied, tolerant of experiment, willing to forgive noise for the sake of a new species. A company pursuing predictable scaling needs a tighter and more uniform style. No style is universally better. What matters is that it supports what the company is walking towards instead of eating away at it. For a foreign company, add one more question to the list, because the honest answer is often no: which of our style requirements are load-bearing, and which are habits from a building we no longer work in?

A route and a way of walking

Strategy is a plan of the route. Culture is how people walk it: in silence or talking, in formation or scattered, trusting the map or trusting their instinct. You can draw a flawless route and still fail to arrive, if the people walking it move in rhythms that do not fit together. Seeing that rhythm before it announces itself through somebody’s quiet resignation is what working with culture means.

If you are managing a Russian operation from another country, the first useful exercise takes an hour. List the artefacts you currently treat as evidence that work is happening, and mark which ones carry information you actually use. Then ask the local team the same question about you. The gap between the two lists is your style conflict, drawn on one page, before it turns into a departure you will explain to yourself incorrectly. A working session with an outside strategist is one way to run that conversation without either side defending itself.

Frequently asked questions

Sources

• Russian version of this article on belokrylovo.ru: Почему культура ест стратегию на завтрак