Design
User Experience
The principles and patterns that shape every ECC surface. Designed for professionals who do consequential work — fast, safely, and with a clear audit trail.
Principles
- Truthful by default. Numbers always show their source, vintage, and last-updated timestamp.
- Reversible when possible, deliberate when not. Destructive actions require confirmation that names the object and consequence.
- Field-aware. Mobile flows assume bad networks, gloves, glare, and one-handed use.
- Quiet UI, loud signals. Color is reserved for status, deltas, and warnings.
- Keyboard parity. Anything possible with a mouse is possible with a keyboard.
Information architecture
- Primary axis: module (Pipeline, Portfolio, MRV, Marketplace, Reporting).
- Secondary axis: tenant + environment + as-of date in the sticky context bar.
- Tertiary axis: object focus (a deal, a plot, a credit batch) with deep links and breadcrumbs.
Interaction patterns
- Command palette (
⌘K): jump to any object, run any action, search across tenants. - Inline edit: click a value to edit,
Escto cancel,Enterto save; optimistic with rollback. - Drawer over modal: drawers preserve page context; modals reserved for hard blocks.
- Split view: list + detail with synchronised filters; remembered per user.
- Multi-step approvals: a single review screen shows all evidence side-by-side; one decision, one signature.
Empty, loading & error states
- Empty: explain what lives here and offer the first useful action.
- Loading: skeletons that match final layout; no spinners on full pages.
- Error: human-readable cause + suggested next step + retry. Include a copy-able trace id.
Accessibility
- Color contrast 4.5:1 minimum (3:1 for large text); tested in light and dark themes.
- All interactive elements reachable via tab, with visible focus rings.
- Form labels associated programmatically; errors announced to assistive tech.
- Reduced-motion preference honoured for transitions and chart animations.
Localisation
Strings are extracted to ICU MessageFormat files. Numbers, currencies, and dates use the user's locale. Right-to-left layouts supported at the design system level even though no RTL locale ships at launch.
Research cadence
- Two usability sessions per sprint on the most-changed flow.
- Quarterly diary studies with field agents during active MRV campaigns.
- Continuous in-product feedback widget routed to the relevant product owner.