Case study · a design practice project by Danila Kolbasin

A practice tool for design decisions. Not an AI that designs.

This is a practice project for designers, not an AI design tool. The site makes no AI calls: the four practice cases are written in advance.

As the tool says on its first screen: “Directions are pre-written: drafted with AI, edited by me.”

  • Practice tool
  • No live AI
  • No sign-up
  • Stays in your browser

AI can draft design options in seconds. Choosing one, and saying why, is still the designer’s job. This tool trains that part.

How a round works

  1. 1

    Pick a case

    For example, a fitness app: get a new user to their first booking in under 2 minutes.

  2. 2

    Get a situation

    Drawn at random, like “You have 2 weeks and one engineer.”

  3. 3

    Choose and change

    Pick one of three directions, each with a sketch and its trade-offs. Change it to fit the situation.

  4. 4

    Say why

    Write why, and what you give up. You keep it as a decision record.

Directions screen: the case 'Get a new user to their first class booking in under 2 minutes', a black situation card 'You have 2 weeks and one engineer.', and three directions with grey screen sketches. The same Directions screen in the dark theme.

One case, one situation, three directions. The situation changes which one is right.

What it trains

Three habits that AI can’t do for you, practised in short rounds.

Why it matters to a product team

  • Fewer decisions argued twice.The record holds the goal, the situation, what was chosen and rejected, why, and the cost. That is a format a team can reuse in reviews and handoffs.
  • Sharper design reviews.A 90-second round is a warm-up for critique: people practise reasoning from a constraint before they discuss real work.
  • Onboarding and interviews.Junior designers see that “right” depends on the situation. A hiring team can read how someone reasons, not only what they make.
  • Using AI without giving up judgment.AI makes the options; a person chooses and signs the reason. Every screen says who drafted what.
A saved decision record: goal, situation, chosen direction, change, rejected directions, why, and what is given up, with buttons to copy Markdown, download, or copy a share link.

What you keep: a decision record. Copy it as Markdown, download it, or share a read-only link.

These are the uses I designed it for. It hasn’t been tested with teams yet.

How I built it

I directed an AI coding agent, Claude Code, with a short rulebook and five review gates where it had to stop and wait for me. I chose the four cases, edited all 12 direction cards, approved 12 situations and 24 changes line by line, and set the look. The agent wrote the code and the first drafts.

Two decisions that shaped it

Decision recordv2 · 4 Nov

My own test showed I was making reasons up

Situation
Version 1 asked “Why this one?”. On a made-up case, nothing is at stake, so the reason was made up too.
Chose
A random situation card, and a step to change the chosen direction. Now the question is “Why this change?”.
Gave up
One more step. The time goal moved from 60 to 90 seconds.
Decision recordv3 · 5 Nov

“Why is the AI fake?” without paying for AI

Situation
Live AI on my API key meant cost, abuse on a public site, and a long wait.
Chose
“Your own case”: copy a ready prompt into your own AI, paste the answer back. The site still calls nothing, and those screens say “Drafted by your AI”.
Gave up
Two app switches and a paste. Quality depends on your AI.

What real AIs did with it

The morning after “Your own case” was built, I ran three test goals through ChatGPT, Claude and Gemini.

Limits and next steps

There are no usage numbers: the site has no analytics, by design, and I haven’t tested it with real users yet. Next, I want to watch a few designers use it. Do the situations change their choices? Do their reasons get more specific?