Questions we hear most before an engagement starts

Not necessarily. In many cases the issue isn't the formal reporting structure but the lack of agreement on who owns which decision. Sometimes that's solved by clarifying RACI, without touching the org chart at all.

Yes, though the scope is smaller. Even a single factory with multiple production lines can have ambiguity between centralized decisions (shared raw material procurement) and decentralized ones (per-line scheduling).

Both. The written output (operating model map and RACI) is the foundation, but the implementation stage includes real changes to how decision meetings and reporting actually happen — not just a file sitting on the CEO's desk.

Structural changes typically show results later than operational ones (like an MRP tool) — it usually takes two to three decision cycles (quarterly or monthly) before the real effect of the new alignment shows up in performance.

No. A reliable MRP engine can be built in Excel, as long as the BOM explosion logic and net requirement calculation are implemented correctly. That said, as SKU count grows, migrating to a system like SAP becomes advisable.

Typically one decision-making representative (not just a status reporter) from sales, production, procurement, and finance, plus the cycle facilitator. Meetings larger than 8-10 people usually reduce decision-making effectiveness.

Full cleanup before starting usually delays the project by months. A better approach is starting the pilot on a product category with cleaner data, and cleaning the rest of the data in parallel during rollout.

For each department representative, typically one to two working days per month to prepare inputs and attend the different stage meetings of the cycle — not just the final executive session.

When no real alternative exists, negotiation leverage shifts from price to other areas: long-term volume commitment, payment terms, or joint product development. Part of the negotiation strategy is precisely identifying those alternative levers.

For strategic suppliers, typically quarterly; for low-risk, low-volume suppliers, a six-month or annual cycle is sufficient.

No. Fewer suppliers can increase bargaining power, but it also raises concentration risk. The right call depends on how critical the commodity category is and how many real alternatives exist.

Quick wins (order consolidation, contract renewal with better terms) usually show up within one or two purchasing cycles; more structural effects (diversification, supplier development) take several quarters.

Items with no history are typically treated as Class Z (irregular) with a more conservative safety stock policy until enough data accumulates for more accurate classification — usually after three to six sales periods.

At minimum, 12 months of SKU-level sales or consumption history, each item's supply lead time, and approximate ordering and holding costs. More precise data produces more precise results, but incomplete data doesn't block getting started.

This depends entirely on the current demand pattern's variability and the quality of the existing policy, and can't be quantified before analyzing the organization's real data; what can be guaranteed is a simultaneous reduction in both stockouts and excess through a policy fitted to each SKU.

For industries with seasonal demand, a quarterly review is recommended. For more stable industries, a six-month or annual review is usually enough, unless a major shift occurs in the market or product portfolio.

No. The usual approach starts with the network's most expensive or least productive node, then gradually extends the design logic to the rest of the network once initial results stabilize.

The outsourcing decision is part of network design, not separate from it — because transport cost and flexibility directly affect how many warehouses are needed and where.

Yes. Even in small networks, a wrong call on a warehouse's location or scale can have a disproportionate effect on total cost; structured analysis at this scale is also faster and cheaper to run.

Based on that market segment's actual value (sales volume, margin, customer sensitivity to delivery time) — not a single standard applied across the whole network.

Yes, though the sequencing logic differs — instead of product similarity, priority is usually set by committed delivery date and material availability.

At least three months of recent daily production data, recorded downtime (planned and unplanned), and standard changeover time between each product pair, if available.

A large share of the reduction comes simply from resequencing production based on product similarity and requires no investment. Physical improvements (like SMED) are an optional next step.

The order prioritization rule is designed for exactly this and agreed with sales — so resequencing by product similarity doesn't unilaterally disrupt key customers' delivery dates.

That's exactly where it matters most — when there's no alternative, a relationship that doesn't end in legal conflict is the only way to ensure supply continuity through a crisis.

Yes, for legal finalization. Our work defines the operational logic of the clauses (what conditions need covering and why); final legal drafting should go through the organization's legal counsel.

Typically between 5 and 15 suppliers, depending on organization size — more than that dilutes the management time needed for genuinely strategic engagement.

The constructive-dialogue framework is specifically tuned for this kind of interaction — with more emphasis on written documentation and clarifying assumptions, precisely because cultural or language differences can amplify misunderstanding.

Not necessarily. In many cases, partial diversification (a backup supplier for critical materials) or simply clarifying contractual terms for crisis situations is enough.

A multi-hour session with the management team where a hypothetical disruption scenario (a key supplier suddenly stopping, for instance) is put on the table, and the team has to decide in real time — with no real consequence, but real time pressure.

Typically the three to five highest-probability, highest-impact scenarios — not an exhaustive list of every possibility. A response plan for countless scenarios ends up covering none of them well.

Not always. Some resilience measures (clarifying contract clauses, defining warning indicators) carry no direct cost. Real cost usually shows up in physical measures like emergency inventory buffers or geographic diversification, which need to be weighed against the cost of an actual disruption.

By starting small on a domain with reliable data, and showing the dashboard's match with a reality the team already recognizes — trust is built through repeated correct experience, not a one-time presentation.

No specialized data team is needed to get started. The initial architecture and dashboard design are done by us; training the internal team to maintain and extend it is part of the capability transfer stage.

Yes, but only once the underlying data is clean and reliable. More advanced models (like machine-learning demand forecasting) built on dirty data just repeat mistakes faster.

To start, one named data owner is enough — someone who understands both the business logic and can edit the dashboard. As scope grows, this role can expand into a small team.

If done without differentiation, yes. That's why this project uses ABC-XYZ classification to target the reduction precisely at low-risk, dead-stock items, not critical, high-demand ones.

If it's part of a balanced negotiation (not a one-sided demand), no. Better payment terms are usually negotiated in exchange for a long-term volume commitment or multi-year contract — something valuable to both sides.

A lot — this project is inherently cross-functional. Without finance's active participation in setting goals and reviewing the shared dashboard, results don't stay durable.

Inventory-related changes usually show up within one or two sales cycles; supplier payment-term changes depend on contract renewal timing and can move more slowly.

Not directly. The focus is on developing the existing team. If diagnosis shows a gap that genuinely requires hiring, that's delivered as a separate recommendation, not part of project execution.

Through structured interviews conducted alongside real work (not abstract Q&A), and capturing decision logic against real scenarios that person has actually faced before.

No. Content is segmented by each role's designed career path — junior specialists focus on foundational technical skills, senior ones on cross-functional coordination and strategic decision-making.

Through a visible reduction in key-person dependency (the team's ability to keep functioning without one specific person) and hands-on assessment of trained skills against real issues, not just a test score.