I wrote this book because I kept having the same conversation.

It would come up in meetups, in communities, over coffee with designer friends. A designer would describe a situation at work. They could see a problem clearly. They knew what needed to change. They had the skills to fix it. But nobody was listening. The product manager had already decided. The engineer was already building. The executive had already committed. The designer was left to paint in the decisions other people had made.

The frustration was typically about having no mechanism to do anything about problems that are obvious. About watching bad decisions happen in slow motion and being told, implicitly or explicitly, that it wasn’t their place to intervene.

I lived this myself. For over a decade, across companies in Nigeria and the United Kingdom, across fintech, mobility tech, and education, I’ve been in rooms where I could see what was going wrong and had to figure out how to change it without the authority to simply say ‘stop, we’re doing this wrong.’ Sometimes I succeeded. Sometimes I didn’t. But over time, I started to figure out and notice patterns in what worked and what didn’t. I started to see that the designers who had the most impact weren’t necessarily the most talented. They were the ones who not only understood that design skills and leadership skills shared many commonalities, they also knew how to intentionally deploy them together as a complete package.

I looked for a book that made this argument. There are excellent books on design craft. There are excellent books on leadership. But I couldn’t find one that spoke directly to designers and said: the thing you already do every day is leadership. You don’t need to learn a new discipline. You need to recognise the one you already have and execute it beyond the boundaries of your job description.

The book is structured in two parts. Part One makes the foundational case: what leadership actually is, and why designers are uniquely suited to it. Part Two deals with the part nobody likes talking about: organisational politics, stakeholder dynamics, and what to do when the organisation resists despite your best efforts.

You can read it front to back. You can also dip into whichever chapter addresses what you’re dealing with right now. If you’re struggling to get a seat at the strategic table, start with Part Two. If you need the philosophical foundation before anything else, start at the beginning.

One thing to note. Every example in this book is fictitious. The characters, companies, and scenarios are composites drawn from patterns I’ve observed across the industry over many years. If you recognise yourself or your company in these pages, it’s because these patterns are remarkably common, not because I’ve written about you specifically.

This book is for the designer sitting in a meeting right now, watching a bad decision take shape, wondering whether it’s their place to say something. This book tells you it is. This book shows you how.

Raymond Emamezi Okoro

United Kingdom, 2026