Data Ingestion
The data ingestion project focused on duplicated data within QuickBooks, such as duplicated transactions, product or service information, customers, and so on. This was particularly noticeable after importing data from third-party platforms like banks, Amazon, and Shopify into QuickBooks.
Background Story
My business partner and I identified this project as a top priority due to its strategic importance. However, resource constraints meant no engineering team was initially assigned to it. To address this, I proactively collaborated with two other teams that would also benefit from this feature. We collectively agreed that our team would oversee the design aspects while their squad would handle the development tasks.
What made this feature significant to me and my team?
Accuracy in Users Books - Redundant data disrupts users' financial records, which holds significant importance for our users.
BoCoRa or Book Closing Rate - BoCoRa is a pivotal metric for QuickBooks product teams, serving as a vital measure of success. The presence of duplicated data complicates matters for our customers, particularly during closing their books, significantly diminishing the success rate.
My process
Layout Exploration
Side by Side Version
To match View
Side by Side Version
Matched View
Side-by-Side Version
Pros:
Enhances user understanding of the process and required interactions
Simplifies the interaction required to match or unmatch items.
Cons:
Requires significant back-and-forth comparison to confirm information.
Offers space-saving benefits.
Stacked Version
To match View
Stacked Version
Matched View
Staked Version
Pros:
Facilitates easy comparison of data, enabling users to pinpoint differences effectively.
Offers ample space for displaying additional information.
Cons:
Occupies more space on the interface.
It poses cognitive challenges for users when determining how to match or unmatch data.
Stacked version was more successful in concept testing and more aligned to project’s design principals