In supply chain planning, alignment is often treated as a meeting outcome.
Teams come together. They review the situation. They discuss what needs to happen next. They agree on a plan.
But in an increasingly complex and uncertain environment, agreement is not always enough.
In my conversation for the first Voices episode of The Decision Room by Sunstice, we discussed decision-making, planning, culture and the realities of operating in increasingly complex supply chains.
One question captures an important part of how I approach this topic:
“Are we actually really aligned, or are we just politely agreeing?”
It is a simple question. But for supply chain, S&OP and planning leaders, it is also an important one.
I have seen situations where teams seemed to be on the same page, but were actually only politely agreeing. The consequences then appeared afterwards.
What we unpack
- How can you tell whether a team is truly aligned or simply avoiding disagreement?
- What does it take to balance agility and stability in supply chain planning?
- Why can a decision that looks right today have a very different impact months later?
- What makes end-to-end planning work in practice, beyond tools and processes?
- Why do data quality and culture matter so much for the future of planning?
For my full perspective on those topics, watch the complete episode of The Decision Room.
Here are five lessons I would take from the discussion.
1. True alignment must be tested, not assumed
“Are we actually really aligned, or are we just politely agreeing?”
One thing I have seen is that alignment can be misleading.
People may appear to be on the same page. They agree in meetings. They move forward. But that does not always mean that misunderstandings or different expectations have disappeared.
For planning teams, this matters because supply chain decisions cannot be looked at one department at a time. We need to bring together a bigger network and make decisions across it.
So alignment cannot simply mean that no one objects.
For me, it requires a layer of trust and the ability to challenge one another until we actually agree. If we are not aligned, we need to dig deeper and understand where there are still misunderstandings or different expectations.
The question is not only whether everyone agreed in the room. It is whether we are really on the same page.
2. Supply chain planning has to balance agility and stability
One of the central tensions I see in supply chain today is the need to remain agile while preserving stability.
There are many expectations on supply chain teams. AI creates a feeling that we constantly need to keep up, while uncertainty also comes from geopolitical issues, electronic shortages and everything happening in the outside world.
Supply chain is a difficult area in which to adapt continuously because it is already so complex.
That is why, for me, the biggest tension is between agility on the one hand and stability on the other.
We need to adapt and keep up, but we also need a certain sense of stability.
The challenge is having to do both at the same time.
3. Planning must show future impact, not only current status
Another important role of supply chain planning is to provide the full picture.
That means looking across the network rather than allowing individual departments to make decisions in isolation. But it also means looking ahead.
Certain things may look okay today, while their real impact only becomes visible a few months later, in half a year or even in a year.
This is one of the reasons planning matters so much.
Good planning needs to help us project into the future, not only on revenue, but also on inventory and working capital.
Those future projections influence how we take decisions today.
Planning therefore needs to help teams understand both what is happening across the network now and what the decisions they take today could mean later.
4. End-to-end planning is a behavior, not only a process
End-to-end planning is often discussed in terms of processes, systems and planning structures.
But there is also a very human side to it.
For end-to-end planning to work, people need to feel attached to the end-to-end cases they are working on. They need ownership and motivation to work on the decisions that need to be made.
They also need to understand the business story behind a case, challenge their own decisions, follow up on that story and stay on top of the actions they have decided on.
Information, processes and tools matter too.
We need access to information, shared objectives, shared KPIs, a strong network, processes, software and tools.
But ultimately, all of those elements should lead to connected behavior: people working together on decisions and end-to-end cases, and following through until they reach the goal they want to reach.
That also means enabling people to make decisions.
I think we need to get used to the idea of decentralized decisions. There is little point in building all of this structure if people then remain dependent on leadership to take every decision.
On an operational level, people working directly on end-to-end cases may even be better placed to take those operational decisions. Leadership still plays a very important role, but escalation should happen when it is really necessary.
End-to-end planning becomes meaningful when people actually behave in a connected way.
5. AI readiness still depends on data quality and culture
Looking ahead, I see two major challenges for planning teams: data quality and culture.
The point on data quality is especially important in the context of AI.
Data quality is the basis for planning systems and software in general. Every expectation we have of AI, and everything we want to improve with AI, is only possible with the right data quality and data structures in place.
Software also helps us identify and evaluate critical end-to-end cases.
In a complex network, it can help make impacts transparent. For example, without the right software, it would be extremely difficult to understand whether sending more air freight to solve one issue could have a negative impact somewhere else.
But the future of planning is not only about technology.
Culture matters just as much.
We need motivated people and a cultural foundation that encourages them to work on business stories and end-to-end cases. That culture is difficult to build. It takes time, and it needs to keep adapting and evolving as new people join or attention moves elsewhere.
For me, that is a process that never really ends.
Toolbox: Six questions to pressure-test decisions throughout the S&OP cycle
In practice, there are six questions I believe are useful for challenging decisions throughout an S&OP cycle:
1. Data & signal preparation
Which emerging signal could materially affect the plan if we wait until the next cycle to act on it?
2. Demand Review
Which demand change could have the biggest downstream impact over the next few months?
3. Supply Review
If we solve this constraint here, where could we create a new problem elsewhere in the network?
4. Pre-S&OP / Reconciliation
Where could two teams leave this meeting with a different interpretation of the decision?
5. Executive S&OP
Which of these decisions genuinely requires executive arbitration, and which could be resolved at operational level?
6. Follow-through
What change in the situation would mean we need to revisit this decision?
A question every planning leader should ask
Of all of these, the question I would keep coming back to is:
“Are we really aligned, or are we just politely agreeing?”
If the answer is not clear, we need to dig deeper: where are the misunderstandings, and where do expectations still differ?
For me, that captures much of what good supply chain planning requires: bringing the right people together, giving them the information and tools they need, and enabling them to make decisions and follow through.
Because ultimately:
“You can only do it together.”
Watch the full episode
Watch my full Voices episode of The Decision Room by Sunstice to hear the complete discussion on supply chain decision-making, agility and stability, end-to-end planning, decentralized decisions, software, data quality, culture and communication.
.webp)
.webp)
.webp)
.webp)
.webp)
.webp)
