The offer email lands and your instinct is to reply 'yes!' in five minutes. That reflex is exactly what costs people thousands - an offer is the start of a conversation, not the end of one.
A portfolio isn't a collection of pretty screens. It's a story about how you think. Understand what makes portfolios effective and how to communicate your design thinking.
Before any design work begins, the team has to agree on where the product is going and why. Vision defines the destination; strategy maps the route; the spec writes it down.
A funnel is a bucket with a hole: you pour users in the top and keep paying to refill what leaks out the bottom. A growth loop is different - each user you get helps bring the next one. This module is how to build the loop.
Even a product people love leaks users - a finished project, a tighter budget, a failed payment. This module is the defensive side of retention: spotting the users slipping away, catching them in time, and winning back the ones who already left.
Prioritization & RoadmappingStep 6: Business & growth
You've decided what to build - now you have to show the plan without promising dates you'll have to break. A roadmap is a communication tool, not a delivery contract.
Two products with the same features, and one is the obvious choice. Differentiation is the reason - the point of difference users actually care about, and the trade-off behind it.
If you can't say why you in one sentence, neither can your customer. The USP and the classic positioning-statement template that pin it down - filled from evidence, not wishes.
You can build the best product in the category and still watch launch day pass in silence. Go-to-market is the plan for how a product actually reaches the people it's for - and convinces them to care.
A launch isn't the moment you deploy - it's the moment people notice. And after the big launch comes the quieter, steadier work of telling users what's new, release after release, so the product never feels stalled.
Lessons
1Launch & Release Marketing2 min
2Launch Types - Soft vs Hard3 min
3Release Marketing - Notes, Changelogs & Announcements3 min
A channel is a path to reach the people you're for. There are dozens, they all cost time or money, and the fatal move is trying all of them at once. This module is about picking the few that matter.
The habit of zooming out from the screen to the whole thing - the need it serves, the business behind it, the bet it represents. It's the jump from making products nice to helping decide what gets made.
Meeting the requirements should be the floor, not the goal. Products that only work are easy to replace; products users feel something about are not. That feeling is the soul.
Discovery leaves you with a pile of notes, not a decision. This module is the disciplined path from raw signals to a clear, one-paragraph bet the whole team can get behind.
Thirty pages of notes into clear patterns - the concrete four-step process: break notes into observations, cluster by affinity, count and weigh, then pull out jobs, pains, and gaps.
You shipped the feature - but did it work? Metrics are how a team answers that with a number instead of a shrug, and this topic is how to pick numbers that mean something.
Goals tell you where to aim - these are the numbers that tell you where you are. The core metrics every product runs on, how to spot the ones that lie, and the unit economics behind a bet.
You can spend months making a product more usable and ship nothing leadership can point to as a win. That's the UX trap. Growth design escapes it by tying design decisions to the metrics that decide whether a business survives - the AARRR funnel.
You've got a growth goal and five ideas for hitting it, and everyone's certain theirs is best. Experimentation is how you let reality settle the argument instead of the loudest person in the room.
Lessons
1Experimentation2 min
2Hypotheses - Turning Goals into Testable Bets3 min
Acquisition fills the top of the bucket; retention is whether the bucket has a bottom. It's the cheapest growth there is - keeping a user costs a fraction of winning a new one - and the thing that decides whether a product compounds or leaks.
A backlog of 200 items and everyone's pet feature - prioritization is how you decide with evidence instead of volume, and a roadmap is how you communicate the plan without promising dates you can't keep.
You can know your users cold and still lose - because you never looked outward. This is the market side of strategy: reading the landscape, and claiming a spot in it that's yours.
Clients forget the pixels and remember the experience of working with you - whether you were reliable, clear, and easy to trust. This module is about the communication that runs through a live project and turns one client into a repeat one.
A client said yes to talking - now you have to turn that interest into a signed, well-scoped, fairly-priced deal. This module covers the paperwork that protects you: proposals, pricing, scope, and contracts.
What works in a five-person startup will get you ignored at a 5,000-person enterprise, and vice versa. How you communicate has to flex to the size, stage, and shape of the place you're in. This module shows you how to read the room - at the scale of the whole company.
The talks you dread - pushing back, delivering bad news, asking for more money - are the ones that shape your career most. This module makes them less scary by giving you a method instead of nerves.
Being understood isn't the same as being agreed with. Clarity gets your idea across the table intact. Persuasion is what moves people who weigh your design in revenue, risk and roadmap space.
Lessons
1Arguing Design Decisions - Introduction2 min
2Anatomy of an Argument3 min
3Stakeholders & Their Metrics4 min
4Evidence for a Decision3 min
5The Four UX Laws4 min
6Storytelling & the Rhetorical Triangle4 min
7Handling Objections4 min
Practice
1Translate a Design Decision for Stakeholders45 min
You know discovery matters - now the how. This is the toolkit: talk, watch, ask at scale, or read what's already known, and how to pick the right one for the question in front of you.
This is the PM's discovery toolkit - talking to and watching users to decide what's actually worth building. Understand it, and you stop designing what the spec guessed and start designing what people need.
Interviews aren't the answer to every question. Match the method to what you're trying to learn - talk, watch, ask at scale, or read what's already known.
When a stakeholder says 'I don't like how this looks,' opinion beats opinion and the loudest voice wins. Measuring design gives your work the same evidence-based language finance and marketing already speak.
Lessons
1Measuring Design2 min
2Design-Quality Metrics - Task Success & Top Tasks3 min
The offer email lands and your instinct is to reply 'yes!' in five minutes. That reflex is exactly what costs people thousands - an offer is the start of a conversation, not the end of one.
Freelancing lives or dies on a steady flow of work, and the designers who struggle are usually strong at design and unpracticed at finding clients. The search has to run while you are busy.
Presenting is two skills wearing one name: the thing you build, and the way you deliver it live. A great deck delivered at speed loses, and a confident delivery of a muddled deck confuses.
Strong authentication wants complexity. The person at the screen wants to get in. Push complexity too far and users route around you with reused passwords and sticky notes, which leaves you less secure than when you started.
A table of ten thousand rows is useless as ten thousand rows. What makes it work is everything around the rows: what you cut, what you sort by, what you can act on, and what survives a phone.
A comparison table exists for the purchase somebody agonizes over, where too many similar options and a real cost of choosing wrong produce a freeze. It only works if the data underneath it is complete.
Lessons
1Feature Comparison Tables - Introduction1 min
2Anatomy of a Comparison1 min
3When a Table Belongs2 min
4The Data Underneath2 min
5Selecting and Comparing2 min
6Coming Back to a Comparison2 min
7Helping Somebody Decide2 min
Practice
1Design a Comparison Table for a Considered Purchase50 min
A mega menu shows a whole level of the site at once, hanging off one word in a header. It works when the structure underneath it is good, and nothing about the panel can rescue a structure that is not.
A team splits its thirty-field application into five steps and the completion rate goes down. Nothing was removed, and the form now announces that the work is five screens long. Splitting a form is a real fix for a real problem, and it only works when the cuts and everything between the screens are designed.
Signups arrive in the numbers marketing promised and two thirds never come back. The gap sits between trying the product and understanding it well enough to return, which is where most products leak their growth.
Nobody reads a pricing page. They compare it, in a sweep across rows with a periodic glance back at the headers, and the layout either supports that or gets abandoned.
Somebody who searches has already told you exactly what they want, in their own words. Baymard's 2026 benchmark still finds 56% of sites with mediocre or worse search, which makes it the clearest signal most products throw away.
Four modules of typography were about serving the reader: making content clear, legible, and easy to navigate. Expressive typography is a different project — one where the form of the type becomes part of what's being said.
Theory lands differently when you're staring at 47 components, a dark mode requirement, a data viz problem, and a stakeholder who hates the primary color. This module is about working with color in actual product conditions.
Copy is usually settled by opinion — but words measurably change behavior. Treating microcopy as a decision you can research and test is what separates reliable copy from lucky copy.
Most products eventually serve other languages and regions, and copy written for one quietly breaks when it travels. Mismatched copy signals the product wasn't built for them.
A consumer product is used by people who found it a minute ago, owe you nothing, and will leave the instant it asks too much. No training, no procurement, no patience, and a competitor one tap away.
About 70% of baskets are abandoned, and the biggest fixable reason is a cost that appears at the last step. This domain runs on somebody spending their own money, which changes what every screen owes them.
A dashboard exists so somebody can decide something in the time they have. Most of them display numbers instead, and the difference shows up as twelve charts nobody acts on.
Most of the money lost to payment fraud is sent by the account holder, on purpose, through an interface that worked exactly as designed. That is the problem this domain hands you.
In most products a confused user abandons a purchase. In a health product they take a wrong dose, miss an appointment they needed, or share a record they meant to keep private.
Most products are used by somebody who already knows what they want. A learning product is used by somebody trying to become different, which changes what a wrong answer means and what progress has to look like.
Every other product in this course does what it is told. An AI feature produces a confident answer that is sometimes wrong, and the interface is what decides whether that costs somebody a moment or a mistake.
One route can offer 8,777 combinations, and the form asks you to describe the flight you want before you have seen a single price. This module is the method from the other eight domains applied end to end.
Gen Z—born between 1997 and 2012—grew up online. Smartphones, memes, and social feeds are second nature to them. They’re not just tech-savvy—they’re tech-native. And when it comes to digital products, their expectations are high. This guide is here to help you design experiences Gen Z will enjoy, trust, and return to.
You've got the case studies. Now they need a real home online - a fast, custom site a recruiter can open in one click. AI and modern design tools let a designer build one in days, not months.
A job search isn't one big ask - it's a funnel. You find many roles, apply to a focused set, and convert a few into conversations. Treat it like a pipeline, not a lottery.
The interview isn't a test you cram for the night before - it's a performance you've already rehearsed. Most of what decides the outcome happens before you say a word.
Most communication advice quietly assumes the extrovert ideal - speak up faster, network harder, think out loud. If that's never felt like you, this module is the reframe: your temperament is an asset, and here's how to use it.
Lessons
1Communicating as an Introvert - Introduction2 min
Somebody waits three minutes for a file to arrive and gets one line saying the upload did not work. The rules that would have stopped it were on the page all along, underneath the button, in gray.
Jared Spool collected several hundred Word settings files and found fewer than 5% of people had changed any of the 150 settings. The defaults are the product, and the settings screen is where a team hides the decisions it could not make.
Nielsen's third heuristic asks for a clearly marked emergency exit. Most products answer it with a confirmation dialog, which asks somebody to be certain in advance instead of letting them be wrong for ten seconds.
Collapsing content makes a page look shorter without making it smaller. Everything hidden is content somebody has to choose to reveal, and most of them will not.
Back was 41% of all navigation actions in 1994 and 14.3% a decade later. The drop tracks the web becoming applications, where a press of back is an undo for whatever just happened rather than a request for the previous document.
Asking for a birthday looks like the easiest field on the form, so designers reach for a calendar or three dropdowns to prevent mistakes. Both create more friction than they prevent, and a field people struggle with returns worse data, not better.
A trail makes three promises at once. Every ancestor is somewhere you can go, the separator says the left contains the right, and the last item says you are here. Every problem with the pattern is one of the three being broken.
Erik Runyon measured a university home page carousel at barely 1% click-through, with 84% of those clicks landing on the first slide. Four teams had content in it and three of them were talking to nobody.
Ofcom found 7.5 million people in the UK using subtitles, 18% of the population, of whom only 1.5 million were deaf or hard of hearing. Four out of five caption users can hear the audio perfectly well.
The blank screen a new person meets before they have added anything is often their first real look at the product. It is also the one screen that only appears when the designer is not looking, so it ships saying No data.
Error messages get written last, read at the worst possible moment, and blamed first. The distance between a dead end and a recovery is almost entirely design: which kind of error it is, where the message sits, what it says, and whether anyone can perceive it.
A greyed-out button is the reflex answer, and it is often the wrong one. Whether a control should be hidden, disabled, read-only or left alone comes down to one question, and the rest of this module is what to do once you have answered it.
A list that loads forever is smooth in a demo and expensive in production. It trades orientation and return for continuous browsing, which is the right trade for a feed and the wrong one for almost everything else.
A text box and a dropdown are the two defaults, and both are wrong more often than they are right. The control decides how many taps the answer costs, which keyboard opens on a phone, and whether the format can be wrong at all.
A Dutch traveler opens the site from a hotel in Tokyo and lands in Japanese. Location was read as language, which is the assumption underneath almost every problem with this component.
Flagging errors as people type ships as a default best practice and usually backfires. It interrupts unfinished work, misfires on real names and real phone numbers, and promises a green tick the server later refuses. Late validation wins almost every time.
Every product waits on something, and the wait is designed whether anybody decided to or not. Two products with identical response times can feel a second apart, and the difference is entirely in what the screen does while nothing has arrived.
A modal stops everything and demands an answer, which makes it the most expensive component in any product. Four teams adding one each to the same screen is how a product ends up interrupting people on the way to what they came for.
Somebody arrives knowing exactly what they want to do and has to reverse-engineer an organization chart to find it. A navigation query asks for the intent instead, and routes from there.
Every event in a product produces the same small box in the corner, so people stop reading them, and the one that mattered goes past unread. Feedback is a ladder from barely there to stop everything, and most teams only use one rung.
A shop has forty reviews and every one is five stars, because only happy customers were ever asked. Purchase likelihood peaks somewhere near 4.5 and falls as it approaches a perfect score.
Lessons
1Reviews & Testimonials - Introduction1 min
2Anatomy of a Review2 min
3What the Research Says2 min
4Asking for a Review2 min
5Showing the Score2 min
6Inside a Single Review2 min
7Keeping It Honest2 min
Practice
1Design a Review Collection and Display System40 min
Pinning a bar to the top of the screen is a default in most design systems. It costs the same pixels on every screen of every session, and the pixels are charged against the thing people came for.
Tabs promise that everything behind them is an alternative to everything else. Most of the trouble with the pattern comes from putting something behind a tab that was never an alternative at all.
In one study of 27 toggle designs, the most common treatment in the wild, red for off and green for on, produced a 32.5% error rate. A control this small has one job, and half of getting it right is deciding whether it should be a switch at all.
Taking the underline off a link looks like a small styling decision. It is a decision about who can find the link at all, and it is made most often by people who can see the color perfectly well.
Lessons
1Underlined Text - Introduction1 min
2Anatomy of a Link2 min
3The Underline Convention2 min
4Writing the Anchor2 min
5One Link Style Everywhere2 min
6Saying Where It Goes2 min
7Links People Can Reach2 min
Practice
1Audit Your Links30 min
Communicate with Typefaces: History, Mood & Connotation
Typography's vocabulary — body, leading, upper case, lower case, font, point — all comes from a single room in 15th-century Europe. Knowing the origin explains why the tools work the way they do.
Four principles underlie every typographic decision: hierarchy, contrast, proximity, and rhythm. Get them right and the layout works almost automatically. Ignore them and no amount of typeface shopping fixes it.
Lessons
1Typographic Principles4 min
2Paragraphs4 min
3Headings4 min
4Punctuation & Special Characters5 min
5Type Scale4 min
6Type for Data and Tables4 min
Practice
1Set a Type Scale30 min
2Make a Screen Readable35 min
Communicating with Color: Psychology, Culture & Brand
Most color mistakes in products aren't taste problems — they're system problems. Colors without roles, palettes that work on one screen and fall apart on the next, dark mode added at 11pm before launch. This module is how you avoid all of that.
Users scan, they don't read — so microcopy that competes with itself loses. The first job of information structure is restraint: surface only what the current action needs, and let the rest of the flow carry the rest.
Failure is an emotional low point, and people judge an experience by how they recover from it. Error copy decides whether a stuck user pushes through or leaves.
Empty screens, spinners, and confirmations are usually an afterthought — yet users hit them constantly. They shape first impressions, perceived speed, and closure.
You design on a big screen with a precise cursor and hover to spare. Your user has one thumb, a 5-inch screen, and no hover at all. Mobile design is mostly the discipline of un-learning the desktop assumptions baked into your tools.
A portfolio isn't a collection of pretty screens. It's a story about how you think. Understand what makes portfolios effective and how to communicate your design thinking.
You became a designer to design, and most of your working day is writing: Slack messages, tickets, docs, feedback. Your work travels to other people as words long before it travels as screens.
Designers want the work to speak for itself. It rarely does. A good idea argued badly usually loses to a weaker idea argued well, so communication is what decides whether your design survives the room.
Every common interaction has been designed thousands of times, tested against millions of people, and settled into a shape that works. A pattern is that settled shape, and reaching for one is how you save the invention for where it counts.
A font is software, not a picture — and that changes everything about how you can use it. Here's where fonts come from, how licensing actually works, and how to keep your library under control.
More than 90% of online information is text — which means typography isn't decoration, it's most of the interface. This article explains what typography is and why it's one of the highest-leverage skills a designer can develop.
Picking a color in isolation is the fastest way to get one that doesn't work. Color only exists in relation to what surrounds it — which means working with color is really about working with relationships.
Color lands before text does. Before a user reads a word, they've already registered the mood, the brand, and which button matters. This article explains what color does and why understanding it changes how you design.
A button is the smallest piece of copy in your product and the one that carries the most weight — the exact point where intent becomes action, or hesitation.
