Why Your Team Keeps Chasing Updates Instead of Doing the Work

If you lead operations in a small nonprofit or small organisation, this may sound familiar.

People are busy and trying to stay on top of things. They send reminder emails, check spreadsheets, post in Slack, ask who is waiting on what, and try to confirm whether something has actually moved forward.

From the outside, that can look like good teamwork. But when a lot of the week goes on checking status, there is usually a design problem underneath it.

The issue is often not effort or attitude. It is that the work depends on people manually creating visibility as they go.

Work still gets done, but only because someone is remembering, checking, following up, and stitching the gaps together.

When chasing updates becomes part of the job

You can usually spot this in the ordinary details of the week.

Someone sends a reminder because they cannot tell whether a task has started. Someone else checks two or three spreadsheets to work out which figures are current. A meeting gets used to piece together status that nobody can see in one place. Progress depends on who remembers to ask.

This shows up in all sorts of small-team settings.

A fundraising or programme team may keep emailing for updates on a report because the figures sit across different spreadsheets, and nobody is fully sure which version is current.

An operations lead may spend time chasing approval status for supplier payments or expenses because the handoff between requester, approver, and finance is informal and mostly lives in inboxes.

A small nonprofit preparing for a board or funder update may need to ask several colleagues for progress by hand because there is no reliable shared view of what is on track, delayed, or blocked.

In each case, the work does move. But it moves because people are chasing, checking, remembering, and filling in gaps.

That has a cost.

Time goes into reminders and status checks. Delivery gets squeezed. People interrupt each other to answer questions that should not need asking. And nobody can see the real status of the work without going around the team collecting fragments.

What is usually going wrong

When teams keep chasing updates, the problem is usually not that people do not care.

More often, task status is not visible in the normal flow of work. So the team recreates that visibility manually through messages, meetings, spreadsheets, and staff memory.

That usually points to some combination of three things.

First, handoffs are unclear. One person thinks they have finished their part, but the next person does not realise something is ready. Or nobody is quite sure what counts as complete enough to pass on.

Second, ownership is vague. Several people may be involved, but no one is clearly responsible for driving the next step. So follow-up becomes the way work keeps moving.

Third, there is no simple shared view of what is in progress, what is blocked, and what is waiting for the next action.

When those things are unclear, repeated check-ins fill the gap. People send reminders not because they are difficult or controlling, but because the setup gives them no easier way to tell whether something is moving.

In small organisations, this often builds up gradually. A spreadsheet gets inherited. A reporting routine grows around exceptions and workarounds. An approval process starts informally and never gets clarified. Over time, chasing starts to feel normal.

Why “we just need better communication” is often the wrong diagnosis

It is common for teams to describe this as a communication problem.

Communication does matter. But there is a difference between communication supporting a clear process and communication compensating for a weak one.

If people can only find out status or next steps by interrupting someone, the setup is relying too heavily on memory and follow-up. More reminders will not change that. More meetings usually will not either.

In many small nonprofit teams, the first explanation is, “we just need to communicate better.” But when you look closely, the real issue is often that nobody can see task status or next steps without asking someone directly.

That changes the diagnosis.

The problem is not simply that people are failing to keep each other updated. It is that the work relies on updates being chased in the first place.

If that feels familiar, this piece on When ‘We Just Need to Be More Organised’ Is the Wrong Diagnosis expands on the same pattern.

How to tell what kind of problem you have

If you want to reduce follow-up, it helps to get more specific about what is creating the drag.

Visibility problem

This is when people ask for updates because there is no trusted way to see current status, blockers, or next actions.

You might notice people checking several places for the same answer, or asking in Slack who has the latest version. You may also see teams rebuilding status for board papers, funder reports, or internal planning because the information is scattered.

The issue here is not lack of effort. It is that the current state of the work is hard to see.

Handoff problem

This is when work stalls between people or teams because the transfer point is unclear.

For example, a payment request may be submitted, but nobody knows whether finance is waiting for approval, whether the approver has seen it, or whether something is missing. A report may be “done” from one person’s point of view, but not in a state the next person can actually use.

When handoffs are weak, people check in to make sure nothing has been dropped.

Ownership problem

This is when a task has contributors but no clear driver.

Several people may be involved in producing a board update or preparing a report, but nobody is clearly responsible for moving it to the next stage. In that situation, progress depends on someone remembering to chase.

If follow-up is the main way tasks move forward, ownership probably needs clarifying.

Often these problems overlap. A task can be hard to see, unclear to hand over, and lacking a clear owner at the same time. But separating them helps you decide what to fix first.

For a more practical way to spot the difference, see How to tell if the problem is your setup, not your team.

A simple place to start

You do not need a big redesign to begin.

Pick one recurring piece of work that regularly creates chasing. Choose something ordinary: a monthly report, expense approvals, a board update, programme reporting, or supplier payments.

Then walk through the work from start to finish and note three things:

• where status cannot be seen without asking someone
• where work changes hands unclearly
• where next-step ownership is fuzzy

That will usually show you where the drag is coming from.

Then fix one point at a time.

Make status easier to see in the normal flow of work. Clarify what triggers a handoff and what “ready” means. Name who owns the next move, even if several people contribute.

The aim is not to add more process. It is to reduce avoidable follow-up.

When that works, the team spends less time reconstructing status and more time moving work forward.