monospace.studio
← Approach

Approach to Work

How I approach focused design engagements.

Design systems, sprints, and AI-augmented practice — the craft work I bring to focused engagements with product teams.

Design systems & scaling UI

Component model · documentation site · designer library · adoption review

I treat systems as adoption work before component work.

A design system only matters when it becomes the easiest path for the people shipping the product. I align primitives, documentation, contribution paths, and review habits so the system can spread without becoming a second product nobody has time to use.

Changes behavior

Teams can adopt incrementally, engineers and designers share the same language, and pattern review becomes a source of speed rather than control.

Proof

At Oracle Netsuite I led a 3–4 person team through a refresh, UI Catalog, designer library, and progressive adoption starting with Analytics.

Super-primitives essay →

Design sprints & workshops

Five-day sprint · content workshop · decision map · prototype review

I use workshops to force decisions, not theatre.

I run sprints when a team needs a shared model before it needs more artefacts. The work is to expose vocabulary, map the decision, and leave with a direction people can build against.

Changes behavior

The team leaves with a sharper frame, a smaller set of live options, and enough shared language to stop re-litigating the brief.

Proof

At Telanto I ran the content workshop that drove the marketing narrative, product language, design system, and shipped site as a team of two.

Content workshop method →

AI ops & augmented design practice

Multi-model IDEs · custom skills + agents · MCP-wired tools · platform CLIs

I run the design loop on AI rails.

I treat AI tooling as operating infrastructure, not a novelty layer. I keep design judgment in the loop and let the model carry the repetitive distance: research synthesis, taxonomy work, prototype scaffolding, IA stress-tests, and design-system contribution.

Changes behavior

Designers spend less time on artefacts the model can produce and more on the judgment calls only people can make. Prototypes get cheap, so design enters product loops earlier and exits with more evidence.

Proof

Bloom, Hatch, and Pip — my own AI tooling — power Labs prototypes Beebop, agentic onboarding IA, and vibe-coding. This site runs on the same stack.

Labs →

Methodology

Double Diamond Design Process

The spine of every product engagement — discover, define, design, deliver.

UX Architecture

Strategy + Operations: the blueprint for treating UX as infrastructure.

Ready to start a focused engagement?

See packages →