The Super Mario Logic
The logic of Super Mario's levels applied to business architecture: from simple to complex, level by level.
Part 1 of 1 of the series The Super Mario Logic.

Décio Dalke Jr. — Arquiteto de negócios. Sócio-gerente no ecossistema MitUP (mitup.pt).
If you were born on planet Earth at any point in the last 40 years (or at least you’ve lived here a good while, even if you came from somewhere further away), you’ve heard of Super Mario.
It was a game that revolutionised the world of video games and became iconic for an entire generation. But our aim here isn’t to help the Italian-American plumber save his princess. We just want to borrow the psychology behind how the game builds its levels and challenges. That’s the logic and the dynamic we’re bringing over here!
Business architecture is the discipline that organises how the parts of a company fit together: business, data, tools and technology. It isn’t a wall chart — it’s what decides whether strategy survives execution. And the point where it touches every other area of knowledge has a name: Management.
You start a new game with a run of very easy levels that teach you the characters’ dynamics and the context you need. You get to know the enemies, you get to know the moves, you settle into these challenges and build an initial base of knowledge about how things move and a sense of timing and space. As the game goes on, the difficulty climbs and new enemies show up. But because you already understand how everything works and connects, the new elements slot in easily. You already know where you are, what you’re doing, and how to link the pieces. Harder? OK! I just need to get the hang of it!
That’s my proposal here too. This introduction sets the context for the content and how it’s structured. It’ll help you find the topics and see how they connect. From the easiest to the hardest. New elements will keep turning up, but you’ll already know how to “connect the pieces”. You’ll get to know the world and its scenarios. And with that, everything starts to make sense.
Why? Because the subject of business architecture is more or less like a full playthrough of Super Mario. You need a range of skills (not just AI skills), and knowledge from different places that can often look disconnected. Some subjects and areas of knowledge are careers in their own right. In other words, you can work purely in that one field (Project Management, for instance). But remember: you still need to understand the “world” you’re standing in for any of it to make sense!
What is this content about?
To share and discuss the areas of knowledge that make up business architecture from an integral, joined-up perspective. Am I going to limit myself to TOGAF? No. I’ll also talk about Business Analysis and BABOK, or Project Management and PMBOK. I want to bring a personal, experience-based view that runs across all of them.
Whose point of view is this?
Everything here can speak to a manager, to a more technical professional, or to a hybrid of the two. But the point of view behind it belongs to someone who used to be technical, now works in management, and moves between both worlds.
What’s the context behind this?
Two basic concepts sit underneath everything:
- Management is made up of People, Processes and Tools.
- Business architecture directly involves several areas: business, data, tools and technology. That’s the concept. The interface between business architecture and the other areas of knowledge happens in Management. Implementation and day-to-day management force these areas to interact at those interfaces.
Which interfaces will we cover?
- Organisational management: the practical application of the People, Processes and Tools pillar. Where everything meets. And the small everyday concepts, such as PDCA, failure analysis, the ABC curve, Pareto and so on.
- Project management: the concept of a project — it is NOT routine work; it has a specific objective, an expected end, and defined resources. In other words, almost everything is a project!
- Contract administration: operationalising the relationship between organisations properly, through contracts and the tools around them. From drafting to ongoing management. Any well-thought-out strategy falls apart if execution is mismanaged with a problematic supplier.
- Management and compliance systems: an integrated management system covering every applicable vertical — quality, environment, governance, compliance, data protection, among others. One modular machine. A new vertical means a new module, not a reinvention of the company and its business.
- Technology and Processes
- Processes as a way of organising the business (from the value chain through to implementing a management system).
- Technology as the tool that implements, operates and supports the processes.
- AI — Artificial Intelligence
- AI can’t be treated as just another technology or tool. It’s a living, individual component within a business strategy.
Other concepts
This section will grow.
What are the rules of this world?
I’ve always liked allegories and parables. I think that if you can pull the core logic out of a simpler or more playful story, by the time you reach denser material you’ll find it easier to grasp what matters, without burning time on extra explanations. If I tell you project management is interdisciplinary and cuts across every area of knowledge, I might not get through to you. If I tell you a good project manager plans a rocket launch the same way they’d plan a birthday party, I make myself understood.
I also like practical examples, so I’ll start with one of my own: some years ago we set up a training programme for planners on a project I worked on, the construction of RNEST (Ipojuca, Pernambuco, Brazil). The idea was to recruit young people from the local population and give them the content and training to work as industrial project planners. We put the training and the material together with real care and professionalism. Where did we go wrong? For many of them, the concept was too abstract. They had the theory. But their day-to-day reality didn’t contain the elements we were trying to explain. We had to swap theory for practice, and let the theory click into place afterwards, not before.
In short: don’t be alarmed if a piece here brings up witch burnings. At some point the subject will surface. And when practical examples come along, go looking for the theory that only practice can teach!
Game on?