duo-perceived-progress

Make effort feel like it is going somewhere — pick the granularity of your progress number, size the unit of work that ends in a completion event, set an honest timeline, and decide what to say when a user stalls because they succeeded. Covers shipping a fine-grained scalar alongside a coarse tier, anchoring one portable number to an external standard and writing it in can-do terms, publishing the real timeline with a ladder users can locate themselves on, milestones weeks out rather than months, shortening the unit of completion, naming the capability gained at the end, and putting maintenance work on the forward path. Use when progress feels flat, when users quit in the middle, or for questions like should I show a tier or a score, how often does the number need to move, why do users skip review, or what should I promise about how long this takes.

Version

2.0.0

License

MIT