The organization watchdog
Five checks that tell you when the organization's health or a team's capacity is slipping.
Once a day Noots checks the organization's health history against five rules. The Overview's Watchdog section shows what applies to the scopes you can see, worked out when you open it.
| Check | When it speaks up |
|---|---|
| Health is slipping | An organization, division, team, program or project has dropped a health band (green, amber, red) compared with 7 or 28 days ago. |
| The team is stretched | A team's committed work has been above 110% of its available time for two weeks, or its share of overdue work rose by 10 points or more over 28 days. |
| A lead or owner is missing | A lead or an accountable person a unit had a week ago is gone. |
| Less work is getting finished | Cards finished in the last 7 days are more than 30% below the weekly average of the four weeks before, with the same number of people. |
| Short-handed next week | Approved time off leaves a team under 60% of its usual time next week. |
- Checks about a team's people need at least five people in the team. For a smaller team the Watchdog says too few people to show instead, so nobody's load can be worked out.
- Alerts carry counts and percentages, never a person's hours.
- Detection is plain arithmetic over the health history. No AI is used to decide that something is wrong.
- The accountable person for a unit, and people who manage members, get one notification per alert per week in the bell. There is no email.
- An alert about a private project only reaches people who can see that project, and health that includes private projects is worked out only from what each reader can see.
Still stuck? Open a support ticket and we'll help you out - tracked right inside Noots.