Google Fellowship
🎤 Selected as a Fellowship Voices presenter, 10 minutes, Day Two. The general cohort guidance is a strict 6-minute slot covering presentation and Q&A. Build the 10-minute version, hold a 6-minute cut ready. Script version 3, rebuilt Aug 20: eleven slides, built around the Thalia Merino process interview. Deck drafted, rehearsal Aug 19–20. Source files: Institute_Presentation_Script.md and Institute_Deck_Sept17.pptx.
"How might we use Google Stitch, Nano Banana, Gemini Gems, and NotebookLM to build a Cognitive-Process Assessment framework that captures the domain expertise UX/UI designers apply when directing, writing, and refining AI-assisted design, making the invisible 'intellectual fingerprint' of expert design judgment verifiable, assessable, and protectable as student IP, scaled as the global standard for design higher education by 2027?"

Read this before rehearsing

One full-length video, and the number is still tighter than it looks. Every second of video is a second I cannot speak.

The times below are measured, not estimated. They are counted from the actual word count of each section at 145 words per minute. At 130 wpm, which is likelier in a room this size, add about 11 percent to every number.

#SlideWordsSpoken
1Open1090:45
2Grounded at FIT1020:42
3The Workflow1140:47
4What CPA Grades1210:50
5Verification Is Critique1310:54
6Think Gemini (video 1, full)0video only
7The Judgment Underneath2651:50
8What She Did Next1851:17
9What Co-Working with AI Proved ⟨CUT⟩910:38
10Open Source800:33
11The Book750:31
Full script spoken: 8:47 at 145 wpm, 9:48 at 130. Without Slide 9: 8:09 at 145, 9:06 at 130. Video 2 was cut on Aug 17, and the old Slide 9 was merged into the CPA material on Aug 19, which then split into Slide 4, what I grade, and Slide 5, where I check it.

The cut order, decided in advance

If total video runsFull script lands atThen
0:309:48Cut Slide 9. Lands 9:08
1:0010:18Cut Slide 9. Lands 9:38
1:3010:48Cut Slide 9. Lands 10:08
Middle and right columns assume 137 wpm, between the two likely speeds. Time the video before deciding anything else. It is the only number here I don't control, and it decides whether Slide 9 stays. Slides 7 and 8 are the argument. Do not cut those to protect the video. Decide before walking up, not while standing there. No live demo. The only motion is the one video.

Slide 1: Open 0:45

Twenty years of teaching, and I have always weighted the iterative process and the holistic approach over the final artifact. That part is not new.

What is new is that once AI can produce good enough work in seconds, a student who relies on it alone cannot prove how they got there. The work looks finished. The thinking is invisible, and none of my rubrics could tell me whether it happened at all.

So I started building a way to grade the thinking directly, instead of reading it off the work. Cognitive-Process Assessment. CPA.

Slide: one AI-generated UI screen, full bleed. One line of type. "This took eight seconds. What does it prove?"

Delivery. Two sentences carry this slide and both are easy to throw away. "Twenty years of teaching" is the credential, so let it sit for a beat. It is what stops the room hearing CPA as a panic response to AI. "A student who relies on it alone cannot prove how they got there" is the stake, and note whose stake it is. Not a grading inconvenience, a student unable to demonstrate authorship of their own thinking. Every faculty member in the room has a student like that. Say it as their problem, not mine, and the surveillance objection gets much harder to make later.

Slide 2: Grounded at FIT 0:42

Before I built anything, I wanted to know whether the premise held up at my own institution. James Pearce, our Technical Manager for Faculty Research Space and Emerging Technology, confirmed that FIT has no AI detection tools in place and no plan to build any.

If your campus has no detection tool either, and most don't, you are in the same position. When you can't verify AI use from the outside, the only honest path left is to grade the process itself. That's what CPA is built on.

Slide: the Pearce quote, attributed, nothing else.

Slide 3: The Workflow 0:47

Research starts human led. Gemini Notebook synthesizes it. Gemini and Gemini Gems direct the UX writing and strategy, with the student acting as copywriter and strategist. Students craft three art directions in Figma and choose one, and only then does Stitch generate the first UI, from a direction the student already owns. Then create visual image and photo assets with Nano Banana. Finalize the design and the craft in Figma.

Domain-specific knowledge is applied at every step, and that is what makes each decision. Students work with AI from the first day. A human makes the decision at every handoff.

Delivery: this is the densest slide. Tool names live on the diagram. If I am pointing and reading, I have lost twenty seconds I needed elsewhere.

Slide 4: What CPA Grades 0:50

Eight dimensions, and the one to name first is error catching. Did the student catch an Attribution Error, a claim the AI simply made up? Or a Logical Error, a step that doesn't follow even from true premises? That language is Google's own, from the REVEAL paper, mapped into the rubric after Session 1.

I have since added a third, from my own R&D and from an interview with one of my students. A Representational Error: when the model returns a demographically skewed default, over and over, against an explicit instruction. Not a fabricated fact, and not bad reasoning. A different failure, and it needs its own name.

Slide: three error cards across the top, Attribution / Logical / Representational, the third marked NEW. Eight dimension chips underneath, Critical Curation highlighted.

Delivery: this slide answers what I grade. The next one answers where I check it. Don't run them together, and don't start explaining critique here.

Slide 5: Verification Is Critique 0:54

So where do I check all this? In critique. In every class we discuss the what and the why of the work. Design education has run on critique for a century.

And it cannot be only written. That was the objection I worried about most, so I put it to Thalia Merino, a student of mine who had never seen my rubric.

"I wouldn't recommend 100 percent written, simply because it's easy for people to just AI it. Which sounds horrible, but trust, it will probably happen."

A written log can be generated in seconds. A spoken one cannot, because I can stop a student and ask why they rejected the other three directions, and we find out in real time whether they know.

That conversation is what timestamps the record.

Slide: the headline, then her quote at full size, attributed. Nothing else. A quote slide, so the type carries it.

Delivery: read the quote as written, then stop for a full second. She is the student in the video that follows, so this slide introduces her, and the room meets her as a critic before it sees her work. Split from Slide 4 on Aug 19: what I grade and where I check it are two questions, and the second was arriving without a headline.

Slide 6: Think Gemini video 1, full · file titled "Google Case Study"

▶ Roll it cold. No setup, no narration. Say nothing over it. Let it finish, and let the room sit with it for a beat before speaking.

Staging: the room needs to be impressed by the artifact before being told the artifact isn't the point. That is the Slide 1 premise, staged live.

Slide 7: The Judgment Underneath 1:50

Think Gemini. A semester-long project, answering the Young Ones Google brief. Before they generated anything they ran empathy interviews with students and instructors, and built the whole thing from what they found.

Let me be clear about what this is. My students, my course, my pilot.

I guided them through the process. I did not show them my grading rubric. That's teaching.

I asked Thalia to walk me through the judgment calls in her own words.

The teacher character. The team wanted a racially diverse cast, and text prompts would not produce one. Ten to twenty generations, and she was not getting there by writing better sentences.

That is the part worth naming. Prompting is not just words and description. When words stop working you have other moves, and she used them. She stopped rewriting the prompt and changed what she fed the model: a second reference image, on top of the team's art direction reference. Style from reference one, likeness from reference two.

All four team members are credited in small type under the quote attribution, and again on the video slide. On the slide deliberately, not read aloud.

"Sometimes words aren't enough to tell the AI what we want. But it also made us think, maybe there is bias within the AI itself. Maybe it's not intentional, but it does happen."

She diagnosed a model limitation, separated it from her own prompting, and did not accuse anyone of intent. That is critical curation, one of the eight, and that is the Representational Error I named earlier. I had already seen the pattern in my own R&D. Hearing a student describe it unprompted is what convinced me it needed a category of its own.

Delivery: say the disclosure flat and move on. Hurrying past it or over-explaining it both read as discomfort. "That's teaching" is the turn: not an apology for the pilot, a name for what guiding a process without handing over the rubric actually is. Then read the quote as written and stop for a full second. Don't explain it before the room has heard it. "Style from reference one, likeness from reference two" is my line, not hers, from my own analysis in the interview report. Narration, never introduced as a quote.

Slide 8: What She Did Next 1:17

They wrote four KPIs to measure whether their idea worked. One of them was whether a student could explain their reasoning without looking back at what the AI had said. That is almost exactly my seventh CPA dimension. Reflective Reasoning.

So I asked her how she arrived at it. She told me she would throw it out. Too abstract, written in a time crunch while they were preparing the submission. Then she gave me four better ones, all traced back to the pain points from her own interviews.

I asked what made it obvious months later that was not obvious then. She had presented the project many times, people kept asking questions, and somewhere in answering them she realized there was a better way to think about it.

Nobody was grading her. She reopened her own decision, named why it was weak, and rebuilt it out of her research. That is reflective reasoning. It happened because people kept asking her questions, in portfolio reviews and job interviews, which is exactly why I want a rubric that asks on purpose, in every critique.

Slide: her original KPI on the left, greyed and struck through, with a note that the revision came by email months after the course ended. All four revised KPIs on the right, numbered. Her sentence pulled out large: "I honestly think these are a bit too abstract and outdated." Her four, in full, are on the interview page.

Delivery: this is the turn. Pause before "she told me she'd throw it out," not after. The room expects me to defend the framework and I am doing the opposite. Don't soften her critique into "she offered some refinements" or the slide is lost.

Slide 9: What Co-Working with AI Proved 0:38 · the cut

21
Young Ones awards this year, 8 in newly created AI categories
1
Gold Cube, Art Directors Club, for AI Process, not AI Output
3
D&AD New Blood: The Portfolios 2026, Digital Design
6
Students hired before graduation

Think Gemini is one of many. And CPA is not only retrospective now: CT302, Digital Product Design I, runs its full fifteen-week semester on the eight dimensions.

That is what the workflow produces: designers empowered with AI.

Slide 10: Open Source 0:33

CPA doesn't depend on a licensing tier or on detection software, so it can work for any program facing this gap. So I'm sharing all of it, as open source.

The CPA rubric, all eight dimensions. There's a printed copy for everyone in this room, and it's on the site. Use it and tailor it for your own class. Reweight the dimensions your course actually cares about, drop the ones it doesn't, and it doesn't have to stay in design.

Slide: the rubric, one offering, nothing else. No book on this slide. The CC BY 4.0 line sits under the body copy in small type, to be read and not said. No QR code here, because the handout is already in their hands with the URL on it. Full rubric and license on the rubric page.

Delivery: this slide asks for nothing, and that is the whole posture. Don't say "free." It is shared as open source and there's a printed copy in every hand, so "tailor it for your own class" is the line that does the work. Print enough for the room and set them out before I start. Aug 20: "not only the well resourced ones" came out, because "any program facing this gap" already says it without pointing at anyone's budget.

Slide 11: The Book 0:31

[pick up the book]

And this is the book it came from. Empowering Design Education with AI, with my co-author C.J. Yeh. CPA is Chapter 2. Much of the rest belongs to other people: our students, and the industry professionals who talked honestly with us about where this is going.

If you're wrestling with the same question, how do you know a student actually did the thinking, I'd love to compare notes over the next two days. Thank you.

Slide: the book cover, both names, QR code. Nothing else, because I'll be holding the object.

Delivery: split from Slide 10 on Aug 20. The rubric is what I give away, the book is what I made, and they were fighting for the same slide. Hold the book, don't present it. Pick it up mid-sentence the way you'd pick up anything you made. Held up to the room, it reads as a sales close. Aug 17: three asks became two, then none. Aug 19: the Field Guide offer came out, because the book is a purchase and the rubric is the open source piece.

Held in reserve: the leave-behind and Q&A

Not in the ten minutes. Ready for hallway conversations and the one-pager.

DimensionWhat it measuresTools
Prompt ArchitectureStrategic intent, vocabulary depth, and context behind AI instructionsGoogle Stitch / Gemini
Orchestration LogicHow the student chains multiple AI tools into an end-to-end workflowGemini Notebook
Strategic & Content DevelopmentCritical thinking behind feature scope, content priorities, and value proposition, grounded in researchGemini Notebook / Gemini
Critical CurationEvaluating and stress-testing AI output, naming each catch as an Attribution or Logical Error, or as a Representational Error (provisional third category, one observed case)Gemini
Creative Art DirectionTaste and aesthetic choices that override default AI biasesGoogle Stitch
Domain Specific Knowledge ApplicationVisual communication craft, typography, hierarchy, color, composition, used to elevate work beyond generic Gen AIGoogle Stitch, Figma
Reflective ReasoningThe student's ability to explain their reasoning, step by stepGemini Notebook / Gemini Gems
Direct Creative ContributionWhat the student sketches, develops into original artifacts or moodboards, writes, or fundamentally transformsGemini Notebook, Google Stitch, Figma
  • Bunny Quest, by Kokona Akatsu and Haein Noh. CT&D minors personified as bunny mascots, extended into posters, stickers, social personas, and an AI-powered quiz. Gold Cube in AI Process, not AI Output
  • The Socratic Problem Breakdown and the full Vulnerability Map, including the parts that are unresolved. See the Institute page
  • The CT302 gradebook, all 8 dimensions scored 0 to 3, auto-converting to the 40/30/20/10 breakdown. This is the answer to "does it actually work in practice"
  • WEF data: nearly half of entry-level tasks expected to be automated by 2027; design and UX sit in the moderate-substitution zone, so the cognitive layer is what's protected
  • Both empathy interview write-ups
  • Empowering Design Education with AI, the book behind the pedagogy

Rules for this talk

  • Ten minutes still rewards one clear argument. The temptation is to fill the extra four minutes with what the six-minute version dropped. Don't. Spend all four on the case study
  • Credit all four Think Gemini team members by name, on the slide and out loud. This is a team project and the room will notice which way it is handled
  • Be precise about what is retrospective and what is prospective. Think Gemini was not scored under CPA, it predates the CT302 rollout. Say so. The awards prove the underlying skill is real and valued; the periodic-presentation verification layer is what CPA adds going forward
  • Written in the book's voice, not a keynote voice. Where the approach is contrasted with others, stay descriptive. The room should feel invited