Understanding user needs

Keela’s transaction system wasn’t built to handle multi-item transactions, such as event tickets and donations processed together. This created friction for users integrating with platforms like Raisely and restricted how they could manage financial data within Keela.

Restructuring transaction system

As Design Lead, my goal was to redesign Keela’s transaction system to support split transactions while maintaining clarity and usability. This required:

• Aligning Keela’s data structure to accommodate multi-item transactions without disrupting existing workflows such as Campaigns, Pipelines, Impact Areas, and Reporting.

• Simplifying the Revenue vs. Donation distinction to reduce user confusion and improve financial reporting. Through research, we found that the preferred terminology is Tax Deductible vs. Non-Tax Deductible.

• Enhancing the user experience by creating a more intuitive and focused transaction flow that allowed users to clearly track, edit, and categorize multiple transaction types.

• Collaborating across teams to ensure a scalable solution that worked seamlessly with integrations like Raisely and aligned with Keela’s long-term product vision.

The transaction data structure connects multiple areas of the platform, from financial reporting to donor management. Any misalignment can break workflows, cause missing records, or miscategorize data. Like a surgical procedure, every connection must be precise to ensure smooth integration and prevent data loss.