VCM thought leadership
5 Steps How to Transition to a Networked Operating Model (Easy Guide for Decision-Makers)
You know that feeling when a critical decision gets stuck in a "black hole" of internal approvals? You’ve seen it: a great idea for a customer service improvement is born in marketing, gets delayed by IT capacity, hits a budget wall in finance, and by the time it reaches the customer, the market has already moved on.
It’s frustrating. It’s expensive. And frankly, it’s the natural byproduct of the traditional vertical hierarchy. We’ve all been taught that clear lines of command and functional silos: Sales here, Operations there, IT in the basement: are the only way to manage a large business. But in today’s volatile market, these silos act like friction points, slowing down your response time and alienating your best talent.
At Value Chain Management, we aren't magicians. We can’t wave a wand and make your legacy systems disappear overnight. However, we have seen that when businesses move away from rigid "top-down" structures and toward a Networked Operating Model, the results are transformative. This isn't just about "being agile": it’s about restructuring your business to follow the flow of value rather than the lines of an org chart.
If you’re ready to break down the silos and create horizontal alignment, here is our practical five-step guide to making the transition.
Step 1: Define Your Strategic Narrative and the "Why"
Before you move a single desk or change a single reporting line, you have to answer the question everyone in your office is thinking: “Why are we doing this?”
Change is hard. If your team thinks this is just another management fad or a disguised cost-cutting exercise, they will resist it. As a decision-maker, your first job is to create a compelling narrative that links the new model to real business survival and growth.
How can I make the case for change? Start by looking at where you are failing today. Are you losing market share because your product development cycles are too slow? Is your customer churn high because your support and product teams don't talk?
We suggest focusing on 3–5 measurable outcomes you want to achieve in the next 18 months. This might be a 20% reduction in time-to-market or a significant jump in Net Promoter Score (NPS). When the narrative is about solving customer problems rather than just "reorganizing," people get on board.
Step 2: Map Your Value Streams (Not Your Org Chart)
Most businesses are organized by function (what people do). A networked model is organized by value (what the customer gets).
To transition, you must stop looking at your department list and start looking at your customer journeys. We call these value streams. For example, "Order to Cash" or "Idea to Launch."
As a leader, you should:
Identify 3–5 critical journeys: Where does the money actually come from? Where do the most frequent customer complaints happen?
Diagnose the bottlenecks: Ask your frontline staff where the "handoffs" fail. Usually, it’s where one department’s responsibility ends and another’s begins.
Pick your starting point: Don’t try to change the whole company at once. Pick one or two journeys where leadership is supportive and the impact of improvement would be highly visible.
If you're unsure where your biggest gaps lie, you can explore our projects page to see how we’ve helped other firms map their value chains for maximum efficiency.
Step 3: Design Your Network of Teams
Once you know the "value flow," you need to build the teams to support it. In a networked operating model, we move away from functional departments and toward cross-functional squads.
Instead of having a marketing person, a developer, and a customer success lead sitting in three different buildings reporting to three different VPs, you put them in one "squad" dedicated to a specific product or customer segment.
Focus on these four design elements:
Shared Accountability: The team owns the outcome (e.g., "Increasing customer retention"), not just their individual tasks.
Clear Decision Rights: Define what the team can decide on their own. If they have to ask permission for every £500 spend, they aren't a networked team; they're just a committee.
Horizontal Alignment: Ensure teams are aligned with each other. They need a shared language and shared data. This is where data transformation becomes the "glue" that holds the network together.
Minimal Governance: Keep the central controls for things like legal, compliance, and major capital expenditure, but decentralize the day-to-day operations.
Step 4: Pilot, Learn, and Protect
We often see leaders get excited and try to "flip the switch" on the whole organization. This usually leads to chaos. The most successful transitions we’ve witnessed at Value Chain Management happen through deliberate scaling.
Start with your 1–2 pilot journeys. Give these teams the air cover they need to work differently. This means protecting them from "old world" bureaucracy. If a pilot team needs a new software tool to move faster, don't make them wait six months for a general IT audit if you can help it.
What metrics should you track? Don't just look at financial ROI in the first month. Look at:
Cycle time: How much faster are things moving?
Employee engagement: Are the people in the pilot happier and more productive? (Usually, the answer is a resounding yes).
Quality: Is rework going down because the right people are in the room from the start?
Step 5: Embed and Institutionalize the New Ways of Working
The final step is the hardest: making sure you don't snap back to the old ways. Human beings are like rubber bands; we love the comfort of the status quo.
To make the networked model permanent, you have to update your "operating system": your HR policies, your finance cycles, and your leadership style.
The "Clean Up" Phase:
Incentives: If you still reward people based on their functional performance (e.g., "IT stayed under budget") rather than the network's performance (e.g., "The customer journey was seamless"), you will recreate silos.
Leadership Coaching: Your managers need to move from being "task-masters" to "roadblock-removers." This is a huge psychological shift. Leaders in a networked model don't provide all the answers; they provide the environment where the teams can find the answers.
Continuous Improvement: A networked model isn't a destination; it’s a capability. You should be reviewing the model itself every quarter. Do we have the right teams? Are the decision rights still clear?
For more on how we support this long-term evolution, check out our About Us page to understand our philosophy on sustainable business transformation.
Why Horizontal Alignment Matters for Your Bottom Line
Transitioning to a networked operating model isn't just a "nice to have" or a HR initiative. It is a strategic imperative. When you break down silos, you reduce the "hidden costs" of your business: the endless meetings, the political infighting, and the missed opportunities.
By aligning your people horizontally across the value chain, you ensure that everyone is pulling in the same direction: toward the customer. It makes your business more resilient, more agile, and ultimately, more profitable.
We know this transition can feel daunting. You might be worried about losing control or creating confusion. That’s why we’re here. We work alongside you to design a model that fits your specific culture and industry, ensuring that the transition is smooth and the results are measurable.
If you’re ready to stop managing silos and start managing value, let’s have a conversation. You can book a session with us to discuss your current challenges, or browse our FAQ for more insights on how we work.
The future of business isn't a pyramid; it’s a network. Let's start building yours today.