Client Stories

Testimonials

The UX notes on our export wizard were blunt — operators were inventing workarounds we had never seen in QA. We reordered three screens before the next release.

I wished we had booked two weeks earlier; the maintainability scorecard arrived mid-sprint and forced some awkward prioritization. Still, the coupling map was the first artifact our new hires could actually use.

We only bought the walkthrough session. It was enough to settle an argument about whether our batch queue needed a redesign or just clearer progress states. We kept the queue and rewrote the status panel.

The change-risk briefing talked us out of a full Electron rewrite. That saved budget, though it also meant admitting our WinForms shell still had years left if we isolated the report module first.

Project story: export friction in a video workstation

A Chiang Mai media-tools company asked for a full UX & Maintainability Review ahead of version 4. Operators spent most of their day inside the timeline, but support tickets clustered around the export dialog. During walkthroughs we watched editors rename files outside the app because the dialog’s preset names collided with house naming rules.

On the code side, the export UI owned its own copy of preset logic, diverging from the render service. The report ranked that duplication above several visual polish items. The team fixed the shared preset module in one sprint and deferred a larger dialog redesign. Three months later, support volume on export naming dropped; the dialog still looks dated, but operators stopped inventing side paths.

Project story: rewrite paused for an HMI suite

An industrial HMI vendor planned to rewrite its desktop shell after a failed attempt to add multi-monitor layouts. The change-risk briefing mapped which panels depended on a shared global state object. The finding: multi-monitor support was blocked by that object, not by the UI toolkit. The company postponed the rewrite, spent a quarter extracting panel state, and shipped dual-monitor layouts on the existing stack. The briefing’s mild reservation — that extraction would feel slow to the sales team — proved accurate, but the product stayed shippable during the work.