← Back to overview

ILLUSTRATIVE EXERCISES

Explore the details.

Explore how I think about interfaces, quality, and AI-assisted delivery. These authored simulations demonstrate an approach; they are not client projects or reports of company incidents.

An experience is
more than its screens.

Prepare a product-review brief. Compare two ways of presenting the same choices, change direction, and notice what happens to your attention and your work.

PRODUCT REVIEW · LOCAL DEMONSTRATION
  1. 01 Intent
  2. 02 Depth
  3. 03 Brief

START WITH THE PERSON USING IT

What should feel easier?

Choose the experience you want to examine.

Review focus

MATCH THE REVIEW TO THE MOMENT

How closely will you look?

Your focus: Finding a way in.

Review depth

More detail is useful when it changes a decision. A smaller review can be the right starting point.

YOUR REVIEW BRIEF

Finding a way in

A focused pass · One representative journey

  1. Is the next meaningful action apparent before the user reads every label?
  2. Does the hierarchy make the important choice feel distinct from supporting information?
  3. Does the next screen carry enough context to feel like a continuation?

Start with the point where someone hesitates. Make the observation specific before proposing a change.

A review should lead to a decision.

Record the observation, its effect on the person, the proposed refinement, and how you will check it.

Nothing is submitted or stored. Your choices stay available while you explore this page.

A FEEL FOR THE DETAILS

Good interfaces feel different.

The details reveal themselves when real actions overlap.
Keep typing. Undo. Receive a change. Keep your place.

THE INTERACTION STRESS TEST

One interface.
Competing realities.

The user keeps moving.
The interface has to keep its promises.

TRY THIS SEQUENCE

Edit again before the save finishes.

Change the note, save it, then keep typing. Does “Saved” describe the version you are looking at?

Release deskSIMULATED WORKSPACE

Review queue

8 items

The interactive queue is available with JavaScript.

Scroll the queue. Open an item. Keep your place.

ITEM DETAILSVersion 1

Release handoff

No unsaved changes.
Everything here is local to this illustrative workspace. Try the guided sequence or interact directly.
THE PROMISE UNDER PRESSURE

Your latest edit belongs to you.

An acknowledgement belongs to a specific version. If you typed after sending it, those words remain unsaved—even when the earlier request succeeds. A failure should preserve the draft and a clear retry.

Inspect what actually happened
  1. Choose a collision and try it.

Guided sequences deliberately overlap actions in this local simulation. Compare the same sequence in both treatments; no company incidents or production performance are implied.

Inspect individual timings, loading states & transitions

THE FEEL OF AN INTERFACE

The moments
between the states.

Try an action. Notice the wait.
Change your mind before it finishes.

OPEN AN ACTIVITY FEED
YOUR ACTIVITY

Review checklistYour last activity is still here.

Earlier

Engineering notesA familiar place to continue.

Earlier
More to inspect: geometry, alignment & state correctness
THE PRECISION REVIEW

Looks right.
But does it feel right?

Inspect the interface. Choose a diagnosis.
Reveal the construction, then refine it.

INSPECT / OPTICAL BALANCEOriginal

An action icon at rest.
Does its placement feel balanced?

YOUR REVIEW

What would you adjust?

Choose what you would change, or reveal the guides to inspect it.

Read the review notes

A triangle carries more visual weight toward its broad edge. A mathematically centered bounding box can still feel left-heavy. A small optical adjustment balances the icon within the circle.

The goal is perceived balance; the right offset depends on the shape, size, and surrounding interface.

Illustrative review exercises. The differences are intentional; the controls remain keyboard accessible.

Explore the fundamentals: feedback, spacing & pace
01 / FEEDBACK

Make it feel responsive.

Feedback should be immediate, clear, and in the right place.

02 / PRECISION
A considered interfaceClarity in the small things.

Notice what feels off.

Alignment, spacing, and hierarchy quietly shape the experience.

03 / MOTION
Balanced

Move with intention.

Motion connects states and helps the eye follow what changed.

Beyond assisted coding.
Toward agentic delivery.

My focus: how engineers can guide capable agents, verify their work, and stay accountable for the result.

THE DELIVERY LOOPAN INTERACTIVE CONCEPT

01 / DEFINE

Start with shared understanding.

Give agents a clear requirement, acceptance criteria, and relevant context before implementation starts.

THE HUMAN ROLE

Set the intent, resolve ambiguity, and define what a good result looks like.

A demonstration of the workflow I’m developing toward. Select a stage to explore it.

TRY THE HANDOFF

What would you give
the agent?

The request: “Let a team member change a project’s status.” Select the context you would include, then review the gaps.

Illustrative workflow · authored examples
Build the handoff
A feature request is a starting point.

Choose the context, then inspect what still needs to be defined.

01 /

Agent orchestration

Coordinating specialist agents across implementation, tests, and independent verification—with explicit handoffs and review.

Current direction
02 /

Engineering context

Connecting requirements, repositories, and tools so agents can work from relevant context instead of isolated prompts.

Workflow development
03 /

UI & motion intelligence

Bringing my eye for UI behavior and detail into agents that understand interfaces, interaction patterns, and motion—then translate them into thoughtful implementation guidance.

Research & prototyping

A green build.
Would you release it?

I manage the QA team as part of my engineering operations role. Quality brings together the implementation, its behavior, and the evidence behind the work.

TAKE THE REVIEWER’S SEATILLUSTRATIVE RELEASE · NO REAL PRODUCT DATA
Automated checks passedProject status change · core flow covered
BUILD READY

The build is green. Review the evidence before deciding what that means for release.

Evidence not reviewed yet

Open the three evidence cards. A passed check only speaks for the behavior it actually exercised.

YOUR RELEASE DECISION

What happens next?

0 of 3 evidence areas reviewed

Inspect the evidence, then make the call.
How I frame quality

My work combines QA team management with engineering coordination and attention to UI behavior. This exercise explores how the impact of a finding and the scope of verification inform a discussion about release.

The scenarios define their own assumptions. Real release decisions depend on the product, users, risk, and agreed criteria.

FROM THE PRODUCT ARCHIVE

Project screens

Explore the project