Problem
Pre-AI Education
Curriculum teaching tools and aesthetics while industry asked different questions.
Education · Curriculum · 2024
Built an AI-integrated design curriculum where AI literacy, DesignOps, and product building replace studio traditions that no longer match industry reality.
Problem
Curriculum teaching tools and aesthetics while industry asked different questions.
System
Five courses integrating AI, systems thinking, and real product constraints.
Process
Teaching philosophy treating each module as a product iteration.
Outcome
Graduates equipped for AI-era product and design leadership.
Artifacts from this engagement
When IIAD brought me in as Associate Professor in 2022, design education in India was still largely pre-AI — teaching tools and aesthetics while the industry was already asking different questions. This is the story of building a curriculum that didn't exist: where AI literacy, DesignOps systems thinking, and the realities of product building replace the studio traditions that had governed design education for 40 years.
Design education in India in 2022 was predominantly studio-based — hand skills, visual aesthetics, typography exercises, print traditions. At institutions that had updated their digital curricula, the focus was on tools: Figma, Adobe Suite, interaction design patterns. The industry had moved past both of these. The designers being hired in 2022 were being asked to think in systems, work in AI-augmented pipelines, understand DesignOps governance, and operate as strategic partners to product and engineering teams — not as aesthetic consultants at the end of a brief.
The gap between what students were learning and what they were being hired to do had become a full degree's worth of distance. IIAD's brief was to close it. Not incrementally — structurally.
Every course was treated as a product with a user. The student is the user. The learning outcome is the product. When a module consistently produced confused students, that was a design failure — and it was treated as one. Modules were redesigned mid-semester when the signal was clear enough. No curriculum is fixed. All of it is version-controlled.
First semester spent as much in observation as in teaching. Documented what students could do, what they couldn't, and the gap between their mental models and the mental models industry was expecting. Ran structured exercises to test systems thinking, AI familiarity, DesignOps literacy, and research rigour. Results confirmed the briefing: the gap was structural, not skill-level. You couldn't close it by teaching harder. You had to teach differently.
No existing academic framework for teaching AI literacy to design students. No DesignOps curriculum template. Both had to be built from first principles — drawing on industry experience (Nagarro, Porsche, Verizon) to define what graduating students actually needed to know. AI & Design Thinking v1 was a 12-week module treating prompt engineering as a design skill, AI tools as collaboration partners, and ethics as a structural constraint — not an appendix. First cohort tested it, it worked, it became a core course.
Replaced approval-seeking critique with structural critique: every review required students to present the decision logic behind their choices, not the choices themselves. "Why this layout?" not "here's the layout." Introduced failure documentation as a graded deliverable — the most valuable design artefact in any sprint is the thing that didn't work and why. Students initially resisted; by semester three, the critique sessions were the most referenced part of the course by students in exit interviews.
Introduced live industry briefs in year two: real problems from real organisations, with real stakeholders providing feedback. Students designed for Bolo Buddy (actual product requirements, actual user constraints). They built components for design systems that were actually deployed. The brief was not simulated. The consequence of a bad decision was visible. That shift — from academic exercise to real accountability — produced a step-change in the quality and rigour of work.
A course is a product. The student is the user. The learning outcome is the value delivered. The critique session is the onboarding flow. The failed assignment is the error state. Every design principle that applies to building a good product applies to building a good course — and the feedback loop is faster, because students tell you immediately when something doesn't work. The best design education I ever got was designing courses.
The most useful thing I brought to IIAD was not academic knowledge — it was client experience. The Rapipay field research methodology became a course exercise. The Porsche governance framework became a DesignOps module. The Nagarro hiring rubric became a course assessment criteria. Industry experience is not supplementary to design education. For the disciplines that matter most — systems thinking, AI integration, product strategy — it is the curriculum.
Every student who graduates with AI anxiety rather than AI literacy is the product of a curriculum that failed them. The anxiety comes from treating AI as a force acting on design rather than a tool used by designers. The moment students understand the mechanism — what LLMs actually do, how they fail, what they cannot do — anxiety dissolves and utility thinking takes over. Demystification is the first pedagogical act.
Well-structured critique is the highest-leverage educational intervention available. It surfaces reasoning, exposes assumptions, forces articulation of decision logic, and models professional discourse — simultaneously, in real time, for everyone in the room. Most institutions use it for validation. Used rigorously, it is a systems thinking exercise, a communication skills session, and a design methods workshop all at once. The investment is zero. The return is compounding.
Speaking engagements, workshop facilitation, curriculum consultation, or research collaboration at the intersection of AI, DesignOps, and design education. The academic context and the consultancy practice inform each other continuously — that bidirectionality is available to the right partner.