How you picture a company is how you run it

One executive describes the company as a well-oiled machine. Another calls it a living organism. A third sighs: “we have our own culture here, nothing to be done about it.” Three metaphors, and in practice three different companies, even if all three are talking about the same office with the same people in it.

These are not slips of the tongue or a matter of style. They are a diagnosis. Gareth Morgan, in Images of Organization, showed that the way a person mentally pictures an organisation is the way they will manage it. The metaphor is not decoration. It is a working tool that decides in advance what you will do with people, resources and crises. Change the metaphor and a different set of actions appears in your hands.

For a company that sells into Russia from another country, this is a practical question rather than a philosophical one. The head office holds one image of its Russian operation. The local team holds another. The market itself, with its own platforms and habits, keeps insisting on a third. Most of the friction I see in such projects comes from those images never being said out loud.

Why the metaphor matters more than it seems

A manager rarely states their metaphor aloud. It hides inside routine phrases: “tune the process”, “motivate the team”, “build up competencies”, “work on the culture”. Behind each phrase is an entire model of what an organisation consists of and what inside it can be influenced at all.

If the organisation is a machine to you, you will look for a fault in the process and repair the procedure. If it is an organism, you will look for an unmet need and negotiate. If it is a brain, you will find where the information got distorted. If it is a culture, you will look at whose style suppressed whose. The same problem, say low engagement, will receive four different diagnoses and four different remedies, depending on which metaphor is running in your head.

Morgan describes eight such images. Four of them line up into a coherent sequence, from the most rigid and mechanical view to the most fluid and stylistic.

How the manager’s job changes with the image

As you move from metaphor to metaphor, the view of the company changes, and so does the actual work of the person running it.

The organisation-as-machine needs a process architect. Their job is specification: describe who does what, in what order, to what standard. This is where a bureaucratic apparatus is born, in the functional rather than the pejorative sense of the word: a structure that holds predictability in place.

The organisation-as-organism needs a motivator. Regulating it is pointless. You have to negotiate with it, understand its needs, synchronise its efforts with the environment. This is where an HR function appears, and with it the first notion of strategy: not an order, but a reconciliation of interests.

The organisation-as-brain needs a coach. The company here is a self-learning system with information flows and predictive analytics, and the manager’s task is to grow its ability to recognise signals and learn faster than the market. This is where a corporate university appears.

The organisation-as-culture needs someone who manages style. Not process and not motivation, but the way things are done in this company: loudly or quietly, in a structured way or spontaneously. This is where a meaningful logo and an internal style of communication appear. What used to form on its own is finally spoken aloud.

Morgan’s list continues beyond these four: the organisation as a political system, as a psychic prison, as flux and transformation, as an instrument of domination. Each has its own kind of manager, a mediator of ideology, a facilitator of self-organisation, an environmental strategist, a legislator of the rules of the game. For practical work it matters less to memorise all eight than to catch the principle itself. A metaphor does not describe reality neutrally. It prescribes what you will do next.

One situation, four answers

Picture a simple situation: the team keeps missing project deadlines.

The process architect sees a hole in the procedure. The instruction needs clarifying and a checkpoint needs adding.

The motivator sees a shortage of meaning or resource. You need to find out what is really getting in the team’s way, and agree rather than push.

The coach sees a gap in information. Someone does not know what another department knows, so the fix is to set up knowledge exchange rather than punish the slip.

The manager who works with style sees a clash of working cultures inside the team. One person loves structure, another works in inspired bursts, and without a shared language their tempos collide. The thing to align is not the deadline but the way of working together.

None of these answers is “correct” in a vacuum. Each one works if the nature of the problem has been read correctly. The mistake is not choosing the “wrong” metaphor, because a metaphor is always partly true. The mistake is applying it without thinking, in a place that calls for a different one.

The Russian operation seen from abroad: the machine by default

Here the topic stops being general and becomes specific to companies entering Russia. Distance shapes the image. When an operation sits several time zones away, speaks a language the head office does not read and reports through a spreadsheet, it is easiest to picture it as a machine: a set of processes that worked at home and now need to be replicated with local inputs. The website gets translated. The Google Ads structure gets copied into Yandex Direct. The local team receives a specification and a reporting cadence.

The Russian environment, meanwhile, keeps behaving like something that needs to be negotiated with, which is the organism’s demand. Search here means Yandex first, with its own auction, its own quality signals and its own way of reading a landing page. A meaningful part of the buying conversation moves into Telegram and WhatsApp rather than email. Marketplaces and aggregators occupy the paid slots above your listing and intercept the demand you created. None of this is a fault in the procedure. It is an environment with needs of its own, and a machine image has no vocabulary for that.

The brain’s demand is there as well. Yandex Metrica, Wordstat and the search query reports produce signals that the home office analytics stack does not know how to read, and often does not receive at all because the tracking was set up for Google. A company that manages its Russian operation as a machine will file those signals as noise. A company that manages it as a brain will treat them as the fastest available lesson about local demand.

And the culture is the last thing to be noticed, because nobody thought it needed managing. The local team has its own tempo and its own way of saying “yes” that may mean “I heard you”, and the head office reads this through its own style. The collision looks like missed deadlines or thin reports. It is actually two working cultures that were never introduced to each other.

The typical failure pattern is one mismatch in each direction: the head office applies a procedure to a problem that is really an unmet local need, and the local team asks for “understanding” where what the head office actually needs is a clear specification. Both are right about what they see. Both are using one metaphor in a place that calls for another.

How to tell which metaphor you are thinking with

The practical benefit here is simple. Before fixing a problem in a team, or in a distant operation, ask yourself which metaphor you are currently reading it through. Not “what happened”, but “how am I picturing what happened”.

If you catch yourself thinking “let’s just write the procedure more clearly”, that is the machine. If it is “we need to understand what they lack”, the organism. If it is “let’s get the departments exchanging information”, the brain. If it is “it is not about the tasks, it is about how we are used to working here”, the culture.

A conscious choice of metaphor is not abstract philosophy. It is a saving of effort. A company that applies a rigid procedure to a live motivational gap gets new resistance instead of a solution. A company that tries to cure a clash of styles with a corporate university gets polite incomprehension instead of results. A company that responds to a local market’s needs with a thicker reporting template gets a fuller spreadsheet and the same sales.

For a foreign company in Russia I would add one specific habit: before each quarterly review of the local operation, name the image out loud. If the review is a list of process deviations, you have decided it is a machine. Then ask whether the problems on that list are really process problems, or whether they are the environment asking to be negotiated with. That single question often reroutes the whole conversation, and it belongs at the marketing strategy level rather than in the campaign account.

One metaphor does not cancel another

An organisation does not choose once and for all to be a machine or a brain. It passes through these images, sometimes returning, sometimes holding several at once in different parts of itself. The production floor lives as a machine, the product team as a brain, and the company party exposes a culture that nobody has ever put into words.

A Russian operation of a foreign company is the same in miniature. Order fulfilment and compliance genuinely are a machine here, and should be specified like one. Sales and partner relations are an organism. The work of reading Yandex data and translating it into decisions is a brain. And the way the local team and the head office talk to each other is a culture that will assert itself whether or not anyone manages it.

The manager’s task is not to find the single true image of the company. It is to learn to recognise quickly which metaphor is currently steering their own view, and to change it in time. That is what ongoing marketing support for a Russian operation mostly consists of: noticing which image is running the conversation this month, and asking whether it fits the problem.

Later in this series: the four metaphors in detail, machine, organism, brain and culture. Each with its own logic, its own crisis, and its own type of error that a manager makes when they stay inside one image for too long.

Frequently asked questions

Sources

• Russian version of this article on belokrylovo.ru: Как вы представляете компанию, так вы ей и управляете