Business Functions and How They Interact

Org charts lie; workflows tell the truth

Most companies publish org charts with boxes labeled Marketing, Sales, Finance, Operations, Engineering, and HR. Students memorize definitions. Managers live in handoffs: the moments when work passes from one function to another. Value is often lost in handoffs, not inside departments.

Marketing generates leads Sales calls unqualified. Product ships features Operations cannot support at scale. Finance cuts travel while Sales misses quota because executives stopped visiting key accounts. Engineering optimizes uptime while Product needs speed to test a new pricing model. Each function looks locally rational. The company fails globally.

Lesson 1 explained firm boundaries. Lesson 2 separated value creation, delivery, and capture. Lesson 3 showed stakeholders with conflicting claims. This lesson connects those ideas to how work actually moves inside the boundary. Functions are mental models. Workflows are reality. The MBA skill is seeing the company as a flow, not a collection of departments.

What each function optimizes (and how it fails)

Each function answers a different core question and tends toward a characteristic failure mode when unchecked.

Strategy sets choices about where to play and how to win. It fails when slides never become budget allocations. Marketing creates demand and shapes WTP (Lesson 2). It fails when brand spend does not convert to qualified pipeline. Sales converts interest into contracts. It fails when discounts and promises outrun delivery capacity. Product decides what to build for which jobs to be done. It fails when roadmap volume replaces outcome learning. Engineering implements reliably and securely. It fails when technical elegance delays customer value. Operations fulfills promises at scale. It fails when local efficiency hides global bottlenecks. Finance allocates capital and enforces discipline. It fails when control slows necessary bets. People / HR supplies talent and culture infrastructure. It fails when policies ignore manager judgment.

No function is "the villain." Local optima conflict when metrics are misaligned.

The revenue engine chain

For most commercial businesses, trace this chain weekly:

Awareness → Consideration → Purchase → Delivery → Retention → Expansion

Functions map roughly as follows:

• Marketing: awareness, consideration
• Sales: consideration, purchase (especially B2B)
• Product + Engineering + Operations: delivery
• Customer success / Product: retention
• Sales + Product: expansion (upsell, cross-sell)

If retention is weak, do not only blame Customer Success. Trace upstream. Did Marketing acquire the wrong customers? Did Sales oversell? Did Product miss the job to be done? Did Operations fail OTIF? Lesson 5 will model these delays as system feedback. Here, assign diagnostic responsibility across functions instead of letting the last handoff owner absorb all blame.

Cross-functional interfaces: where careers go to die

Interfaces deserve documentation like APIs (application programming interfaces): inputs, outputs, service levels, escalation paths.

Marketing ↔ Sales

• Interface: lead definition, ICP (ideal customer profile), messaging, handoff timing
• Conflict: Marketing wants volume; Sales wants qualified pipeline
• Typical failure: MQL (marketing qualified lead) definitions drift; Sales ignores leads; Marketing blames "bad sales"; Sales blames "bad leads"
• Fix: Shared definitions, joint pipeline reviews, compensation tied to qualified opportunities, not raw lead count

Product ↔ Engineering

• Interface: roadmap, specs, technical debt tradeoffs, release quality bar
• Conflict: Product wants dates; Engineering wants stability
• Fix: Explicit capacity allocation for debt; outcome-based commitments; DRIs (directly responsible individuals) per initiative

Finance ↔ Everyone

• Interface: budgets, headcount, pricing approval, vendor terms
• Conflict: Control vs speed
• Fix: Tiered approval thresholds; finance partners embedded in business units; fast-track path for small experiments

Operations ↔ Sales

• Interface: capacity promises, customization limits, implementation timelines
• Conflict: Sales promises dates Operations cannot meet
• Fix: Configure-to-order rules in CRM (customer relationship management software); deal desk review before signature

Customer Success ↔ Product

• Interface: churn reasons, feature gaps, onboarding friction logs
• Conflict: Customer Success wants roadmap fixes; Product wants quantified impact
• Fix: Weekly churn review with tagged reasons; Product allocates fixed % capacity to top churn drivers

People / HR ↔ All functions

• Interface: headcount plan, role definitions, compensation bands
• Conflict: Managers want bodies fast; HR wants quality and equity
• Fix: Rolling 90-day headcount forecast tied to constraint (Lesson 5); hiring freeze exceptions only via DRI approval

When interfaces are undocumented, each function optimizes its metric and the customer feels chaos.

The operating cadence: from strategy to weekly rhythm

Strategy sets direction once or twice a year: which customer segments, which geographic markets, which capabilities to own versus buy (Lesson 1). Annual planning translates strategy into budgets and headcount. Quarterly business reviews test whether bets are working. Weekly operating reviews surface handoff failures before they become churn.

Many companies skip the weekly layer and wonder why quarterly numbers miss. By the time finance closes the quarter, the causal chain started twelve weeks earlier in a Marketing-to-Sales handoff or a Sales-to-Operations promise. Weekly cadence is not bureaucracy for fast companies. It is how fast companies prevent rework.

A useful weekly agenda (30 to 60 minutes, same core attendees):

1. North-star metric and guardrails (two minutes)
2. Funnel or delivery bottleneck from last week (ten minutes)
3. Customer evidence: one call clip or three support themes (ten minutes)
4. Decisions needed with DRIs and dates (ten minutes)
5. Escalations only if unresolved (five minutes)

Lesson 3 reminds you that employees experience this cadence as either clarity or chaos. If weekly meetings are slide theater without decisions, tacit knowledge stays hidden and handoffs keep failing.

When the revenue engine breaks: diagnostic order

Use a fixed diagnostic order so teams do not argue from function bias:

1. Is the customer the right customer? (Marketing / Sales ICP)
2. Was the promise credible? (Sales / Product)
3. Did we deliver on time and completely? (Operations / Engineering)
4. Did the customer realize economic value? (Product / Customer Success)
5. Did we capture fairly and retain? (Finance / Sales expansion)

Skipping steps produces familiar mistakes: Customer Success blamed for churn caused by bad ICP; Engineering blamed for delays caused by Sales promising custom work; Marketing blamed for "bad leads" when the product no longer solves the advertised job (Lesson 2 creation failure).

Document findings in plain language: "Churn rose because implementation backlog exceeded 30 days for enterprise segment," not "Customer Success needs to try harder."

Role of the general manager as integrator

The GM (general manager, the leader accountable for a product line or business unit P&L) exists to resolve cross-functional tradeoffs that no single function will optimize voluntarily. GMs translate Lesson 2's value triangle and Lesson 3's stakeholder map into weekly choices: which segment to pursue, which handoff to fix first, which metric to relax temporarily to protect the constraint (Lesson 5).

Without a GM integrator, functions negotiate through escalation. Escalation is expensive and slow. A GM with authority over headcount and priorities can subordinate local KPIs when the system constraint demands it, then restore balance after capacity expands.

In smaller companies, the CEO plays GM integrator. In larger companies, GMs sit at business unit level while functional VPs provide expertise. Either way, someone must own the revenue engine chain end to end, not only a single box on the org chart.

Integration mechanisms that work

Four mechanisms appear repeatedly in well-run companies.

1. Shared metrics. One north-star metric (for example, active paying accounts or weekly completed orders) plus a few supporting metrics owned by functions. If every function has unrelated key performance indicators, they will fight. The north star should map to Lesson 2's triangle, not only capture.

2. Cadence. Weekly operating reviews with the same attendees and agenda: metrics, blockers, decisions. Monthly strategic reviews for bets and resource shifts. Cadence turns handoffs into habits instead of escalations.

3. Single-threaded leadership. For critical initiatives, one DRI with authority across functions. Matrix management without authority creates paralysis.

4. Customer evidence in the room. Bring customer calls, churn reasons, and support tickets into cross-functional meetings. Functions align faster around reality than around slides.

These mechanisms cost management time. They reduce expensive cross-functional failure. Lesson 3 noted that employees carry tacit knowledge about handoff breakdowns. Integration mechanisms surface that knowledge before customers churn.

When rolling out a new mechanism, start with one pilot business unit. Publish before-and-after metrics on handoff failures (for example, implementation delays or rejected leads). Scaling a mechanism without proof creates "process theater" that employees ignore. Proof builds the trust Lesson 3 requires across employee and owner stakeholders. Start small, measure handoffs, then scale.

Designing interfaces when incentives conflict

When two functions fight, the fix is rarely "communicate better" alone. Incentives and definitions must change.

Document the interface: what input Marketing promises Sales, by when, in what format, with what minimum data fields. What Sales promises Operations before contract signature. Ambiguity is expensive.

LumenHR sells payroll software to mid-size employers. It launches LumenHR Plus, a tier with white-glove onboarding and compliance advisory. Marketing campaigns exceed targets. Sales sets a quarterly demo record. Sixty days later, churn on new Plus accounts is 2.4× the core tier.

Part A: Symptom vs blame

Part B: Handoff trace

Part C: Quantified impact (simplified)

Check first-year Plus contribution: Gross profit 75% on $28,000 = $21,000; minus CTS $11,500 = $9,500; minus higher support $2,300; minus allocated CAC $9,000 ≈ negative contribution. ✓

Part D: Fix as interface redesign

1. ICP gate: Plus only for employers with ≤3 states unless deal desk approves.
2. Deal desk: Sales cannot promise go-live date without Operations calendar slot.
3. Launch playbook: Product and Support ship macros and videos before campaigns go live.
4. Finance model: Bundle 10 advisory hours; price additional hours.

Managerial read: The failure was not "bad marketing." It was missing interfaces between Marketing, Sales, Operations, Finance, and Support.

Part E: Six-month follow-up metrics

After interface fixes, LumenHR tracks:

Check contribution after fix: $28,000 × 75% = $21,000 gross; minus $7,500 CTS; minus support $2,000; minus CAC $8,000 ≈ $3,500 positive ✓

The system improved because functions shared definitions and guardrails, not because any single department worked harder in isolation.

Northstar Retail is a 40-store sporting goods chain. Same-store sales are flat. Inventory is high. Marketing wants a 20% off weekend blast. Operations warns OTIF from warehouse is already 91%.

Part A: Functional proposals

Part B: Shared metric choice

Northstar adopts weekly gross margin dollars after markdowns as north star, with OTIF and inventory weeks of supply as guardrails.

Part C: Decision

Run targeted markdown on 120 slow SKUs plus ship OTIF recovery plan (overtime in warehouse for two weeks). Defer chain-wide 20% event.

Part D: Outcome logic

Marketing still drives traffic on selected items. Operations protects delivery credibility. Finance avoids blanket margin destruction. Sales gets staffing plan with forecasted traffic, not a surprise blast.

Check: Decision uses one north star plus two guardrails ✓

The classic mistake is declaring victory on marketing pipeline while delivery and capture leak, the same triangle error from Lesson 2 wearing functional clothing.

SignalDesk sells incident management software. Facts:

Tasks:

1. Compute new ARR (annual recurring revenue, yearly subscription revenue) per month from this funnel.
2. Identify the two likeliest interface breaks and which functions own them.
3. Propose one shared metric and one cadence change.
4. Estimate ARR if SQL acceptance rises to 55% with same close rate (show check).

Solution

1. New ARR per month

SQLs 320 × win rate 22% = 70.4 wins ≈ 70 customers
ARR 70 × $16,000 = $1,120,000 per month

Check: 320 × 0.22 = 70.4 ✓

2. Interface breaks

• Marketing ↔ Sales: 60% MQL rejection suggests definition drift or weak ICP targeting.
• Sales ↔ Operations/Product: Implementation 31 vs 14 days likely drives 11% churn.

3. Integration fixes

• Shared metric: % of new customers live within 21 days (sales promise tied to operations delivery).
• Cadence: Weekly 30-minute funnel review with Marketing, Sales, and Implementation lead reviewing rejected MQL reasons and overdue implementations.

4. ARR if SQL acceptance 55%

MQLs 800 × 55% = 440 SQLs
Wins 440 × 22% = 96.8 ≈ 97
ARR 97 × $16,000 = $1,552,000

Increase: $432,000/month ARR if quality holds. Check: 440 × 0.22 = 96.8 ✓

Caution: Raising acceptance without fixing implementation may increase churn. Interface fixes should run in parallel.

Draw a handoff map for a B2B company you know with at least four functions. Label one broken handoff. What metric causes local optimization at global expense?

Solution (exemplar)

Example map: Marketing → SDR (sales development representative, outbound qualification) → Account Executive → Customer Success → Finance billing.

Broken handoff: Account Executive → Customer Success (promised integrations not in onboarding checklist).

Local metric causing global harm: Sales compensated on bookings without logo retention at 90 days, encouraging oversell that destroys delivery and future capture.

Key takeaways

• Functions are labels; workflows and handoffs determine customer experience.
• Most strategic failures are cross-functional misalignment, not single-department incompetence.
• Map interfaces with definitions, metrics, and escalation like APIs.
• Shared north-star metrics and steady cadence beat ad hoc escalations.
• Customer evidence is the neutral ground for aligning Lesson 2's value triangle across functions.

1. List three handoffs in your work that feel broken. Who owns each side? What input/output is ambiguous?
2. Identify one metric that causes local optimization at global expense in your organization.
3. Continue to Lesson 5: Reading a Business as a System.