An overhead desk view — a laptop on a remote call, with a wireframe, a marked-up review document and a flow diagram laid out side by side, beside a coffee, a notebook and sticky notes

SERVICES // Start here

Stop guessing
what to fix.

Most UX problems get argued, not measured. I settle them upstream — before the brief, before the real question has already been decided for you.

altimn is the independent practice of Kuo — Senior UX Strategist & AI Practitioner. Four ways in, from a single strategy session to a custom engagement. Scope, deliverables and pricing, all stated up front.

Full story is on the homepage LinkedIn

20 years in UX
Director of UX, Isobar
Strategy lead, dentsu X
HCDE, University of Washington
10+ AI agents built — one of them runs the audit above

01 Entry point Co-designed

Strategy Session

One remote session for teams who want a senior read on where they stand — before committing to anything bigger.

This is for you if —

You want a senior read on where you stand — before committing to anything bigger.
There is a decision to make this month, not this quarter.
You would rather test the working relationship on something small first.

What you get

A short self-report form before we meet — so the meeting starts at the real question
60–90 minute remote meeting
One-page memo afterwards
Three priority recommendations

02 Most clients start here

Website UX Review

For teams who know their website needs work, but aren’t sure what should change first.

This is for you if —

You know the website needs work — but not what to change first.
A redesign is being discussed, and you want to aim it before it starts.
Your team can’t agree on what’s actually broken.

What you get

A structured self-report form first — it fixes the scope, and names the goal the site is supposed to serve
Five pages reviewed: navigation/IA, homepage, a key product page, your enquiry page, plus one you choose
AI-assisted audit — structured input is what makes severity measurable instead of a matter of opinion
Scored on five dimensions: clarity of purpose, findability, conversion path, trust signals, content completeness
An overall score and a score per page — so you can see where it actually breaks
Top findings ranked by severity, each tied to its business impact
A report of three pages or less — plus an explicit list of what was not covered
No meeting needed — the report stands on its own. (Want to talk it through? That’s the Strategy Session.)

03 Co-designed

UX Engagement

The custom one — for when five pages aren’t enough. We question the brief before it locks you in, and build the direction together. Done by hand: a problem this size can’t be handed to an agent.

This is for you if —

The problem is bigger than five pages — a platform, a large site, or a product and service flow.
You have a long list of UX problems, and no agreement on which ones matter.
You need a direction your team actually owns — not a strategy handed to you.

What you get

A structured self-report first — we set the goal and the scope together
We question the brief, before it locks you in
I work from what you already have: research, analytics, past decks, support tickets
Deep analysis against that goal — turning “something feels off” into named, specific problems
The deliverable is chosen to fit the problem, not the other way round: a decision report, a service blueprint, a customer journey, or a working prototype (wireframe)
Direction built with your team, not handed over — misalignment surfaces in week one, not at the final review
Working sessions with your team — this is the one that needs them

04 Pilot — 2 slots Co-designed

AI Workflow Diagnostic

A service blueprint of how your workflow really runs — and one or two specific places where an AI agent would genuinely make it faster. Plus the places it shouldn’t touch.

This is for you if —

You want to use AI — but not where it would quietly make the work worse.
Your team is already experimenting, and the results are inconsistent.
You want someone who has actually built one — and who will tell you what not to build.

What you get

We walk your current workflow together — with the people who actually run it
A service blueprint: how the work really flows today, not how the org chart says it does
One or two specific, concrete places where an AI agent would genuinely make it faster
A mockup of what that would look like in use — it shows the scenario, so the team can argue about something real. It is not a working agent
Where human judgment has to stay — and what would quietly break if you automated it
A written recommendation your engineers can build from
Not included: build, deployment, API work or systems integration — technical feasibility stays with your engineers. I work at the workflow and service level: what is worth doing, and why

How this works

Every package starts with a structured self-report — and that is not paperwork. It forces the goal to be named before anyone opens a screen. That is the upstream move: it is why the findings land on decisions, instead of on a slide.

It is also what makes the work fast. Structured input is what lets an AI agent I built score severity at all — but only where the problem is bounded enough (a five-page website audit). Where it isn’t, I do it by hand. AI won’t shrink research; it splits it. The agent is faster at the execution layer. The thinking layer is mine — and knowing which is which is the job.

You don’t get a prettier deliverable. You get different decisions.

How I built the agent — and what it couldn’t do

Not sure which one you need? Write to me first — one email usually settles it.

Get in touch

Stop guessingwhat to fix.

Stop guessing
what to fix.