Before we start

Front matter

I want to make the argument before I earn it, so you know what you’re agreeing to read.

Every other mistake in this job is survivable. Wrong channel, wrong message, wrong timing, wrong number, wrong hire, wrong quarter. I’ve made all of them, several more than once, and every one of them left something behind that I could learn from.

The one you don’t come back from is making something nobody remembers. Not because it’s the most expensive mistake, but because there’s nothing to fix afterward. Nothing happened. You spent the budget, you filled the calendar, you hit every deadline, everybody did their job, and the market never noticed that you were there. There’s no post-mortem for that, because there’s no body.

That’s the whole book. Everything else is mechanism and method.

Where this came from

My senior yearbook page has an ambition printed under the photo. Mine says: “To find something I’m good at, and make a lot of money doing it.”

That’s what a seventeen-year-old writes when he has absolutely no idea what he wants to do.

My senior yearbook page. Read the ambition.
My senior yearbook page. Read the ambition.

Marketing came easy, so I majored in it. Freshman year we had to design a cereal box, and I got extra credit for my groundbreaking idea: make it colorful, and put it on the bottom shelf, where a kid in a shopping cart can grab it. I got extra credit for describing the cereal aisle. What I remember about it isn’t pride. It’s a small, uncomfortable feeling that it had been too easy, and that I wasn’t learning anything.

So I took one sociology class, and it broke my brain a little. It turns out there’s a science to why people in groups do what they do, and very little of it is logic. I switched majors. There weren’t a lot of jobs for sociologists, so I taught myself to code, almost went for a PhD, and spent seven years as a developer instead, which is a strange job for somebody whose favorite subject is other people. Then I joined a startup and fell back in love with marketing, this time through the lens of why people actually decide. I’ve been marketing in cybersecurity ever since, starting around 2008: CloudLock, Hexadite, Axonius, and now 7AI.

I’m telling you this for two reasons. The first is so you know I’m not an outsider throwing rocks. I’m a vendor marketer in cyber, with the same tools you have and the same pressure you’re under, and I’m going to implicate myself throughout. The second is that every turn in that path started the same way. Something got easy, and easy started to feel wrong.

This book is mostly about that feeling, and about why we’re all wired to ignore it. Nearly every chapter leans on a finding from social psychology or sociology, because the things we treat as “just how it works” usually have a name and decades of research behind them. If your own path looks like a mess, good. The detours are where I got everything in here.

Who this is for

You work in cybersecurity marketing. You might run the function or you might be one of six people in it or you might be the entire function at a Series A company where the CEO still writes the social posts. The book is written so that none of that changes what you can do with it, because the expensive part of this work has never been the budget.

If you’re reading this as somebody who controls a large budget, you’ll find that most of the methods here don’t need one, which should worry you slightly.

If you’re reading this as somebody who controls none, you’ll find that every chapter ends with the version that costs nothing, and those versions aren’t consolation prizes. Several of them are the better option.

What it will cost you

About four hours to read and considerably more than that if you actually run the exercises, which is the only reason to read it.

It will also cost you some comfort, which is the point and also the joke in the title. There’s a chapter in here about the most expensive failure of my career, told in more detail than my publicist would prefer, and if I’m asking you to look honestly at the work your team approved last quarter, I should go first.

How to use it

Read it in order the first time. The argument builds, and Part Three won’t land if you skip Part One.

After that it’s a reference. The audits, templates, and inventories are collected in the appendices so you don’t have to hunt through chapters for them.

The one thing you need before Chapter 1

There’s a tool that runs through this entire book. It appears at the end of every chapter, filled in against whatever that chapter was about, and by the end you’ll have watched it applied about twenty times, including once where it fails completely and I have to explain why.

It’s three questions. You can run it this afternoon, on anything, without asking anybody for permission or money.

The Comfort Check

1. What’s the comfortable assumption?

Not “what’s our strategy.” What are we treating as simply how this works? Usually it’s the thing nobody in the room would think to question, because nobody has ever said it out loud.

2. What’s the true objective?

Not the activity. The outcome. Be honest here, because the activity is always easier to write down and it always feels like progress.

3. What’s the redesigned approach?

If you threw out the current process entirely and built backward from that outcome, what would you actually do?

Three questions. No budget, no permission, no headcount, no software.

Before you start Chapter 1, pick one thing your team is currently doing because you did it last year, and write down the answer to question one. Just the first one. Don’t solve it.

Most people find that writing the sentence is harder than they expected, and that’s the first useful thing this book will tell you.