Administrators could create custom fields, but lacked a clear view of reuse, placement, permissions, and downstream impact.
Enterprise HR platform · Retrospective redesign
Create the field once. Understand its impact everywhere.
A redesigned custom-fields experience that helps HR administrators create, reuse, place, and govern employee data with clearer scope, access, and lifecycle context.
At a glance
A configuration tool reframed as a governed system.
Connect discovery, configuration, preview, impact review, and ongoing governance in one lifecycle.
A concept that makes field health, scope, access, dependencies, and change consequences visible before and after publishing.
01 · The challenge
Flexibility had become a governance problem.
Creating a field was possible. Understanding the system around it was not.
Administrators needed to know whether a similar field already existed, where a field would appear, who could access it, which companies and workflows would use it, and what might break if it changed later.
The redesign centered three needs: findability, confidence, and governance. Together, they shifted the problem from completing a form to managing employee-data configuration responsibly over time.
02 · Reframed journey
Move from one-time creation to lifecycle management.
The experience follows the decisions administrators make—not the internal structure of a form.
Discover or reuse
Search existing fields and understand what is already available.
Configure safely
Define the field with the right placement and permissions.
Review impact
Preview how the field will be used, by whom, and where.
Govern over time
Monitor usage, manage access, and adapt with confidence.
03 · The redesigned experience
Show the system—not just the form.
The library, guided configuration, and impact review work together to expose context before a consequential change is published.
Surface field health
Bring drafts, duplicates, unused fields, and best-practice guidance into the library view.
Configure with feedback
Pair task-oriented steps with quality checks and a persistent employee preview.
Review before publishing
Summarize scope, access, dependencies, and audit behavior at the point of commitment.
04 · Validation and reflection
Evaluate comprehension—not just completion.
The proposed validation plan measures whether administrators can understand scope, access, and consequences—not merely finish the workflow. These are planned measures, not reported study results.
05 · Outcome
A safer model for flexible employee data.
Find before creating
A searchable library and duplicate guidance encourage reuse before another field enters the system.
See scope before publishing
Placement, access, company availability, and dependencies remain visible at the decision point.
Govern beyond launch
Field health and lifecycle status support maintenance after the initial configuration is complete.
Next project