The most frequently told story in my youth, hands-down, was the time my dad and his best friend ran away from home on the Vespa scooter, scoot scooting their way from Brooklyn to California. In Arizona, my father grabbed a flight to LA and left the scooter with Lanny, who proceeded to crash it into a Greyhound bus. Lanny survived (he still tells me Michael stories via email when he thinks of them), but he never did make it to California.
The last time Lanny told me this story, it occurred to me: most of us keep our eyes pinned to the road immediately in front of us. Or we focus on the rear-view mirror, spinning our wheels over past experiences. But this tendency means we’re tuning out our peripheral vision.
Peripheral vision, though, is what gives us context. It’s how we notice the unexpected sneaking up on us, the Greyhound bus drifting over the yellow line into our path. Spend too much time focusing only on what’s in front of you, and you lose sight of that stuff. The next thing you know, you’re running into a bus on a Vespa scooter while your best friend basks in the LA sunshine.
White-knuckling it with your hands at ten and two
Loosening your grip long enough to take in the landscape isn’t always comfortable. It feels counterintuitive. Why spend so much time auditing a website we already know is broken? Why interview people who aren’t even using our app or programming yet? It feels like busy work. We don’t have time for this—we’ve got to get the new site up!
This obsessive focus on moving quickly is understandable. There‘s so much reverence for the “agile” mentality of “move fast and break things.” It’s easy to get caught up and mistake it for “don’t do the due diligence that feels like busy work.” Shortcuts now can hurt you in the long run, though. Raise your hand if you’ve learned this the hard way; I promise I won’t judge.
Boeing’s grounded 737 Max airplane may be the most visible example of what can happen when we rush to launch. Engineers “were pushed to submit technical drawings and designs at roughly double the normal pace,” according to the New York Times.
“A technician who assembles wiring on the Max said that in the first months of development, rushed designers were delivering sloppy blueprints to him. He was told that the instructions for the wiring would be cleaned up later in the process…His internal assembly designs for the Max, he said, still include omissions today.”
Sure, sure: your team isn’t building airplanes. But that may be why due diligence is even more critical for you. I’m guessing you don’t have the budget to survive a full grounding—to completely redesign your website or rewrite your entire interface should it turn out this isn’t really what your audience wants, after all. No; you probably want to set yourself up for success from the very beginning.
What does content due diligence look like?
How you handle this depends on what business you’re in, of course, and what your specific goals are. For most of my clients, content due diligence takes two main forms: a diagnostic content audit, and user research and testing. These are both processes that can be done internally by pretty much any team able to prioritize them.
Looking inward: your own content
When we talk about content due diligence, most of us think of the conventional content audit. Audits are actually pretty easy to do without any specialized expertise. It starts with putting together a laundry list of all the content on your website (or in your app), along with a bunch of statistics and data points for each item. You then evaluate everything against various criteria. The criteria should change based on your strategic goals, and the output allows you to identify important patterns, gaps, and opportunities for improvement and alignment.
A quick Google search will turn up plenty of tutorials that typically focus on ROT (redundant, outdated, trivial) criteria. The problem with ROT is that—while helpful at a basic level—these criteria can be subjective. They’re also not at all comprehensive. ROT doesn’t catch issues like whether or not a page is usable or accessible, for example. (I’ve actually been piloting a new diagnostic service with some clients to help solve for this. My Content Diagnosis goes well beyond a typical content audit and includes prioritized fixes for what’s broken. It’s gotten a good reception so far, so let me know if you’re interested and I’ll send you more info.)
Looking outward: your audience
On the flip side, audience research and testing complement the inward-looking content audit by shifting our peripheral vision outward. Watching actual humans outside of our organization interact with our content and hearing them talk about their own perceptions, needs, and concerns—in their own voices—can provide mind-blowing insights into whether our content is hitting the mark or not. It can tell us where, how, and why people are tripping up. While a diagnostic audit can identify inconsistencies with your navigation menu, for example, something like tree testing can tell you which menu labels are particularly hard for visitors to understand. In other words, user testing and research provides depth and context to our diagnostic work.
It also helps us understand our audience’s expectations, language, and mental models. Hands up if you feel like you have a pretty good grasp on the audiences you serve. You can probably list off a host of descriptors and demographics. Maybe you even have some audience profiles or personas. The thing is, unless you’ve actually watched, listened, and questioned your audiences as they use your website, you’re really taking a best guess. You’re making an assumption that the experience you’ve created—the way you’ve grouped content on your site, the language you’ve used in navigation menus, the categories of topics you’ve created—are going to be familiar and understandable to visitors. It’s amazing how much our own personal lens can color our design decisions.
But what if you’re not quite right? Our audience’s mental model always prevails in the end; either they embrace our content or they ignore it.
So why don’t we do our digital due diligence?
By far the most common excuses for avoiding user research and testing are time and money (and our own
arrogance belief that our assumptions about our audience are correct). This is a terrible excuse, though.
The reality is that it’s a hell of a lot cheaper to uncover problems early—before we’ve locked ourselves into decisions, designs, code, and especially office politics. If you don’t believe me (or the research), feel free to ask the former CEO of Boeing.
How will you survive the
Greyhound bus 737 Max in your path?
It doesn’t matter whether your organization is trying to save us from climate change, develop new economic systems, or disrupt the space-time continuum. We all share a common goal: we want our efforts to be effective. My argument, ultimately, is that to be effective—to accomplish our organization’s long-term mission—we need to stop focusing on the shiny distractions directly in front of us and start using our peripheral vision. Content due diligence is a strategy.
So, answer me this: what’s currently distracting you from the oncoming bus? What’s eating up all your time and attention? What do you see when you shift your gaze from the road immediately in front of you to what lies on the horizon in six months, at the end of the year, in 2-5 years? 2020 is young yet—let’s make some plans.
This post was originally sent to subscribers of my semi-regular email update. It’s safely occasional (like a sundae). Join us!