Internal tools fail when they're designed like consumer apps. The real challenge is modeling workflows, states, and permissions so operators can handle exceptions, maintain data quality, and move fast—without workarounds. I design operational interfaces that hold under pressure.
Who it's for
Operations-heavy teams building internal tools, ERPs, dispatch systems, or complex workflow applications. The real product is coordination, data quality, and exception handling—not the interface alone.
Problems this solves
- Operators work around the tool instead of through it—manual steps, spreadsheets, and Slack threads fill the gaps.
- State transitions, permissions, and error paths are an afterthought, causing escalations and data inconsistencies.
- The tool was built feature-by-feature without an information architecture that scales.
- New team members take weeks to ramp up because the workflow logic is implicit.
What you get
- Workflow maps with explicit state models, transitions, permissions, and exception paths.
- Service blueprints connecting the frontstage UI with backstage operations (SLAs, handoffs, escalation rules).
- Prototypes validated with operators—not just stakeholders—before build commitment.
- Dev-ready specs with edge cases, error states, and auditability requirements documented.
How it works
Typically 4–8 weeks for v1, depending on workflow complexity. Starts with operator shadowing and state-model mapping, moves to IA and prototype validation, and closes with dev-ready specs and delivery support. I stay through the first release cycle to handle what surfaces in production.
Proof
Frequently asked questions
- Do you work with legacy systems?
- Yes. Most internal tool projects involve legacy constraints—APIs, data models, or workflows that can't be replaced overnight. I design around what exists and sequence changes to minimize disruption.
- How do you handle permissions and roles?
- Roles and permissions are designed as a first-class concern, not bolted on later. I map them alongside state transitions so the tool enforces the right access at the right stage.
- Can you stay through delivery?
- Yes. I provide delivery support through the first release and iteration cycle—handling edge cases, operator feedback, and the inevitable surprises that surface in production.
Start a conversation
Describe your constraints and the decision you need to make. I'll tell you if I can help.