Eric Guess

System-Level Decisions

• Designed a semantic token layer to enable multi-brand theming without duplicating components.
• Prioritized API stability over feature velocity — breaking changes required explicit migration paths.
• Invested in adoption tooling (linting, migration scripts) before documentation to reduce friction for product teams.

Governance & Adoption

Established lightweight governance through cross-team reviews and shared ownership. Adoption scaled from one team to three within six months — driven by tooling and trust rather than mandate.

The table component evolution demonstrates how these architectural decisions played out in practice.

Key Challenges

• Designing interfaces that scale from simple workflows to highly complex automation without overwhelming users
• Balancing power for engineers with approachability for less technical operators through progressive disclosure and clear patterns
• Aligning design intent across globally distributed teams with consistent documentation and shared terminology

What I Delivered

• Workflow builder interaction model: node types, configuration panels, validation, and error handling
• Dashboard system: chart-selection guidelines, color rules, standardized layouts, and configurable widgets
• User management UX: simplified role/permission flows with scalable search and filtering

Core Constraint

The same platform had to support rapid internal prototyping while also acting as a production-grade surface for enterprise deployment—so usability improvements could never compromise auditability, permissions, or clarity under risk.

Impact

• ~40% faster solution deployment for client implementations
• ~40% reduction in UI development time through component reuse
• Faster onboarding through standardized patterns and documentation templates

Collapse ↑

Design Constraints

• Unreliable connectivity in mechanical rooms and multi-building campuses—offline-first was a hard requirement.
• Time-critical work (including emergencies) demanded fast capture, clear status, and low-error interaction patterns.

What I Focused On

• Streamlined work-order flows to reduce steps, minimize typing, and keep primary actions obvious under pressure.
• Offline UX: clear sync states, resilient drafts, and predictable recovery when connectivity returns.

Outcome

Usability testing showed a 60% reduction in task completion time. The redesign delivered 100% offline capability and improved response speed and data quality for maintenance teams.

Collapse ↑