Custom Fields
- Role
- Sr. Product Designer
- Core activities
- Feature-designConfigurationData Model
- Period
- 2024
- Product Tags
- ScomplerConfigurationFeature-design
Context
Enterprise clients needed to capture structured information across topics, stories, articles and reporting workflows. Fixed product fields were not flexible enough for different content operations and organizational structures.
Product Landscape
Scompler / 2024
Custom Fields connected product strategy, user workflows and implementation constraints. The work needed to support the immediate feature scope while leaving the product easier to extend.
Configurable structured-data foundation for custom enterprise workflows.
- Feature-design scope
- Configuration scope
- Data Model scope
- SaaS scope
Challenges
The work started with a set of product, workflow and system constraints that had to be resolved without slowing delivery.
- Custom data had to work across multiple objects and workflows.
- Configuration needed to be powerful without overwhelming admins.
- The feature had to support future reporting and filtering use cases.
Approach
Design process
I translated the product problem into reusable UX structures, validated the direction with stakeholders and prepared implementation-ready design specifications.
- Mapped field usage across product objects and permissions.
- Designed creation, editing, validation and display patterns for configurable fields.
- Connected field logic with list, detail, filtering and reporting surfaces.
Outcome
The result was a clearer product experience, stronger delivery alignment and a more scalable foundation for future work.
- Gave enterprise teams a scalable way to adapt Scompler to internal processes.
- Created a stronger structured-data foundation for future reporting and automation.
- Reduced dependency on one-off customization requests.
Reflection
General experience
Good system work is less about perfect component inventory and more about creating repeatable agreement between product, design, and engineering.
The most useful artifacts were the ones teams could apply immediately in delivery: decision rules, naming conventions, reusable states, and practical examples.
Featured Projects
My product design cases from the last few years.
