How to stop chasing people for updates

Chasing updates feels like management, but it is usually a design problem. When ownership is fuzzy, data lives in five tools, and the only way to know status is to ask, you end up pinging people all day. This guide shows how to replace that habit with a system people can follow without you in the middle.

By Tansher Dhawan, Founder, Trenston. 2026-10-19.

Why chasing updates fails

Every "any update?" message costs focus for you and for the person you interrupt. The answer is often incomplete because they have to dig for it too.

If the same question comes back every week, the company does not have a reporting problem. It has an ownership and visibility problem.

Name one owner for each open item

An item with three people "on it" has no owner. Write one name next to every open deal, purchase, hire, or decision.

When something slips, you talk to that person once. You do not broadcast a group ping and hope someone answers.

Put the next step and the date in writing

Status is not a feeling. It is the next concrete step and when it is due. "Working on it" is not a status.

Ask for the next action in one sentence and a date. If the date moves, the owner updates the date. That is the whole ritual.

Keep the numbers in one place

If cash lives in accounting, pipeline in a CRM, and tasks in chat, you will always chase. Pick one place the leadership view is assembled from.

People can keep working in their tools. What changes is that the CEO does not have to assemble the picture by hand every morning.

Review exceptions, not everything

A good update system surfaces what changed, what is late, and what needs a decision. Everything else stays quiet.

Spend your time on exceptions. If nothing is late and nothing needs you, do not invent a status meeting to fill the calendar.

Stop accepting updates only in chat

Chat is fine for a quick clarification. It is a bad system of record.

When someone answers in Slack, ask them to put the same note on the task or deal so the next person does not ask again.

If a department goes quiet for weeks, treat stale data as a signal, not as proof that everything is fine.

Stopping the chase in Trenston

Trenston gives each open item an owner and a place in Briefing, Decisions, Tasks, and department pages so you see what changed without pinging the team.

When a department has not updated in a while, Briefing says so and points to who to ask. You still talk to people about judgment calls. You stop using chat as your only status system.