Context
A client at one of Indonesia's prominent digital banks asked me to write something for her team. She had taken System Work Level 2 herself and wanted to sponsor the course for her directors, VPs, and middle managers. Fully paid. All they had to do was show up. The problem, as she described it, was predictable. They'll say they're too busy. In a heavily operational bank, this is the default excuse, and it is not entirely dishonest. There is always something urgent. There is always a reason to stay at your desk. Though as she pointed out, the same people who can't leave operations for four days somehow manage a week in Japan without the bank closing down. Level 2 is a different course from Level 1. Where Level 1 works at the scale of the individual and the one-on-one, Level 2 focuses on groups and systems. If you finished Level 1 and felt a kind of helplessness when you looked up from yourself toward the larger organization, that's not a failure of the course. It's the honest limit of what Level 1 was designed to do. Working at the system level asks for different skills and a different lens. So I wrote this for them. Not to convince, exactly. More to name what they already feel but haven't yet decided to do anything about.
You already knew something was off. A tightness in your chest during a meeting you couldn’t explain. A conversation with a colleague that went sideways and you couldn’t figure out why.
You started to be aware more after Level 1. You started naming what you feel. You started noticing your body. You began to see that the language you use doesn’t just describe reality but makes it.
And then you went back to the operational rhythm. The approvals, the committees, the quarterly targets. You probably told yourself what most of us tell ourselves: I’ll apply what I learned when I have the time. And around you, most of your colleagues haven’t done this work at all. They haven’t sat with what Level 1 asks you to sit with. So when things go wrong, the instinct is familiar: the problem is out there. It’s the other department, the unreasonable client, the boss who doesn’t listen.
But here is the honest part. Level 1 gave you clues about yourself and the person sitting across from you. The intra and the inter. Yet your job rarely stays that intimate. Most days you walk into rooms with eight, twelve, twenty people, and something else takes over. The dynamics get larger and stranger. You find a director who speaks and everyone goes quiet, not because they agree but because disagreeing feels unsafe. You watch an initiative die slowly across three departments because no one can name what’s actually stuck. You see a team that delivers on its KPIs and is still, somehow, not okay. These aren’t problems between two people. They’re patterns in the system.
You know better, or at least you’re starting to. You’ve seen enough to suspect that we are always part of the system we’re trying to fix. That before we diagnose what’s broken around us, it helps to notice what we’re bringing into the room ourselves. And yet, the problems you face daily are real system problems. And they don’t respond to harder work or better spreadsheets.
Level 1 gave you a way of seeing yourself inside a system. Level 2 gives you a way of reading the system itself. You get to witness, in real time, what the old saying ‘culture eats strategy for lunch‘ actually looks like when it happens in a room. You learn to notice what a group is doing beneath the surface of its agenda. You learn to see where power is concentrating, where trust is thin, and where the unspoken rules are shaping more behavior than the written ones. You learn to build what the course calls containers: intentional spaces where real work, the kind people avoid, can actually happen.
I know you’re busy. I know the thought of four days away from operations feels irresponsible. But consider the cost of the alternative. Consider how many meetings you’ve sat through this month that moved nothing forward. Consider how much energy goes into managing people problems that keep coming back because they were never really diagnosed.
This is not a soft-skills retreat. It is a experiential course in organizational perception. You learn to see what’s actually happening in your system, and to intervene with the precision that the situation demands.
Your colleague who sponsored this believed it would matter for you. She went through it herself and decided it was worth offering to the people she cares and works with every day.
That says something. Four days is all she’s asking. The only real question is what you’ll keep choosing not to see.