Async estimation fails when participants forget to vote. Automated reminders via Slack increase participation 3x.
The Async Estimation Participation Problem
Asynchronous planning poker offers incredible flexibility for distributed teams across time zones. Teams can estimate stories without coordinating 2-hour synchronous meetings. Product managers in California can vote at 9am while developers in Berlin vote at 5pm their local time. In theory, async estimation is perfect for global teams.
In practice, async estimation often fails due to one critical issue: people forget to vote.
When estimation happens in a live meeting, social pressure and real-time accountability ensure participation. Everyone's on camera, everyone sees who hasn't voted yet, and the facilitator can directly ask stragglers to submit their cards. But when estimation spans 24-48 hours asynchronously, participants get distracted:
- The notification arrives during focus time and gets dismissed
- The Slack message scrolls off-screen under 50 other messages
- People think "I'll do this later" and genuinely forget
- No real-time accountability means procrastination becomes the default
Result: After 48 hours, only 40-60% of team members have voted, making the estimation invalid. The product owner either waits another day (delaying sprint planning) or makes decisions with incomplete data.
Why Manual Follow-Up Doesn't Scale
Some scrum masters try manual reminder messages: checking who hasn't voted and sending direct messages. This creates new problems:
- Time-consuming: Checking vote status and crafting individual messages takes 15-30 minutes per estimation session
- Awkward: Feels like nagging team members who may be legitimately busy
- Inconsistent: Easy to forget to follow up or miss someone
- Not scalable: Works for a 5-person team, impossible for 15+ people across multiple time zones
Teams need automated, intelligent reminders that nudge participants without creating notification fatigue.
Effective Reminder Strategy for Async Estimation
Successful async planning poker requires a structured reminder cadence that balances urgency with respect for people's time:
Initial Notification (T+0)
When stories are ready for estimation, send the first notification via Slack:
📊 Planning Poker: 5 new stories ready for estimation
Voting closes in 48 hours (Wednesday 5pm PT)
[Vote Now] button
This notification should:
- Clearly state the deadline
- Show how many stories need estimates
- Provide one-click access to voting interface
- Appear in the team's dedicated estimation channel
24-Hour Reminder (T+24h)
Halfway to deadline, send targeted reminders to participants who haven't completed voting:
👋 @sarah You still need to vote on 3 stories
Voting closes in 24 hours (Wednesday 5pm PT)
Stories: "User authentication", "Payment flow", "Email notifications"
[Vote Now]
This reminder should:
- Be personalized: Direct message or @-mention
- Be specific: Show exactly which stories need votes
- Create urgency: "24 hours remaining" triggers action
- Remain helpful, not nagging: Friendly tone matters
Final Reminder (T+46h, 2 hours before close)
Two hours before voting closes, send the last reminder:
⏰ FINAL CALL: Voting closes in 2 hours
@mike, @alex still need to vote on Story #127 "API integration"
[Vote Now]
This reminder:
- Creates urgency with "FINAL CALL" language
- Publicly shows who's blocking (gentle social pressure)
- Gives enough time to vote but not so much that people procrastinate again
Discussion Trigger Notification
When outlier votes appear (e.g., one person votes 3 while others vote 8), automated notifications trigger discussion:
🤔 Story #128 has vote spread: 3, 5, 8, 8, 13
@dev_team: Outliers, please explain your reasoning
Facilitator will resolve after discussion
This ensures asynchronous discussion quality matches synchronous sessions.
Tools That Support Async Reminders
Several tools integrate with Slack to provide automated reminder workflows:
Polly (Slack Native)
Polly offers Slack-native polling with configurable reminders. Teams can:
- Create estimation polls directly in Slack
- Set reminder schedules (24h, 12h, 2h before close)
- Trigger reminders to non-voters automatically
- Export results to CSV for Jira import
Pros: Zero context-switching, native Slack UX Cons: Limited to basic Fibonacci scales, no velocity tracking
Alignlee
Alignlee provides dedicated async estimation in the browser—no accounts, no plugins, no external services to wire up:
- Rolling voting windows so participants estimate on their own schedule
- Required comment fields so outlier votes have to explain their reasoning
- A facilitator view showing who has voted and who is still pending
- A shareable room link you post in whatever channel your team already uses (Slack, Teams, email) to nudge non-voters
Because Alignlee doesn't integrate with chat tools directly, you send the reminder yourself—paste the room link into your team channel. Many teams prefer this: one link, no bot setup, and it works with any messenger.
Pros: Full planning poker features, clean session history, zero setup Cons: Reminders are manual (share the link); requires a tab switch to the estimation interface
Custom Slack Bot
For teams with development resources, building a custom bot using Slack's API takes 2-3 hours:
- Monitor estimation session via webhook
- Check vote status every 6 hours
- Send direct messages to non-voters
- Post summary when all votes collected
Pros: Fully customizable to team needs Cons: Maintenance burden, requires engineering time
Best Practices for Reminder Notifications
Effective reminders balance urgency with respect. Follow these principles:
1. Progressive Escalation
Start gentle, increase urgency:
- First reminder: Informational ("FYI, stories ready")
- Second reminder: Specific ("You have 3 pending")
- Final reminder: Urgent ("Final call, 2 hours left")
2. Respect Do Not Disturb
Never send reminders outside working hours in the recipient's time zone. Slack's scheduled send feature handles this automatically.
3. Public vs Private Reminders
- First reminder: Public channel (creates awareness)
- 24h reminder: Direct message (personal, not embarrassing)
- Final reminder: Public @-mention (mild social pressure acceptable at deadline)
4. Make Voting Frictionless
Every reminder should include a direct link to the voting interface. Zero friction = higher completion rates.
5. Show Progress
"7 out of 10 team members voted" creates momentum. People want to be part of the group that completed the task.
Measuring Reminder Effectiveness
Track these metrics to optimize your reminder strategy:
- Participation rate: % of team members who vote before deadline (target: 90%+)
- Time to vote: Average hours between notification and vote (optimize to reduce)
- Reminder-driven votes: % of votes that occur within 2 hours of reminder (shows reminder effectiveness)
- Discussion quality: Number of outlier explanations per story (should remain consistent with sync sessions)
If participation stays below 80% despite reminders, the problem isn't the reminder system—it's estimation process buy-in or story clarity issues.
Hybrid Model: Async + Sync Fallback
For maximum reliability, use a hybrid approach:
- Async first: 80% of stories estimated async with reminders (simple, well-defined stories)
- Sync fallback: 20% of stories (complex, unclear) scheduled for short 30-minute sync session
This reduces meeting overhead from 2 hours to 30 minutes while maintaining high participation and discussion quality.
Learn more about async planning poker strategies
Start Async Estimation with Automated Reminders
Async planning poker only works when participation is consistent. Automated reminders via Slack bots transform async estimation from a failed experiment into a reliable workflow. Teams report 3x higher participation when reminders are implemented correctly.
Alignlee includes built-in Slack reminder integrations to automate async estimation follow-up, allowing facilitators to focus on quality discussions instead of chasing votes.