Intuition in a Data-Driven World
Structural Tensions
As systems get bigger, an increasing proportion of their resources must be expended on overhead--administration, coordination, "work about work" if you will. The natural optimization impulse of the overhead is toward standardization, fungible components, feedback cycles, and automation--the left over fever-dream of mid-century cybernetics.
I don't pass judgement, without some flavor of these things massive enterprises simply don't work, public or private. This reified anima of management science does serve a serious purpose beyond being a rich target for artists' disdain.
The other side, of course, is that many system components are people, not servers or robots. And people are not their job description, the shoddy strictures of their "role" never captures the full picture.
Take a moment to think about what your job description actually says, contrasted with what you actually do, framed against the context of your full lived experience: travel, relationships, victories, failures, disappointments, realized dreams, and so on. An awkward composition, no?
I'll save deep diving this for a future management essay, but as both a person and a manager I posit that the lion's share of your contribution to your role comes from the fullness of your humanity, more or less secretly, applied to the common goals of your team, org, company, whatever--and not from rote execution of functions on a list.
Administrative Legibility
Doing some gradient of your "job" is table stakes for a place in the game, but you won't long keep it without the something special you bring--nor will the enterprise do particularly well without it. While common knowledge among people, precious few policies or management playbooks will even acknowledge this.
To adapt an idea from Scott's Seeing Like A State, the enterprise needs you to be legible in order to administrate the processes in which you are constituent (such as your employment), ergo the job description, millions of policies, many layered hierarchies both formal and matrixed, management information systems, and on and on and on. Again, this isn't inherently bad as it keeps the machine turning. It just isn't the whole story.
The more administratively legible you are, unfortunately, the less you bring the real stuff of your humanity to bear on your work. Usually then reducing your performance (among other things, like satisfaction..) and making the company's outcomes worse. Your immediate manager knows this, or ought to, but your distant skip probably doesn't (despite knowing the same for their directs).
(Tangentially, I think this is a particularly egregious contributor to the information filter that inevitably arises moving up through any hierarchy.)
We Are Data-Driven!
Now let's zoom back in a little. I suspect nearly everyone reading this has heard something akin to "we make data driven decisions" if not today, in the past week. I'll save my critique of how that usually works in practice for a later part of this series. Here, I will proceed assuming that we're talking about an stereotypical org culture that embraces data, rationality, and metrics-governed management.
For some companies, the reality is... notional. Others truly live and breathe metrics--and others still fall everywhere in between. This matters to us for our purposes here because that "data driven decisions" interface is the primary administrative surface most employees interact with most of the time--think WBR, MBR, QBR, annual planning justifications, impact justifications during perf reviews, in writing docs for designs or proposed work or promotion justifications.
(See a theme? There's much to explore regarding justification supplanting judgment, but we'll save that for another time.)
Everywhere numbers, and in the most extreme cases nothing happens at all without a metric to support it--which leads to all sorts of hi-jinks more suitable for a future management essay. Goodhart's Law, anyone?
Before we move on, just to be clear--I am a huge exponent of a rigorous quantitative picture underpinning all ops and most material decisions generally. Much more on that further down the road to the Red Queen.
Without the numbers, on my view, you're lost. However, paraphrasing Vannevar Bush, "Data Is Not Enough"--high function requires those illegible human elements, too.
Intuition Revisited
Data, of course, isn't information unless it's interpreted, contextualized, and put to work somehow. Reducing the interpretation of the data that drives decisions to "more number more better" anchored to some KPI is not often a recipe for being effective. The people who build, maintain, move, sell, support, and repair a thing often come to understand it in ways that are hard to describe, and are not especially possessed of administrative legibility.
One thing taught at Amazon, which I carry with me everywhere, is that when data and anecdote don't align, find out why. The data might be wrong, the orthodox interpretation skewed, whatever it is, figuring it out can only help you. For this approach to work, and it does, folks need to be empowered to share those anecdotes, to give voice to their intuitions, without fear. When they do, leadership needs to listen.
That sliver of humanity that sneaks into the great machine in the form of being a little illegible is the soul of operations. Instead of you or your people stabilizing and rectifying the system in the dark, integrate the effective action into your general ops activities. It's not an easy thing, but some illegible activities can become legible with sustained leadership support.
Embracing intuition enhances quantitative decision making by taking seriously inputs from outside of the system structures that capture and process your data. Computers do only what we tell them to do, and despite the cleverness with which we manage to do so, can't recover from incorrect instructions. Taking human intuition seriously is a mechanism by which you can suss out such issues over time, a dose of humanity to keep all of the math in check.
Before wrapping up with some actionable ways to make intuition a part of your org culture, I'll quickly situate my advocacy here within the larger project.
Intuition on the Road to the Red Queen
As we go along the road toward Seeing in a Strange Wilderness, you will quickly find that I am usually championing a middle path of some kind. In this discussion, I no more support intuition-only than I do data-only decisions. One of the principles underpinning my project here is:
Reductionist thinking is a luxury one can ill afford when playing a game without knowing the rules. The competence and command that you're used to is gone. Adopt a beginner's mind.
To go from the general to the specific, especially from first principles to applications, is the pinnacle of knowledge applied--and a flow that we've all become accustomed to in the triumph of science in the back half of the 20th century.
If we accept that the world is changing in big ways that we don't yet understand, we have to shed this hubris and work back up to it in whatever the new paradigm settles on. Having cake and eating it too is a perennial seduction with a universally unfortunate end.
Intentionally integrating intuition into operations is both practically effective for many purposes and is itself a key component of the ideas we're building up to here. We'll soon deep dive models for knowledge and I will argue the merits of a rather peculiar one centered on a criterion that requires the application of intuition to work well.
Practical Ways to Adopt Intuition
Like any cultural or mindset shift, there are no shortcuts--I don't have a secret Latin phrase for you to say three times over your JIRA board toward instant intuition integration. That said, here are some things that have worked for me, in several contexts, and will, in some form, likely work for you in yours.
For Managers
I normalize intuition as a part of operations by asking people for theirs. Use stand ups, retros (add a column--and add to it at least the first few times), regular syncs, one-on-ones, whatever your rituals are and ask folks questions like:
-
Is there anything on your mind that just doesn't seem right? I'm not looking for a metric to justify your feeling, I'm sincerely interested in the way things seem to you.
-
If you could do any work to improve things for our customers or make the team's life easier that you don't know how to justify, what would it be? Why that?
-
Is there anything you're aware of that feels under utilized that you don't know how to justify pursuing? What do you think a world in which that work is done looks like relative to present state?
On call hand off meetings are wonderful for this. The outgoing on call, whatever the job family is, just spent however long primarily looking at how things are going. On my teams, primary oncall is absolved of their project responsibilities during their shift. I recommend this for many reasons, not the least of which is establishing a mechanism for the whole team to look long and deep at your domain, without the distraction of delivery, across the year.
Whatever the details look like for your org, the most important thing is for you to explain what you're asking for, that it's okay to provide basically any answer, and that the org will seriously consider what folks raise in response to such asks.
In the beginning, especially if your org is deeply entrenched in quantitative justification, take the time to explicitly qualify these asks as not seeking metrics. Remind your folks that there is value in their perspective and that the team can benefit from it.
The flip side is equally important. When you have an intuition that something isn't right, pursue it! If you frame your investigation in the language of intuition, your team will see that it's okay.
When you start seeing your people ask each other such questions, you've probably succeeded in normalizing and internalizing intuition as a tool for farming non-obvious ops inputs.
Another thing I find profitable to do a couple of times per year is asking folks in one-on-ones what docs they've written or know about that never went anywhere but feels like they ought to have.
Doing the same when talking to partners, leadership, peers, and so forth can also produce excellent results. In particular I find that, coming from the tech side, these questions can do a great deal of work for me in refining my understanding of what my non-technical partners actually need.
For ICs
This varies wildly by level. Tenured ICs with a lot of moral authority in the org can proceed very similarly to managers. Less tenured and early-career folks have less agency to do so in many places.
What you can do, however, is pursue your intuitions anyway and use the exercise to demonstrate the value of doing so back to the team. This might look like putting a doc together about what troubles your mind and socializing it to your seniors and management.
If you are in a context wherein saying "no metric but take me seriously" just doesn't work, I recommend framing your doc as seeking to measure the dynamic that troubles you. This keeps you in the fold but knocks on the door of your concerns anyway.
Wrapping Up
The intuition that has gotten you this far in life matters, even in sterile, heavily instrumented technical environments. Integrating intuition into operations provides local, practical benefits for teams and can counter the dehumanizing impulse of administration at scale toward better net outcomes within the machine.
I particularly love that embracing intuition often has the knock-on effect of encouraging more voices to speak up. I find that a greater diversity of my team participates actively in a broader swath of situations when having a metric story isn't prerequisite for being heard.
"Only human" is a common euphemism for imperfect, flawed, irrational, and messy, lacking. We so easily forget that we are the most complex, incredible, and completely unparalleled constituents of the known universe. The highest achievements of the most advanced technologies don't even remotely compare to the hardware between your ears.
Remember that, and make room for a little messy humanity in sterile spaces. I suspect you'll be pleased if you do.