Model the rules
I map roles, permissions, states, dependencies and failure paths before committing to screens.
Before the interface
Debora MoratallaI makeconst focus = "";from the logic up.
Start somewhere
Pick a question and I’ll take you to the project, decision or prototype behind the answer.I started with spaces, images and stories. Product gave me a new material: behaviour.
Selected work
01Board
A budgeting product where status had become a coordination problem.
- ProblemFinance teams could see the process, but not what was blocked or who owned the next move.
- ComplexityDistributed approvals, dependencies and regional roles.
- OwnershipFramed the workflow problem and defined the reusable rule system.
- OutcomeAdopted by SUEZ for the FY2026 budgeting cycle.
TAP Design System
Keeping product, design and code in sync as the system grows.
- ProblemComponent drift made each release slower to document and harder to keep aligned.
- ComplexityFigma, code, tokens, Storybook and a 28,000-instance product surface.
- OwnershipLed foundations, API reduction and the bridge between design and implementation.
- OutcomeReduced 55 public concepts to 38 and cut documentation from 45 minutes to under 2.
TAP Mindset
Turning one feature-led product into three role-based experiences.
- ProblemOne feature-led product was serving three jobs with overlapping paths.
- ComplexityRole-specific onboarding, shared capabilities and progressive personalisation.
- OwnershipLed product architecture and the 12-month redesign with design and engineering.
- OutcomeReduced decisions before a first session by 38%.
Fluxy
An autonomous commuting agent that knows when to act — and when to wait.
- ProblemA narrow top-up brief hid the larger burden of managing a changing commute.
- ComplexityGoal protection, proactive suggestions, consent and uncertain network conditions.
- OwnershipDefined the autonomy model, journey logic and interaction prototype.
- OutcomeValidated three trust-critical moments across 12 commuting scenarios.
Civeo
A municipal operations surface that preserves context from overview to action.
- ProblemTeams relied on Excel and separate service views to reconstruct the state of municipal operations.
- ComplexityFour-level navigation, editable widgets, live data states and a grounded contextual assistant.
- OwnershipDefined the product model, information architecture, interaction rules and working POC.
- OutcomeReplaced an Excel-led process with one operational surface for 15 internal workers.
How I work
02
Expose the trade-offs
I make defaults, exceptions and product judgment visible while they are still inexpensive to change.
Before the debt
Stay through implementation
I bring engineering constraints into the work early and stay close enough to protect the intent as it ships.
Before the handoff// A NOTE ON IMPOSSIBLE OBJECTSComplex systems rarely look impossible all at once. The contradiction appears when you follow the rules from one decision to the next. My job is to find that break before it ships.
Make the logic visible. Keep the intent buildable.
Lab
03Earlier work
04
A note
05That path still shapes how I work: looking for structure, noticing what is missing and making difficult ideas easier to navigate.
I’m especially interested in AI systems that know when to act, when to wait and when to hand control back.