Why cross-functional growth programs stall

Growth in insurance and financial services rarely belongs to one department. A new proposition may require customer insight, product design, underwriting, distribution, marketing, technology, operations and measurement. Each team can deliver its own responsibilities while the complete growth outcome still moves too slowly.

Functional excellence is necessary, but not sufficient

Organizations are usually designed to manage functions. Growth outcomes cut across them. This creates a structural tension: budgets, targets and governance sit inside business units, while value depends on decisions and dependencies that cross those same boundaries.

Traditional project reporting can hide the problem. A workstream may be green because it met its milestone, even though another team cannot use the output or a critical dependency has not been funded.

Four sources of cross-functional friction

1. Different clocks. Strategy, technology, product and channel teams often plan on different cycles.
2. Different measures. Functions optimize local targets that may not combine into the intended business outcome.
3. Unclear trade-offs. When priorities compete, decisions escalate because no owner has authority across the complete value path.
4. Hidden dependencies. Teams discover operational, data or capability requirements only after commitments have been made.

Manage the value path, not only the workstreams

A connected growth operating model starts with the outcome and works backward. It identifies the sequence of customer and business changes required, the capabilities that enable them and the decisions that keep the work moving. Workstreams remain important, but they are managed as parts of one value path.

Leadership should be able to see where the outcome is constrained, what evidence is available, which decision is required and who owns it. This shifts governance from reporting activity to accelerating value.

Build coordination into the operating rhythm

Cross-functional execution improves when the organization has a repeatable cadence for reviewing outcomes, resolving dependencies and reallocating resources. The cadence should be light enough to support speed and disciplined enough to prevent the same unresolved issues from returning month after month.

The aim is not more bureaucracy. It is a smaller number of better decisions, made with a shared view of value and carried through by teams that understand how their work connects.