<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "HowTo", "name": "How to Use: Orient", "description": "Sensing that something in your supply chain capability needs attention but without a clearly named initiative or investment in view. This is where most capability investment journeys begin.", "url": "/journey-stages/orient", "inLanguage": "en", "about": { "@type": "Thing", "name": "Orient decision stage", "description": "Sensing that something needs attention — but not yet sure what kind of change is forming" }, "step": [ { "@type": "HowToSection", "name": "Interpretation", "text": "If you are in a period of orientation — sensing that something in your supply chain capability needs attention but without a clearly named initiative, timeline, or investment in view — this is the most common starting point for what eventually becomes a significant capability investment journey. Many significant capability investments only fail later because they were framed too early, too narrowly, or around the wrong problem." }, { "@type": "HowToSection", "name": "Why the Orient stage", "text": "Decisions typically move into later stages when certain conditions begin to show up: a clearly defined problem, a shared sense of what success looks like, visible senior sponsorship, identifiable trade-offs, and some form of commitment pressure. Acting too early can be riskier than waiting until the decision is framed clearly enough for others to engage with it confidently." }, { "@type": "HowToSection", "name": "Where teams get stuck", "text": "Teams at this stage often feel pressure to do something before the problem is fully understood. Common patterns include jumping prematurely to solution areas before the root cause is clear, conflating symptoms with root causes, and struggling to articulate the issue clearly enough for others to engage meaningfully." }, { "@type": "HowToSection", "name": "What tends to help", "text": "Leaders in similar situations typically benefit from developing a shared way of describing the problem that different functions can recognise themselves in, making implicit assumptions and mental models explicit before discussing solutions, and pressure-testing whether something is truly worth acting on now." } ], "mentions": [ { "@type": "Person", "name": "Donella Meadows" }, { "@type": "Person", "name": "Megan Smith" } ], "provider": { "@type": "Organization", "name": "BestPractice.Club", "description": "A practitioner-led environment for working through complex, high-stakes supply chain capability investment decisions", "email": "info@bestpractice.club", "url": "https://bestpractice.club" } } </script>

ORIENT

Sensing that something needs attention — but not yet sure what kind of change is forming

You can’t predict the behaviour of a system by studying its parts

Donella Meadows

Interpretation

If you are in a period of orientation — sensing that something in your supply chain capability needs attention but without a clearly named initiative, timeline, or investment in view — this is the most common starting point for what eventually becomes a significant capability investment journey.

Many experienced leaders are surprised to find themselves here. That reaction is common and usually reflects the complexity of the situation rather than the maturity of the team. Supply chain capability investment decisions are rarely straightforward. The organisations that navigate them well are often the ones that slowed down deliberately at this stage rather than reaching for a solution before the problem was fully understood.

This stage is not passive. It is where experienced leaders clarify what they are actually trying to achieve, why it matters now, and what good would genuinely look like if they got this right. The work here is less about choosing a solution and more about understanding what kind of organisation, capability, or operating model you are really working towards.

Many significant capability investments only fail later because they were framed too early, too narrowly, or around the wrong problem. The discipline at this stage is to resist that pressure.

Why the Orient stage?

Decisions typically move into later stages when certain conditions begin to show up: a clearly defined problem, a shared sense of what success looks like, visible senior sponsorship, identifiable trade-offs, and some form of commitment pressure — whether from time, budget, reputation, or dependency.

If those signals are not yet consistently present, that does not mean a decision is not forming — only that it has not yet solidified into something most stakeholders would recognise as a concrete project requiring sustained commitment. Key elements of a well-framed decision are still emerging: the real alternatives may not yet be clear, consequences are still being explored, uncertainty remains high, and it is not yet obvious what would be hard to reverse later.

This is a common and often sensible position in complex contexts. Acting too early can be riskier than waiting until the decision is framed clearly enough for others to engage with it confidently.

Why the Orient decision stage?

Decisions typically move into later stages when certain conditions begin to show up:

  • a clearly defined problem,
  • a shared sense of what success looks like,
  • visible senior sponsorship,
  • identifiable trade-offs,
  • and some form of commitment pressure (time, budget, reputation, or dependency).

Based on your responses, those signals don’t yet appear to be consistently present. That doesn’t mean a decision isn’t forming — only that it hasn’t yet solidified into something that most stakeholders would recognise as a concrete project requiring sustained commitment of time, attention, or capital.

In practice, this usually means that while there is intent or concern, key elements of a well-framed decision are still emerging: the real alternatives may not yet be clear, consequences are still being explored, uncertainty remains high, and it’s not yet obvious what would be hard to reverse later.

This is a common — and often sensible — position in complex contexts, where acting too early can be riskier than waiting until the decision is framed clearly enough for others to engage with it confidently.

Where teams typically get stuck

Teams at this stage often feel pressure to do something before the problem is fully understood — particularly when signals are coming from multiple directions simultaneously.

Common patterns include:

  • Jumping prematurely to solution areas before the root cause is clear
  • Conflating symptoms with root causes — treating the visible performance gap as the problem rather than investigating what is producing it
  • Struggling to articulate the issue clearly enough for others to engage meaningfully

A related challenge is that different functions are often working from different mental models at this stage. Supply chain, finance, IT, and leadership may all be using different language to describe the same situation. Until those differences are surfaced, teams can appear aligned on the surface while talking past each other underneath.

What next:

What tends to help at this point

What is most useful at this stage is better framing, not answers.

Leaders in similar situations typically benefit from:

  • Developing a shared way of describing the problem that different functions can recognise themselves in
  • Making implicit assumptions, language, and mental models explicit before discussing solutions
  • Developing sharper language for what is and is not in scope
  • Understanding the range of ways problems like this eventually turn into real capability investment decisions — and what triggers the transition
  • Pressure-testing whether something is truly worth acting on now, or whether the conditions for a well-framed decision are not yet present

This is about orientation and clarity, not commitment. The aim is to be better prepared when this turns into something others need to weigh in on.

Suggested next steps

If this resonates, a light-touch approach usually works best at this stage.

Exploring how other supply chain leaders have framed similar challenges — and how those framings shaped the decisions that followed — is typically the most useful first step. The Perspectives content below is organised around the patterns most practitioners encounter at this point.

If you find content that reflects your situation accurately, the most useful next step is simply to stay close to the conversation. The aim is not to commit to anything yet — it is to develop a clearer and more grounded sense of what the problem actually is before others need to engage with it.

You are welcome to sign up for relevant updates from BestPractice.Club — we will send you practitioner cases and session announcements that are relevant to where you are. The frequency depends on what our members are working through and reporting, which means it may be sporadic. We will not fill the gap with content that does not earn your attention.

See what practitioners at this stage are reading

You can’t understand a complex problem without understanding the people who live inside it

Megan Smith

A quick note on how to read this

BestPractice.Club is not a consultancy and does not provide advisory services based on full organisational discovery.

What you see here reflects pattern recognition drawn from many years of conversations with supply chain and operations leaders facing real, high-stakes decisions. It is intended to help you orient yourself, clarify your decision position, and understand what often proves useful at similar points — not to provide definitive advice tailored to your specific circumstances.

Any suggestions are indicative, not exhaustive, and are made without full visibility of your organisation, constraints, or risk profile. Decisions remain yours, and should be tested against your own data, context, and governance processes.

If this framing doesn’t quite fit, that’s normal. Real decisions rarely move in straight lines, and teams often revisit earlier stages as new information emerges. If it would help to talk through your situation and sense-check where you are, you’re welcome to schedule a short conversation.