E8 — Firman — S&OP & Allocation — Executive Brief

Meeting: next week (date TBC) · Prepared: 2026-07-09

Mission Use the first meeting with Firman to understand where allocation authority really sits, why S&OP is structurally outside the commercial line, and whether the observed weakness is primarily a Firman-team problem or a line-ownership problem disguised as one.

Win Condition - [ ] A credible answer to where customer allocation decisions are actually made when demand exceeds supply. - [ ] A clearer read on whether Integrated Reconciliation (IR) functions as the real decision forum in practice, not just on paper. - [ ] A grounded view on whether S&OP is an early-win process area you can shape, or a politically fenced zone you should influence indirectly.

Working Hypothesis The real issue is less "Firman's team is weak" and more that S&OP was designed as a facilitation layer without formal line authority, while the line chairs may not be showing up consistently enough to make the system work as intended. Test: "When demand and supply genuinely conflict, who leaves the room owning the decision, and how often is that the formal chair versus Planning by default?"

Critical Unknowns - Does Firman see S&OP as a governance mechanism, an operating-control tower, or a transformation project still trying to gain legitimacy? - Is allocation under constraint genuinely decided in IR, or through informal escalation outside the formal cadence? - Is the manual forecasting setup a tolerated limitation, or a known gap with no real sponsor? - Why are toll/supplier review and CAPEX escalation explicitly excluded for LR/PGR: deliberate scope design, capability gap, or operating neglect?

Priority Questions 1. "Help me understand the history first: why does S&OP sit in Transformation rather than in the commercial or operating line?" 2. "When demand exceeds supply, where is the real allocation decision made in practice, and who has the pen?" 3. "The playbook says IR is the escalation and reconciliation forum, chaired by the Head of Business Segment. Does it actually work that way in real life?" 4. "From where you sit, where does the real friction come from today: the process design itself, the data and tooling, or whether the formal chair-led model is fully landing in practice?" 5. "The LR read shows 80% S&OP attainment, 69% demand forecast accuracy, and a shrinking opportunistic pipeline. What do you see as the root cause?" 6. "Why are toll/supplier performance review and CAPEX escalation not performed for LR/PGR? Was that an intentional simplification or just never revisited?" 7. "Given Demand Review is still manual SAP + Excel with no statistical forecasting, is that a known accepted constraint or something on a real improvement path?"

Decision Watch - If Firman frames allocation as formally owned elsewhere but informally absorbed by S&OP, that is a major decision-rights finding, not just a process observation. - If he frames the problem mainly as tooling and resourcing, test whether that explanation survives the facilitator-versus-chair split in the playbook. - If he asks what you mean by a possible gap versus the playbook, anchor it carefully: on paper IR is a chair-led reconciliation and escalation forum, while the LR evidence shows weak attainment, weak forecast accuracy, manual forecasting, and some playbook steps not being performed for LR/PGR. Treat that as a reason to ask, not as proof that governance is failing. - If he signals that the process is politically sensitive or outside your lane, treat that as a stakeholder-mapping output, not a reason to force an early-win agenda.

Political Signals - Whether Firman speaks like a process owner with influence, or a facilitator carrying accountability without authority. - Whether he names specific line leaders as engaged decision-makers, or describes escalation in abstract process language. - Whether he treats Commercial as a partner, a client, or a source of non-compliance. - Whether the Transformation Office placement sounds intentional and strategic, or historical and unresolved.

Red Lines - Do not go in as if you are auditing Firman's function. - Do not offer fixes in the first meeting; earn the right to help before suggesting changes. - Do not assume low S&OP attainment automatically means Planning failure; the evidence already suggests a broader structural issue. - Do not turn the meeting into a debate about where S&OP should report.

Immediate Follow-up - 30 min: capture what moved from [OPEN] to [HYP] or [FACT] on allocation authority, IR reality, and S&OP ownership. - Same day: update Weekly_Loop.md and the Planning / Frontier workbooks. - Next step: decide whether the implication is "support Firman informally," "escalate decision-right clarity with Shashi," or "stay diagnostic until mandate and authority are firmer."

AI Working Notes

The meeting matters because S&OP is not just another enabling process. It is the point where customer promise meets physical reality. For your role, that makes it one of the few cross-functional seams that can directly validate or invalidate the charter gap: if no one clearly owns allocation under constraint, strategic customer leadership is structurally weak no matter how good the front-end account work becomes.

The most important judgment going in is not to accept the presenting problem too quickly. The current narrative in the system is that S&OP has weak buy-in and is under-resourced. That may be true, but the new evidence from the playbook changes the interpretation. Head of S&OP is formally a facilitator across all five review layers and chairs none of them. That means a weak process can reflect weak line-chair ownership as much as weak planning capability. The meeting should therefore test whether Firman's team is failing to run the process, or whether the business has designed a process whose decision owners do not consistently own the decision.

The second live issue is allocation authority. The formal design points to IR as the closest thing to an allocation forum, chaired by the Head of Business Segment. But the Weekly Loop is right to keep this open. If the real decision still happens informally, or if Planning effectively decides because others do not, then the organisation has a governance gap at exactly the point where key-account commitments are won or lost. That is strategically important for you because it tells you whether customer performance is mainly a commercial-execution problem or a deeper enterprise decision-rights problem.

The third theme is maturity. The LR read already shows low forecast accuracy, over-forecasting, order rescheduling, and a narrowing opportunistic pipeline. The playbook adds that statistical forecasting is not implemented and Demand Review is still manual SAP plus Excel. So one possible conclusion is simply that the process is immature and under-tooled. But even that has two versions: immature because nobody has sponsored improvement, or immature because the organisation does not truly rely on S&OP to decide. Firman is one of the few people likely able to distinguish between those stories.

The best posture in the room is curious, not prosecutorial. Firman sits outside your line, your scope is not fully set, and this is a first meeting. If he experiences you as someone trying to understand the system rather than place blame, he is more likely to reveal where the real friction is. That matters politically as much as analytically, because if S&OP turns out to be an early-win area, you will need his trust before you need his process map.

If Firman asks what specifically prompted the question, the clean answer is the comparison between designed governance and observed operating evidence. The playbook says IR is the formal reconciliation and escalation forum, chaired by the Head of Business Segment, with Head of S&OP facilitating rather than chairing. The LR datapoints do not prove that model is breaking, but they do show enough strain to justify the question: 80% S&OP attainment, 69% demand forecast accuracy, manual SAP-plus-Excel forecasting, a shrinking opportunistic pipeline, and some playbook steps explicitly not performed for LR/PGR. The safest line is: "I'm not assuming a governance failure; I'm trying to understand whether the friction is mainly process maturity, tooling, or whether the formal model is landing unevenly in practice."