Skip to content

AI structures. You shape.

How leaders use AI to clarify responsibility, protect their own time, and maintain interfaces — the daily, non-delegable work that keeps a function running.

Organizing is one of the core leadership tasks — and it sits in direct connection to objective-setting. A leader who sets objectives without creating the conditions to reach them has not finished the work. A leader who creates conditions without clear objectives organizes into a void. This is not about large structural questions or reorganization projects — it is about the daily, often unnoticed work that determines whether the people in your function know on Monday morning what they are working on, whether they have the means they need, and whether the interfaces to other functions actually function. What changes now that AI sits inside the apparatus is that routine coordination becomes radically cheaper. What does not is that responsibilities have to be clarified, that interfaces have to be maintained, and that your own time as a leader is itself part of the task.


Why organizing stays a leadership task — even with AI

Drucker captured the core in three questions every leader should put to their function on a regular basis: Is the customer at the center — and staying there? Can your people deliver their contribution? Is top management attending to the important things? The questions sound simple; they are hard to answer in practice and harder to keep answering with a yes. Asked honestly, most leaders find more friction, more unclear ownership, and more lost time than they would have liked. That is the entry point of the task.

Organizing as a continuous leadership task has three dimensions that work together and require equal attention:

  • The work of the function — who does what, with whom, by when, with which means, at which interface.
  • The leader's own work — what you spend your time on, what you hand off, what you let go of, how you stay decision-capable.
  • The connections outward — to other functions, customers, suppliers, units that enable or block your work.

Drucker laid out a principle on accountability that has not aged: the duties, authority, and responsibility of a position must match each other. International organizational practice formalizes this as the congruence principle. Whoever carries responsibility needs the authority to exercise it; whoever has authority should answer for its consequences. The principle is also the precondition for any effective delegation: when you hand off a task, you must hand off the authority and the responsibility with it. Hand off the work but keep the responsibility, and you have not delegated — you have distributed work, and the outcome still rests with you. From this follows a simple but hard test: every task in your function must clearly belong to a position. Where this is unclear, the typical symptoms appear — duplicate work, waiting times, status meetings without substance, escalations that needlessly bind the top. Many problems described as „communication problems" are in truth organizational problems: responsibilities have not been clarified.


Whatever organizational form your function operates in — the daily task is yours

„Every reorganization is an admission of failure. It should be the last, but not the first, resort." (Drucker) Reorganizations cost a lot and often deliver little. They are justified when strategy or market shifts fundamentally, or when existing structure systematically blocks performance. They are not justified as occupation therapy for the executive floor. The continuous organizing work is the quieter, more important task — and it sits before any methodological choice:

Approach When it works best Risk if misapplied
Classical organizational structures
(line, function, division, matrix)
Stable value creation with clear reporting lines, predictable processes, and unambiguous accountability — the default in most established firms Once interfaces are unclear, the work is patched through meetings, distribution lists, and informal channels — the actual organizing quietly migrates into the apparatus
Process and value-stream organization
(Lean, Six Sigma, TPS)
Industrial value creation with clear bottleneck logic and customer orientation as a structural principle Hard to transfer to knowledge-intensive functions where work cannot be modeled as a value stream
Agile and self-organization models
(Scrum, SAFe, Spotify model, Holacracy, Sociocracy 3.0, Teal)
Short cycles, high team accountability, purpose orientation as an explicit structural feature In scaled variants, a bureaucracy of rituals, roles, and synchronization meetings emerges that quietly walks back the original promise

Cutting across these sits Stafford Beer's Viable System Model, with viability as the standard — VSM logic is increasingly part of the organizational debate. Likewise across them sit the tools for assigning work: the functional matrix in continental practice, RACI in the international canon, supplemented by role descriptions. They force explicit assignment — and lose their effect once they are kept as a compliance exercise instead of a leadership instrument.

Three settings relieve the self-image of this task. First: there is no „good" organization. All forms produce conflict, coordination overhead, interfaces, and friction. Real organizations are hybrids of multiple base forms, not pure textbook models. The choice is not between good and bad organization, but between worse and less-worse. Second: good management produces remarkable results within weak structures — bad management cannot be compensated for by good structure. Third: „organizitis" — the constant restructuring to keep things in motion — is not dynamism, it is a leadership failure. Knowledge workers need stretches of stability and quiet to deliver substantive work; constant restructuring produces precisely the inertia it claims to fight.

A standard catalogue of symptoms tells you whether your function has an actual organizational problem — and not merely a leadership one: the proliferation of management layers, constant talk about „cross-functional working", meeting density, overstaffing, a growing demand for coordinators and assistants, role designs of the „a bit of everything" kind. This catalogue is more current today than twenty years ago — amplified by hybrid work, scaling bureaucracy, and method-of-the-month thinking.


Organizing with AI: what speeds up, what stays human

AI does not change the what of organizing — it shifts the how. Drucker's three questions — customer, people, top management — remain the lens; AI does not move the questions, it moves how much of them can actually be answered.

What AI handles reliably

  • Visibility of symptoms — meeting density, ad-hoc rate, escalation patterns, response times at interfaces, process bottlenecks are readable from the systems where work already happens. Process Mining (van der Aalst, Celonis) and Organizational Network Analysis (Cross, Connected Commons) are the established disciplines.
  • Reducing meeting load — without touching the core — aggregation, minutes, handoffs into downstream systems: AI takes the organizational portion of a meeting down sharply. The core (negotiation, conflict, decision) it does not. Microsoft's Work Trend Index 2025 shows that without deliberate steering, the trend runs the other way: more meetings, scheduled at shorter notice, often outside core hours.
  • Maintaining work assignments instead of letting them rot — functional matrices and RACI grids are static and quickly age. AI helps in two places: ongoing maintenance of these documents, and in what McKinsey discusses as dynamic RACI — connecting formal assignment with real-time data on actual processing and surfacing discrepancies before they escalate. Diagnosis, not control.

What stays with the human

  • The architecture of accountability — who carries what, where the human stays in the loop, where the system acts autonomously, where the handoff gets documented. These cannot be answered by the system itself. They are leadership decisions with legal, cultural, and organizational consequences.
  • Quality judgment — AI produces formally correct output effortlessly. What gets called AI slop — formal correctness without substance — is not produced by AI; it is produced by the absence of judgment. Passing AI drafts on unchecked is not delegating work, it is delegating responsibility.
  • Negotiation and relationship — where functions hold different objectives, where change touches habits, friction emerges that gets resolved in conversation. Trust forms through consistent behavior over time. AI can prepare and follow up; the encounter itself it does not replace.
  • Consciously shaping pace — AI accelerates operational work. Whoever follows the system's tempo gets brain fry (BCG, Bedard et al., 2026): cognitive exhaustion precisely where AI eases execution, while judgment remains — and judgment is more demanding than execution. High performers are disproportionately affected. What stays synchronous and what runs asynchronously is a leadership decision.

The real risk is not faulty AI suggestions — it is the breach of the congruence principle. The principle was designed for human positions: duty, authority, and responsibility in one hand. When an agent executes, the three split: execution at the agent, authority in the system, responsibility still with the human. RACI cells stay formally fillable; what shifts is what those letters actually stand for. Without explicit clarification, false accountability follows — organization that works on paper and not in practice. On top of that come the regulatory guardrails: the EU AI Act (high-risk obligations for personnel decisions — selection, promotion, evaluation, termination — most apply from 2 August 2026), EU co-determination regimes (Germany under §87 BetrVG, similar frameworks in Austria, the Netherlands, and other member states require employee representation involvement once systems can monitor behavior or performance), non-discrimination law (Germany's AGG and EU equivalents covering indirect discrimination through proxy variables). These frames are not a brake — they are the precondition for use.

Mid-term, the organizing task itself shifts: McKinsey describes the agentic organization, in which agents execute workflows and coordinate other agents. MIT Sloan paints the emerging agentic enterprise with a dense middle management layer — the role moves from passing information forward to orchestrating agents and tending the human interfaces between them. A double orchestration emerges: the human orchestrates agents, which in turn coordinate sub-agents. Responsibility, judgment, and negotiation remain human — the layers through which they act simply go deeper. This is not the everyday reality in most mid-cap firms in May 2026. It is the direction.

You want to clarify responsibilities in your function, reduce your meeting load, and protect your own time under AI's tempo — without losing accountability to agents that cannot carry it?
Let's talk about your leadership team →


Better organizing with AI: coaching, leadership development, and workshops

I work on this topic in three formats: in executive coaching, in leadership development programs, and in leadership workshops for intact teams — from mid-cap to enterprise, anchored in Drucker's management thinking, the cybernetic tradition of self-regulation, and the regulatory guardrails for AI use. Some of the underlying framings I share at international leadership events, including ATD APC Taipei 2025. „Organizing" is rarely booked as a training topic. It surfaces when you look behind meeting fatigue, reorganization pain, or AI pilot programs. Five questions sit at the center of every format:

  • Where are responsibilities in your function unclear? The congruence check, applied to each central task: are duty, authority, and responsibility in one hand? Wherever this falls apart, you find almost every „communication problem" you observe.
  • Which meetings do you actually need? Before any automation, the question of whether the meeting is needed at all — effectiveness before efficiency. Whoever runs unneeded meetings faster with AI is efficient, not effective.
  • Where does AI shift the architecture of your accountability? Which tasks are or will be handled by an agent — and which human accountability remains? Which co-determination, EU AI Act, and equal-treatment questions need clarifying before a pilot enters production?
  • Where are you directing the AI dividend? The freed capacity does not flow into productive work by itself. Default is more of the same — more meetings, more reports, more drafts. Conscious direction creates room for judgment, relationship work, and exploration.
  • How do you organize your own time when AI accelerates the day-to-day? Drucker placed the leader's own time as the first material of leadership work — the question „what do I spend it on, what do I hand off, what do I let go of" sharpens, not softens, under AI acceleration. This is the layer where brain fry forms — or is prevented.

What you take away is not a new method — but a sharper view of what actually needs to be organized in your function, and which routines you should drop, keep, or rebuild under AI conditions.


7 practical routines for better organizing with AI

Small habits you can start immediately.

1. Three-questions check (quarterly, 60 minutes)

Apply Drucker's three questions honestly to your own function: Is the customer at the center — and staying there? Can your people deliver their contribution, or are they trapped in the apparatus? Is top management attending to the important things, or sinking into operations? AI can supply the state on each question from operational data — customer-conversation sentiment, meeting density per person, share of strategic versus operational topics on calendars. The judgment is yours. With each quarter, the picture sharpens.

2. Symptom audit (annually)

Walk through the standard catalogue: proliferation of management layers, constant talk about cross-functional working, meeting density, overstaffing, growing demand for coordinators and assistants, „a bit of everything" role designs. AI provides the data from calendars, ticketing, project, and email tools. Where symptoms cluster, diagnosis begins — not reorganization. Whoever restructures without a symptom finding trades one problem for several new ones.

3. Meeting audit (annually, half a morning)

Every recurring meeting gets reviewed: Do we actually need it? Who needs the outcome? What gets decided here, what only aligned? What can run asynchronously? What does not need to take place gets retired, not automated. Rule of thumb: anyone unable to state the purpose of a meeting in one sentence has produced the proof of its expendability.

4. AI-pause block (daily or weekly, fixed in the calendar)

60 to 90 minutes of focused work without AI tools: notifications off, sidebar suggestions closed, pull instead of push. Whatever the AI offers during the pause is collected at the end of the block. Protecting concentrated work is a leadership discipline, not a comfort question — it gets modeled, or it does not happen. The routine is the most effective antidote to the brain-fry effect.

5. RACI with AI lane (ongoing, plus a weekly agent check)

For each central task, an additional column in the functional matrix that makes visible where AI prepares, suggests, or executes. The AI lane is never the carrier of accountability — that stays human. Maintaining the matrix itself can be handed to AI. Where agents are running in production, add a brief weekly agent check — performance, deviations, escalations from the prior week.

6. Decision log for AI-assisted decisions (ongoing)

For every relevant decision in which an AI system delivered recommendations, a short note: What did the system recommend? What was decided? On deviation, with what reasoning? A column in your project system or a single spreadsheet is enough. Three functions: traceability for co-determination and oversight, a learning loop on the quality of AI recommendations, protection against false accountability.

7. AI-dividend balance (quarterly, 30 minutes)

A quarterly accounting: Which routine tasks did AI take on this quarter? How much capacity was freed? Where is it flowing now — into more of the same, or into work that previously wasn't happening? The question forces explicit direction instead of leaving it to the default. Efficiency that everyone has is not an advantage. Where the surplus flows is a leadership decision — not a tooling question.


Leadership development, coaching, keynote — how we work together

Leadership development & workshops

For leadership teams recalibrating their organizing practice under AI conditions — anchored in your real functional matrix, your meeting cadences, and the interface architecture of your business, not generic cases.

See programs →

Executive coaching

For individual leaders looking to clarify accountability, reduce meeting load, or set up an AI pilot with a clean architecture — confidential, with a sparring partner who has no stake in the outcome.

Schedule a conversation →

Keynote

For leadership conferences opening the conversation on accountability, meeting load, and AI use in the organization. No hype show — an honest look at what leadership requires in the AI era.

Request a keynote →


Common questions on organizing, RACI, and AI in collaboration

How do I know whether my function is actually well-organized?

Drucker's three questions are the diagnostic core: Is the customer at the center — and staying there? Can your people deliver their contribution, or are they trapped in the apparatus? Is top management attending to the important things, or sinking into operations? Three honest yes answers mean the function is organized at its core. If, on the other hand, the standard symptoms cluster — meeting overhead, constant talk about cross-functional working, growing demand for coordinators, „a bit of everything" roles — there is an organizing problem. The answer is almost always continuous tending: sharpen accountability, make interfaces explicit, thin out meetings — not a structural project. AI can deliver the state on each question from operational data; the judgment is the leader's.

How do I distribute responsibility when an AI agent takes on tasks?

The congruence principle does not transfer to agents. AI can execute tasks — it cannot carry responsibility. Every assignment must keep visible which person stands behind the outcome, even when part of the work is done by a system. Practically: an additional AI column in the functional matrix that makes visible where AI prepares, suggests, or executes — with a note that this column is never the carrier of accountability. One human owner per agent. Plus a decision log for AI-assisted decisions, which holds up under co-determination scrutiny and prevents false accountability.

How do I cut meetings without losing information?

The first question is not how a meeting becomes more efficient, but whether it is needed at all — effectiveness before efficiency. Anyone unable to state the purpose of a meeting in one sentence has produced the proof of its expendability. Where a meeting really is needed (negotiation, conflict, decision), AI takes the organizational portion down: aggregation, minutes, handoffs into downstream systems. Pure status updates run asynchronously — AI summarizes, the recipient reads when it suits. What remains are the formats that require actual negotiation. Practical experience: the annual meeting audit alone typically reduces meeting load by 20 to 40 percent — without losing information.

Do I need a separate AI column in my functional matrix or RACI?

As soon as an AI agent runs regularly within a task: yes. Without that column, the handoff from human to system stays unclear — who reviews which suggestions, who carries the consequences. With the column, false accountability becomes visible: if no one is responsible for overruling the system, the system is effectively the decision-maker — even if the formal matrix says otherwise. Important: the AI column is a diagnostic and design aid, not a position of its own. Accountability stays in one of the human columns.

Will AI make middle management redundant?

It changes — it does not disappear. MIT Sloan's emerging agentic enterprise shows a denser middle layer: the role shifts from passing information forward — which AI does in its sleep — to orchestrating agents, tending the human interfaces between them, and shaping the architecture of accountability. That is more demanding than information passing, not less. Whoever defines middle management as „relayers of directives downward" will indeed lose the role. Whoever understands middle management as the architect of the function gains room to operate — provided they don't refill that room with the operational details the faster system has only just made visible.

How do I protect deep work against AI's acceleration?

AI accelerates operational work — the temptation to follow the system's tempo is significant. Counter-measures: AI-pause blocks (60 to 90 minutes without tool notifications, pull instead of push), conscious separation of synchronous and asynchronous, protection of deep work as a leadership discipline. Brain fry (BCG, 2026) shows that high performers are disproportionately affected: AI eases execution, judgment remains — and judgment is more demanding than execution. The middle layer is hit particularly hard: it sits at the interface between faster systems and slower negotiation processes. Whoever does not regulate the pace deliberately loses the depth of decisions — and with it the actual value contribution.


Related: ensuring objectives, deciding, monitoring, sidekicks

Deeper reading

Cookie-Einstellungen