pranaykotadia.
What I do
What I do best
  • Product Design
  • UX Research
  • Prototyping with AI
Where I play
  • Writing
  • Endurance
  • Vibe Coding
Pranay on the Georgia Tech campus in a grey Georgia Tech hoodie, Tech Tower behind him.
Education
MS HCIGeorgia Tech, now
B ArchSEA, University of Mumbai
Recognition
  1. 01Team of the Quarter, Prudential India Design at Dentsu2026
  2. 02Finalist, Service Design Award, for Context2023
  3. 03Finalist, Helen Hamlyn Design Award, for Context2023
  4. 04University topper, undergraduate architecture thesis, 10/10 SGPA, University of Mumbai2023
  5. 05Academic Award for Exceptional Thesis Performance, SEA2022
  6. 06Academic Award for Complex Design Thinking, Semester 7, SEA2022
  7. 07Silver Medal, Architectural Rookies Award, all-India level2022
  8. 08Special Mention, India Lost and Found Research Competition2020
{{p.alt}}
{{p.city}}{{p.year}}
20 citiesPick up a photo and move it around

How I use AI

My approach

My AI process

I use AI to make drafts faster. I still decide what’s good.

I use AI to get to working drafts faster and to try more options than I could by hand. The parts that decide whether it’s any good are still on me: framing the problem, giving it the right context, checking what comes back, and deciding what changes.

Plan, generate, review, repeat
Five rules I work by
In my processIn what I design
01Research and sketch firstI only write a prompt after the research and a rough sketch.
02Treat prototypes as draftsEven a polished one is a draft until someone has tested it.
03Review more than I generateMaking versions takes seconds. Choosing the right one takes the time.
04Test before the next promptI put each version in front of a real user before moving on.
05A person decidesThe AI can suggest things, but I make the decisions.
How I write a prompt

A real prompt from Edequity, sent the evening after a round of teacher tests. It has eight parts, and each one is there for a reason.

Set the scene01–02Say what to change03–05Shape the result06–08
Read the full prompt
PPranay, to ClaudeMDteacher-test-notes.mdPNGlesson-editor-v3.png
1
ok, feedback from today’s test with 4 Fellows from the Pune cohort (notes attached). The structure of the editor works. Everything that broke was about whose plan it feels like, so only fix that.
2
ContextThis is the lesson editor. First-year Fellows open it the night before, usually after 10 pm, and have 10 to 15 minutes to finish tomorrow’s plan. 35 to 40 kids, mixed levels, and every lesson follows CPA (concrete, pictorial, abstract) because that’s how TFI trains them.
3
What’s wrong right now1. Every section comes pre-filled by the AI, in the same black text as what they wrote themselves. 3 of 4 asked some version of “did I write this?” and then stopped trusting the whole plan.2. Accept is the loudest thing on the screen. Two of them hit it on every card without reading, and said afterwards it didn’t feel like their lesson.3. There’s no way to see why a suggestion is there. They wanted to know where it came from before using it.4. Before hitting Review, they can’t tell how much of the plan is theirs.
4
What I want- One suggestion waiting at a time, inside the section it belongs to. Pink dashed card, a “Suggestion” label, the source (“From Monday’s quick check”) and a “Why this?” link on the right.- Anything the AI drafted that the Fellow hasn’t touched: grey text with a dotted underline. The moment they edit a word it turns black. No banner, no modal.- Actions: Accept, Edit first, Dismiss. Edit first becomes a real button next to Accept, not a text link. Small keyboard hints on the right (⌘↵ accept, Esc dismiss).- Top right, next to Review: a “Yours” meter, the % of words they wrote or edited, with a thin bar and “2 waiting”.- Put the assistant in a panel on the right, attached to this lesson, not on its own page. It should say what it looked at, like “Looked at Monday’s quick check, class profile, Ch. 3”.
5
Don’t changeThe left nav, the outline with minutes per section, the CPA labels and their colours, the serif for lesson text and sans for UI, the spacing.
6
Visual directionCalm, like a notebook, not a dashboard. The only colours should be the suggestion pink and the purple for actions. No new icons unless you really need one.
7
OutputUpdate the existing desktop screen (1440) with real copy from the Subsets lesson (Grade 7A, Wed 24). Then a second artboard with the suggestion card in every state: waiting, edited, accepted, dismissed.
8
Before you show me, check it against our four principles and tell me which one you think it still breaks.