Selected Work

Work that ships and holds up in reality.

I don’t showcase everything. Only work where thinking, execution, and outcomes aligned across systems, machines, and operations.

Digital systems as the backbone. Industrial execution as the reality check. Implementation as production-proof discipline.

These cases illustrate how design decisions translate into operational behavior after go live, across systems, machines, and teams.

Browse selected work Start a conversation

Work philosophy

Proof, not promises.

Most projects fail quietly. Not during development, but during operations. My work is designed for the day after go-live.

Outcome before output

Systems and machines matter only when they change real decisions.

Context beats best practice

What works in theory often breaks in production. I design around real constraints: people, tools, time, and error.

Build once, scale responsibly

Every solution must withstand growth, handover, and team change without falling apart.

Selected work

A quiet archive of work.

Grouped by domain. Select a case to review the framing, decisions, and design intent.

A curated selection. No vanity metrics.

Browse

Select a case. The reading sheet updates on the right.

Flagship cases3

Digital systems3

Industrial & manufacturing1

Platform implementation2

Case overview

Select a case

Industry— Stage— Client—

Choose a case from the left to view details.

Problem framing

—

Key decisions

01—

What was designed / implemented

—

Intended outcome: —

How I think

Decisions first. Build second.

I start where projects usually break: handovers, edge cases, and the day after go-live. The goal is simple — make the system survive reality without constant escalation.

If it can’t survive shift changes, it’s not done.

01

Define constraints Lock scope, success metrics, and operational boundaries before design expands.
02

Lock irreversible decisions Resolve what can’t be changed cheaply later — flow, roles, control points, and data truth.
03

Build the minimum that scales Keep it lean, measurable, and handover-ready — without creating fragility.

If it needs to hold up in real operations, we should talk.

I’m selective with projects. The first step is a conversation to see whether the problem is worth solving and whether the fit is right.

Email Back to top

Prefer clarity over speed. Always.