How I managed the project
- 01
Interview and research. Several users, to learn how they felt about these apps, and getting properly informed about the menstrual cycle.
- 02
Propose the direction. Observe without predicting, without steering how you feel.
- 03
Define the MVP with a hard filter. Logging a day must take under 60 seconds.
- 04
Manage it in Jira. Epics, stories and Given/When/Then criteria, one commit per delivery.
- 05
Park it with clear criteria for bringing it back. Every feature earns its place through real use.
The decisions that shaped the product
The app observes, it doesn't predict
Prediction is the sector's star feature and what everyone expects, but it's the root of the problem, if the app tells you a phase is coming, it nudges you to feel it and your data stops being clean. In the interviews, several users told me those predictions were influencing how they felt. Checky doesn't label phases or forecast ovulation; the cycle day is calculated only from the bleeding the user marks.
Score the day with a number
Anything you don't record is forgotten. A daily 1-to-10 number turns a vague feeling into data; looking at the whole week you see how it really was, not how you remember it.
You're the one who sees the pattern
The luteal phase is the most stable part of the cycle, so the app doesn't need to predict. On top of what's observed, the pattern shows up on its own. The analysis layer shows you your cycles without naming any phase for you.
A chat that reads your data, never a doctor
From the chat you ask Checky about your own data, and it can jot things into your notes or update an entry for you. The rule is firm, Checky never gives medical advice, it only reflects back what you've observed.
The bet
It wins by subtracting
In a sector that competes by adding fields and predictions, Checky is defined by what it leaves out, only the essentials to get to know yourself, recorded without the app interpreting it for you. The best cycle app turned out to be the one that dares not to guess.
Today
In real use, growing clean
The MVP delivers. Logging a day takes under 60 seconds and the database grows without a single assumption from the app. The success measure is concrete, three months of consistent daily logging, enough for the first personal pattern to emerge; not for the app to tell you, but for you to see it yourself.