Focus over noise
Only show what the team needs for the decision in front of them.
A PRODUCT DESIGNER'S STORY
Poker Planning started with a simple observation: estimating work is already difficult. The tool should not make it harder.
One clear place for the ticket, the vote and the decision.
01 — THE MOMENT
“We were trying to reach consensus, but the experience kept getting in the way.”
As a product designer, I watched my team use another planning poker website during our estimation sessions. It worked — technically. But the experience felt dated, crowded and disconnected from the way we actually worked.
Important actions were hard to find. The interface created friction at the exact moment the team needed focus. Tickets lived in Jira, decisions happened somewhere else, and the result had to be carried back by hand.
02 — THE QUESTION
Not another utility with cards on a screen. A calm, collaborative workspace where the team can bring in real tickets, vote privately, discuss openly and leave with a clear decision.
03 — THE PRODUCT
I designed Poker Planning around the moments that matter in a real estimation session — before the vote, during the discussion and after the decision.
Only show what the team needs for the decision in front of them.
Keep votes hidden so every teammate can think independently.
Keep the ticket, its description and the discussion in one workspace.
Connect estimation back to Jira so the result does not get lost.
04 — TODAY
Poker Planning now brings ticket creation, Jira import, private voting, team consensus and estimation history into one focused experience. It is still evolving — and every team that uses it helps make the next session better.
Try Poker Planning