BizOps

WHAT IT IS BizOps is the function that makes a company's internal operations work across functional boundaries: the planning and goal cadence, the business systems that support it, process design where work crosses teams, and the analysis brought to significant decisions. It is deliberately general — its subject is the seams between functions, which is precisely where nobody else is accountable. **Not this:** BizOps is not ProductOps: it owns how the company as a whole plans, decides and runs its internal processes, not the operational machinery of the product management function. WHY IT EXISTS Companies scale their functions faster than they scale the connections between them. Each function optimises locally, handoffs become lossy, and the same question gets answered differently depending on whose spreadsheet you open. BizOps exists because cross-functional process is everyone's problem and therefore nobody's, and because significant decisions otherwise get made on whoever assembled the most confident narrative. WHEN TO USE IT Adopt it when planning cycles produce goals nobody can trace to work, when two functions report different numbers for the same thing, or when a recurring process breaks at the handoff every quarter. Very small companies do this implicitly in one room; the need appears when the room stops fitting. WHO OWNS IT A BizOps or strategy-and-operations function owns the cadence, the cross-functional process design and the analysis. Functional leaders own execution within their areas — BizOps that starts running other functions has become a bottleneck rather than a connector. The executive team owns the decisions themselves; BizOps owns the quality and neutrality of the input, which only survives if the function is not advocating for an outcome. WHAT GOOD LOOKS LIKE There is one planning cadence with a documented calendar, and goals connect to work people recognise. Cross-functional processes have an owner and a written definition, especially at the handoffs. Business systems are integrated well enough that the same entity means the same thing across them. Significant decisions have a written basis, including the uncertainty, and are revisited against what actually happened. Reporting is reconciled — the discipline in /analyticsops applies directly, since a contested metric definition is a contested business decision. HOW TO IMPLEMENT Start with the calendar: write down the actual planning cadence, including what is decided when. Map one broken cross-functional process end to end and fix the handoff rather than the parts. Reconcile the two or three numbers the leadership team argues about most, and agree definitions in writing. Introduce a lightweight decision record for significant choices — what was decided, on what basis, what would change it — and revisit a few honestly. Resist owning execution; the value is in the connective work. HOW TO ASSESS YOURSELF Ask two functions for the same headline number and compare. Ask someone mid-organisation to explain how their work connects to a company goal. Take a decision from last quarter and ask what it was based on and whether that held up. Take the scored self-assessment at /assess, then sequence with /roadmaps.