Making Users smile, One design at a time!

Outsystems Internal Client Dashboard 

Project Context:

OutSystems Professional Services — global engagements across 500+ clients 

Goal: streamline client management  for low‑code customer projects while improving clarity, accessibility, and Sales handoff..

Role:

Senior UX/UI Expert — design system & content systems owner. I led content strategy for the application, information architecture, and governance for the Outsystems internal CRM app.​

Wins

- Reduced development rework  — design‑to‑dev handoff cycles shortened and localisation effort decreased.
- Scaled consistent experiences across 500+ customer details, enabling cross functional team to get high level view and further clear path to deep dive.
- Improved clarity in high‑risk states (errors, compliance copy), reducing support escalations on client projects (qualitative improvement reported by delivery leads).
 

 

Problems Identified

Inconsistent microcopy, labels, and IA across client projects caused repeated UI rework, localisation friction, and slower handoffs between sales, design and engineering.

Complex enterprise domains required clearer taxonomy and component content rules to reduce user error and speed implementation.

Approach (how I solved it)

  1. Content audit: reviewed 20+ client projects to identify inconsistent terminology, duplicate labels, and common error states.
  2. Taxonomy & metadata: created a standardized field taxonomy and labeling conventions to unify terminology across modules and integrations.
  3. Component content patterns: defined copy rules for component families (forms, tables, empty states, error messages, tooltips, CTAs) and added content tokens to the design system.
  4. Figma libraries & specs: built developer‑ready components with content placeholders, character limits, and localisation notes.
  5. Governance & adoption: ran hands‑on workshops and onboarding sessions for PS team.

Deliverables

  • Content audit report and content inventory spreadsheet.
  • Figma component library with content-level guidelines and copy decks for each component family.
  • One‑page Content Playbook and review checklist for design sprints.
  • Workshop materials. 

Screenshots from project

* Detailed work product is protected by NDA