No amount of internal testing prepares you for real users. The first week of TestFlight took assumptions we had held for months and either confirmed them hard or demolished them entirely. Here is what the early Operators taught us.
What worked immediately
The onboarding quiz landed. People understood the comfort-loop framing instantly and several said the act of naming their loop was itself the most useful moment. The rank system that does not reset on a missed day was the single most-praised feature — it removed the dread that had killed habit apps for them before.
What needed rethinking
Quest difficulty was tuned too aggressively at the start. We had calibrated for motivated power users; real first-week Operators needed a gentler on-ramp. We shipped a difficulty curve that starts lower and climbs as rank grows, and engagement in days two through five jumped noticeably.
Notification timing was also wrong. Fixed morning prompts assumed everyone runs the same schedule. They do not. We moved to adaptive timing based on when each Operator actually engages.
What we got completely wrong
We assumed people would want more quests. They wanted fewer, better ones. The instinct to maximise output was exactly backwards — a single well-calibrated quest a day outperformed a list every time. We cut the default volume and quality perception went up.
Week one is brutal because it is honest. Every wrong assumption surfaces at once. But that is also why it is the most valuable week of the entire build — and why we are so grateful to the Operators who ran the Protocol while it was still rough.