Open to strategic conversations

Designing software for people who operate complex systems.

I work on interfaces, workflows, and platform systems for environments where clarity, latency, and decision support matter as much as visual polish: autonomous systems, operational software, AI-enabled workflows, and AR/XR.

01Featured case study

Autonomy Research Center

A multi-year engineering platform investigating how domain specialists collaborate with AI-generated guidance in dynamic, physically demanding operational environments.

Spatial sensing camera positioned over a technical human-machine teaming telemetry interface. — FIG. 00 · Spatial sensing and operator telemetry

Systems UXHMIResearchAR / XR

Problem: Operators lose situational awareness when AI guidance interrupts at the wrong confidence threshold.
Solution: An interaction grammar built on a single behavioral constraint: no context-switching under load.
Architecture: Spatial computing, multimodal input, and explainable AI instrumented as one research platform.

Inspect full case study

02Selected work

Operational Interfaces & Systems Usability

Operational platforms, brand systems, and product surfaces built as one structural practice. Additional case studies are available on request.

Filter3 / 3

Extended process documentation available on request.

03About

Systems UX Architecture for complex software and operational environments.

The practice spans enterprise, research, and consumer-facing products, translating technical and organizational complexity into interfaces, workflows, and systems people can understand and act on.

The work starts with the system around the interface: actors, states, constraints, dependencies, and failure modes. Those models become the basis for interaction, information hierarchy, and product behavior, not decoration added afterward.

Design is purposeful rather than restrictive. Minimalism is treated as signal-to-noise control, not empty space. When the context supports it, visual ambition can be pushed deliberately toward something bold, distinctive, and memorable without losing the underlying usability.

Research, engineering, hardware, and design are treated as connected parts of the same problem. The strongest outcomes come from sharing evidence early enough for each discipline to shape the system.

Practice modelThe system around the interface

FIG. 05

LayerL1 · Actors

Who operates the system

People, teams, and machine agents who act on the system, each with their own goals and authority.

04Capabilities matrix

Methods, systems, and tooling.

A working inventory of the practice: research methods, operational interface disciplines, delivery craft, and prototyping workflows.

Capability index[ 4 Lanes · 23 Entries ]

C-01UX Research & Discovery: Workflow Mapping & Analysis
Contextual Inquiry
On-Site Observational Research
Usability Testing
Heuristic Evaluation
Research Synthesis
C-02Operational & Systems Interface Design: Human-Machine Interaction (HMI)
Autonomous Systems UX
Real-Time & Constrained Interfaces
Information Architecture
System-State Communication
Data-Rich Interfaces
C-03Design Systems & Engineering Collaboration: Component Architecture (Variables / Auto-Layout)
Design System Delivery
HTML / CSS / JS Fundamentals
Technical Design Specifications
Agile / Scrum Integrations
Design QA
C-04Prototyping & AI-Accelerated Workflows: High-Fidelity Prototyping
Rapid Interface Iteration
Feature Exploration
AI-Assisted Component Generation (Lovable / Miro AI)
Advanced Prompt Architecture

05Design approach

Designing for clarity under complexity.

I start with the system, not the screen. I map the people, states, constraints, and failure modes around the work, then design the interface around what users actually need to know and do.

Separate the visible request from the operational problem underneath it.
Understand users, environments, workflows, and constraints through direct research and observation.
Map actors, states, dependencies, and constraints before committing to the interface.
Make interaction, hierarchy, and visual decisions serve the task, context, and experience.
Prototype, test, and expose what the initial model got wrong.
Bring research, system logic, interaction, and visual design together into a coherent product experience.
Evaluate the work against its goals and available evidence. Identify what worked, what did not, and what should change next.

I care about purposeful design, not restraint for its own sake. When the context calls for it, I’m happy to push toward bold, innovative, even unexpected experiences. The goal is knowing when to reduce the signal and when to amplify it.

FIG. 06Process instrumentation: seven-step pipeline

Evidence returns to framing

Step01 · Definition

Frame the problem

Separate the visible request from the operational problem underneath it.

06Contact

Availability.

Open to discussing strategic, Systems UX Architect opportunities.

gelibnll@gmail.com

Select work is subject to NDA. Extended case studies are available on request.

System modelR-01

Actors/States/Constraints/Dependencies/Failure Modes/Interface

System model → resolved surface