The AI Prototyping Mastery Ladder
The 15 essential skills for mastering AI prototyping as a product manager
Hey there 👋 This guide is a preview of some of the content from my course, AI Productivity, which is designed to help product managers bring AI fluency to every aspect of their role, whether it’s prototyping, customer & data insights, product strategy, or execution. Next cohort starts April 7th. Learn more.
AI prototyping is fundamentally reshaping the way the best product teams design, validate, and prioritize what to build.
What’s been equally fascinating to watch is just how quickly this approach has gained adoption amongst Silicon Valley technology firms. We are now at the point where Meta, for example, expects PM candidates to use popular AI prototyping tools like Figma Make, Lovable, or Claude Code to prototype a feature live during their interview process.
When I talk to product managers though, it’s become clear that while many of them may have played around with these AI prototyping tools and potentially built a few prototypes, rarely have they really developed a strong mastery of AI prototyping. Their prototypes often generically solve the customer problem, lack branding, lack meaningful differentiation, and often lack depth.
As AI prototyping has become an essential capability of today’s AI native product managers, I realized we needed a far more rigorous approach to teaching PMs how to truly master this new capability. That’s why I developed the AI Prototyping Mastery Ladder, which catalogs the 15 distinct skills PM need to master to prototyping effectively.
In this comprehensive guide I will motivate why AI prototyping matters, introduce the AI Prototyping Mastery Ladder, and guide you through learning each of the requisite skills to take your prototyping to the next level.
The Case for Prototyping
Before diving into the skills, I want to make the case for why every product team should be prototyping. There are two primary arguments I want to make, the first an evolutionary one and the second a revolutionary one.
The Evolutionary Argument
When I started my career at Microsoft as a product manager, I used to write 30-page specs for relatively small features. That was just the name of the game. As an industry, we’ve evolved quite a bit since then. We gained maturity on our design tools, from Photoshop to Figma, and we realized that a picture is worth a thousand words. Today, teams rely heavily on annotated design mockups to communicate what they envision building because those designs are far higher fidelity than you can achieve in words alone.
Prototyping is simply the next evolution of that progression. A prototype goes beyond a mockup by adding interactivity and even functionality, increasing the fidelity even further.
We’re now seeing organizations move fast to adopt this new medium. Jin Su Park, a lead designer at Notion, recently shared that he attended a design crit where no one shared work via Figma. It was all AI prototypes. Design reviews, exec meetings, customer validation sessions are all moving toward vibecoded prototypes as the primary medium of communication.
The Revolutionary Argument
Now this is where I get particularly excited about the potential of prototyping: I believe prototyping has the potential to change how product teams fundamentally prioritize their roadmaps.
Traditionally, teams start by prioritizing customer problems on the roadmap. Once a problem is prioritized, the team then goes about building a potential solution, going through design reviews and some customer validation.
But the best teams don’t actually work this way. They do something I call product shaping. The idea is that instead of prioritizing problems and then building solutions, these teams build a bunch of prototypes for potential problems, test those prototypes with customers, and then prioritize on the roadmap the most successful prototypes. This might sound subtle, but the difference is profound. You’re prioritizing problem-solution pairs that you know have worked because you’ve already prototyped and tested them.
My favorite example of this is Apple. Johnny Ive was in the lab working on a multi-touch interface for a tablet. He shows it to Steve Jobs, who sees the prototype, and rather than pursuing a tablet, they shelved the entire tablet project, went on to create the iPhone, and ultimately change the world. The prioritization decision was driven by the prototype and what it revealed was possible.
Now, why doesn’t everyone do this? It turns out running an expensive prototyping lab where you’re going to throw away 90% of your prototypes is insanely expensive. Most organizations could never justify that. But AI prototyping completely changes that equation. Now we can all be making throwaway prototypes, testing them, and picking the best ones, as fast as we currently wait for our designers to come up with mockups. That’s the revolutionary potential of AI prototyping.
Now, this isn’t some theoretical future state. This is already happening today. Take, for example, the Claude Code team at Anthropic. They are already operating in this exact fashion. The team produces a variety of prototypes of new features for Claude Code and then ships them internally for dog-fooding. If people love the feature internally, they ship it. If the feature gets limited usage or constructive feedback, they go back to the drawing table to improve it or scrap it. With this approach the prototypes effectively drive their roadmap, not the other way around.
The AI Prototyping Mastery Ladder
Hopefully I’ve now convinced you of why your team should be prototyping. The essential question then comes how do you actually become great at it?
After spending months working with PMs to improve their prototypes, I’ve identified 15 essential skills that you need to master to become a truly effective AI prototyper.
I’ve organized them into a hierarchy of skills because it turns out you have to master the basics before moving on to intermediate and advanced levels, much like the progression of craftsmen from apprentice to journeyman to master.
Let me walk you through each of the three levels:
Apprentice
At the apprentice level, we are really focused on mastering the foundational skills of prototyping, which include the following:
Prompting - The way prototyping tools work is we spend most of our time prompting in English to have them generate code on our behalf. So the first set of skills is around effective prompting.
Editing - We then spend most of our time editing our apps, refining and improving what was generated. There are multiple ways to edit effectively (prompting, prompting w/ selection, visual editing, and code editing), and learning the trade-offs between each is important.
Design consistency - Beyond that, design consistency is critical. The default output of these tools doesn’t look anything like the products we build. We need to learn how to get our prototypes to incorporate our design guidelines and design systems so they look and feel like products from our company.
Designer collaboration - We also shouldn’t be building prototypes in silos, so learning to collaborate with designers is essential.
Limitations - Equally important is learning the real-world limitations of AI prototyping so we understand when not to reach for a prototype for the task at hand.
Tools - Finally, we want a deep understanding of the landscape of prototyping tools and which ones are best suited for our prototyping use case.
Once you’ve mastered these skills, you are well equipped to start building a few prototypes for your team.
Journeyman
At the journeyman level, we are learning advanced prototyping techniques that enable us to deeply incorporate prototyping into our daily product development workflow. The critical skills at this stage include:
Versioning - Versioning refers to keeping track of different iterations of your prototype so you can compare, roll back, or fork your work without losing progress. Knowing how and when to fork, in particular, becomes critical for managing a rich prototyping workflow.
Debugging - As you start prototyping in earnest, you’ll inevitably hit bugs. If you’re non-technical, this can be overwhelming. So learning how to debug as a non-developer is a crucial skill.
Diverging - And then there’s diverging, which is this idea that we shouldn’t just take the first idea in our head and build it. Instead, we should learn how to use AI as a thought partner to come up with multiple design variations, just like we would with a human design partner.
Customer validation - One of the primary use cases for prototypes is validating them with customers. But prototypes offer so much more in terms of validation opportunities than static mockups. So we need to learn how best to leverage these new opportunities to maximize our validation.
Executive reviews - Prototypes are quickly replacing design mockups as the primary presented deliverable in executive reviews, so it’s important to learn how to use them effectively in this setting.
Master
At the master level, we are fundamentally reshaping our product development process due to our new AI prototyping capability. To unlock this, we need to master the following skills:
Technical editing - I’ve found those that are most successful at prototyping get technical enough to gain far more precise control over their prototypes. Technical editing is all about getting technical enough to wield this control.
Functional prototyping - We can make our prototypes go beyond experience prototypes and make them fully functional, where they call real APIs, store data, and support actual user behavior. This skill is all about learning exactly how to do so.
Engineering handoffs - Once we’ve developed our prototype, we need to hand it off to engineering for turning it into a production app. We are starting to see some best practices emerge on how to do this most effectively.
Product shaping - As I mentioned, the real unlock for prototyping isn’t just improving our customer validation process, but fundamentally reshaping our roadmap prioritization process. There are some crucial best practices for making the transition to this new prioritization approach.
Skills In Action
To help you get started on your journey to becoming a master prototyper, I want to go deep on four of these skills that I think are particularly transformative: design consistency, diverging, functional prototyping, and customer validation. (Better yet, watch the video to see each of these demos live).
Keep reading with a 7-day free trial
Subscribe to Sachin Rekhi to keep reading this post and get 7 days of free access to the full post archives.