How do you keep your project plans updated when reality changes?

Hey everyone! 👋

I'm exploring a problem that many engineering teams face: project plans become outdated as soon as priorities shift, dependencies get delayed, or new blockers appear.

Teams end up spending hours updating tickets, chasing status reports, and manually adjusting timelines just to understand what's actually happening.

We're building Keel, a project workspace designed to keep plans aligned with reality.

The idea is simple:

• Automatically identify tasks and dependencies that are falling behind.

• Show where the projected timeline differs from the original plan.

• Turn conversations, meetings, and development activity into meaningful project updates.

• Let AI propose schedule changes while keeping humans in control.

I'd love to hear from people managing software projects:

1. How do you currently track project delays and changing dependencies?

2. What's the most frustrating part of keeping your project management tools updated?

3. Would you trust an AI tool to propose timeline changes if it explained the reasoning and let you approve them?

We're interested in learning from real experiences, not just collecting feature requests.

Thanks for sharing your thoughts!