Make it feel responsive.
Feedback should be immediate, clear, and in the right place.
ILLUSTRATIVE EXERCISES
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.
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.
START WITH THE PERSON USING IT
Choose the experience you want to examine.
MATCH THE REVIEW TO THE MOMENT
Your focus: Finding a way in.
More detail is useful when it changes a decision. A smaller review can be the right starting point.
YOUR REVIEW BRIEF
A focused pass · One representative journey
Start with the point where someone hesitates. Make the observation specific before proposing a change.
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
The details reveal themselves when real actions overlap.
Keep typing. Undo. Receive a change. Keep your place.
THE INTERACTION STRESS TEST
The user keeps moving.
The interface has to keep its promises.
Change the note, save it, then keep typing. Does “Saved” describe the version you are looking at?
The interactive queue is available with JavaScript.
Scroll the queue. Open an item. Keep your place.
Your draft is still in the editor. Review the team’s change before choosing which version to keep.
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.
Guided sequences deliberately overlap actions in this local simulation. Compare the same sequence in both treatments; no company incidents or production performance are implied.
THE FEEL OF AN INTERFACE
Try an action. Notice the wait.
Change your mind before it finishes.
Review checklistYour last activity is still here.
EarlierEngineering notesA familiar place to continue.
EarlierOpen Release review. Use Back—even while the transition is moving.
Choose a view, then change direction before it arrives.
Travel is slowed for inspection. Watch whether it changes course or finishes a journey you no longer want.
Inspect the interface. Choose a diagnosis.
Reveal the construction, then refine it.
An action icon at rest.
Does its placement feel balanced?
Scan the values as a column.
Where does your eye have to readjust?
Watch the action’s position
when the status arrives.
Watch the selected filter
and the results beneath it.
YOUR REVIEW
Choose what you would change, or reveal the guides to inspect it.
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.
Feedback should be immediate, clear, and in the right place.
Alignment, spacing, and hierarchy quietly shape the experience.
Motion connects states and helps the eye follow what changed.
My focus: how engineers can guide capable agents, verify their work, and stay accountable for the result.
01 / DEFINE
Give agents a clear requirement, acceptance criteria, and relevant context before implementation starts.
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.
The request: “Let a team member change a project’s status.” Select the context you would include, then review the gaps.
Illustrative workflow · authored examplesCoordinating specialist agents across implementation, tests, and independent verification—with explicit handoffs and review.
Current directionConnecting requirements, repositories, and tools so agents can work from relevant context instead of isolated prompts.
Workflow developmentBringing my eye for UI behavior and detail into agents that understand interfaces, interaction patterns, and motion—then translate them into thoughtful implementation guidance.
Research & prototypingI manage the QA team as part of my engineering operations role. Quality brings together the implementation, its behavior, and the evidence behind the work.
The build is green. Review the evidence before deciding what that means for release.
Open the three evidence cards. A passed check only speaks for the behavior it actually exercised.
0 of 3 evidence areas reviewed
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.