It is Thursday afternoon and your VP just asked you for a status update on three projects. You open Jira — tickets are outdated. You check Slack — the relevant threads are buried under memes and off-topic discussions. You think about the standup from this morning but honestly cannot remember what anyone said about the payment integration. So you do what you always do: DM four people individually, wait 45 minutes for responses, then piece together a status update from fragments.

If figuring out how to know what your team is working on feels like detective work, the problem is not your team. It is your system.

Why Knowing What Your Team Is Working On Is So Hard

This should be simple. You manage a team. They do work. You should know what that work is. And yet most managers spend an embarrassing amount of time each week just trying to get basic visibility into their team's progress.

The reason is structural. Modern work happens across dozens of tools. Code lives in GitHub. Designs live in Figma. Tasks live in Jira or Linear. Conversations happen in Slack, email, and Zoom. No single place aggregates the answer to the straightforward question: "What is everyone actually doing right now?"

Project Management Tools Show Plans, Not Reality

Jira tickets represent what was planned, not what is happening. A ticket marked "In Progress" might have been sitting untouched for three days because the developer got pulled into a production incident. Another ticket marked "To Do" might actually be half-finished because someone started it informally. The board tells you what was supposed to happen, not what did happen.

According to Atlassian's own research, teams waste significant time each week in status meetings and updates partly because their tools fail to reflect real-time progress. The tools are great for planning. They are terrible for pulse-checking.

Standups Give You a Snapshot That Expires Immediately

Even if your standup works perfectly, it gives you a point-in-time verbal snapshot that is stale by lunchtime. Priorities shift. Blockers emerge. Someone finishes early and picks up something new. The standup told you the state of the world at 10 AM, but by 2 PM it is a different world.

And as we explored in our post on why standups don't work, most standups do not even deliver that snapshot reliably.

Asking Directly Feels Like Micromanaging

Here is the uncomfortable truth. The most reliable way to know what your team is working on is to ask them. But asking too often makes you the hovering manager everyone dreads. Your senior engineers do not want to justify their time to you every few hours. Your designers do not want to explain why a mockup is taking longer than expected. The more you ask, the less trust you signal, and the more guarded the answers become.

Harvard Business Review has documented how remote managers often over-monitor to compensate for lack of physical presence, inadvertently damaging the autonomy and trust that make remote work effective.

The Real Cost of Low Visibility

Not knowing what your team is working on is not just inconvenient. It creates cascading problems.

Duplicate work. Two people start solving the same problem because neither knew the other was on it. This happens more often than anyone admits, especially on larger teams.
Missed blockers. Someone is stuck but does not want to interrupt the team. Without a structured way to surface blockers, they sit quietly for days before anyone notices.
Misaligned priorities. An engineer spends three days building a feature that was deprioritized in a meeting they missed. Without regular visibility, alignment drifts silently.
Delayed decisions. When you cannot quickly assess team capacity, every resource allocation decision requires a round of investigation. Staffing a new project takes a week of conversations instead of an afternoon.
Stakeholder frustration. When leadership asks for updates and you cannot answer quickly, you look disorganized. Worse, you start scheduling "status update meetings" with your team just to prepare for status update meetings with your boss. It is meetings all the way down.

Why the Usual Solutions Fall Short

Most managers cobble together visibility from multiple imperfect sources.

The Slack Polling Approach

You post in the team channel: "Quick update everyone — where are we on the Q2 deliverables?" Two people respond immediately. Three respond hours later. Two never respond. The responses are scattered across threads and reactions. By the time everyone has chimed in, the original message is buried and you have to scroll back to compile the picture.

The Weekly Status Email

You ask everyone to send you a weekly summary email. It works for two weeks. Then people start forgetting. The ones who do send it write either way too much or way too little. You spend 30 minutes reading and another 20 minutes following up on the vague ones. After a month, compliance is below 50%.

The "Update the Board" Mandate

You tell the team to keep Jira updated in real time. Engineers hate this because context switching into a project management tool to move a card interrupts their flow. So they batch-update on Friday afternoons, which means the board is inaccurate Monday through Thursday. The tool designed for visibility becomes a lagging indicator at best.

The Better Approach: Structured Async Check-Ins

The solution is a system that collects structured updates from your team on a regular cadence, without requiring a meeting and without requiring anyone to log into a separate tool.

Here is what that looks like in practice:

A prompt goes out at a set time — usually end of day or start of day — via email.
Each person replies directly from their inbox with short answers to two or three questions: what they worked on, what is next, any blockers.
All responses land in a single dashboard where you can scan the entire team's status in minutes.

No meeting. No chasing. No logging into a separate app. The information comes to the team member, not the other way around.

Zlorex handles this workflow end to end. You configure a check-in with your questions, set the schedule, and add your team. Each person gets an email prompt, replies inline, and you see every response on one screen. It takes about two minutes per person to fill out and about five minutes for a manager to review an entire team.

The key difference from Slack or email: the responses are structured, centralized, and searchable. You can look back at what someone was working on three weeks ago. You can spot patterns — like someone who has been blocked for two consecutive days. You get the visibility without the overhead.

Before and After: A Real Scenario

Before: Sarah manages a product team of seven. She spends roughly 45 minutes each day piecing together team status from Slack messages, Jira, and direct questions. She has a standup three times a week that runs 20 minutes each. When leadership asks for updates, she needs another 30 minutes to compile a coherent summary. Total weekly overhead for team visibility: approximately 7 hours.

After: Sarah sets up daily async check-ins through Zlorex. Her team fills out updates in about two minutes each, directly from email. Sarah reads all seven updates in six minutes each morning. When leadership asks for status, she shares the dashboard or pulls specific updates instantly. Total weekly overhead for team visibility: approximately 50 minutes.

That is six hours per week returned to Sarah. For her team, the math is even better — they went from three 20-minute standups to daily two-minute written updates, saving over an hour per person per week.

Making It Work: Practical Tips

If you want to implement async visibility, a few things matter.

Ask the Right Questions

Avoid generic prompts. "What did you work on?" invites vague answers. Better questions:

What did you make progress on today?
Is anything blocking you or slowing you down?
What is your top priority for tomorrow?

These are specific enough to generate useful answers but open enough to cover any type of work. We covered this in detail in our guide on standup questions for engineering teams.

Respect the Responses

If people take time to write thoughtful updates and nobody reads them, compliance will tank. Read every update. Acknowledge blockers within hours, not days. Reference updates in your one-on-ones. Show the team their updates matter.

Don't Stack It on Top of Existing Meetings

Async check-ins replace meetings. They do not add to them. If you launch async updates but keep the daily standup, your team will rightfully feel like you added homework. Cut the standup first, or at least reduce it to once or twice a week.

Keep It Short

Two or three questions. That is it. If your check-in takes more than three minutes to fill out, people will start skipping it. Brevity drives consistency.

Conclusion

Knowing what your team is working on should not require detective work, back-channel Slack messages, or 25-minute meetings. A structured async check-in gives you clear, consistent, searchable visibility into team progress — and gives your team the autonomy to report on their terms, on their schedule.

The goal is not more oversight. It is better signal with less noise. When you get that right, everyone benefits — you manage more effectively, your team works with less interruption, and nothing falls through the cracks.

Spending too much time chasing your team for status updates? You should not have to DM five people just to answer a simple question about project progress.

Zlorex solves this. You create one update, your team responds from their inbox, and you see everything in one dashboard. No meetings, no follow-ups, no chasing.

Explore Zlorex. Free for up to 5 team members →