- ✓Iterative prototyping, the practice of building a series of progressively more refined versions of a solution rather than trying to get it right first time, is particularly valuable when working with emerging technologies where established patterns and best practices may not yet exist.
- ✓Each prototype iteration should be guided by a specific hypothesis or question: building without a clear learning objective produces code and artefacts but not necessarily insight.
- ✓The feedback gathered from showing working prototypes to potential users, even very early and rough ones, is almost always more valuable than additional time spent refining assumptions in isolation.
- ✓Emerging technologies often have limited or immature tooling, documentation and community support, which means developers need to be comfortable with uncertainty, comfortable reading primary source documentation and willing to experiment and fail quickly.
- ✓Documenting the lessons learned from each prototype iteration, including what worked, what did not and what questions remain open, is essential for building cumulative knowledge and for communicating your development process in academic assessments.
Listen to the full episode inside the course. Enrol to access all 80 episodes, plus assignments, tutor support and Student Finance funding.
Start learning →Alex: Welcome back to The Study Podcast. Today we're looking at the prototyping process for emerging technologies, which is where research meets practice. Sam, why is prototyping particularly important with emerging technologies?
Sam: Because with established technologies you can often draw on the accumulated experience of many practitioners who have solved similar problems before. With emerging technologies, that knowledge base is thin or doesn't exist yet. Prototyping is how you generate the knowledge you need about how the technology actually behaves in your specific context, for your specific use case, with your specific constraints.
Alex: What does an iterative prototyping process look like in practice?
Sam: It starts with defining a specific question or hypothesis that the prototype will test. Not 'let's explore this technology' but 'if we use this technology for this specific purpose, will it achieve this specific outcome?' The specificity is important: a prototype that tries to test everything discovers nothing. Then you build the simplest version that could test that hypothesis, what's often called a minimum viable prototype. You evaluate it, extract the learning, refine your hypothesis and build the next iteration. Each iteration should be faster and more informed than the last.
Alex: What are the specific challenges of prototyping with emerging technologies?
Sam: Documentation is often incomplete, out of date or simply nonexistent for the most cutting-edge tools. The APIs and interfaces may change between versions, breaking your prototype in ways that are hard to diagnose. The community knowledge that you rely on for conventional technologies, Stack Overflow answers, blog posts, GitHub issues, may not exist yet for very new tools. This means you spend more time reading academic papers, reaching out to researchers and working directly with the technology in exploratory ways.
Alex: What's the right mindset for this kind of work?
Sam: Comfortable with ambiguity. Willing to fail quickly and learn from it. Curious rather than frustrated by surprises. And disciplined about documenting what you discover, both what worked and what didn't. The documentation of a prototyping journey is often as valuable as the prototype itself: it captures the learning that makes the next iteration faster and better informed.
Alex: What should the output of a prototyping process be, in terms of what you document for an assessment?
Sam: A log of the iterations: what you set out to test, what you built, what you observed, what you concluded and what it implied for the next iteration. An honest assessment of the technology's capabilities and limitations as demonstrated by your prototype. A reflection on what the prototyping process revealed that research alone could not have shown. And a realistic view of what would be needed to move from prototype to production, which often involves much more work than the prototype itself suggests.
Alex: Really practical guidance for a challenging unit. Thanks, Sam. We'll look at the ethical dimensions next.