Spotting a project that has gone quiet
Silence is the most reliable warning sign in delivery work and the easiest one to miss. Nobody escalates a project nobody is thinking about.
A project stops generating noise. No meetings, no questions, no complaints. It looks calm on every dashboard.
Six weeks later the client is unhappy and the explanation begins with nobody realising.
PeopleMuster watches for the absence rather than the event. A project row shows how long since its last meeting, and warns past a configured number of days.
Filing is what makes the signal work. A meeting attached to the wrong project makes one look busy and another look abandoned, and the unassigned filter exists because that happens routinely. Reassigning is a move action on the meeting. A weekly pass over unassigned meetings keeps every gap counter honest.
Why one record instead of two
Silence is only visible if something is watching both sides. A project with no meetings and no logged hours is a different object from one with no meetings and forty hours a week. Meeting history is delivery data, hours are people data, and the diagnosis needs both.
What is switched on
- Projects
- A staleness warning on the row, driven by a configurable meeting-gap setting.
- Meetings
- Meetings import automatically with transcript and duration, and file against the project.
- Meetings
- Meeting detail carries risk signals, admin only, with flags such as no client present.
- Daily recap and timesheets
- A project with a meeting gap and no logged hours is a different problem from one with hours.
- Clients
- Quiet against one client across several projects is a bigger signal than one quiet project.
- Notifications
- A scheduled Slack digest is how a signal reaches somebody who was not looking.
What the week looks like
Ongoing
Meetings import as they happen and attach to the project they belong to.
Ongoing
The gap counter runs. Past the configured threshold, the row carries a warning.
Weekly
Sort by last meeting. The oldest rows are the list worth reading.
When flagged
Open the signal. A recurring no-client-present flag is a different story from a one-off.
Cross-check
Compare with logged hours. Quiet with hours means heads-down. Quiet without hours means stopped.
Act
Book the call. The signal's whole value is that it comes before the complaint.
Questions people ask
How long is too long between meetings?
You choose. The meeting-gap warning is a tenant setting, with a default of fourteen days. A slow retainer and a delivery sprint can be judged differently.
How should a risk signal be read?
As a prompt to look. Each signal is stamped with the prompt version and model that produced it, so an admin can tell an old read from a new one.
What if a meeting is filed against the wrong project?
There is a move action to reassign it, and an unassigned filter that lists meetings with no project yet. Both matter, because a misfiled meeting makes one project look busy and another look dead.
Where does a quiet project show up?
On the project row, as a warning once the gap passes your threshold. Sorting the portfolio by last meeting brings every quiet project to the top.