This is where the quality of the eventual decision is most often determined — and where independent peer input is most scarce and most valuable.
If you have named the problem — you have a working hypothesis about what is limiting supply chain capability and what kind of investment might address it — but you have not yet committed to a direction and are actively testing whether your read is correct, this is where the quality of the eventual decision is most often determined.
This stage sits between general orientation and vendor evaluation. You are past the point of wondering whether something needs to change. You are not yet at the point of inviting vendors to present. The work here is resolving what kind of solution architecture is actually appropriate for your situation — before any vendor has had the opportunity to anchor the conversation.
Teams at this stage often move forward with more certainty than is warranted.
Common patterns include treating early hypotheses as settled decisions and moving to solution evaluation before the problem framing has been independently tested; relying on a narrow set of perspectives, particularly those of people who already share the same assumptions; assuming alignment where assumptions actually differ across teams, which only becomes visible when finance, IT, or leadership engage; and skipping the architecture direction question by moving directly from problem awareness to vendor demonstrations without resolving what kind of solution is actually appropriate.
Because progress feels real at this stage, these gaps often go unchallenged until they surface later as resistance, rework, or loss of confidence in the investment case.
The assumption most practitioners at this stage are operating on is that the diagnosis is broadly right, that the capability gap has been correctly identified, and the question now is how to address it.
The evidence from comparable decisions suggests that the diagnosis is more often partially right than wrong.
The presenting problem is usually real. What tends to be missing is an honest account of the conditions that produced it... the operating model decisions that were never made, the data foundations that are assumed to be adequate, the organisational appetite for change that has been tested in workshops rather than in working conversations about what the change will actually require. Those gaps are not visible from inside the organisation, because the internal team has adapted to them. They tend to surface only when someone with a genuinely different vantage point asks the questions that internal advocates and vendor representatives do not.
Testing assumptions well means creating the conditions for disconfirmation: actively looking for evidence that the diagnosis is wrong, not just confirmation that it is right. That is harder to do from inside than it sounds, and it is the specific kind of challenge that peer scrutiny from practitioners with no stake in the outcome is best placed to provide.
BPC's outside-in view at this stage comes from practitioners who have tested comparable diagnoses in comparable organisations. Tell us about your context and we can find the most relevant comparisons.
Timing: Thu 16 Jul · 15:00 BST · 60 minutes
Focus: Supply chain leaders who are earlier in their planning transformation journey — new in role, new to a capability area, or not yet clear on the specific problem they are trying to solve.
Format: Practitioner-led peer discussion facilitated by BestPractice.Club
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 a pattern doesn’t quite fit, that’s normal. They are distilled from many examples from varying contexts. Decisions rarely move in straight lines with teams often revisiting 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.