Teaching portfolio · Micro-teaching reflection

Practicing a workshop, in twenty minutes.

This page documents the design and delivery of a single twenty-minute micro-teaching session for the course Enhancing Learning Experiences with AI. It traces the path from the contextual reasoning that came before, through the article that quietly redirected my approach, to the live session itself and the feedback I received afterwards.

The micro-teaching session in progress: Faruk seated at a long table with a laptop, the portfolio page shown on a large wall-mounted screen, two participants partially visible in the foreground. In the room · 30 April 2026
In the room. EKA · Spring 2026
Course
Enhancing Learning
Experiences with AI
Format
20 min
micro-teaching
Delivered
30 April
2026
Context
Learning & Teaching
in University, EKA
01 The process

Six pieces of thinking, one short performance.

Long before the twenty-minute session, the work was already underway. I had mapped the course context, written its aim and intended learning outcomes, and drafted a course canvas. The micro-teaching slot was where all of that quietly distilled into a single, performable shape, the part of the course I could actually stand up and do.

Somewhere in the middle, I read an article about how studio-art teachers in higher education actually assess student work, and recorded a short voice reflection about it. That reflection became the hinge: it changed what I thought a twenty-minute teaching slot was for.

01 / before
Context map
Who is in the room, what is fixed, what is open, where the tensions live.
02 / before
Aim & ILOs
A two-sentence aim, six ILOs spanning Bloom from identifying to reflecting.
03 / shift
Article reflection
A study on studio-art assessment, and a voice memo that reframed what the session should do.
04 / plan
Session design
An interactive web app, not a deck. Sentiment in, prototype out, twenty minutes.
05 / do
Delivery
Live, with QR codes, generated ideas, and a randomised teacher pick.
06 / after
Peer feedback
Notes from a peer and a structured letter from a lecturer, gathered together.
02 Where I started

The context map made the constraints visible.

The course I am designing is a one to two day workshop for teachers who are curious about AI but do not see themselves as technical experts. Before I could plan a twenty-minute taste of it, I had to map the situation: a small group of five to eight participants from mixed institutions, with AI experience ranging from never used to daily, attitudes ranging from curious to skeptical, and each one returning to a different institutional culture afterwards.

The map made one thing clear: the workshop must hold space for both the enthusiasts and the resisters, and it cannot pretend to deliver mastery in two days. What it can deliver is one good prototype each, plus the confidence to keep going.

Context map · before
A workshop, mapped.
01 · STUDENTS
Participants
5–8 teachers from mixed institutions. Curious to skeptical.
02 · CURRICULUM
Format
1–2 day workshop. Learning by making. AI as creative partner.
03 · RESOURCES
Setting
EKA seminar room, BYOD laptops, modest funds, time-bounded.
04 · INSTRUCTOR
My role
Solo. Facilitator, not expert. Comfortable with the content, less so with the conventions.
Designed before this session. Open the full visual document below.
03 Intentions for the session

Three things I wanted the twenty minutes to do.

A micro-teaching session is a strange object. It is too short to teach anything in depth, and too long to be merely a demonstration. I decided to treat it as a condensed prototype of the workshop itself: a small, complete arc that participants could walk into curious and walk out of having seen, felt, and tried something. The session needed to do three things at once.

01
Show, do not explain.
If the workshop is about treating AI as a creative partner, the session itself had to be one. So rather than open a slide deck about AI, I built the session as a live web app where AI is generating the room's experience in real time.

The medium is the message.
02
Make participation visible.
Every person in the room had a phone and a voice. Sentiment votes, course submissions, and live results were collected via QR code and shown back on screen. The point was to demonstrate, in seconds, what active learning can look like with these tools.

Voting is teaching.
03
Land one risk gracefully.
The riskiest moment was a live AI build: take one teacher's course idea, generate a prototype with Lovable on the spot, in under three minutes. If it worked, the whole workshop premise would be felt. If it failed, we would still have a story.

Magicians rehearse.
04 Mid-process · article reflection

Halfway through, a study about studio teachers redirected the brief.

I recorded the reflection as a voice memo rather than a written note, because I wanted to catch the unfinished thinking: the moment something shifts before it has become an argument. What surfaced was that the article was not really telling me about AI. It was telling me about who is in the room.

The study describes a specific kind of professional. They are accomplished in their practice. They were trained to make work, not to teach it. They inherit a vocabulary, rubrics, intended learning outcomes, criteria, that often feels borrowed from elsewhere. And underneath the inherited vocabulary, what most of them actually use to judge a student's work is intuition: a gestalt formed through years of making and looking. The article is honest about this. It also notes that there is rarely a departmental conversation in which this can be said out loud.

That reframed the workshop for me. The point is not to add AI to teaching practice. It is to create a small, well-supported space where teachers can talk about teaching at all, with AI as the pretext and the playground. The session should not perform mastery. It should make room for the same ambiguity, experiment and failure-tolerance that studio teachers already work inside, and treat AI as another tool that produces ambiguous, sometimes useful, sometimes irrational output: a creative partner in the same mode as the practice itself.

Voice reflection · on the article
A short note from the middle of the process.
Recorded after reading the article, before the session was finalised. Roughly two and a half minutes.
The reading
Art, Design & Communication in Higher Education · a study of how studio-art instructors assess student work.
Open the article ›
05 The session itself

Twenty minutes, one live web app, one room.

Instead of slides, the session ran inside a single Next.js app deployed to Vercel. Participants scanned a QR code on their phones to vote and submit; the host screen showed the live aggregation, the generated ideas, and the final build. The full session is embedded below.

Live session app · 30 April 2026 If the embed is sluggish, open the session in a new tab. The app is unchanged from the day of teaching.

Inside the twenty minutes.

00:00
Welcome & QR
Quick framing of the session, role clarification, scan the QR to join. No slides. The host URL stays on the projector.
02:00
Sentiment in
Three sliders on each phone: AI familiarity, excitement, concern. Live aggregation revealed on the host screen. The room sees itself.
05:00
Topic & goals
A short stretch of direct teaching: what AI as a creative partner means in practice, why the workshop format is small and low-stakes, the goals for the demo.
07:30
Submit your course
Each teacher submits a course title and one sentence describing what students should get out of it. Submissions appear on the host screen as they arrive.
10:30
Idea generation & random pick
Claude generates an AI-supported activity for each submission. A randomising animation cycles through names and lands on one of the submissions.
12:30
Live build with Lovable
The picked teacher's brief is turned into a PRD on screen, then handed to Lovable. We watch a working prototype assemble itself in roughly two minutes.
16:00
Other use cases
A short storytelling stretch: how AI fits into large lecture settings, grading workflows, and the boring repetitive parts of course preparation.
17:30
Sentiment out
The closing slider vote, set next to the opening one. The room sees how it shifted, or did not, across twenty minutes.
19:30
Close
A breath. A thank you. Questions.
What worked

The session did what it tried to do.

  • Structure was visible. Slides had timeframes, roles were clarified at the start, the arc was readable.
  • Voting created a fast read of the room. The opening sentiment vote turned twenty strangers into a measurable group in under two minutes.
  • The mid-session storytelling pivot. Leaning back from the laptop and speaking freely changed the pace and gave the room permission to listen rather than do.
  • The emotions wheel found a new context. A familiar tool used in an unfamiliar way reframed it for a colleague in the room.
  • The live build landed. The prototype assembled in time. The room saw a working artefact emerge from a teacher's one-sentence brief.
What I want to develop

Where the next iteration should put its weight.

  • Designed questions, not improvised ones. When time allows, prepare specific whole-class and small-group prompts in advance, to manage timing while still leaving room for spontaneous threads.
  • The EKA GPT for ILOs. The lecturer's letter pointed out that EKA has a GPT tool that goes from course description to ILOs. My demo went in the reverse direction. Worth connecting the two.
  • Posture as pedagogy. The lecturer noticed the moment I stepped back from the screen. I want to make that shift in posture and pace a deliberate move, not an accident.
  • A graceful fallback path. The Lovable build worked. Next time I want a pre-baked fallback ready, so a technical hiccup costs five seconds, not five minutes.
  • Closing the loop more slowly. The final two minutes were tight. The closing comparison deserves room to breathe.
06 Feedback received

Two voices, two registers.

After the session I received feedback in two different forms. A peer took live notes during the session, capturing the moment-to-moment observations as they happened. The lecturer sent a structured letter afterwards, written in the describing, interpreting, relating form we have been practicing in class. I have kept them both here in their original shape because the difference in register tells me something about how the same twenty minutes was read from two distinct vantage points.

06 · A Peer notes, taken in the room. Handwritten · in-session
From a peer › observing · in the moment

Read live, not later.

The note is short and made on the fly: a few numbered observations under the heading Faruk Shuaibu › the feedback. What I read in it is a particular way of looking. The observer was tracking the choreography of the session, posture, sequencing, the use of waiting time, more than any single argument I was trying to make. I take that as a sign that the form of the session was visible and legible as form.

The note also flags two open prompts (2. ...the course has, 3. ...that the actual knowledge in my class might be weak) that read like questions held in the air rather than conclusions. I value them precisely because they are not resolved.

Observations, transcribed
  • Posture and pace. Sitting, then diving into the task directly. Active tasks. "Body is moving, my input matters."
  • The tool, named. Lovable.dev as a design tool, an AI tool that lets you build apps through chatting with AI.
  • Use of time. Moving between tasks well, when one thing is loading, explaining the next.
  • The ethical question landed. Bringing in ethics as the question, and the possible negative side, was noted as important.
  • An unfinished prompt. "...the course has —" a question left open about what the workshop carries with it.
  • A self-directed worry. "...that the actual knowledge in my class might be weak" — an observation the peer was reflecting back onto their own practice, not mine.
06 · B Lecturer letter, written afterwards. Structured · post-session
From a lecturer › describing · interpreting · relating

Dear Faruk,

I'm sending my feedback on the micro-teaching session. It loosely follows the same structure we used in class: describing, interpreting, and then relating it back to myself. If anything is unclear or if you'd like me to expand on something, just let me know, I'd be happy to.

Your teaching session had a very clear structure, with the introductory interactive activity at the beginning, followed by the main content, and later a conclusion with a short reflective task. You used digital tools (instead of paper and pen) to engage participants, which made it possible to quickly gather and see the group's overall attitudes toward the topic. The slides had a timeframe, which helped us understand how long and how deeply we were expected to engage with the topic.

You explained what we were going to do and clarified your role. Since participants had to write down the objectives of their own course, this activity also helped us step into our own roles. The task about our attitudes and writing the ILOs gave us time to transition from the previous topic and focus on the current one. Overall I believe you balanced the technical and more serious aspects of the topic very well with a fun and interactive activity, allowing space for both.

I noticed a shift in your behaviour in the middle of the session when you were explaining how AI tools can be useful in large lecture settings. The situation made me think of storytelling. You leaned back a little from the computer and spoke freely, which signaled that we can listen and focus our attention on you. It changed the pace and made your micro-teaching session more dynamic.

We also had an open and critical discussion, which you helped to further develop and connected back to the industry for a broader context. In the future when you have more time, you could think about what kinds of questions, either for the whole class or as a smaller group task, could help generate this kind of discussion. A small group task allows you to manage time more precisely, while a whole-group discussion works well in a setting where participants feel safe and can spontaneously bring in new ideas.

When you showed how the ILOs we wrote could be used to generate learning activities, it made me think about how EKA has a GPT tool for teaching staff to help formulate ILOs from course descriptions, and why it might be useful to also approach this the other way around.

The way you used the emotions wheel made me reflect on myself as a teacher that I've used it before in another context, but it hadn't occurred to me that the wheel could be used in this way. Thank you for showing me this possibility.

Best regards.

My written reply › received · acknowledged · forward

Thank you.

Thank you very much for taking the time to write such detailed and thoughtful feedback. I really appreciate how you structured it and connected it back to your own teaching practice.

I'm glad the overall structure of the session and the use of digital tools came through clearly. Your observation about the moment I stepped back from the computer and moved into more of a storytelling mode was particularly useful. It helps me see, more consciously, how changes in posture and pacing can signal a shift in attention and make the session feel more dynamic. I will keep developing that deliberately.

Your comments about structuring open and critical discussions were also helpful. I like the idea of designing specific whole-class and small-group questions in advance, to manage time more precisely while still leaving room for spontaneous contributions when the group feels safe.

It was especially interesting to read that the way I used the emotions wheel gave you a new perspective on that tool. That means a lot to me. I am very interested in the emotional aspects of learning and I am happy it resonated with your own experience.

I was also intrigued by your note about the EKA GPT tool for helping formulate ILOs from course descriptions. I hadn't connected it directly with the reverse direction I showed in the session, and I would be very interested to learn more about how teachers are using it in practice.

Thank you again for the encouraging feedback and for the concrete suggestions I can build on.

Carry forward · 01
Designing for posture is designing for attention. The shift away from the screen mattered as much as what was on it.
Carry forward · 02
Most studio teachers were never trained as teachers. The workshop is for the conversation about teaching that institutions rarely make space for, with AI as the pretext.
Carry forward · 03
Building the session inside a working app, not a slide deck, made the workshop's premise legible without having to argue for it.
Carry forward · 04
A short voice note can shift a design more than a long rewrite. I want to record more of these.

The micro-teaching session is a rehearsal, not the workshop. What it gave me is harder to put on a slide: a felt sense of how the workshop wants to move, where it slows down, where it asks for hands, where it asks for silence.

The next pass at this course will not start from the slides. It will start from this twenty minutes, asking which parts deserve to grow, and which were honest only because they were short.

Designed and delivered solo. Documented as part of the EKA Learning & Teaching in University course portfolio, May 2026.