Hub 08 Operating Models

The three procurement org models, their decision-rights logic, and when each fits. For data centers, long-lead electrical categories demand central leverage and factory-slot control while site-level buying stays local — which is why hybrid-by-category dominates the field. Builds on: Hub 05 — what the function actually does.

Category management as a P&L discipline: defining categories, the category strategy process, and what a category manager owns end to end (strategy, sourcing, supplier relationship). The expert hiring bar: market knowledge, stakeholder influence, negotiation, and cost-driver fluency. Builds on: 08.10 (where category managers sit), 05.20 (cost-driver fluency).

How to build a DOA ladder: threshold tiers by role, current-state spend analysis to set them, and the governance traps (rubber-stamping, approval bottlenecks, maverick spend). The data center stakes: someone must be empowered to commit a multi-million-dollar transformer PO on a Friday without a two-week approval chain killing the factory slot. Builds on: 08.10 (the org), 05.10 (why commitment speed matters for LLE).

The RACI across the four functions procurement touches. The expert insight is the construction interface: procurement dates must live on the build schedule, not in a separate system, or long-lead equipment arrives after the crew has demobilized. Builds on: 08.10 (the structure), 03.50 (the construction schedule it must join).

The make-or-buy framework for the procurement function itself — necessity vs. opportunity arguments for insourcing, reusable scoring models, and the time-horizon effect (outsourcing wins short-term on labor cost; insourcing wins mid-to-long-term on control and equipment economics). The analytical core of any in-sourcing recommendation. Builds on: 08.10-08.40 (the function), 06.50 (the financial case for the in-source option).

Which roles to hire first when standing up a procurement function and why order matters — typically a category lead for the dominant spend, then contracts and commercial support, then expediting and analytics. Covers the role most orgs miss: the expeditor who lives between the factory, the freight forwarder, and the site. Builds on: 08.50 (the model determines the roles), 05.70 (the expeditor's world).

The procurement KPI stack — spend under management, procurement ROI, cost savings vs. cost avoidance discipline, cycle time, on-time delivery, maverick spend — and setting targets from baselines rather than aspirations. The expert move is measuring adoption alongside outcomes, since reported process change is not operational change. Builds on: 08.10-08.60 — measuring the designed function.

Key sources: Usetorg on procurement org design; Skill Dynamics on org structure; The Strategic Sourceror on delegation of authority; SNIC Solutions on procurement KPIs.