You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To help spur or maintain long term motivation for FitDevs participating in Challenges like OneMillionMinutes (OMM), it would be helpful to create some light gamification elements that induce intrinsic motivation. One of the most prevalent tactics used in both fitness and non-fitness apps is Milestone Badges accompanied by shout outs for success.
The badge might come in a later phase, perhaps even with listing on the site in a profile area and not on Twitter. For this Issue/Suggestion though, I am focused primarily on the ability to provide further value back to members from data already being collected from Tweets.
Using the OMM challenge as an example, we can follow guidance from sources like Hooked by Nir Eyal and Clearer, Closer, Better by Emily Balcetis as well as established programs like Peloton's to determine frequency of rewards (replies for effort milestones). Creating Milestones for small intervals and increasing the spacing over time will create higher encouragement at the beginning of the journey when it is most needed, as well as occasional dopamine rewards for members who have already transitioned into a pattern of healthy practices.
Here are some examples from Peloton:
Given the varied state of individual current fitness levels when joining, starting with something like a message of "You've completed 100 minutes. Congrats! Keep go!!" and then "Yassss! You go! 1,000 minutes." would be good representations of reuse of current data. Other callouts for things like the number of days in a row minutes have been posted and/or the number of consecutive weeks a Dev has made at least one post would also encourage continued effort regardless of overall size.
Here is one example of manually responding to someone who was obviously motivated by this process and keeping track of her proximity to a near goal.
I know this is a fairly broad idea so feedback or questions are definitely welcome.
The text was updated successfully, but these errors were encountered:
To help spur or maintain long term motivation for FitDevs participating in Challenges like OneMillionMinutes (OMM), it would be helpful to create some light gamification elements that induce intrinsic motivation. One of the most prevalent tactics used in both fitness and non-fitness apps is Milestone Badges accompanied by shout outs for success.
The badge might come in a later phase, perhaps even with listing on the site in a profile area and not on Twitter. For this Issue/Suggestion though, I am focused primarily on the ability to provide further value back to members from data already being collected from Tweets.
Using the OMM challenge as an example, we can follow guidance from sources like Hooked by Nir Eyal and Clearer, Closer, Better by Emily Balcetis as well as established programs like Peloton's to determine frequency of rewards (replies for effort milestones). Creating Milestones for small intervals and increasing the spacing over time will create higher encouragement at the beginning of the journey when it is most needed, as well as occasional dopamine rewards for members who have already transitioned into a pattern of healthy practices.
Here are some examples from Peloton:
Given the varied state of individual current fitness levels when joining, starting with something like a message of "You've completed 100 minutes. Congrats! Keep go!!" and then "Yassss! You go! 1,000 minutes." would be good representations of reuse of current data. Other callouts for things like the number of days in a row minutes have been posted and/or the number of consecutive weeks a Dev has made at least one post would also encourage continued effort regardless of overall size.
Here is one example of manually responding to someone who was obviously motivated by this process and keeping track of her proximity to a near goal.
I know this is a fairly broad idea so feedback or questions are definitely welcome.
The text was updated successfully, but these errors were encountered: