Findings from a Cross-Functional Alignment Engagement
Locating the Business
Engagement Summary
Casterbridge Partners was retained in Q3 2024 by the Chief Operating Officer of [Company] to conduct a cross-functional alignment assessment with the stated objective of “improving the relationship between Engineering and the Business.” The engagement was scoped at twelve weeks. It lasted seven months. This report explains why.
The engagement began with a reasonable premise: that [Company] suffered from a misalignment between its technical functions and “the Business,” and that a structured discovery process — interviews, workflow mapping, a stakeholder analysis — could identify the friction points and produce an actionable remediation plan. The phrase “the Business” appeared in the original engagement letter fourteen times. At no point during the scoping process did either party define it.
Methodology
The assessment followed Casterbridge’s standard Cross-Functional Alignment Protocol (CFAP™), which begins with stakeholder identification. The protocol requires that the consulting team identify all parties referred to by the engagement’s key terms, map their relationships, and conduct structured interviews with representatives of each. The key term in this engagement was “the Business.”
We began with Engineering, since the COO’s framing positioned Engineering as the function that needed to align with something. In the initial interviews, Engineering leadership was unanimous: the Business was Product Management. “We build what the Business tells us to build,” said the VP of Engineering, with the particular resignation of someone who has said this sentence many times and expects to say it many more.
We therefore proceeded to Product Management.
Findings
Product Management
Product Management was surprised to learn that Engineering considered them the Business. “We’re not the Business,” said the Senior Director of Product. “We’re the translation layer. The Business is Sales. They’re the ones with the customer relationships and the revenue targets. We just prioritise what the Business tells us matters.”
Sales
Sales rejected the designation immediately. “We’re not the Business in the way you mean it,” said the CRO. “We execute. The Business is the people who decide what we’re selling and to whom. That’s Marketing and Strategy. Talk to them.”
Marketing
Marketing was categorical. “Marketing is not the Business. Marketing is a cost centre. The Business is the revenue-generating side — Sales, Customer Success, maybe Partnerships. We support the Business.” When informed that Sales had directed us to Marketing, the CMO paused for eleven seconds before responding: “That doesn’t sound right.”
Strategy
Strategy declined to be called the Business on the grounds that Strategy is, by definition, the function that advises the Business on what the Business should do, and therefore cannot be the Business itself without creating, in their words, “a reflexivity problem.” They suggested we speak with Finance, which, they said, “is where the actual business decisions get made.”
Finance
The CFO was the most direct interviewee in the entire engagement. “Finance is not the Business. Finance counts the Business. If we were the Business, who would count us?” She directed us to Operations.
Operations
Operations identified itself as “the Business’s infrastructure” and suggested that the Business was “probably the customer-facing teams.” When asked to name these teams, Operations listed Sales, Customer Success, and Partnerships — all of whom had already denied being the Business.
Customer Success
Customer Success said it existed to serve the Business’s customers on behalf of the Business. When asked who the Business was, the VP of Customer Success said: “Honestly? I’ve always assumed it was Engineering. They’re the ones who decide what the product actually does.”
Legal
Legal was not part of the original interview plan but was added after six departments had been surveyed with no convergence. The General Counsel listened to our summary of findings, nodded slowly, and said: “Everyone calls everyone else the Business. It’s how people here say ’not my problem.'”
We did not include Legal’s observation in the interim report, as it was not actionable under the CFAP™ framework. We include it here because it is the only accurate statement anyone made during the entire engagement.
The Referral Map
At the conclusion of the interview phase, we produced what CFAP™ designates a “Stakeholder Referral Map” — a directed graph showing which functions identify which other functions as “the Business.” The expected output of such a map is a tree structure terminating in one or more nodes that accept the designation: these are the Business.
The map produced by this engagement is not a tree. It is a cycle. Engineering refers to Product, which refers to Sales, which refers to Marketing and Strategy, which refer to Finance, which refers to Operations, which refers to Sales and Customer Success, which refers to Engineering. There is no terminal node. There is no function that, when the referral chain reaches it, says: “Yes. We are the Business. The Business is us.”
The graph has a secondary feature that merits comment. Several functions — notably Strategy and Finance — made referrals that skipped nodes in the primary cycle, creating what graph theory would call chords. These chords do not resolve the cycle. They create shorter cycles within it. The overall topology is not a circle but a torus: a shape with no outside and no inside, which is, we respectfully suggest, an apt representation of the organisation’s relationship with the concept of “the Business.”
Diagnosis
“The Business” at [Company] is not a referent. It is a direction. It points away from the speaker, always, and it points toward the place where non-technical, non-procedural, demand-generating authority is believed to reside. The term’s function is not to identify a group but to create one — or rather, to create the absence of one, since no group accepts the identification. Every function uses “the Business” to name the source of requirements it must fulfil but did not choose, decisions it must implement but did not make, and priorities it must accept but does not understand. The Business is the organisational unconscious: the permanent elsewhere from which unreasonable demands originate.
The word “business” should, on its face, denote the activity that constitutes the company’s reason for existence — the thing the company does. That this word has come to mean the opposite — the opaque, irrational Other, the non-technical, the non-procedural — suggests a condition in which every function has defined itself against the company’s core activity and identified that activity as someone else’s responsibility. The company does not lack alignment between its functions and the Business. The company lacks a function willing to be the Business. Every function has defined its identity as the thing that is Not the Business, and the Business has become what is left over, which is nothing, which is everything, which is the organisation itself, unowned and unnamed.
Recommendations
Retire the term. “The Business” should be removed from the organisation’s working vocabulary and replaced with specific referents: the name of a team, a function, a role. This recommendation has been made by consultants at this company before. The previous engagement’s report, which we located in a SharePoint folder labelled “Business Alignment Initiatives,” made the same recommendation in 2019, in 2021, and in 2023.
Conduct the engagement again in eighteen months. Based on the historical pattern, the term will return within six months of any intervention, and the cycle will reconstitute itself within a year. Casterbridge Partners is available for recurring engagements and offers a discount for clients on triennial retainer.
Accept the condition. The most cost-effective recommendation, and the one most consistent with our findings, is to accept that “the Business” is a structural feature of the organisation and not a problem to be solved. The term will persist because it performs a function that no alternative can perform: it allows every department to externalise the source of its constraints without naming — and therefore without confronting — the actual source, which is the organisation’s own inability to locate its core activity within any of its parts. This is not a dysfunction. It is an equilibrium. The Business is nowhere. The business continues.
Casterbridge Partners — Cross-Functional Alignment and Organisational Cartography
This report is classified CONFIDENTIAL — FOR THE BUSINESS ONLY