Spike: Explore Estimated Reach logic for boosts
Goal
Provide meaningful estimates on boost reach to boosting users
What needs to be done
Devise a strategy to provide users meaningful estimates on Boost Reach
QA
No deliverable to QA in the traditional sense - we should peer review the ideas created from this card.
UX/Design
No UX and design however we may need to make subsequent design changes based on the outcome of this card.
Personas
Boosting users.
Experiments
The eventual feature will be under the parent dynamic boost epic flag.
Acceptance Criteria
-
Create a proposal for a strategy for delivering estimated reach that provides users a meaningful estimate with a reasonable degree of accuracy. - Lower bound is especially important - if we do not believe we can do this accurately, we should consider omitting it.
- Estimates should be conservative so that we under-promise / over-deliver the majority of the time.
- Be aware the amount in the pool WILL shift and move as different users drop different amounts of funds in. Playing with the max daily amount is one way we could try to minimize this volatility.
- Doing different things at different stages of release is an option.
-
Create subsequent tasks for backend implementation and front-end changes.
Definition of Ready Checklist
-
Definition Of Done (DoD) -
Acceptance criteria -
Weighted -
QA -
UX/Design -
Personas -
Experiments
Edited by Ben