Procurement Strategy and KPI Handbook

Executive summary

Procurement strategy is a set of deliberate choices about where procurement will focus, how it will work with stakeholders and suppliers, which risks it will accept or reduce, and how value will be measured. A list of savings projects is not a complete strategy. A dashboard of activity is not a performance system.

This handbook connects enterprise context, spend evidence, category strategy, stakeholder alignment, objectives, measures, governance, and continuous improvement. It uses the Kraljic portfolio concept as one analytical lens, not as a substitute for judgment. It also defines a KPI discipline that makes the population, formula, source, owner, target, and action explicit.

Table of contents

1. Build a strategy from enterprise context
2. Establish a trusted spend view
3. Segment categories and supply risk
4. Write category strategies
5. Align stakeholders and decision rights
6. Convert objectives into KPIs
7. Define the KPI dictionary
8. Run governance and performance reviews
9. Improve without gaming the measures

1. Build a strategy from enterprise context

Start with the decisions the enterprise needs procurement to support.

Context questions

• Which growth, margin, continuity, innovation, compliance, sustainability, cash, or operating priorities matter most?
• Where is demand changing?
• Which plants, business units, programs, or customer commitments are exposed?
• Which categories or suppliers can materially affect those priorities?
• Which decisions are slow, inconsistent, or difficult to evidence?
• Which technology or data changes are already planned?
• What capacity does procurement actually have?

Translate the answers into a small number of strategic choices. A choice states what will receive attention and what will not.

Northstar Industrial Systems example choices

1. Protect plant continuity in critical maintenance and production-support categories.
2. Increase governed competition and evidence for addressable indirect spend.
3. Establish one supplier qualification and risk-review model for critical suppliers.
4. Connect procurement workflow evidence to ERP execution and reconciliation.
5. Use human-governed assistance for selected analysis and drafting tasks while retaining accountable approvals.

Each choice needs an executive rationale, owner, time horizon, affected categories, risks, and measures.

2. Establish a trusted spend view

Spend analysis should answer a business question, not merely create a chart.

Minimum data model

• supplier and supplier parent;
• category and subcategory;
• business unit and location;
• cost center and account;
• request, purchase order, receipt, and invoice identifiers where available;
• contract reference;
• amount, currency, and date;
• buyer or owning function;
• data source and refresh date;
• classification confidence or exception.

Data-quality controls

Track:

• percentage of in-scope spend loaded;
• supplier normalization completeness;
• category classification completeness;
• duplicate or ambiguous supplier records;
• unmatched purchase orders and invoices;
• stale master data;
• records with unknown business ownership;
• time from source update to usable analysis.

Do not call spend visible merely because it appears in a system. Useful visibility requires coverage, consistent classification, ownership, and enough detail to support a decision.

Analytical views

• category concentration;
• supplier concentration;
• tail spend;
• maverick or off-policy spend;
• contract coverage;
• purchase-order coverage;
• budget versus actual;
• sourcing coverage;
• savings pipeline and realized savings;
• business-unit demand;
• critical-supplier exposure.

3. Segment categories and supply risk

The Kraljic portfolio concept compares business impact with supply risk. Use it to structure questions, then add operational evidence.

Four portfolio postures

• Routine: simplify the buying path, reduce transaction effort, and govern exceptions.
• Leverage: aggregate demand, create competition, and manage commercial performance.
• Bottleneck: secure continuity, alternatives, inventory or service buffers, and escalation.
• Strategic: build executive relationships, joint planning, performance governance, innovation, and risk response.

Category evidence worksheet

For each category, record:

• annual addressable spend and demand pattern;
• business criticality;
• supplier concentration and alternatives;
• switching time and qualification burden;
• market and capacity conditions;
• contract and pricing structure;
• operational and quality risk;
• data, cyber, legal, sustainability, and compliance factors;
• stakeholder priorities;
• current sourcing and supplier strategy;
• decision horizon.

Review the position when evidence changes; do not freeze a category in one quadrant indefinitely.

4. Write category strategies

A category strategy is a decision document.

Category strategy structure

1. Scope: categories, business units, geography, demand, and exclusions.
2. Enterprise need: outcomes the category must support.
3. Baseline: spend, suppliers, contracts, demand, performance, risk, and data quality.
4. Market view: supply structure, capacity, alternatives, cost drivers, and constraints.
5. Stakeholders: decision owners, users, technical reviewers, and affected operations.
6. Strategic choices: demand, sourcing, supplier, contract, risk, process, and data actions.
7. Initiatives: owner, decision, dependency, timing, and evidence.
8. Benefits and risks: value hypotheses, investment, uncertainty, and controls.
9. KPIs: measures that show whether choices are working.
10. Governance: review cadence, escalation, and refresh triggers.

Initiative test

Every initiative should answer:

• What decision or behavior changes?
• Who owns it?
• What evidence supports it?
• What dependency could block it?
• How will progress and outcome be distinguished?
• What would cause the initiative to stop or change?

5. Align stakeholders and decision rights

Stakeholder alignment is not consensus on every tactic. It is clarity about goals, trade-offs, authority, and escalation.

Alignment workshop

Ask each stakeholder to state:

• the outcome they need;
• the risk they are accountable for;
• the evidence they trust;
• the constraint they cannot ignore;
• the decision they own;
• the trade-off they are willing to make;
• the measure that would change their view.

Document disagreements. A strategy is stronger when it records the trade-off rather than smoothing it into vague language.

Governance roles

• executive sponsor: enterprise priority and unresolved trade-offs;
• category owner: strategy and supplier-market action;
• procurement operations: process and data discipline;
• finance: baseline, savings validation, budget, and value;
• operations: service, quality, continuity, and receipt evidence;
• IT/security: architecture, supplier technology risk, and data controls;
• compliance/legal: regulated obligations and evidence;
• supplier manager: qualification, risk, performance, and remediation.

6. Convert objectives into KPIs

Use a strategy cascade:

Enterprise priority -> procurement objective -> operating behavior -> KPI -> threshold -> action.

Example

• Enterprise priority: protect plant continuity.
• Procurement objective: reduce unresolved critical-supplier risk.
• Operating behavior: complete scheduled reviews and close actions by severity.
• KPI: critical-supplier actions past due.
• Threshold: any critical action past due requires named executive review.
• Action: assign remediation, approve acceptance, develop alternative, or adjust the plan.

Avoid selecting KPIs because the data is easy to obtain. Select them because they answer a decision question.

7. Define the KPI dictionary

Every KPI needs:

• ID and name;
• business question;
• formula;
• unit;
• population and grain;
• inclusion and exclusion;
• system source;
• refresh;
• data owner;
• process owner;
• target and threshold;
• segmentation;
• action when outside threshold;
• known limitation;
• review date.

Core KPI examples

Use medians for flow, rates for population behavior, counts for workload, currency for validated value, and distributions where a single average hides important variation.

8. Run governance and performance reviews

Monthly operating review

Focus on:

• demand and workload;
• cycle and queue variation;
• exceptions and root causes;
• data quality;
• supplier and category actions;
• realized versus planned value;
• integration and system issues;
• decisions required.

Quarterly strategy review

Focus on:

• enterprise-priority changes;
• category and market changes;
• supplier concentration and critical risks;
• initiative benefits and investment;
• KPI relevance and gaming risk;
• policy and operating-model changes;
• controlled backlog decisions.

Decision log

Record decision, date, owner, evidence reviewed, alternatives, action, due date, and next review. A KPI review without a decision log becomes reporting theater.

9. Improve without gaming the measures

Metrics can drive unintended behavior. Watch for:

• faster approvals achieved by removing necessary review;
• higher sourcing coverage achieved by including non-comparable events;
• lower exception rates achieved by reclassifying exceptions;
• savings claimed without an approved baseline;
• spend visibility inflated by low-confidence classification;
• supplier-review completion without meaningful evidence;
• on-time metrics changed by moving due dates.

Use counter-metrics and sample review. For example, pair approval speed with return rate and control exceptions; pair sourcing coverage with evaluation quality; pair onboarding cycle with post-approval corrections.

Continuous-improvement loop

1. Observe the measure and distribution.
2. Verify data and definition.
3. Identify root cause.
4. Decide action and owner.
5. Implement controlled change.
6. Review effect and unintended consequences.
7. Update the strategy, process, or KPI definition when warranted.

Workbook elements

The editable workbook should contain enterprise context, spend/data-quality baseline, category portfolio, category strategy one-pager, stakeholder alignment, initiative register, KPI dictionary, monthly review, quarterly review, and decision log. Include fictional Northstar Industrial Systems examples and blank usable rows.