introduction

The Problem This Book Solves

Maybe you’re sitting in meetings where people are throwing around terms like “journey mapping,” “heuristic evaluation,” and “design sprints,” and you’re nodding along while secretly planning to ask an AI assistant to explain it all later.

Maybe you just landed your first UX role and you’re excited but terrified because you’re not sure what you’re actually supposed to be doing. Your boss says “start with discovery” and you think, “Discovery of what? How? For how long?”

Maybe you’ve been doing UX for a while, but every project feels like you’re starting from scratch. You don’t have a repeatable process. You’re constantly second-guessing yourself. You wonder if everyone else has it figured out and you’re the only one winging it.

Maybe you’re the only UX person at your company. You’re doing research, design, testing, documentation, and stakeholder management, all by yourself, and you’re drowning in ambiguity. And now your product manager shows up with screens an AI tool made in an afternoon, and you’re wondering where that leaves you.

Or maybe you’re in a massive organization where UX exists, but you’re navigating politics, conflicting feedback, and stakeholders who don’t understand what you do. You know you’re capable, but you can’t seem to get traction.

Here’s what I want you to know: You’re not alone. And everyone else doesn’t have it figured out either.

The tools and titles of UX are still young. The iPhone came out in 2007. Social media didn’t explode until the early 2010s. Most of the tools we use today didn’t exist when I started.

Even if you’ve been doing UX for decades, your day-to-day work has probably changed dramatically in the last ten years. The tools change. The titles change. The techniques change.

But the fundamentals? Those don’t change.

And that’s what this book is about.

What You’ll Gain From This Book

Here’s my promise to you:

After reading this book, you’ll be able to walk into any meeting, any project, any situation with the confidence and tools you need to succeed.

Specifically, you’ll know where you are in any project and what to do next, no more feeling lost when you join a project mid-stream or when priorities shift. You’ll know which activities to use and when, with a menu of 40+ UX methods and clear guidance on when each one makes sense. You’ll know how to create a plan that actually works using the 5W Framework and Project Design Plan to organize any project in under an hour. You’ll know how to present your work and get buy-in with three storytelling frameworks that help you communicate effectively with stakeholders. You’ll know how to test your work with real people and let the evidence decide. And you’ll develop the mindset that separates good designers from great ones: ownership, craftsmanship, and resilience that will carry you through your entire career.

This isn’t theory. This isn’t academic. This is the practical, tactical framework I use every day and have used to go from a confused junior developer to leading design teams at major brands.

My First Win (And Why It Matters)

Let me tell you about the moment I fell in love with this work.

In 2009, I built an online marketplace where college students could buy and sell textbooks with each other. I genuinely thought it was going to make me a millionaire. (Spoiler: it didn’t.)

But here’s what did happen:

I remember the moment when the first students used the messaging feature to safely meet up on campus and bypass the bookstore altogether to sell directly to each other. It was one of the greatest feelings I’d ever had.

It was the first time I saw an idea come to life, from thought to sketch to wireframe to code to real people I’d never met actually using the site.

It was the first time my thoughts positively and tangibly affected the world around me.

That’s the power of what we do as UX designers. We don’t just make things look nice. We create experiences that change how people interact with the world. We solve real problems for real people.

And to do that well, you need more than just design skills. You need a process. You need to understand the activities. You need to know how to execute. You need to communicate your work. You need to test your ideas with real people. And you need the right mindset.

That’s what this book gives you.

A Short History of the Tools (And What Stayed the Same)

I wireframed that textbook marketplace in AutoCAD, line by line. AutoCAD was architecture software, made for drafting buildings. The design tools you’d reach for now didn’t exist yet, so it was what I had. It took forever.

The marketplace started there and moved to other tools as I learned them: sketches on a whiteboard, then software made for wireframes and clickable prototypes. My title back then was web developer, and most of that work was freelance.

The distance between an idea and the real thing was long back then. An idea had to go from thought to sketch to wireframe to code before a single student could use it. I drew every screen, and my team and I built the site in code. Most of that distance was production.

Then the tools changed, and they kept changing. I learned Sketch, UXPin and Figma, each one on the job, each time right after telling a company how good I was. I felt that pressure every time.

My titles changed too. I’ve been a full-stack developer, a front-end developer, a UX developer, a UX designer, a UX lead and a UX manager.

But every generation of tools shortened the distance. Tools made for screens let me lay out a page far faster than drawing it line by line. Prototyping tools let people click through a design before anyone wrote code. Shared files put the whole team in the same place at the same time.

As I write this, the distance is shorter again. My team goes from discovery to a working prototype to a pull request, which is a proposed change to the product’s real code. In my work, about 80% of working with an AI assistant is putting what we want into words, not drawing frames. What we put in front of people now works. It used to be a drawing. And more and more, the designer is the one who ships it: I’ve started pushing those changes to the real code myself, and my team is heading the same way.

Here’s what I want you to notice. At every step, the job stayed the same. I had to understand the people I was building for. I had to make a guess about what would help them. I had to test that guess with real people and be willing to be wrong. And I had to own the result.

You might know that loop as build, measure, learn. It never left. Each new tool just sped it up.

I don’t think the distance has stopped shrinking. It will keep getting shorter, and one day the tools I just named will feel like a different era, the way drawing a website in AutoCAD does to me now. When that happens, you’ll still have to understand people, guess, test and own the result. So when a new tool shows up, ask what distance it shortens, then get back to the job. The tool was never the job, and Chapter 6 comes back to why.

This Framework Works Everywhere

Whether you’re working at an agency, in a corporate UX org, on a product team, or running your own practice, this framework applies.

Maybe you’re Vee, fresh out of a bootcamp, just landed your first job at a startup, juggling multiple projects and trying to figure out where to even start. You’re talented but haven’t had much mentorship. You ask an AI assistant to explain terms after meetings and hope no one notices.

Or maybe you’re Jordan, switching careers into UX after years in a different field. You’ve done the bootcamp, built some case studies, but you’re struggling to land that first full-time role. You need to understand how UX actually works in the real world, not just in bootcamp exercises.

Or maybe you’re Leo, the only UX person at a 20-person startup. You’re doing research, design, testing, copywriting, and stakeholder management all by yourself. You need systems that help you work efficiently without burning out.

Or maybe you’re Priya, working at a large corporation, navigating stakeholders, politics, and organizational complexity. You’re seasoned but frustrated because your work gets diluted or ignored. You need frameworks for influencing decisions and getting buy-in.

Or maybe you’re Alex, a product manager who wants to understand UX better so you can support your designers and champion good user experience in product discussions.

Or maybe you’re Nia, an experienced designer who was laid off when the team got smaller. You’ve shipped real work for years, and now you’re job hunting while you learn to build what you design. You need a way to show hiring managers that the years still count.

All six of them are up against the same three villains. Crickets is the one outside: you show your work and nothing comes back, because nobody sees your value. Doubt is the one inside: the voice that says you don’t belong in the room. Shiny is the pace: there’s always a new tool, a new term, a new thing to keep up with. You’ll meet each of them again in this book, along with what beats them.

And if you already know the basics, this book is still for you. You might be a working designer a few years in, like Leo or Priya. I wrote the familiar parts as a reminder, because the principles are the first thing to slip when the work moves fast.

Wherever you are, the fundamentals don’t change.

Whether you’re at an agency working across multiple brands and clients on tight timelines, in a product organization continuously iterating on the same products, in a corporate environment navigating complex stakeholder landscapes, or flying solo as a solopreneur or freelancer wearing all the hats. You still need the same six things: a process, the right activities, evidence that your ideas work, a plan, a way to tell the story, and an ownership mindset.

And here’s the thing: With the rise of AI, our job titles will absolutely change. We might interact with different form factors, use different tools, even serve different types of users.

But these foundations will rarely change: having a process to solve problems, understanding which activities to use, knowing how to execute and communicate your work, and developing the right mindset.

This is the framework you’ll use when designing experiences, no matter how the field evolves.

What Changes and What Doesn’t

The questions never change. The order, the artifacts, the tools and the job titles do. This book teaches the questions, and four principles run through it. Each one has a home chapter.

Judgment and taste. When making things gets cheap, deciding what’s good becomes the job (Chapter 2).

Evidence over assumptions. Put the closest thing to the real experience in front of real people before you decide. Sometimes that’s a prototype. Sometimes it’s the real thing, released as a pilot or an A/B test (Chapter 3).

Briefing and delegating. Whoever does the work, a teammate or a machine, needs you to define done, give context and write the process down (Chapter 4).

Owning the whole cycle. You can choose to stay with a piece of work from research until it ships (Chapter 6).

One more thing before we start. The four phases in Chapter 1 aren’t a checklist you finish in order. They’re four questions every project has to answer. On a fast team you might ask all four in one day, and sometimes you build a prototype before you’ve done any research. That’s fine. Each question still needs an answer before you commit.

What’s Coming

Here’s how this book is structured:

Chapter 1: UX Process. Understand the four phases every project goes through (Research, Design, Develop, Continuous UX) and how they connect. I’ll show you how all the major design models (Double Diamond, Design Thinking, Lean UX) are really saying the same thing, just with different words.

Chapter 2: UX Activities. Learn the specific methods and deliverables you’ll use in each phase. From user interviews and wireframes to usability testing and design QA. You’ll know what each activity does and when to use it.

Chapter 3: UX Evidence. Test your work with real people. You’ll learn to write down your guess, pick the cheapest test that could prove it wrong, and be willing to be wrong when the results come in.

Chapter 4: UX Execution. Learn how to plan any project using the 5W Framework, create a Project Design Plan that keeps everyone aligned, and adapt when constraints emerge (because they always do).

Chapter 5: UX Storytelling. Master how to present your work to stakeholders, build compelling case studies for your portfolio, and communicate throughout projects to build trust and credibility.

Chapter 6: UX Mindset. Develop the ownership mentality, understand the path to mastery, learn why the tool was never the job, build resilience to push through obstacles, and adopt the professional mindset that separates good designers from great ones.

Each chapter builds on the previous one, giving you a complete system for approaching UX work with confidence.

How to Use This Book

You can read this book cover to cover, or you can jump to the chapter that addresses your immediate need:

Feeling lost in a project? Start with UX Process (Chapter 1). Not sure which activities to do? Jump to UX Activities (Chapter 2). Want proof your design works before you build it? Turn to UX Evidence (Chapter 3). Need to create a project plan? Go to UX Execution (Chapter 4). Preparing a presentation or building your portfolio? Read UX Storytelling (Chapter 5). Overwhelmed by tools, struggling with confidence, or dealing with obstacles? Start with UX Mindset (Chapter 6).

Throughout the book, I’ll use real examples from my career and walk you through complete scenarios so you can see how everything works in practice. The figures in the worked examples, like timelines, budgets and conversion rates, are illustrative. They show how the thinking works, so don’t treat them as benchmarks.

The frameworks are designed to be referenced again and again. Bookmark the pages. Dog-ear the corners. Come back to them whenever you need them.

Think of this book as your mentor in your pocket: someone who’s been where you are, made the mistakes you’re trying to avoid, and learned the lessons you need to succeed.

Ready? Let’s get started.

When You’re Stuck: What to Do Next

Here’s the short version of the whole book. Find the situation you’re in, ask the question, and take the smallest next step.