Running the JV: Board and Management Practices

15.2 Annual Planning, Budgeting, and Performance Reviews

Annual planning is where shared ownership either becomes shared commitment or reverts into two parent agendas. One parent may push for aggressive expansion; the other may push for conservatism to protect cash or dividends. If the process is not designed, management becomes a mediator and the plan becomes a compromise that no one truly owns.

Annual plan: The JV’s integrated strategy, operating plan, budget, and capital plan for the coming year, including assumptions, risks, and required commitments.

Begin with a plan narrative before debating numbers. State what must be true for the plan to work: volume and price assumptions, capacity and reliability assumptions, hiring and capability assumptions, and parent commitments the plan relies on (sales coverage, supply availability, IT change capacity, transition services). When the narrative is aligned, budgeting becomes an execution tool rather than a political battleground.

Plan narrative: A concise explanation of the plan’s value drivers, key assumptions, required commitments, and top risks, agreed before detailed line items are debated.

Plan in three passes. First, confirm strategy and guardrails: scope, customer focus, investment priorities, and risk limits. Second, agree the operating plan: initiatives, milestones, headcount, and capability build. Third, lock the budget and capital plan with delegation bands and variance rules. Starting with line items usually produces the wrong priorities.

Build a deliberate challenge step into planning. Ask a small group—finance, risk/compliance, and an operator—to pressure-test only the assumptions that drive most value and most downside. The output should be clearer triggers for course correction and explicit decisions on which risks the parents accept.

Challenge session: A focused review that tests key assumptions, downside scenarios, and required commitments, producing explicit risk acceptance or plan changes.

Close planning with a clear operating contract between the board and management: variance bands, reallocation rules, and emergency authorities for safety and compliance. This protects speed while preserving oversight.

Budget approvals should explicitly define management flexibility. Define variance bands for spend and headcount, and define reallocation rights within the approved plan. Pair flexibility with transparency: management reports material variances quickly and explains them through drivers.

Variance band: A predefined range within which management can deviate from plan assumptions without seeking additional approvals, paired with reporting expectations.

Performance reviews should be routine, not drama. Use a steady rhythm: monthly management dashboards and quarterly board reviews. Quarterly reviews should end with owned actions, not only discussion.

• Performance: What happened versus plan and forecast, explained through drivers.
• Diagnosis: What is structural versus timing versus execution.
• Actions: What will change, with owners and expected impact.
• Support needed: Decisions, resources, or parent commitments required.

Performance review: A structured routine that evaluates results, diagnoses drivers, agrees corrective actions, and tracks follow-through.

Protect fairness by making parent dependencies visible. If the JV relies on parent services, capacity, or channel behavior, track that delivery explicitly and review it alongside JV KPIs. Otherwise, the JV will be held accountable for outcomes it cannot control.

Parent commitment KPI: A metric that tracks delivery of parent obligations that enable JV performance, such as SLA attainment, referral conversion, supply reliability, or system availability.

Keep cash discipline central. Establish a rolling forecast cadence that extends beyond the fiscal year and includes a cash runway view, with triggers that require escalation and action. Early visibility turns funding discussions into planning; late visibility turns them into conflict.

Rolling forecast: A periodically updated projection of performance and cash that supports early detection of funding needs and risk triggers.

15.3 Managing Tensions Between JV and Parent Objectives

Tension is normal because the JV is a business and also an instrument of parent strategy. The venture may need neutrality to win customers, while a parent wants preferential access. The venture may need reinvestment, while a parent wants cash. The venture may need to slow for compliance, while a parent wants speed. These are not “relationship problems.” They are recurring tradeoffs.

Objective tension: A recurring conflict between the JV’s enterprise needs and one or both parents’ strategic or financial goals that requires explicit tradeoffs.

Move from fairness language to tradeoff language. “Is this fair?” leads to positional bargaining. “What are we optimizing for, and what do we give up?” leads to decisions. Classify tensions into four types so you choose the right response.

• Structural: Built into the model, such as neutrality versus parent access, or growth versus dividends.
• Execution: Driven by performance gaps, timing misses, or capability shortfalls.
• Interface: Driven by service levels, transfer pricing, or resource prioritization.
• Strategic drift: Driven by parent strategy or market shifts that alter the JV’s role.

Structural tensions require explicit policies and exception rules. If neutrality is required, define uniform pricing and service rules, define what qualifies as an exception, and require post-exception review. If limited preferential treatment is allowed, define criteria and compensate transparently rather than applying informal pressure that undermines credibility.

Exception rule: A predefined policy that specifies what constitutes an exception, who can approve it, what documentation is required, and how exceptions are reviewed.

Execution tensions require driver-based diagnostics and time-bounded corrective plans. Avoid the reflex of tightening approvals to “control” execution; over-approval usually slows the response and worsens outcomes.

Interface tensions should be solved at the interface. If disputes about IT change windows, shared services responsiveness, or supply allocation keep reaching the board, run an interface health review and fix the agreement, incentives, and escalation behavior.

Interface health review: A focused assessment of JV-parent interfaces using SLA performance, cost transparency, dispute patterns, and customer impact, resulting in targeted fixes and owners.

Use a two-layer scorecard to keep agendas explicit. The enterprise layer measures JV outcomes and right-to-operate performance. The parent-benefit layer measures what each parent expects, such as market access milestones or capability development. Visible benefits reduce hidden agenda behavior.

Two-layer scorecard: A performance framework that tracks JV enterprise outcomes and parent-specific benefits separately, reducing hidden agenda behavior.

When tensions recur, put them into explicit “trade rules” rather than re-negotiating each instance. For example, define how quota credit and margin credit work when parent sales teams sell the JV’s offering, or define how scarce capacity is allocated when both the JV and a parent compete for the same slot. Trade rules reduce emotional escalation because people can predict the outcome and focus on improving the underlying capacity or economics.

Trade rule: A predefined, repeatable rule that governs a recurring JV-parent tradeoff, such as allocation of scarce resources, customer exceptions, or crediting of commercial contributions.

Protect management from being squeezed. The board should decide, document, and communicate one integrated direction. Ambiguous “balanced” direction increases escalation and slows execution.