MIKITA SHASTAK · FOUNDER DIARY
When tracking alone is not enough
Use a public challenge as an experiment in support and accountability.
An editorial adaptation of the video diary.
The mismatch behind another tracker
In one diary entry, Mikita reflects on a product critique: a tracker may work best for people who are already consistent, while beginners need more support. He considers proof of completion and visible progress as possible additions. The video documents a product hypothesis, not a controlled study.
From a hypothesis to a social MVP
In the day 84 entry, Mikita announces a web MVP with a social component and says the next task is finding early adopters and improving the main flows. That is evidence of a launch and a feedback plan; it does not establish that accountability has improved retention.
Make the commitment understandable
Before joining a challenge, write an action you can explain in one sentence, a finish date and the kind of update you are comfortable sharing. A useful check-in can be as simple as what you completed and what you will try next.
Choose the audience deliberately
Public progress is optional, not a requirement for every goal. Avoid posting sensitive health, financial or identifying information. Read the challenge’s visibility and participation terms before joining. Use a private tool if the goal does not belong in public.
Try the community, then judge the experience
Browse the current challenges on goaskesis.com. Look for an activity that fits your routine and people whose updates you find helpful. After a week, ask whether the group actually helped you return to the action. The article’s suggested review period is an editorial exercise, not a measured product outcome.
Original sources
Day 68: Habit Trackers Are Designed Wrong ↗0:32–1:00
Day 84: Askesis Web App Is Now Live ↗0:07–0:27
English automatic captions were reviewed for meaning. Unsupported scientific numbers and financial outcomes are excluded.