Estimation
Estimates your team
actually stand behind.
Private voting. Instant reveal. When the votes diverge, that's where the real conversation starts.
Session Flow
Four steps. One shared estimate.
Every estimation session follows the same rhythm — focus, vote, reveal, converge. Each step is designed to surface information that would otherwise stay hidden.
Add stories
The session host drops in backlog items one at a time. Everyone focuses on the same story before anyone votes.
Vote privately
Each person picks a number. No one sees anyone else's vote until all have submitted. No anchoring. No following the senior voice in the room.
Reveal together
All votes surface at once. The room sees every number at the same time — no early framing, no cascade effect.
Discuss & converge
Aligned votes move on. Divergent votes open a conversation. The gap is always a question waiting to be asked — and the answer is always in the room.
The Fibonacci Scale
Gaps that grow on purpose.
Fibonacci gaps grow as the numbers get larger. That's intentional — bigger stories carry more uncertainty, and the scale makes that visible.
Small
Well understood.
Clear scope, low uncertainty. The team has done this before. Assign it and move on.
Medium
Some unknowns.
Possible dependencies or edge cases. Worth a brief conversation before the team commits.
Large
Break it down first.
High uncertainty across the board. This story is probably hiding two or three smaller ones. Split before committing.
Divergence
The gap in the numbers
is always a conversation.
A vote of 8 and a vote of 34 don't mean someone is wrong. They mean someone knows something the others don't.
Estimation disagreements are almost never about opinion. They're about information asymmetry. The person who voted high saw a dependency, a risk, or an unknown the others missed. Revealing the gap forces that conversation before the work starts — not halfway through delivery.
After discussing, the team revotes. Most converge to a shared number. When they can't, the story is flagged as not ready — that's a valid outcome, not a failure.
Access & Trust
Sign in with your work email.
Not just any email.
Work domains keep estimation sessions inside the team, where they belong.
Session invites, vote records, and any future org-level reporting go to the inbox you actually use — the one on your work domain, not the personal account you signed up with three jobs ago.
It also means we know who your team is — which makes org-level features possible when you're ready for them.