Your team does a great job – and yet everything still ends up on your desk
The projects are allocated. The project managers are experienced. And yet: at the end of the day, it’s your comments that approve the plans. It’s your decision as managing director of an engineering or architectural firm that enables the next step. Your final look at the detailed drawing before it goes out. This isn’t a sign of a lack of trust in your team - it’s a sign of a structural problem that no discussion about delegation can solve. This article explains why that is, and what works instead.
The problem has a different name than you might think
Anyone in a position of responsibility in a planning office is familiar with the situation: you have delegated. You have appointed project managers, handed over tasks, and expressed your trust. And yet you still intervene - not because your team is failing, but because something in the process is wrong. An approval is stalled. A consultation with the client is going wrong. A detail doesn’t fit with the design concept.
This is often described as a personal leadership problem. Micromanagement is seen as an expression of insecurity and fear - both of making mistakes and of losing control. That is true in some cases. But in architectural practices, this explanation falls short. Someone with twenty years’ experience in design and execution does not intervene because they are afraid. They intervene because the handover was incomplete - and the system provides for no other course of action.
Tight control often arises where structure is lacking and is later compensated for by corrective action. In the design office, this lack of structure is often invisible. It does not show up in the team structure, but in what was not said during the handover of a project: who decides what. To what extent. And under what conditions matters are escalated.
Why experienced project managers still ask for clarification
Imagine a typical situation: an experienced project manager is working on service phase 5. He knows the project. He knows the client. And yet a question about the choice of materials lands on your desk - not because he doesn’t know, but because he isn’t sure whether his answer is your answer.
Managers intervene in day-to-day operations to regain the ability to act - not because the team is failing. The downside of this mechanism affects the team: they ask for clarification, not because they don’t have an answer, but because the framework for independent decision-making has never been clearly defined. Staff hesitate to make decisions without explicit approval - this creates bottlenecks and missed deadlines.
This mechanism is particularly pronounced in the design office. Making decisions on an ongoing basis, bearing responsibility for many project stakeholders and coordinating it all - this is typical day-to-day work for many owners of architectural or engineering firms. If the owner has historically had the final say in all projects, this becomes an implicit expectation - for the team, for clients, and sometimes for the authorities too. This expectation does not disappear through delegation. It only disappears when the framework for decision-making is explicitly redefined.
Delegating without losing control is not a matter of trust. It is a structural issue.
What it really costs - calculated in concrete terms
The obvious cost is your time. But the real costs arise elsewhere. Micromanaging managers find themselves pressed for time and under increased work pressure because they take on operational tasks and neglect strategic work. In the planning office, this means in concrete terms: business development is left by the wayside. New projects are not developed. Existing client relationships receive less attention than necessary.
There is also a second dimension. Micromanagement is a massive cost driver that often remains invisible on the balance sheet: when highly paid managers spend hours correcting details, these resources are lacking elsewhere. In a planning office with several ongoing projects at different stages of development, this quickly adds up to hours per week that are spent not on billable work but on internal course corrections.
And the team? Micromanagement saps employees’ energy, as they invest their resources in monitoring and justifying their actions rather than in productive work - and team performance suffers too, because commitment and collaboration are undermined by excessive control. Project managers who could be delivering good work are left waiting for approvals. Planning time is wasted. Not because the team isn’t capable enough - but because the system doesn’t allow for enough.
What office managers have already tried - and why it doesn’t help
Most have already tried this: a discussion about personal responsibility. A new matrix of responsibilities. The decision to intervene less. Sometimes a new tool too - a project management system designed to create transparency.
None of these address the actual problem. Effective delegation does not begin with letting go, but with a structured assignment design. Anyone who delegates tasks without clarifying the basics creates uncertainty - and the result is that managers resort to tight control because the structure that would enable trust is missing.
The talk of personal responsibility ends as soon as the next difficult customer meeting looms - and the project manager instinctively takes a step back. The responsibility matrix explains who is responsible, but not to what extent or under what conditions. The project management system shows status - but it does not determine who is authorised to act at which stage.
Delegation does not succeed through ‘letting go’, but through clear task definition: objectives and quality criteria, decision-making scope and specific feedback points should be clarified in advance. It is precisely this clarity that is lacking in most design offices - not because of a lack of will, but because it has never been explicitly established in day-to-day operations.
What works instead: visibility before trust
The problem is not that you delegate too little. The problem is that nobody - not even you - knows exactly where the work is actually getting stuck today. Which decision is waiting for whom. Which project is passing through your hands when it shouldn’t be. Which approval is blocking three subsequent steps.
Only when these patterns are visible can targeted changes be made. Clarity of expectations does not reduce responsibility, but makes control more targeted. That is the crucial difference: you are not relinquishing control - you are shifting control to where it is effective. Approvals that currently arrive on an ad-hoc basis become defined decision points. Projects that currently rely on your attention run through a structure.
Teams with a high degree of autonomy outperform micro-managed teams by 37 per cent in terms of productivity and quality , according to an analysis by the Harvard Business Review. But autonomy does not arise through appeals - it arises through clarity. And clarity does not come from discussions, but from making processes visible: what flows through the office and where friction arises.
What the first step is
Not a new rule. Not another tool. Not the next conversation about delegation.
The first step is: understanding where work actually gets stuck in your office today. Which projects are waiting for your decision, even though your project managers could make them. Which approvals create loops that could be avoided. Where quality isn’t created by your intervention - but happens anyway.
Once you know this, you have a foundation. Not for a new management concept, but for a concrete change - the first one that produces more finished results without you having to work any harder.
This is exactly what Scaled Innovation works out with you over 10 working days: where work is getting stuck in your office, which area should be changed first - and what that means in concrete terms. No methodology. No new software. Just clarity about what is standing in the way today. Find out more at scaled-innovation.com.