Attribute Collection & Mapping

Reducing reporting errors through conditional data capture and standardized attribute relationships.

role

Product designer

focus

Attribute governance · conditional logic · admin UX

platform

Enterprise desktop web

This project explores the design of an administrative interface for configuring how organizational attributes are collected, related, and enforced across downstream reporting.

As organizations scale, inconsistent data entry becomes a persistent source of reporting errors, manual corrections, and operational friction. Admins often rely on documentation or tribal knowledge to maintain alignment between systems that break down quickly as complexity increases (teams, work types, financial structures, etc).

The goal of this work was to give administrators a clear, flexible way to define when specific attributes should be collected and how they should map to one another, without requiring engineering intervention or rigid, one-off rules.

The solution centers on two core capabilities: Collection preferences allow admins to specify whether an attribute is always required or conditionally collected based on other field values, supporting more relevant and streamlined data capture. Custom mapping enables consistent relationships between attribute, such as automatically assigning allocation codes based on work type, reducing ambiguity and ensuring reporting integrity.

The interface was designed to balance power with clarity: exposing complex logic in a way that remains legible, predictable, and scalable. Emphasis was placed on progressive disclosure, plain-language rules, and patterns that support both global defaults and local variation.

This work highlights my approach to designing systems-level tools: focusing on mental models, long-term maintainability, and the needs of the administrators who quietly keep complex products running.