Why Important Work Still Does Not Get Done

We have better tools, clearer plans, and more visibility than ever. Yet important work still gets stuck. The missing piece may be the structures around the work

Sep 24, 2026

Years ago, I was working on a consulting assignment where a manager from the client organization offered to provide some initial material for our work. He seemed to have good ideas and said he would send us a draft that we could use as a starting point.

When a client offers something like this, you obviously take it into account. So we waited.

A couple of weeks passed. I sent a polite reminder. Then another one. At that point, I was becoming reluctant to keep chasing a client manager for something he had offered to do himself. Eventually, the material arrived: a single PowerPoint slide with, if I remember correctly, three boxes on it.

It looked like a few minutes of work. I do not think the problem was that those minutes were impossible to find even in a busy schedule. Something else had happened. The task had simply remained undone for weeks even though the person knew what to do and had apparently intended to do it.

I have seen many variations of the same thing. I need to be somewhat careful with examples from consulting work because of confidentiality. Individual organizations or persons should not be recognizable from my stories. But the examples themselves are hardly unusual.

We all have them. A decision remains open even though everyone has enough information to make it. A short email never gets sent. Someone does not reply to a Teams message that would take half a minute to answer. A document waits for one final review or is not even started. A project task sits on a Kanban board for months without progress. A development initiative appears on the agenda month after month without getting started.

Some of these are pretty small tasks, while other are larger. The common thing is that they are usually important to someone.

There should not be anything to stop them being done. People know what needs to happen. They are competent enough to do it. The tools exist. Often there is even agreement that the work is important.

Still, the work does not get done.

A Lot of Activity Can Mean Very Little Progress

Modern organizations have become quite good at organizing work around work. We have roadmaps, backlogs, task lists, portfolio views, project plans, status reports, steering groups, weekly meetings, monthly meetings, dashboards, and spreadsheets that have become important parts of the operating model without anyone necessarily intentionally designing them that way.

Most of that is useful. Complex work needs coordination, and people need to understand what is happening. Actually, I have spent a good part of my career helping organizations create exactly these kinds of structures, so I am hardly going to argue against planning, documentation, or governance.

But activity and progress are different things. I have been involved in projects where a topic was discussed extensively, workshops were held, material was produced, comments were collected, and the material was updated. Then someone suggested that the stakeholder group was too narrow, which was probably true. A stakeholder analysis followed, more people were invited, and additional views were collected. The material was updated again. Then someone identified another aspect that needed further investigation. Another document or two was produced, followed by several rounds of discussion, comments, and revisions.

In many cases, all of that was perfectly justified. The additional stakeholders genuinely needed to be involved, and the new perspectives and analyses improved the result. Each individual step made sense, and there were good reasons for doing the work.

Still, the schedule kept slipping. The steering group listened to the explanations, nodded in agreement, and approved the revised timelines. After all, each delay had a perfectly reasonable justification. But at some point, you start to get the uncomfortable feeling that the project is doing a lot of sensible things but may never actually finish.

That is particularly easy in expert work because preparation is often real and demanding work. Comparing alternatives, refining a plan, gathering input, preparing a decision, or improving a presentation may require considerable expertise. It cannot simply be dismissed as bureaucracy.

The problem starts when preparation continues after we already know enough to take the next sensible step. At that point, it all boils down to this: If we already know the next sensible action, what exactly are we still preparing for?

Making Work Visible Is Not the Same as Making It Move

One reason this can be difficult to notice is that we have become very good at making work visible.

Project management systems show what is planned. Task boards show what is in progress. Reports and dashboards show what is late. Portfolio tools show where money and resources are allocated. Status meetings make sure that problems are discussed regularly.

That is clearly better than having important work hidden in somebody’s inbox or memory. But visibility has its limits.

A task can be visible for months. Everyone knows that it is overdue. It can appear in every status report and be colored bright red on a dashboard. And still, nobody may do anything that changes the situation.

Sometimes even basic follow-up is missing. A task is assigned, perhaps with a deadline, and then largely forgotten until someone eventually asks about it. In other cases, progress is monitored regularly, but managers do little to address delays, resolve competing priorities, or make sure that somebody actually takes the next step. Reporting can become a routine in its own right, with remarkably little effect on what happens between meetings.

Making work visible, monitoring progress, and actually getting things done are three different things. The first is mainly about information and coordination. The second requires active follow-up and management intervention when necessary. The third depends on what actually happens between meetings. Neither of the first two produce progress by itself.

The Explanations Are Usually Reasonable

When important work does not move, there is rarely a shortage of explanations.

People are busy. Resources are limited. Priorities have changed. We are waiting for another decision. Someone is on leave. A customer issue appeared. The budget process took longer than expected. There was a reorganization, which in a large organization can explain quite a lot. Usually these explanations are at least partly true.

Work life also seems to be almost deliberately designed to make sustained work difficult. Calendars fill with meetings. Responsibilities overlap. Goals remain vague. People work on several topics at the same time. Immediate requests arrive throughout the day and often come with someone else waiting for an answer.

The environment simply kept producing other things to do first.

This is why explanations such as poor motivation or lack of discipline often feel incomplete. Of course motivation matters. But expert organizations are full of motivated and hardworking people whose calendars are already full and whose work contains several competing priorities.

Urgent work has a major advantage here: it usually arrives with a deadline, a meeting invitation, or an important person asking for something. But if work is just important, it waits much more quietly.

Maybe We Are Looking at the Wrong Part of the Problem

When work remains unfinished, we usually have two fairly obvious places to look for the explanation.

The first is management. Is the goal clear? Are priorities consistent? Do people have enough time and resources? Are responsibilities clear? Is management providing enough direction and removing obstacles?

These are all valid questions, and employees are often quite good at identifying problems in this category. Sometimes with good reason. Vague priorities, overloaded roles, poor coordination, and calendars filled with meetings can make focused work unnecessarily difficult.

The second explanation is the individual. Perhaps we simply do not manage our work very well. We procrastinate, organize ourselves badly, avoid difficult tasks, or fail to stay motivated. In less diplomatic language, somebody could just call that laziness.

This is also a familiar angle in personal productivity and self-help literature. The proposed solution is often better habits, more discipline, a smarter task system, time blocking, or some other method for getting yourself to do what you already know you should be doing. There is clearly something to this. Procrastination exists, and people differ considerably in how well they organize their work.

But both explanations can miss something in between: the structures around the work.

A task may have a clear goal but no natural place in anyone’s working week. A project may have an owner, but the owner also has fifteen other responsibilities. A decision may appear on the agenda repeatedly without there being a clear point when somebody is expected to make it. Something may remain an official priority for months while repeatedly losing to work that happens to be more immediate.

An organization can get many things right and still make important work surprisingly hard to complete. It can communicate priorities, assign owners, set targets, and track progress. None of these automatically creates the practical conditions for the work to happen. A quarterly goal is not a working rhythm. A named owner does not mean available time. A dashboard showing that something is late does not tell anyone what should happen on Wednesday morning to change the situation.

This is why I am increasingly interested in structures. By that, I mean fairly practical things: how work enters the calendar, how the next action becomes clear, when decisions are made, how people return to unfinished work, and what helps progress continue after the initial attention has moved elsewhere.

This is somewhat different from the usual management or personal productivity discussion. I am less interested in another prioritization model or the perfect task manager, note-taking system, and morning routine. There are already enough of those.

The question I find more useful is simpler:

What makes important work likely to happen—and keep happening?

I think there is enough material here for a few more articles. Starting with what these structures might actually look like in practice.

🧭 20 Years of Enterprise Architecture, 18 Years of Consulting

A while ago, I realized that I have now spent over 20 years working with enterprise architecture and 18 years in consulting. That is long enough to accumulate a fair amount of material, mistakes, and opinions.

I wrote a separate piece about that journey in my sister publication, Enterprise Architecture Transformation. If enterprise architecture, consulting, or how a career in both gradually develops and what I have learned sounds interesting, you can read it there.