Custom Fields
A reusable Custom Fields system that lets enterprise teams create, manage and apply structured data across content workflows.
- Role
- Senior Product Designer
- Period
- 2024
- Focus
- Feature architectureConfigurationValidation
- Product context
- ScomplerSaaSStructured data
Custom Fields for enterprise content workflows
As Scompler expanded across enterprise clients, teams needed ways to capture their own structured data across Topics, Stories, Articles and reporting workflows. A fixed system was no longer enough.
We designed and shipped Custom Fields as a reusable system that lets users create, manage and apply their own fields across the platform without one-off client-specific solutions.
Flexibility without a one-off system
Enterprise clients had different operational models, reporting needs and internal data structures. Repeated requests for custom inputs made it clear that the product needed a flexible foundation.
The challenge was not simply to add field types. The system had to remain scalable and understandable in everyday work while supporting creation, editing, reuse, lifecycle states, assignment across entities and filtering logic.
- Adapt to varied enterprise workflows without client-specific engineering work.
- Keep configuration powerful without overwhelming administrators.
- Make fields useful at runtime, not only in a back-office setup screen.
- Support future reporting and filtering use cases.
Turning recurring requests into one product capability
I worked with Product and Engineering to translate recurring enterprise requests into a coherent product solution. The feature evolved through several iterations with user feedback before release.
- Shaped the feature structure and UX logic.
- Designed flows for creation, editing, reuse and management.
- Defined patterns across Topic, Story and Article fields.
- Explored edge cases and interaction states.
- Iterated the solution with enterprise users through multiple stages.
A small product system, not one form
Custom Fields was designed as a connected configuration layer: field creation and validation, account-wide reuse and lifecycle management, then natural application inside real content workflows.
Creation and configuration
Users can create and edit text, textarea, dropdown, number, date, radio-group, checkbox-group and checklist fields. Setup covers type selection, naming, value configuration, advanced settings, validation and confirmation states.
Reuse and system management
A Field Library and Field Templates make fields reusable across an account rather than recreated repeatedly. Topic, Story and Article field groups, content-type integration, management views and draft, published and archived states make it a sustainable system layer.
Runtime usage and filtering
Configuration had to connect to real work. The feature renders fields in content views, applies them to articles and structures, and supports custom-field filtering with AND and OR logic across topics and storylines.
Iteration with enterprise users
Intermediate versions were shared with enterprise users at different stages of maturity. Feedback was used to refine how teams create, reuse and apply fields in practice.
This improved usability, consistency, filtering behaviour and the overall structure before release.
A scalable enterprise capability
Custom Fields shipped as a scalable product capability for enterprise clients. Instead of addressing similar requests case by case, Scompler gained a configurable and reusable foundation that lets teams adapt the platform to their own workflows.
The outcome was a more flexible system, stronger enterprise fit and a more sustainable direction than client-specific customisation.
What this case demonstrates
This project shows how repeated client demands can become scalable product capability. It reflects product framing from real enterprise needs, reusable configuration-system design, structured admin and setup flows, and iterative delivery with Product and Engineering.
Featured Projects
My product design cases from the last few years.
