How The World Really Works

Understanding Real-World Power Structures

Most people think the world runs on rules, treaties, and stated intentions. It doesn't. It runs on leverage, incentives, and the things people are willing to do when they think nobody is watching. Learning to see through the noise is the difference between being surprised by events and having a reasonable idea of what happens next.

I used to work in corporate strategy, then moved into international consulting. Early on, I kept getting blindsided by deals that should have worked on paper and completely fell apart in practice. The problem wasn't my analysis of the surface-level facts. It was my failure to map the actual incentive structures beneath them. Once I started asking the wrong questions differently, everything got clearer. Take trade agreements. On paper, they exist to promote mutual prosperity. Operationally, they are negotiation artifacts where each side carved out exemptions for politically sensitive sectors. The survival layer is what really determines outcomes: which industries can threaten electoral outcomes or regime stability, and therefore which concessions are non-negotiable regardless of economic logic. I learned this the hard way during a supply chain project in Southeast Asia. We had modeled a facility relocation based purely on cost arbitrage and labor availability. The government approved it, the numbers worked, and then local labor unrest hit — not because wages were low, but because a rival faction within the ruling party used the foreign investment as a political weapon. The deal didn't die from economics. It died from internal power dynamics we hadn't mapped. The workaround was straightforward once you know to look for it: identify the patron-client networks behind formal institutions, trace who benefits from the status quo, and model your risk around their incentives rather than the official ones. The formal layer is what you see in textbooks and press releases. Laws, treaties, official statements, organizational charts. This layer exists for legitimacy and record-keeping. It is useful for understanding what people claim, not what they will do.

The operational layer is where actual decisions get made. Budgets are allocated here. Personnel moves happen here. Deadlines are set and missed here. This layer often contradicts the formal one. A company may publicly commit to sustainability goals while its procurement team receives bonuses tied exclusively to cost reduction. Both statements are true. The operational layer is the one that determines outcomes. The survival layer is the deepest and most important. It asks: what keeps this person or institution in power? For a CEO, it might be board confidence or stock price. For a minister, it might be coalition stability or electoral districts. For a corporation in an authoritarian market, it might be the relationship with a specific regulatory body. When survival is threatened, operational logic and formal commitments get discarded. This is not corruption. This is baseline institutional behavior.

How to Map These Layers in Practice

The technique is simpler than most people think. Stop reading what organizations say and start tracking what they fund, hire, and punish. Budget allocations reveal priorities faster than any press release. Hiring patterns show where the real decision-making authority sits — the org chart on the website is almost never accurate. Punishment patterns are the most revealing of all. Watch who gets let go and for what reason. The stated reason is almost always different from the real one. I developed a simple framework I call reverse-incentive mapping. You start with an outcome — a policy change, a market entry, a regulatory decision — and work backward to identify who actually benefited. Not who was credited. Who benefited. The beneficiary is usually the decision-maker, even if they never appeared in the official process. This method took me from spending three weeks researching a country's investment climate to three days, because I stopped reading the promotional material and started tracing money flows and personnel rotations.

Common Pitfalls

The biggest mistake people make is assuming rationality. Systems are not rational. They are adaptive. They respond to incentives, yes, but those incentives are often misaligned, outdated, or contradictory within the same institution. A finance ministry may demand cost cuts while a security ministry demands expanded capabilities with the same budget. The resulting decisions are not rational. They are compromises that reflect internal power balances. Another pitfall is over-relying on public data. Official statistics are curated. Economic growth figures, unemployment rates, trade balances — these are political artifacts as much as measurements. I once reviewed a country's economic forecast that looked solid on paper. The underlying assumption was that export revenues would remain stable. Two months later, a single regulatory change by an unrelated ministry cut those revenues by forty percent. The forecast had no visibility into that ministry because it didn't appear relevant to the analysis. Relevant is not the same as decisive.

When This Framework Fails

It fails in situations of extreme information control, where the survival layer is completely opaque and no reliable indicators exist. Small totalitarian states with tightly controlled media and no independent institutions fall into this category. It also fails in genuinely novel situations — paradigm shifts, technological disruptions, or black swan events where no historical precedent exists for the incentive structures. In those cases, the best you can do is monitor for early signals of structural change and update your models aggressively. Waiting for certainty is how people get caught off guard. A more reliable approach in high-uncertainty environments is to build scenario trees rather than predictions. Instead of forecasting one outcome, you map three or four plausible paths with the triggers that would signal movement from one to another. This doesn't eliminate surprise, but it reduces the time between event and response from weeks to days.

A Practical Example

Let me walk through a recent case. A European firm wanted to enter a West African market. The public narrative was about growing middle-class consumption and favorable demographics. Standard market entry analysis. But the real question was who controlled the licensing process and what kept them in power. I traced the procurement approvals for three major infrastructure projects over five years. The pattern was clear: contracts went to firms that employed a specific consultancy, which was linked through a shared director to the ministry overseeing licenses. The consultancy itself was a small operation with no technical advantage. Its value was entirely relational. The firm's initial plan was to compete on price and technology. That would have failed. The adjusted approach was to partner with the consultancy's primary competitor, which had equal access but was positioned as less threatening to the ministry's political interests. The deal closed in four months instead of the estimated eighteen. The difference wasn't better product. It was understanding who actually decided and what they needed to stay in position.

What to Read Next

If you want to go deeper, start with Mearsheimer's work on offensive realism for the geopolitical layer, then move to Williamson Roderick's research on organizational behavior for the institutional layer. For the operational level, none of the academic literature really covers it because it is almost never documented formally. The best source is actually trade press and regulatory filings — the dry, boring documents that nobody reads carefully. Those contain the raw data of what actually happened, stripped of the narrative polish. The world does not reward people who understand the surface. It rewards the people who spend the extra hour tracing the incentive behind the decision. That hour saves you months of rework later.