- Keel
- Blog
The Keel blog
Practical guides on keeping a plan true: critical paths, dependencies, drift, launch health, and AI that proposes instead of acts.
Why status updates go stale, and how to stop writing themStatus is out of date the moment it is sent. The fix is to stop typing it.
What is a critical path? A practical guide for software teamsThe longest chain of dependent tasks decides your launch date. Here is how to find it.
Dependency graph vs kanban board: which view tells the truth?A board shows where cards are. A graph shows what a delay will cost.
How to turn a messy project brief into a plan with dependenciesA repeatable way to go from a rough brief to a plan you can check.
Plan drift: how to catch it before the launch slipsThe gap between the plan and reality grows quietly. Simple rules catch it early.
From meeting notes to action items, without anyone typingCapture decisions and actions from the meeting itself, linked to the moment.
Why AI agents should propose, not act, in project managementOne silent wrong edit can make a team ignore every agent. Proposals keep trust.
How to calculate launch health, and why it must be repeatableOn track or at risk should come from a formula, not a feeling.
Slack, slips and what-ifs: planning for delays before they happenTest a delay before it happens, without touching the real plan.
Tenant isolation with Postgres row-level security: how we do itHow Keel keeps workspaces apart in the database, not just in app code.
Stop writing status updates
Join the waitlist for early access to Keel.