killBottleneck is in public beta — cloud and self-host.killBottleneck is in beta.Beta on GitHub →
Skip to content

Organization — the view from above ​

A project's dashboard answers “how is this project doing”. The Organization page answers “where does the company stall” — one screen across all team and shared projects, computed live from the data.

Where to find it ​

The Organization item in the main navigation — only administrators and managers see it (a member has no such item; Only an admin or manager can see the organization overview.). It is not in the simplified view.

Organization — the tiles on top, the sections below in the order they are read in a meeting.

The four tiles ​

TileWhat it counts
Overdue across projectsOpen goals and tasks past their deadline.
Not moving no movement for 14+ daysWork without a near deadline that nobody touched for 14 days (the change log decides; moving a card is not movement).
Projects N open itemsHow many projects are counted and how much open work they hold.
People behind have something overdueHow many people have at least one overdue item.

Clicking a tile jumps to the matching section below.

The sections in their order ​

  1. Projects by % done (lowest % first) — every project with its percentage, a team · read / team · edit / shared tag and the line N of M done · N overdue · N not moving · N open. A click opens the project dashboard.
  2. Where it stalls most (bottlenecks — holding up further unfinished steps) — the columns What · Project · Who · Blocking (N steps) · Why it stalls (overdue by N days or idle for N days). The same thing the Bottlenecks button shows in the map; here only bottlenecks that hold at least one step. A click jumps to the node in the map.
  3. Overdue across projects — What · Project · Who · Deadline · Overdue (N days), longest slip first. The + N more → link leads to Tasks with the overdue filter.
  4. What is not moving — What · Project · Who · No movement (idle for N days).
  5. People with the most backlog — per person: Overdue (longest N days) · Not moving · Open · Projects. A click leads to Tasks filtered to that person — there are usually more rows there, because Tasks shows everything you can see (private projects and done work included).
  6. What changed in the last 7 days across projects — When · What · Project · Change (status, deadline, assignee, created, deleted, moved) · Who.

Every table shows at most 10 rows and a + N more → link. An external contact shows by name, or as external contact.

Where it stalls most — bottlenecks across projects, with the number of blocked steps.

Report ​

The Report button top right offers Markdown (Monday report), CSV, PDF (to share) — always light — and PDF (as I see it). The numbers are the same as on screen. It serves as meeting material; you can ask the assistant the same question in a sentence (“what's going on in the team”) — see The AI assistant.

Report — Markdown for a chat, CSV for a spreadsheet, PDF to send.

Privacy and what is counted ​

It is computed from team and shared projects only — those you can read (team access, or someone shared them with you, or you shared them). A private project (owner only) is not counted, not even in the totals — not even yours. The page footer says what was counted (Computed from the projects you can read: team (N) and shared (N).) and what was left out (Not counted: …).

The footer admits what was counted and which project was left out.

Limits

  • For administrators and managers only; a member does not see the page.
  • Private projects are never counted — not even yours.
  • Tables show 10 rows; large instances are truncated: The overview is truncated: only the first 500 projects / 2,000 tasks / 500 changes are counted.
  • Without a team or shared project the page is empty: No team or shared project yet. with a Projects → button.

fair-code — self-hosting and internal use are free, reselling as a hosted service is not.