Skill Profile
Prototyping
"Building a low- or high-fidelity testable version of a design or product idea so it can be evaluated with users or stakeholders before committing to full development."
YOUR SKILLS
Problems This Skill Solves
- Catches usability problems before expensive development work has started
- Gives stakeholders something concrete to react to, surfacing disagreements that vague descriptions hide
- Tests whether an idea actually works for real users rather than relying on assumptions
- Reduces the cost of design iteration by making changes cheap and fast before code is written
A prototype has to look like the finished product.
The most useful prototypes are often deliberately rough, because that makes people more willing to give honest feedback and suggest changes.
Research & Outlook
AI-assisted design tools can now generate a first-draft prototype from a text prompt or sketch in seconds, pushing the human skill towards framing the right test question and interpreting user feedback.
See This Skill In Action
Watch a professional demonstrate Prototyping in a real working environment — what it looks like, how it's applied, and why it matters.
Design / UX
Prototyping
Also Known As
Growth Path
Builds simple static or low-fidelity prototypes to communicate a basic idea.
Builds interactive, testable prototypes and runs structured usability tests to validate design decisions.
Chooses the right fidelity and method for the stage of a project and uses prototyping to align stakeholders on complex, ambiguous problems.
How to Practise
- 1.Build a paper prototype for a simple app flow and test it with someone unfamiliar with the idea
- 2.Create a clickable Figma prototype of an existing app's core flow, then improve on a specific pain point
- 3.Practise moving from low-fidelity wireframes to a high-fidelity interactive prototype for the same concept
- 4.Run a short usability test on a prototype and document what changed as a result of the feedback
How to Prove
- ·A portfolio showing prototypes at different fidelity levels for the same project, with reasoning for each
- ·Usability test recordings or notes tied to specific prototype iterations
- ·A case study showing a design decision that changed based on prototype testing feedback