Insights topic
Product Design
Designing the states nobody demos, and picking the domain model that makes half the product obvious.
What this topic covers
- Choosing the right aggregate root
- Loading, empty, error and permission-denied as first-class states
- Accessibility designed in rather than audited at the end
- Content design as part of the interface, not a later pass
Articles
1 published
Pick the right aggregate root and half the product designs itself
In property software, teams model the property. The property is not the thing that persists — the tenancy is. The same mistake recurs across sectors.
NELLA Labs Design · 5 min read
Working on this?
We would rather have the conversation
If something here matches what you are dealing with, the Project Architect turns it into a structured brief — or send a message and a person will reply.
