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

The dashboard and the change log

The map shows the plan; the dashboard shows movement. Every project has a Dashboard — on the project card, and in the map editor as the chart icon in the left rail — with everything a status meeting wants to see.

The café's dashboard: 33 % overall, progress per pillar, who carries what.

What's in it

  • Overall completion and node counts done / in progress / to do.
  • Progress per pillar — which branch is moving and which is stuck.
  • Breakdown by owner — who carries how much and how it's going.
  • Overdue / deadline approaching — what's burning and what's about to.
  • Project tasks — task completion per person.
  • An AI summary of the project — a human-language paragraph for your report (where AI is enabled).

The whole dashboard saves with the Save PDF button — always light, regardless of skin, safe to send to anyone. An empty project is honest about it: "The map has no nodes yet." and "No tasks yet — create them from a node in the map, or on the Tasks page."

What changed

The What changed section is the project's log over 7 days, 30 days, or the whole history. Events come in colored types: Done, Started, Added, Deadline moved, Assignee changed, Removed. Coming back from a vacation = two minutes of reading instead of asking around; a quiet period is admitted honestly — "Nothing moved on this project in this period."

Two honest limits

The log runs since the version that introduced it was deployed — older changes are not in it. And it shows the latest 500 changes; on very busy projects the oldest fall off.

Next

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