Skip to main content

The system behind the work is what makes execution possible.

For a long time, when I thought about structure in an organisation, I associated it with schedules, calendars, timelines and the general organisation of activities.

If work was planned, deadlines were assigned and everyone knew what they were supposed to be doing, I thought we had structure.

Over time, however, my understanding changed.

I began to realise that a schedule is not structure. It is simply one of the things that structure makes possible.

An organisation can have a calendar full of activities, project management software, weekly meetings and carefully documented deadlines and still struggle to execute. Work gets delayed, decisions remain pending, responsibilities become blurred and people spend considerable time trying to establish what is happening.

The problem is not necessarily a lack of planning. It may be that the system behind the plan is not working.

This distinction matters.

The schedule is visible. The structure is underneath it.

A schedule tells us when something should happen. It does not necessarily explain how it will happen, who is responsible for making it happen, what information they need, who has the authority to make decisions or what happens when something goes wrong.

Consider a project with a clearly defined delivery timeline.

The tasks have been allocated. Each activity has a deadline. Progress is discussed during weekly meetings, and the project management platform reflects the agreed milestones.

Yet one task remains incomplete.

The person responsible says they are waiting for information. The person expected to provide that information believes someone else is handling it. The project manager follows up, but cannot make the necessary decision without approval from management.

The deadline passes.

On paper, the project was structured. In practice, the organisation did not have a functioning system for moving the work forward.

The schedule exposed the delay. It did not prevent it.

This is where I began to understand that effective structure exists beyond the organisation of activities. It is the arrangement of responsibilities, relationships, information, resources and decision-making processes that allows work to move from one stage to another.

A recent scoping review by Watson and colleagues (2025), examining research on organisational structures, identifies nine interconnected areas, including authority, communication, coordination, leadership and task structures. This is useful because it demonstrates that organisational structure extends well beyond formal reporting lines or an organisational chart.

Structure influences what people work on, who they interact with and who has influence over decisions.

In other words, it shapes how work actually happens.

What makes execution possible?

If structure is the system behind the work, what does that system need to account for?

There are several important components.

1. Accountability: Who owns the outcome?

Assigning a task is not the same as establishing accountability.

A person may be responsible for completing an activity, but do they understand the expected outcome? Do they have the authority and resources to deliver it? Are they clear about what they can decide independently and what requires escalation?

When accountability is poorly defined, tasks can sit between people.

Everyone may be involved, but nobody feels responsible for moving the work to completion.

Effective structure establishes ownership. It clarifies who is responsible for the work, who contributes, who approves and who needs to be informed.

It also makes it possible to identify where responsibility ends and another person’s begins.

This is particularly important in cross-functional environments, where work moves between departments, teams and individual contributors.

2. Information flow: Does the right information reach the right people?

Work depends on information.

A project manager may have a delivery plan, but the plan is only useful if the people executing it have access to all the information they need.

An account manager may receive a client request, but if the requirements are not communicated accurately to the production team, the work can begin with incorrect assumptions.

Management may expect a project to be delivered within a particular timeframe, but if the team has not communicated its existing workload, the expectation may be unrealistic.

These are not necessarily individual performance problems. They can be information-flow problems.

A functioning structure establishes how information is shared, where it is recorded, who needs access to it and how changes are communicated.

It reduces unnecessary dependence on individuals remembering to pass information along or repeatedly chasing colleagues for updates.

It also helps prevent information from becoming trapped within particular departments or individuals.

3. Decision-making: Who has the authority to move things forward?

One of the most frustrating operational experiences is having responsibility without the authority to act.

Employees may know what needs to happen but cannot proceed because they are waiting for approval.

Managers may be overwhelmed with decisions that could reasonably be made at a lower level.

In other situations, two people may believe they have authority over the same decision, creating unnecessary conflict.

The organisation then develops a pattern of waiting.

Effective structure establishes decision rights. It clarifies which decisions can be made independently, which require consultation and which must be escalated.

This does not mean removing management oversight. It means ensuring that oversight does not become an unnecessary bottleneck.

Joseph and Sengul (2025), in their review of contemporary organisation design research, identify coordination, control, channelisation and configuration as four major approaches to understanding how organisations are designed.

Their work highlights an important consideration: organisational design must account for how people make decisions, how their activities depend on one another and how individual efforts are integrated towards collective outcomes.

The practical implication is that decision-making cannot be treated as something separate from operations. It is part of the system that enables execution.

4. Capacity: Can the organisation realistically deliver what it has planned?

A schedule can allocate ten activities to a team without establishing whether the team has the capacity to complete them.

This is where planning can become disconnected from operational reality.

People have finite time, skills and attention. They may also be responsible for several projects, routine operational duties, client communication and unexpected requests.

When capacity is not considered, organisations can end up with timelines that look reasonable but are impossible to execute consistently.

The consequences are familiar: missed deadlines, rushed work, declining quality, accumulated pressure and employees who spend their time responding to competing priorities.

Structure should therefore account for the resources available to deliver the work.

This includes understanding workload, identifying dependencies, allocating responsibilities according to capability and making decisions about what takes priority when demand exceeds capacity.

It also means having a way to respond when circumstances change.

A plan that cannot accommodate changing priorities, unexpected delays or employee absence is not necessarily a robust plan.

It may simply be a schedule built around ideal conditions.

5. Contingency: What happens when things do not go according to plan?

No operational system can eliminate uncertainty.

Clients change requirements. Suppliers delay deliveries. Employees become unavailable. Approvals take longer than anticipated. Priorities shift.

The question is not whether something will go wrong. It is whether the organisation has a way of responding when it does.

Without contingency arrangements, every disruption becomes an improvised exercise.

Managers begin chasing updates, responsibilities are reassigned informally, deadlines are renegotiated and people try to establish what should happen next.

A functioning structure anticipates at least some of these possibilities.

It establishes escalation routes, alternative ownership, handover procedures and ways of communicating changes.

This creates continuity.

The organisation does not have to depend entirely on one person being available, remembering every detail or personally coordinating every adjustment.

The human factor: A system only works through people

There is another dimension to structure that is easy to overlook.

An organisation can document excellent processes and still struggle to implement them.

Why?

Processes do not execute themselves. People do.

People interpret instructions differently. They have different levels of experience, confidence and capability. They may hesitate to raise concerns, avoid difficult conversations, withhold information or wait for direction even when they have the authority to act.

Sometimes these behaviours reflect individual circumstances. At other times, they are responses to the environment in which people work.

For example, an employee who has repeatedly been criticised for making independent decisions may eventually stop making them. A team member who has experienced negative consequences for raising problems may choose to remain silent when something goes wrong.

Management may interpret this as a lack of initiative or accountability.

However, the organisation should also examine whether its own practices have discouraged the behaviours it expects.

Research on psychological safety by Amy Edmondson (1999) is particularly relevant here. In a study of 51 work teams, Edmondson found an association between team psychological safety and learning behaviour. Learning behaviour, in turn, mediated the relationship between psychological safety and team performance.

The implication is important: people need an environment in which they can raise questions, report mistakes and seek help without assuming that doing so will automatically result in punishment or humiliation.

This does not mean removing accountability or lowering performance expectations.

It means recognising that the way an organisation manages people influences whether its systems work as intended.

If employees are expected to communicate problems early, the organisation must make it possible for them to do so.

If people are expected to take ownership, they need clarity and sufficient authority.

If teams are expected to collaborate, the structure must support the flow of information and coordination between them.

The human element is not an additional consideration to be addressed after the operational system has been designed. It is part of the system itself.

Why more meetings, tools and deadlines may not solve the problem

When execution becomes difficult, organisations often respond by adding more activity.

Another meeting is scheduled. A new project management tool is introduced. More frequent progress reports are requested. Deadlines are brought forward, or employees are reminded to take greater ownership.

Sometimes these interventions are useful.

But they do not automatically address the underlying problem.

If people do not know who owns a decision, another meeting may simply create another opportunity to discuss it.

If information is not reaching the people who need it, a new project management platform may become another place where information is incomplete.

If workloads exceed available capacity, more frequent reporting will not create additional time or resources.

And if employees are reluctant to raise concerns, asking them for more updates may produce more reporting without necessarily producing more honest information.

This is why operational problems should be diagnosed before solutions are introduced.

The organisation needs to understand where execution is breaking down.

Is it a problem of accountability? Is information not flowing? Are decisions concentrated in the wrong places? Is the team operating beyond its capacity? Are employees unclear about expectations? Or are existing management practices discouraging the behaviours required for effective execution?

These questions are more useful than immediately assuming that people need to work harder, communicate more or become better organised.

The objective is not to add more activity to the organisation. It is to make the existing work possible to execute.

Structure should create the conditions for good work

I no longer think about structure primarily in terms of schedules, calendars or how activities are organised.

I think about the system that makes those activities possible.

A schedule is useful because it gives work direction and establishes expectations. But it is only one visible expression of a much broader operational arrangement.

Behind it should be clear accountability, reliable information flow, appropriate decision-making authority, realistic capacity planning and a way to respond when circumstances change.

And underpinning all of this should be an understanding of human behaviour.

People need to understand what is expected of them. They need access to the information and resources required to perform. They need clarity about their authority, and they need an environment in which they can communicate problems before those problems become operational failures.

This is what effective structure makes possible.

It does not mean controlling every minute of someone’s working day or creating a process for every conceivable situation.

It means designing an environment in which people can understand their responsibilities, coordinate their efforts and make progress without unnecessary friction.

Structure is not the schedule. It is the system that makes execution possible.

And when an organisation struggles to deliver, perhaps the first question should not be whether its people are following the schedule.

Perhaps it should be whether the system behind that schedule is giving them what they need to succeed.

References

Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383. https://doi.org/10.2307/2666999

Accessible full-text copy: https://web.mit.edu/curhan/www/docs/Articles/15341_Readings/Organizational_Learning_and_Change/Edmondson_1999_Psychological_safety.pdf

Watson, M. K., Winchester, C. C., Luciano, M. M., & Humphrey, S. E. (2025). Categorizing the complexity: A scoping review of structures within organizations. Journal of Management, 51(1). https://doi.org/10.1177/01492063241271252

Open-access article: https://journals.sagepub.com/doi/10.1177/01492063241271252

Joseph, J., & Sengul, M. (2025). Organization design: Current insights and future research directions. Journal of Management, 51(1). https://doi.org/10.1177/01492063241271242

Open-access article: https://journals.sagepub.com/doi/full/10.1177/01492063241271242

 

Admin

Author Admin

More posts by Admin

Leave a Reply

Share