Case Study
Designing Activity Log: Bringing Transparency to Data at Stratly
Product Designer - Stratly
Nov, 2024
Product & Problem
Stratly is an enterprise B2B fundraising and financial data platform managing highly sensitive financial and donor data for enterprise nonprofits. As data density scaled across the platform, organizations faced a critical compliance gap. Finance teams and administrators had no visibility into data mutation. If a donation amount changed or a major donor contact was deleted, the system offered no historical record of who made the change or when. This lack of traceability created severe financial liability and forced organizations to rely entirely on internal engineering support to investigate data discrepancies.
My Role & Contributions
I led the product design and UX architecture for the Activity Log system. My objective was to design an immutable audit trail that surfaced complex database logs into a readable, actionable interface, giving organizations total transparency and control over their data compliance without requiring developer intervention.
I conducted stakeholder sessions with finance and operations teams to understand audit and compliance workflows, mapped their existing “workarounds” with engineering, and translated these into user journeys. I prototyped the slide-over architecture and diff views in Figma, then iterated based on feedback from internal compliance reviewers before finalizing the production UI.
Key Design Decisions
Contextual Slide-Over Architecture
Dumping raw system logs into a massive, global CSV file creates severe cognitive overload. To solve this, I designed a localized slide-over drawer that surfaces historical data directly on top of the active record. Users can verify changes, such as who updated a specific phone number, without navigating away from the contact profile. This spatial architecture keeps the interaction flow unbroken and contextualizes the data immediately.
Financial Chain of Custody
Donations are the most heavily audited objects on the platform. A simple edit can change a tax receipt and create legal liability. I integrated the Activity Log directly into the localized Donation Receipt view. This allows finance administrators to see a strict timeline of every status change (e.g., 'Payment Successful', 'Refunded') alongside the transaction details, creating a complete and compliant chain of custody for every dollar.
Granular Diff Views for Financial Audits
A generic "Edited by Admin" label is insufficient for financial compliance. Users require precise data regarding state changes. I designed a granular 'diff' (difference) view that explicitly maps the Previous Value against the New Value. If a tax receipt amount changes from $50 to $500, the system visually highlights the exact delta, identifying the user, the timestamp, and the original data point.
Soft Deletion & Active Data Recovery
System administrators occasionally delete records in error. To prevent catastrophic data loss, I introduced a "Soft Delete" state for all critical records across the platform. If a user deletes a donor profile, the system intercepts the database removal, flags the action in the Activity Log, and surfaces a one-click 'Restore Record' action. This transitioned the Activity Log from a passive monitoring tool into an active safety net.
Engineering Workflow & Handoff
Surfacing immutable logs required precise coordination with the backend engineering team to ensure the UI did not cause severe performance degradation. I documented the JSON payload structures required for the front-end to accurately render the 'diff' views. We established strict rules regarding which database events triggered a log entry, prioritizing structural and financial mutations over minor UI interactions to maintain system speed while ensuring total compliance tracking.
The Outcome
Restructuring the hardcoded permissions into a centralized, scalable architecture delivered immediate operational improvements:
Support Reduction
The introduction of the one-click 'Restore Record' action eliminated engineering support tickets related to accidental data deletion almost entirely.
Compliance Efficiency
The granular diff views and contextual timelines reduced the time required for finance teams to conduct internal transaction audits from days to minutes.
System Trust
Providing an immutable chain of custody directly inside the UI allowed Stratly to successfully pass the stringent security and compliance reviews required to onboard Tier 1 enterprise clients.
Challenges & Trade-offs
The primary technical constraint was database bloat. Logging every single keystroke or micro-interaction would rapidly degrade platform performance. I had to make strict architectural trade-offs regarding what constituted a "loggable event." I worked closely with product managers and legal advisors to map out a priority matrix, ensuring we tracked all destructive actions and financial modifications while intentionally ignoring low-risk aesthetic changes to preserve system speed.