- Course
- Interaction Design and Urban Experiences
- Meets
- Monday, Wednesday, Friday, 9:00 to 12:00
- Room
- 3100 A&AB
- Instructor
- Ron Bronson
Overview
This studio treats interaction as one subject across digital interfaces and the built environment. A fork in a hallway, a fare gate, a signup form, and a handoff to an automated agent run on the same small set of mechanics: decision points, affordances, feedback, and state. Students learn to see these mechanics in urban space before they build them in the digital layer.
The first weeks build core skills through fieldwork, drawing, and physical prototyping. From week three, each student carries one urban interaction of their choosing through four stages: discovery, definition, development, and validation. Because each week’s work feeds the next, the final project is assembled from work already done.
Practice
The studio draws on my professional interaction design practice. Over that career I’ve hired, taught, and managed interaction designers and run websites, while the work itself grew from individual tools and pages into products, platforms, SaaS systems, and agents.
The course gives students practical experience reading unfamiliar systems, interpreting how they work, representing interactions clearly, making design decisions, building prototypes, testing them, and revising from evidence. Fieldwork, drawing, mapping, physical prototypes, Figma, HTML and CSS, and other tools give students multiple ways to practice the same core skills across physical and digital systems.
The project arc
1Discover
Study a familiar urban task, looking at how it works today and what it asks of the people using it. Methods include direct observation, shadowing, interviews, doing the task yourself, and analogous experiences.
2Define
Turn what the research surfaced into a reframed challenge with evidence behind it. Accessibility and exclusion sit at the center, drawn through journey maps, current state flows, and requirements.
3Develop
Design the interaction across levels of fidelity, from sketches and paper prototypes through wireframes to a working digital prototype, including the failure states and ending states a full lifecycle produces.
4Validate
Revise the design from the results of usability testing.
By the end
By the end of the term, students will be able to:
- Describe interactions across physical and digital settings precisely, using the terminology, methods, and patterns of interaction design.
- Run qualitative research through direct observation, shadowing, interviews, and analogous experiences, with a clear line from the findings to the design.
- Define a design problem with accessibility and exclusion at its center, built on evidence gathered in the field.
- Represent interactions through sketches, storyboards, maps, task flows, journey diagrams, states, wireframes, and prototypes.
- Build prototypes for testing at several levels of fidelity, from paper through working digital interfaces.
- Reconstruct an existing system from an analysis of its wayfinding, information architecture, and interface behavior.
- Design the full interaction lifecycle, including failure, recovery, completion, cancellation, and transition.
- Prototype conversational and agent interactions to judge where they belong.
Fifteen weeks
The course runs on a weekly cycle, moving between topics as the work calls for them.
- 01Read the environmentOrientation, navigation, signs, decision points, affordances, field observation. Website launch.
- 02Watch people moveEnvironmental interaction, feedback, constraints, legibility, field studies, presentations.
- 03Draw the interactionSketching, sequence, storyboards, diagrams. Observation, shadowing, analogous experiences. Final project issued.
- 04Make it physicalPaper prototypes, physical models, acting it out, fidelity. Interviewing and moderating a test.
- 05Name what existsInformation, classification, taxonomy, hierarchy, labeling.
- 06Rebuild the structureNavigation, organization, reconstruction, comparative analysis. Problem definition and accessibility. Midterm review.
- 07Map the taskTasks, actions, flows, states, transitions. Journey mapping.
- 08Build the interfaceWireframing, components, patterns, interface behavior.
- 09Make it runDigital prototypes, HTML, CSS, and JavaScript concepts, responsive behavior. Wardley mapping introduction.
- 10Design for failureErrors, interruption, edge cases, accessibility, recovery.
- 11Design the endingCompletion, cancellation, deletion, transition, offboarding. Usability testing.
- 12Shape the conversationPrompt engineering, instructions, context, constraints, conversational interaction.
- 13Design the agentAgents, tools, memory, state, permissions, handoffs, evaluation.
- 14Carry it throughFinal project development, prototyping, testing, critique.
- 15Present the workRevision, final presentations, course website completion.
What we read
Each reading is assigned in the week its topic comes up.
- How Artifacts Afford, Jenny L. Davis. Read against wayfinding, affordances, and signifiers.
- Content Everywhere, Sara Wachter-Boettcher. Read against information architecture and content.
- Beyond the Prototype, Douglas Ferguson. Read against physical and digital prototyping.
- Ends, Joe Macleod. Read against endings, offboarding, and failure states.
- The Best Interface Is No Interface, Golden Krishna. Read against prompts, conversation, and agents.
- You Are Not a Gadget, Jaron Lanier. Read against the agent experience weeks.
- What Is a Designer, Norman Potter. Read across the whole term as a stance on the work