Keel
  1. Keel
  2. Product

The plan, the risk, and the reason, in one place

Keel puts dependencies and projected dates first. The board is still there, but it is no longer where you find out what is going wrong.

Launch

Know the launch is slipping before anyone asks

Launch health is worked out from slack on the critical path, open risks, and overdue work. It reads On track, At risk, or Off track, with a confidence figure, and the same inputs always give the same result.

  • A plain-language summary of what is slipping and why
  • Drift alerts, such as a task in progress with no commits for six days
  • A weekly summary for leads, with every claim linked to its source
Northwind checkout launch At risk, 54% confidence

What is slipping, and why

Auth service is 4 days late, which uses all the slack before the Nov 18 launch1. Payments API has had no commits for 6 days2.

  • Auth service At risk
  • Payments API At risk
  • Pricing screens On track
Graph

See every task a delay will touch

Tasks are linked by what blocks what. Keel highlights the critical path, flags tasks at risk, and lets you try a delay without saving anything.

  • Filter by team and follow the critical path
  • Try a what-if delay, then turn it into a proposal if you want it
  • A list view of the same graph for keyboard and screen reader users
What-if: Auth service +4 days Preview, not saved
  • Payments API Nov 7 to Nov 11
  • App integration Nov 12 to Nov 16
  • Mobile release Nov 14 to Nov 18
  • Launch slack 4d to 0d
3 tasks move. Launch date holds.
Proposals

Changes arrive as proposals, never surprises

Each proposal shows the exact change, the reasoning, a confidence figure, and the evidence. Approve or reject in one click, or edit the values first.

  • Grouped changes, like shifting three tasks, can be approved together or one by one
  • Out-of-date proposals are marked and can no longer be approved
  • Approving records both the agent and the person who approved it
Proposals 2 waiting
From a chat message

Shift 3 tasks +4 days

Auth service moved 4 days; three tasks depend on it.

From a pull request

Move Payments API to Checking

PR #212 was merged into main.

Meetings

Decisions and actions, taken from the meeting itself

Upload a recording or a transcript. Keel splits it by speaker and time, then pulls out decisions, action items, owners, and dates. Each one links to the moment it was said.

Decision log
  • Decision
    Apple Pay moves out of the first releaseCheckout sync, Oct 23, 14:02
  • Decision
    Receipts email goes out from the payments serviceCheckout sync, Oct 16, 09:41
Ask Keel

Questions answered with the sources attached

Search across tasks, docs, chats, decisions, and meetings, or ask in plain words. Answers only use what you are allowed to see, and Keel says so when it cannot find evidence.

Why did we drop Apple Pay?Ctrl K

It was cut from the first release in the Oct 23 checkout sync1 because it was the riskiest part of the payments work2.

  1. 1Decision log, Checkout sync, 14:02
  2. 2Transcript, Priya, 14:03
Board

The board is still here, kept up to date for you

Projects and tasks move across Ideas, To do, Doing, Checking, Stuck, and Done. The board shows the same data as the graph, so it never disagrees with it.

Board
  • Doing Auth service, App integration
  • Checking Payments API
  • Stuck Receipts email
  • Done Pricing screens

See it on your own project

Create a workspace, paste a brief, and get a plan with dependencies to check.