Startup Decision Log: Why Fathom Chose Progressive Disclosure Over Feature Flags for New Tools

Tech · 4 min read

Fathom needed to introduce a new suite of charting tools but worried about overwhelming users and complicating support. Traditional wisdom pointed to feature flags for controlled rollouts, yet the product team favored progressive disclosure — surfacing new tools in context, opt‑in inline, and gradually increasing visibility based on behavior — to keep the product consistent while still experimental.

The progressive disclosure approach allowed the team to collect interaction data from users who discovered the tools naturally and from those nudged by contextual hints. This yielded richer signals about discoverability and real‑task utility than an isolated feature-flag cohort might provide. The trade-off was losing some binary control over exposure; to mitigate risk they paired disclosure with telemetry and a rollback plan that removed surfaced prompts rather than toggling backend capabilities.

After six weeks, adoption met conservative targets and support volume stayed within acceptable limits. The team concluded that progressive disclosure better fit their product philosophy — one unified surface with guided exploration — and updated their launch checklist to include behavioral gates for when to favor flags versus disclosure.