Bizops: 当你需要它, 为什么, 最终, 你不会
Yao Choong ,Director, Business Operations, Intercom @yaoc
这篇文章来自 intercom.com。原始 url 是: https://blog.intercom.com/why-business-operations/
以下内容由机器翻译生成。如果您觉得可读性不好, 请阅读原文或 点击这里.
Business Operations (Bizops for short) has inexorably become a thing at certain kinds of companies.
Some of you might come into regular contact with a Bizops team, others might have merely a vague awareness of Bizops, and still others might not have heard of Bizops at all. Regardless of which bucket you fall in, I suspect you don’t have the foggiest idea exactly what Bizops is or why it exists (unless you’re part of a Bizops team).
I don’t blame you at all. I believe our collective failure to articulate the essence of Bizops is a problem. It’s a problem because Bizops can provide so much value to companies, and because the lack of comprehension Bizops sometimes encounters can be a barrier to getting shit done. And because it pains me when a thing is done half-assedly, lacking in why, lacking in intention. So here’s my definition:
Business Operations is a function that is uniquely positioned to solve certain classes of problems for rapidly scaling organizations. It works within, alongside and sometimes outside of the established organizational structure of a company.
Going deeper, let me define Bizops from first principles to show how it can fit into a company and how it can be deployed to solve problems. The first principle is this: Business Operations shouldn’t exist. And yet it does, because of fundamental, intrinsically human limitations to the way we organize ourselves.
When do you need a Bizops team?
Very young companies don’t need Bizops. Anyone can have open-ended freewheeling conversations about anything with everyone else. Everyone wears a bunch of hats, and it all just works. It’s easy when R&D, Marketing, Sales and Finance all fit in a single room and two pizzas are sufficient to feed everyone. But this doesn’t last as the company grows. It’s simple math: if everyone has to be involved in every decision, doubling your headcount quadruples the distinct conversations needed. Obviously this doesn’t scale well.