OAC Phase 1: Work Compression

This is Part 1 of an 8 Phase Executive Development Fellowship. Reach out if you are interested in further information on the Organising Architecture and Culture Journey.

Every executive operates within an information architecture they never designed. Reports arrive because someone once decided to send them. Meetings exist because someone once scheduled them. Escalations reach the executive’s desk because the system below has no mechanism to resolve them. Over years, this accumulated architecture consumes the executive’s entire capacity — not because the work is unimportant, but because it was never designed as a coherent system. The executive becomes a processor of incoming information rather than a designer of how the organisation works. They cannot see the architecture because they are consumed by it.

Phase 1 of the OAC Fellowship — Work Compression — addresses this directly. It is not time management. It is not prioritisation training. It is the executive’s first act of architectural design: making visible how information currently flows to them and then redesigning that flow so they recover the capacity to do the developmental work that the remaining seven phases require.

The KPI tree becomes the structural instrument. As each process is mapped, the executive identifies the result KPIs that emerge from it and the process KPIs that drive those results. Managers become responsible for the result KPIs within their processes. The executive takes responsibility for the process KPIs at the connections between processes — the interfaces where one process hands off to another and where coordination either works or fails. This is the architectural distinction that most organisations miss entirely. The executive’s attention belongs at the connections, not inside the processes. When executives are consumed by what happens within processes, it is because the connections between processes have never been designed.

Each process the executive restructures recovers time — not through elimination but through design. Information that once arrived unstructured now arrives with form. Decisions that once required the executive’s involvement now have clear judgment criteria that others can apply. Escalations that once arrived because the system had no other path now have designed resolution points below the executive. The typical recovery is significant — five to seven hours per week — but the time recovery is not the primary outcome. The primary outcome is that the executive begins to see. They see the information architecture that has consumed them. They see the difference between an accumulated system and a designed one. They see where the connections between processes are the source of coordination failure, not the processes themselves

The method is constructive, not reflective. The executive does not journal about their information overload. They build, one process at a time, the architecture of how information should reach them. They select a process or a meeting where things are unclear — where information arrives misty rather than structured — and begin to create form. They map the workflow, identify who owns each step, establish what the output of each step should be, define the judgment criteria that determine whether the output is good or bad, and design the routine through which that information reaches them. The team members reporting into this process develop the patterns of interaction — the disciplines of how they present information, where in the process they apply their own judgment before escalating, and what the executive actually needs to see versus what has been arriving by habit.

This first act of architectural design is deliberately personal before it becomes organisational. The executive redesigns how information flows to them, which teaches the method through direct experience. By the time they reach Phase 2, they have not merely learned about information architecture in a classroom. They have practised it on their own leadership environment and produced measurable results. They have built KPI trees that trace from strategic intent to daily signal. They have designed routines that develop their team’s capability rather than merely reporting status. And they have recovered the capacity — both in time and in perception — to turn that same architectural lens on their organisation, which is the work of the phases that follow.