Joel Lipton
←︎ Back to work

Domuso / Internal tools

Making financial changes traceable at Domuso

From week-long investigations to immediate access to change history.

Domuso activity log showing who changed a property record, what changed, and when
The delivered activity log, within the existing property workspace. View full size ↗︎

A banking change should not require a week of detective work.

Domuso’s operations team used an internal portal to onboard properties and manage banking details, tax identifiers, fees, and other sensitive information. When something changed, finding out who changed it and when meant asking colleagues or contacting a developer.

I researched and designed an activity log within the existing Ops UI. The constraint was practical: use stock Ant Design React components and fit the tool’s property-by-property navigation.

Original Domuso property administration interface
Before: property settings without an accessible history of changes. View full size ↗︎

Make each change understandable.

Interviews made it clear that recording every action would quickly produce a noisy log. One toggle could reveal multiple fields, creating more entries than someone could interpret at a glance.

I developed a consistent structure around the user, action, what changed, and date. The category, verb, and change details established during exploration carried into the final design, along with support for comments.

Early activity log exploration with a detail drawer
Early exploration: a drawer for inspecting changes. The scope led us toward a simpler approach. View full size ↗︎

Use a flat log, then help people narrow it down.

I explored grouping related entries, with individual changes accessible through a modal, nested page, or accordion. The volume and variety of events made those groups difficult to maintain and navigate.

Exploration grouping related activity log entries
Exploration: grouping related changes added another layer to navigate. View full size ↗︎

A flat log removed that layer. It made recent changes easy to scan, but older events still required too much paging. Filters became essential to the design.

Filter around the questions people actually ask.

Testing informed quick date presets and a custom date range. Users could also narrow the log by person and action type, combining filters to investigate a specific change.

I adapted the available Ant Design components to support these combinations within the existing interface.

Date filter exploration for the activity log
Date controls support common time intervals and a specific date range. View full size ↗︎
Activity log with person and action filters selected
Person and action filters can be combined to narrow an investigation. View full size ↗︎

Give operations direct access to the record.

After several rounds of testing, the activity log rolled out during a two-week sprint and was in production by June 2021. I worked with QA to account for the different log-item edge cases, coordinating across Product, Internal Ops, Engineering, and Systems Administration.

From week-long investigations to immediate access to change history.

The team no longer needed to contact a developer or ask multiple colleagues to reconstruct a change. Information that had taken a week or more to obtain was available directly in the log, reducing developer involvement and operational effort.

Explore moreBack to selected work