QuickBooks
Money
Movement

QuickBooks Online is the world's leading small business accounting software. Yet its core promise was undermined by a fundamental tension baked into its architecture: the product was built on accounting principles, but the majority of its users were not accountants. Small business owners, wedding planners, photographers, construction companies, freelancers, were being asked to navigate a product that assumed double-entry accounting knowledge most of them simply didn't have.

The brief we received from Intuit was direct and unflinching: "We are forcing non-accountants to do accounting, in a product that's based on accounting principles." Our goal was to create the future state of the QuickBooks Online (QBO) transaction landscape, redesigning it from the ground up to be intuitive, guided, and empowering for users without a bookkeeping background. I led this work as Principal Interaction Design Lead, alongside a team of two (visual design and content design).

The research phase revealed the scale of the problem in stark terms. We conducted extensive customer interviews and deployed Storymatic empathy mapping to understand not just what users were doing, but what they were feeling. Sam H., a two-month QBO user running California Chocolates, told us: "QuickBooks make me feel dumb. I feel like I should just get this stuff." Other users described feeling overwhelmed by menus and terminology, confused by concepts like "Chart of Accounts," and frustrated by the inability to find answers to basic setup questions. Twenty-eight percent of users reported feeling overwhelmed by the UX. Twenty-three percent said they didn't know which steps to take. Another twenty-three percent said the product required too much accounting knowledge they didn't have.

The business implications were severe. An estimated 60,000 customers were lost because they found QBO too hard to use during their free trial, representing over $80 million in annual revenue. Sixty-one percent of new customers had no accounting knowledge, creating a structural mismatch between the product's design assumptions and the reality of its user base. Addressing this wasn't just a UX improvement, it was a strategic imperative for Intuit's growth.

We ran a "D4D: Feel the Pain" workshop with the broader cross-functional team, including Engineering and Marketing. Participants role-played as a wedding planner, a photographer, and a supplier, completing real transactions in QBO and then experiencing the chaos when the wedding was cancelled and those transactions needed to be reversed. The empathy was visceral. The workshop surfaced six core design directions: knowing where you are in a workflow, proactive contextual guidance, guided experiences for non-accountants, tactical invoice improvements, automated accounting logic, and deeper third-party integration.

We created and tested two distinct high-fidelity prototypes: a Stepflow model (workflow-based, step-by-step transaction creation) and a Hub model (single-page, centralized project view). The majority of tested users strongly preferred the Stepflow approach. "I wouldn't need the bookkeeper. It's all so automated and simple. It's all just kinda click and send," said one user. "A flow like that is so simple, just point and click." The guided approach removed the cognitive burden of having to hold the entire accounting model in mind, users could focus on one task at a time, trusting the system to handle the underlying logic. The result was a Future State Transactions Map that reorganized QBO's entire transaction taxonomy from an accounting model to an intuitive money-in / money-out model, the foundation for a generation of improvements to QuickBooks Online.