Why are developers still guessing when work will be done?

We have more project tools than ever, yet a lot of software teams still end up guessing.

Not because they lack boards, lists, or planning rituals, but because the connection between discussion, planned work, and actual code is often too weak. And because changing priorities rarely makes the impact on delivery obvious enough.

That’s something I kept running into after years of using Basecamp. I still think it gets a lot right, especially around calmer and more async work. But in software development, I wanted stronger traceability from discussion and intake, to planned work, to code.

I also wanted it to be clearer how reordering work affects when things are likely to be done. If a team works at a fairly steady pace, the order itself can already tell you a lot without needing everything to be estimated first.

That gap is a big part of why I started building Grunnaro, an async-first project tool for developers and small teams.

https://www.grunna.com/grunnaro/

If anyone wants to try it on real work, I’d genuinely value blunt feedback. And if questions come up while testing, I also have a Discord where I can help directly.