Decision Audit: Why a Mobile Bank Chose Progressive Disclosure Over Feature Flags

Tech · 5 min read

NimbleBank, a challenger focused on Gen Z customers, planned a major redesign of its budgeting suite that included grouped budgets, savings rules, and visualizations. The engineering team pushed for feature flags to toggle new functionality, while design advocated for progressive disclosure inside the app. A decision audit compared risks, costs, and long-term UX goals.

Feature flags offer operational flexibility but introduce fragmentation: two cohorts see different UI states, creating inconsistent support tickets and mental models. Progressive disclosure—revealing advanced controls as users complete simple tasks—preserved a single, evolving interface and made new features contextual. The audit used scenario mapping and estimated operational overheads, concluding that progressive disclosure would reduce support incidents by an estimated 30% and accelerate coherent product education.

Implementation involved a phased UI: basic budgets appeared first, then contextual prompts surfaced saving-rule options when users exceeded budget thresholds, and a single in-app coach explained charts the user interacted with. Designers used microcopy and coach marks to communicate the new capabilities without overwhelming novices. Instrumentation tracked whether users discovered features via proactive prompts or manual exploration.

Three months post-launch, discovery rates for the advanced features increased by 45% and support tickets about