# Field Notes No. 6 By Jeff Stowell · 2026-05-28 · Insights > Everyone says they want operators. Almost no one says what one is. A field guide to recognizing the real thing. _Based on some reader feedback, I'm going with some longer form writing. I'll do these a little less frequently and I'll be doing recommendations and other things in the off weeks. I hope you enjoy! Thanks for reading._ # What Do We Mean by "Operator"? _Field Notes -- No. 6_ * * * I was having a conversation with a friend recently and he told me that he had really developed a lot of respect for me as an operator. I've been told before that I'm a good operator, and it's really flattering. But I've never been quite sure what to do with the compliment. It's a strange thing to be called. Partly because I'm not certain it's true, and partly because I'm not certain what it would mean if it were true. I started a company young, more than 15 years before I ever wrote a check as an investor. But at this point I've been a VC longer than I was ever an operator day-to-day. So when someone says "Jeff's a strong operator," what are they describing? Something I did 30 years ago? Some advice I've given recently? Or some project I've helped a company with? A way I show up in a board meeting? A personality type? A label that got stuck to me once and never came off? I got to thinking about this, so I figured I'd explore! The reason I think this exploration matters is because I've come to believe that excellent operators are quite rare. Whether you happen to be one, you cannot build anything of consequence without one (or more!) in the room. So the more valuable skill isn't _being_ an operator. It's being able to recognize one when you see one. Whether that's in yourself, in a founder you might back, or in an investor you might let onto your cap table. So I thought I'd put together something like an appreciation or a field guide. We say we prize operators. It's one of the most common forms of praise in business. Let's figure out what we're actually praising, why it's so scarce, and how you'd know it if it walked into the room. ## The word, stripped down If we strip away mythology, the definition converges on something fairly specific and measurable. Webster's Dictionary defines an operator as... I'm joking. An operator is execution-driven. I think the job is to take ambiguity and turn it into structure and momentum. In a startup, it is to make a fragile thing real before anyone has created certainty about whether "it" will work. Doug Levin describes operators as people who create structure and forward motion before the clarity exists. \[1\] That feels about right. One operator I know describes himself more plainly: the job is to shift between thirty-thousand-foot strategy and on-the-ground execution in the same afternoon. The hardest part isn't any one skill or capability. The hardest part is the "context-switching" that this requires. If we're building a "field guide," I also think it's important that we clarify some language: "operator" is a _role_, not a _rank_. It's tempting to treat it as the top tier of serious people. But I don't think that's right. A useful framing splits leaders into visionaries (who invent what's next), craftspeople (who define the product and the strategy), and operators (who scale the team, align the organization, and unblock execution).\[2\] The whole point is that a healthy company needs all three. An operator isn't a better founder. An operator is a different function. Frank Slootman is one of those people who are known for being operators. As far as I know, Slootman has never founded anything, but companies like ServiceNow and Snowflake turned to him to run their companies. If there's a philosophy underneath the role of operator, Slootman gave it a blunt form in his book _Amp It Up_ (worth a read).\[3\] His claim is that execution comes before strategy. That you can travel a surprisingly long way on a mediocre strategy executed superbly, and essentially nowhere on a brilliant strategy executed poorly. The subtler point is the one that's stuck with me: you can't even _diagnose_ whether your strategy is wrong until you've ruled out execution as the cause. Most of the time the strategy is fine and the execution is the problem. But execution is unglamorous and strategy is the fun part that carries few consequences, so we reach for the strategy lever first. An operator is someone who reaches for the right lever. The cleanest test I've come across is the one Keith Rabois applied in a talk he literally titled "How to Operate."\[4\] I don't love gun metaphors, but in this talk he sorts capable people into two groups: "ammunition" (talented, hardworking, but they need to be aimed) and "barrels" (people who can take an idea from conception all the way to completion, and who pull other people along with them). His arithmetic is that a company can only do as many things at once as it has barrels; adding ammunition doesn't change the number. I find that framing useful when thinking about companies. Who are the people who carry a thing across the finish line and bring others with them? And are there enough of them? ## Operators are rare Rabois is emphatic that barrels are very difficult to find. Not just uncommon, but rare. He goes further: a barrel at one company may not be a barrel at another, because the trait is partly chemistry. Over the years I've become a HUGE believer in this point. Just because someone did a thing at one place and in one time definitely does NOT mean they'll do it again in the place and time you may be choosing them for. Rabois emphasizes that success depends on the problem, the team, and the moment. You cannot reliably manufacture "barrels" and you cannot easily transplant them. What that means for our Field Guide is that most talented, successful, valuable people are ammunition. Most of the work that matters gets done by people executing brilliantly inside a frame someone else holds. One can be exceptional, like a world-class engineer, a brilliant strategist, or a closer who can sell anything, and not be an operator. That's not a deficiency. It's just a different shape. The mistake we make is rarely being or having ammunition. The mistake is being or having ammunition and believing you are or have a barrel, and then staffing the company, or the fund, or the board, as if the barrel seat is already filled. That's the failure that actually hurts, and it's really common, because the label "operator" is flattering and nobody volunteers to wear other labels. ## It's fine not to be one. You still can't skip it. So let's say you've looked in the mirror and you've looked around the room and you've concluded you're not really an operator. Or the person you're hiring/investing in/working with is not really an operator. The good news is that you are in rare and excellent company; it is no small feat to admit you're "not it" or "don't have it." It changes nothing about whether you can win. It simply tells you what you have to go find. The math is, in my experience, a little unforgiving. If the ceiling on what an organization can accomplish is the number of "Rabois Barrels" it has, then a company with zero operators has a ceiling of roughly zero, no matter how visionary the founder or how clever the strategy. There is no version of this where you skip the operator and substitute something else. You either _are_ one, or you _find_ one. I don't think there's a third door. For a founder, that usually means your most important early decision isn't a feature or a market... it's whether you've got a real "barrel" with you. And if you're the visionary, whether you've been honest enough to admit you need an operator with you. For an investor, it is the same problem wearing a different hat: either you bring genuine operating empathy yourself, or you're clear-eyed that your edge is judgment and capital, and you make sure the founder is surrounded by operators so you don't have to be something you aren't. Either way, the job reduces to the same skill; recognizing an operator. Which is the hard part, so let's get specific. ## How you actually recognize one In my experience, the trap is often mistaking fluency for the thing itself. Operators and people who are _good at sounding like operators_ present almost identically across a coffee or a pitch. The story is not the evidence. Here's what I'd actually look for instead: **Look at the wake.** The single most reliable signal is whether the stuff that passes through this person comes out the other side more finished than it went in? Not busier or more discussed. More _done_. Operators leave a wake of shipped, closed, resolved things behind them. **Watch how they prioritize.** Slootman has a line I glommed on to when doing some research for this piece: "The moment you have many priorities, you actually have none." My experience tells me that the great operators are, often stealthily, obsessive about this; they'll do the one thing and let ten reasonable things wait, because they know the real results come from sequence, not from effort. Someone juggling nine priorities with great energy is usually telling you, without meaning to, that they can't pick. **Notice who picks up the orphans.** Every organization is full of unowned, undefined, slightly-too-hard problems that everyone steps around. The great operator is often the one who instinctively reaches down and grabs one. Not because it's their job, but because it's broken and they're constitutionally unable to leave it that way. **See if they pull people with them.** Rabois's phrase is that a barrel can charge up the hill and bring the team. Execution at any scale is a team sport; the operator who can only do it solo isn't really one. Watch whether people follow them into the hard thing. **Ask for the receipts.** What have they personally taken from idea to execution, with their name on the outcome? And maybe more importantly, without their name on the outcome. "I scaled revenue from two to forty" is a completely different sentence from "I had a senior title at a company that scaled from two to forty." And "we scaled from two to forty" might actually be the most valuable of them all. But it's important to ask people to be specific, and listen for whether the specifics are theirs. ## A note on AI One complication I've recently observed is that "Generative AI" has become excellent camouflage. A weak operator with a good prompt can now produce a polished memo in twenty minutes, turn around a board update overnight, ship a clean-looking plan for a workstream they haven't actually thought through, and generally _appear_ to be leaving a wake of finished work. The artifacts look like the artifacts an operator would produce. The turnaround time looks like the turnaround time an operator would have. And several of the surface signals we used to lean on like polished docs, fast responses, well-structured plans, have quietly become much weaker evidence than they used to be. This doesn't mean the underlying signal is gone necessarily. Nor am I bagging on the use of "AI." It means you have to look one layer deeper. The wake that still counts isn't "did a deliverable appear?" It is "did the thing the deliverable describes actually happen, and did it work?" Did the plan get executed, or did it just get written? Did the people on the other end of the memo move, or did they nod and go back to what they were doing? Did the workstream resolve, or did it just get documented? AI can generate the artifact of operating. It cannot generate the outcome. The recognition skill, going forward, is mostly about refusing to grade the artifact and insisting on the outcome. ## Recognizing one across the table: the operator-VC Now let's point that same lens at the person who wants a seat on a cap table. "I was a strong operator" is one of the most common things an investor will tell a founder, and it deserves the same scrutiny as any other claim. I know it's something that I have claimed. If I'm being honest, it's a claim worth challenging just a bit more (rifles through receipts). Two of the venture industry's most-discussed firms were built around opposite answers to this exact question. Andreessen Horowitz, founded in 2009, was built by two people who had unambiguously operated: Marc Andreessen co-founded Netscape, and Ben Horowitz ran product divisions there before co-founding and running Loudcloud/Opsware which he sold to HP for about $1.6 billion.\[5\] They seemingly built the entire firm on the conviction that having sat in the founder's chair is what lets you help the people in it. They then backed that belief with infrastructure: a large "platform" of in-house operators including recruiting, marketing, policy, business development and more, and a partnership stocked with former founders. To this day a16z describes itself as fielding the largest team of operators in venture.\[6\] Ben Horowitz has said the firm was designed to be "the anti-Benchmark." Which is the other half of the story. Benchmark is no slouch either. They have been one of the most successful venture firms in history, with early bets on eBay, Twitter, Uber, Snapchat, Instagram, and OpenTable, while doing almost the opposite of a16z. It is deliberately small: a handful of general partners who seem to share profits generally equally, with few junior partners and no services platform.\[7\] Its partners have described themselves not as operators but as a guild of craftspeople, and its best-known investor, Bill Gurley, came to venture from hardware engineering and Wall Street research rather than from founding a company.\[8\] Two firms and two opposite theories of what an investor is for, both spectacularly successful. So "did you operate?" plainly doesn't sort the good investors from the bad. But there's no real need to be cynical. I think this means that operating experience is one real and rare ingredient, not the whole recipe. There's good evidence it can matter in a specific and conditional way. In a 2022 study with the dry-but-perfect title "Transferable Skills? Founders as Venture Capitalists," Harvard's Paul Gompers and Georgetown's Vladimir Mukharlyamov found that VCs who had previously founded a startup _and exited it successfully_ had investment success rates about 6.5 percentage points higher than career investors.\[9\] But the same study carries the caveat that founders who became VCs _without_ a successful exit did roughly 4 points _worse_ than the career investors. The ingredient that correlated with results wasn't "I operated." It was "I operated, and I won." The authors found the outperformance was consistent with those investors adding value after the check cleared, not merely seeing better deals. There's also a simpler truth... What usually transfers from operating to investing isn't the ability to do the job for you! A partner sitting on ten boards is not going to out-execute the head of sales you'd hire. If your investor is the one building your go-to-market, something has gone wrong. (I am specifically guilty of this kind of thing BTW). What transfers is _empathy_: having sat in the chair, knowing which fires are existential and which only feel that way at 11pm, knowing the unwritten rules, most of which are about raising the next round, etc. That kind of stuff is real, and it's valuable, and it's a more modest and more honest claim than the label usually implies. An investor who has "operated and won" can be an extraordinary partner. You just have to confirm it's the real thing rather than the decorative version. Conveniently, founders already have a tool for this. ## The field test Founders run reference checks on companies before they buy. Few run real checks on the investors they're about to be married to for a decade. They should. This is the same move one would use to verify _any_ operating claim, so it does double duty here. The early-stage firm CRV, which encourages founders to do this on CRV itself, lays out the mechanics about as well as anyone: do it after the term sheet and before you sign, and aim for something like five to seven conversations.\[10\] Two can come from the investor's curated list. The rest you find yourself. Map the firm's portfolio, trace the partner's prior firms, and deliberately seek out the founders who _aren't_ in the marketing materials. I think the most important calls are with founders whose companies **struggled or failed**, because that is exactly where operating help either shows up or it doesn't. Anyone can be useful when the chart goes up and to the right. What you ask matters as much as who you ask. Don't ask "is she helpful?" It is in NO ONE'S best interest to answer this with anything other than an enthusiastic "YES!". Ask what she actually _did_ when things went sideways: the specific decision she changed, the intro that landed, the night she rebuilt the model with you before the board meeting. "She's great" is noise. "She spent two hours fixing our pricing the week before our raise" is signal. One question, borrowed from CRV's guide, tends to unlock real honesty: _What would you tell a close friend who was about to take money from this person?_ The clearest red flag is usually pretty simple. A reference who hesitates, hedges, or changes the subject when asked whether they'd do it again. If the operating claim specifically is what you're testing, add two questions, and ask the investor directly: _What kinds of things did you own, end to end?_ and _What's an operating call you got wrong?_ A real operator has a graveyard of hard decisions that didn't work and can walk you through them without flinching. Someone trading on the label tells a story that only ever goes up. ## Where I land If there's a takeaway, it's this: stop asking whether someone is an operator as if it were a credential to be conferred. Start asking whether you can _recognize_ one. The first question is mostly vanity. The second is a high-leverage skill. Because real operators are scarce, you probably can't manufacture one, and you may not be one yourself, but if you can spot one, you can always go find one and get them in the room. * * * ### Notes & Sources 1. Doug Levin, "What Does It Mean to Be a Startup Operator?" — [_douglevin.substack.com_](http://douglevin.substack.com). 2. The visionary / craftsperson / operator framing draws on "Not Just Operators," [_thecuriousleader.work_](http://thecuriousleader.work); see also Julia Chou, "What Is a Startup Operator?," [_dreamerdoer.co_](http://dreamerdoer.co). 3. Frank Slootman, _Amp It Up: Leading for Hypergrowth by Raising Expectations, Increasing Urgency, and Elevating Intensity_ (2022). 4. Keith Rabois, "How to Operate," Lecture 14 of _How to Start a Startup_ (Stanford CS183B / Y Combinator, Fall 2014), available on YouTube and in published transcripts. 5. HP agreed to acquire Opsware — founded as Loudcloud in 1999 — for $14.25 per share, an enterprise value of roughly $1.6 billion; announced July 23, 2007 (HP press release; Opsware SEC filings). 6. Andreessen Horowitz (founded 2009) describes its operator "platform" and team at [_a16z.com_](http://a16z.com). The "anti-Benchmark" characterization is Ben Horowitz's, quoted in Tad Friend, "Tomorrow's Advance Man," _The New Yorker_, May 18, 2015. 7. "How Twitter and Uber Backer Benchmark Is Winning at Investing Early and Staying Lean," _TechCrunch_ (2013) 8. Bill Gurley's pre-venture career: design engineering at Compaq and several years as an equity-research analyst on Wall Street before he joined Benchmark in 1999 (Gurley biographies; Benchmark partner profiles). 9. Paul A. Gompers & Vladimir Mukharlyamov, "Transferable Skills? Founders as Venture Capitalists," NBER Working Paper No. 29907 (April 2022). 10. CRV, "Reference Check Questions for Founders" and related VC due-diligence guidance — [_crv.com_](http://crv.com). --- Canonical URL: https://hayseedcapital.com/blog/field-notes-6 Site: The Hayseed (https://hayseedcapital.com) — writing, coaching, teaching, and early-stage investing by Jeff Stowell. Operated by Hayseed Capital, LLC, Park City, Utah.