OneCause: Unified Platform Architecture
Unlike my later sprint-based work at OneCause, this initial project gave me three months of creative freedom to explore and architect a solution for their most pressing challenge: unifying multiple acquired products into one cohesive platform.
Working outside the typical agile framework, I conducted deep discovery across their fragmented ecosystem and prototyping a unified architecture that could guide the product roadmap for years to come. This exploratory phase allowed me to think holistically about the user experience without the constraints of two-week deliverables.
Unifying a Fractured Fundraising Ecosystem
OneCause, a leading nonprofit fundraising platform, had acquired multiple companies to expand their offerings—mobile bidding, event management, peer-to-peer campaigns, and donation tools. The result was a fragmented product suite that confused users and created heavy support dependencies.
I designed a unified product architecture through high-level IA mapping and mid-fidelity Figma prototypes, integrating these disconnected tools into one cohesive platform.
The goal: reduce help desk reliance by enabling learn-as-you-work experiences, and establish OneCause as the essential self-service fundraising suite for nonprofits.
Story Mapping with Stories on Board
Stories on Board is a collaborative user story mapping tool organized as: Goals → User Steps → Stories.
I used it to collect and distill project goals, inventory all needed flows and screens, enable real-time PM collaboration, run visual planning meetings, prioritize stories, and plan development hierarchy. It became our shared source of truth for the entire user journey—keeping the team aligned from discovery through development.
Mapping IA with Flowmapp
Flowmapp is a visual planning tool for creating sitemaps and user flows that map out information architecture and user journeys through screens and decision points.
I used it in synergy with Stories on Board—translating the prioritized user stories into a detailed sitemap and user flows that defined the IA. While Stories on Board organized what we were building and why, Flowmapp showed how users would navigate through it, revealing dependencies and edge cases that informed how many screen variations I needed to design.
Dashboard Flows
These medium-fidelity prototypes show product structure, not full designs. Many screens are from the current product. Using Figma and a component library allowed quick changes, skipping wireframes to focus on flows and build a scalable base. Final design details and accessibility come later.
Event Section Demos
Create Event Flow
Ground Zero dashboard
Create and manage event
View built-out dashboard
View event-specific analytics
Create Tickets Flow
Ground Zero dashboard
Create tickets
View built out dashboard
View ticket specific analytics
Create Tables Flow
Ground Zero dashboard
Create and manage tables
View built-out dashboard
View table-specific analytics
Auction Items Section Demos
Add Auctions
Ground Zero dashboard
Create collection
Create Silent Auction Collection
Add lot
View lot’s item-specific analytics
Converted silent auction to fixed price.
View collection specific dashboard
Add Items flow
Add item flow
Demo Settings panel
Manage items dashboard
Adaptive Dashboard Design: Empty Canvas to Command Center
The Events module example below demonstrates a pattern that extends throughout the entire platform. Every module follows this same progressive framework- guiding nonprofits from first login to full mastery:
Zero State - The Starting Canvas
Empty sections aren't dead ends—they're invitations. Each landing page previews what's possible once users start building, with clear CTAs that let them jump in anywhere. No prerequisites, no rigid order—just pick a task and go. This approach reduces overwhelm while creating a visual roadmap of what's to come.
Getting Started - Building Momentum
As users create their first event, the interface responds immediately. The zero state hero transforms into an active event card, providing instant visual feedback. The dashboard begins populating with real content, creating a sense of progress that motivates users to continue building out their fundraising infrastructure.
Hero State - Full Command Center
The mature dashboard prioritizes what matters most: recently worked events pin to the top automatically, while secondary CTAs move to a dismissible panel to reduce clutter. Older events organize into a scannable table below. This intelligent hierarchy means power users can work efficiently while untapped features remain discoverable but not distracting.
Core Page Patterns
Full Screen Task Panel Demo
Keeps main area clutter-free
Designed for users to return and complete later
Not overwhelming—only asks for the most relevant information
Allows settings to be configured via accordion, one at a time
Organization Structure Collections are organized into Silent, Live, and Fixed categories.
Item Types Items include Value, Procurement, Gift Certificate, and Donor Info
Task Panel Drawer
Acts as a bridge to the next screen, creating a feeling of seamlessness. Decreases page load time while increasing awareness of their action and reducing cognitive load.
Accordion Edit Page
Used for tasks with extensive data entry where all information is required. The accordion format breaks complex forms into manageable sections with clear completion status. Currently used for Event Details and Communications Campaigns.
What Came Next:
After this strategic foundation was set, I transitioned into the sprint team where I designed specific features in the existing architecture including Show Manager, login flows, the check-in tool, and table management.
I also created rapid concept prototypes for board presentations, demonstrating future possibilities through quick proof-of-concept videos. I’m happy to share more upon request.