By Décio Dalke Jr. · Oct 2026

World 1 of Organisations, level 1: where it all begins

Managing a company starts with a client's problem, internal or external, and with the tripod of people, processes and tools. The organisation chart comes later.

Part 1 of 3 of the series World 1 of Organisations.

It all starts with a problem — pixel-art three rooms at different heights, joined by grey pipes hidden from outside

Décio Dalke Jr. — Arquiteto de negócios. Sócio-gerente no ecossistema MitUP (mitup.pt).

World 1 of Organisations — level 1 of 5: level 1 · level 2 · level 3 · level 4 · level 5

In the first world of Super Mario there are green pipes scattered across the level. Some lead to rooms you can’t see from outside, others drop Mario back at a point further ahead. First-time players walk past them without suspecting a thing, and only later realise the world is much bigger than the screen shows.

An organisation works in a similar way. What an outsider sees is the organisation chart, the job titles and the tools. Yet what connects one department to another is rarely drawn anywhere, and those pipes are exactly where the work flows.

This section of the blog is about managing that world. Before any management tool, it is worth understanding what, after all, is being managed.

What is business management, once you strip out the buzzwords?

Business management tends to come wrapped in big words: vision, alignment, synergy, a results culture. Hardly any of them help someone who has a company to run on Monday morning.

I prefer a shorter definition. Managing an organisation means making sure it solves someone’s problem, every day and in a repeatable way, and that it keeps solving it when people change, volume grows or the market turns.

Notice that systems, methodology and the organisation chart were left out of that definition on purpose: they come in later, to serve that sentence.

What problem does the company solve, and for whom?

A business starts when we solve a client’s problem. The same goes for an internal solution: a process is born to serve a client, and the internal client counts too.

I have started a few businesses from absolute zero. An idea, zero processes and controls. In every one of them, the first useful question was the same: what problem are we solving, and for whom? The answer shapes everything that follows, from who gets hired to what gets measured.

When that question goes unanswered, the company keeps working, although it ends up working for itself. Reports exist because they have always existed, approvals turn into ritual and each department defends its own patch. Nobody is doing anything wrong, and even so the client feels it.

What comes before and after each process?

Every process receives something from someone in order to start and hands something over to someone so the work can carry on. You always have to think about what comes before and what comes after.

Whoever designs a process looking only inside it tends to optimise the wrong part. The step gets faster, while the queue builds up right after it, in the department that receives the output. The process improved on paper, and the company is still waiting in the same place.

Before changing anything, it pays to ask where the process’s input comes from and where its output goes. Those links are Mario’s pipes, joining parts of the world that can’t see one another.

People, processes and tools: why is the tool only a third?

Every solution in an organisation rests on a tripod: people, processes and tools. You always have to build with all three in mind.

The most common move is to start with the tool, because it can be bought, installed and shown in a presentation. Visible as it is, on its own it only automates what already existed, confusion included. A well-designed process without people prepared for it stays on paper. And good people without a process depend on heroics, which work until the day someone goes on holiday.

When one of the three legs is missing, the other two carry the weight for a while, until they give way.

Organisational structure: does the organisation chart show how the company works?

Organisational structure is the way a company divides work and authority: who reports to whom, who decides what, where each function sits. The organisation chart is the drawing of that structure, and it has its value, because it shows hierarchy and responsibility.

What it shows very little of is the path the work takes. A client order goes through sales, operations, purchasing and finance, and none of those hand-offs appears in the boxes. The chart tells you who is in charge; the flow of work tells you how the company delivers.

That is why structure comes after the problem and the process. First you understand what needs solving and where the work flows, and only then do you decide how to organise people around it.

Where do organisations lose their way without noticing?

Almost always in the hand-offs between departments. Each team does its part, hits its own indicator and closes the month in the green, whereas the client waits longer than they should and nobody can say where the time went.

The second place is the tool that arrives before the question: the system is bought to solve a problem nobody has put into a sentence, and then the problem is bent to fit the system.

The third is growth. What worked with five people, because everyone talked to everyone, stops working with fifty, and the company only notices once the friction has already become a cost.

In projects, the opening question was what will exist at the end that doesn’t exist today; in operations, however, the question comes back every day: what problem are we solving, and for whom.

So what comes next?

The rest of this world follows the order in which the game teaches:

  1. Knowing where the organisation stands before changing it (level 2, the diagnosis).
  2. Choosing what to tackle first, when everything demands attention at once (level 3).
  3. Improving in cycles and holding on to the gain (level 4).
  4. Deciding where the organisation is going (level 5, strategic planning).

Management tools appear along the way, each one in the level where it answers a question.

Quick questions

What is business management? Making sure the company solves a client’s problem in a repeatable way, and keeps solving it when people, volume or the market change.

What is the tripod of people, processes and tools? The three legs of any solution in an organisation. A tool on its own automates what already exists, mistakes included; it needs a designed process and prepared people.

What is organisational structure? The way a company divides work and authority. The organisation chart draws that division, but shows little of the path the work takes between departments.

Does an internal client count as a client? It does. An internal process is born to serve someone, and that someone is who tells you whether it works.