Performance Insights
Observability for Data Center admins. Turning a wall of instance telemetry into something you can act on before the 2am page.
read the case studyI like complex problems, and I care what the answer looks like when it's finished.
At Atlassian I design enterprise software. Data-dense admin surfaces, used by the people who get called when something breaks.
Chemical engineering → marketing → content design → product design. Took the scenic route.
Observability for Data Center admins. Turning a wall of instance telemetry into something you can act on before the 2am page.
read the case studyDesign ownership across optimization, performance and security. Four surfaces, one mental model, for admins responsible for uptime they can't fully control.
Years of UX writing before this. The microcopy calls that decide whether a product reads as clear or as homework. Still the layer I think in first.
Five colors, two typefaces, one motion curve, and a football pitch hidden under the whole thing. Small enough to memorize in ten minutes. This site is built from it, and the proof is one keypress away.
A small-group habit app. The bet is the hook. Four people who know you watching is the actual mechanism. Witness, not audit.
Teaching code to draw like a hand. The trick was never the figure, it was the formation, players linking arms into the shape of a ball. Generative, with the cultural grammar respected and no rituals borrowed.
Influence isn't a louder voice. It's built quietly, through listening, timing, and learning to speak each teammate's language.
Why "say it straight" is a design principle, not just a writing rule.
Building things that reward curiosity without ever demanding it.
Clarity for the people already in the room. That's a different thing from an audience.