Hey everyone,
I’ve been working as a tech lead/manager for a while, and one challenge I’ve consistently seen in Agile teams is around estimation discussions getting unintentionally influenced.
For example:
- someone says a number early → others gravitate toward it
- quieter team members don’t always share their thinking
- or we skip deeper discussion because a number “feels right”
But at the same time, I strongly believe:
👉 the real value of estimation is in the discussion and alignment — not the number itself.
So I built a small tool called Estimioo 👉 https://estimioo.com
The intent is not to replace voting or team discussion.
Instead, it’s designed to:
- help team members think through complexity individually before the session
- reduce anchoring by avoiding early verbal estimates
- encourage teams to discuss first, vote later (like proper planning poker)
In fact, the way I see it being used is:
- everyone reviews the story + (optionally) uses the tool privately
- team discusses assumptions and edge cases
- votes are revealed only after discussion, not influenced upfront
So it actually tries to reinforce:
- independent thinking
- better quality discussions
- and more meaningful alignment
I’d love to get feedback from people here:
- Would this approach help or still feel risky?
- How would you improve it to better fit Agile practices?
- Any concerns I might be missing?
If anyone’s open to trying it, I’d really appreciate honest feedback 🙏
(There’s a free version — no signup friction)
Happy to share learnings as well if people are interested.
Thanks!