Pugh Matrix Decision Framework
Solution Selection Through CTQ-Driven Analysis
Section 3: Strategic Design - From Requirements to Solution
After competitive analysis (Porter's Five Forces) and organizational assessment (McKinsey 7S with SWOT), the challenge was to design a strategy that satisfies BOTH competitive requirements AND organizational constraints simultaneously.
This section shows how we extracted Critical-To-Quality (CTQ) requirements and used them to evaluate alternative solutions through a Pugh Matrix analysis.
Interactive Pugh Matrix Evaluation
Detailed scoring of three alternatives against Critical-To-Quality requirements from stakeholder voice and analytical validation
Combined Totals Across All CTQs
Vendor Platform
-31
REJECTED
Fails stakeholder requirements
Custom Big Bang
-22
REJECTED
Fails stakeholder requirements
Phased Internal Build
+38
SELECTED ✓
Only viable solution
Score Breakdown by Category:
Primary: Stakeholder
Vendor: -14 | Custom: -13 | Phased: +16
Supporting: Competitive
Vendor: -5 | Custom: +1 | Phased: +8
Supporting: Organizational
Vendor: -12 | Custom: -10 | Phased: +14
What stakeholders explicitly said they need
| CTQ Requirement | Vendor Platform | Custom Big Bang | Phased Internal Build |
|---|---|---|---|
| S1: Quarterly results + 5-year strategic optionality | -2 3-4 years to ROI violates quarterly results requirement | -2 18-24 month development + 6-12 deployment violates quarterly results | +2 Value from Month 1 (quarterly) + 18-month transformation (5-year optionality) |
| S2: Decisive investment + exit ability at any phase | -2 $2-5M upfront commitment, no exit optionality | -2 $3-7M total commitment, cannot stop mid-development | +2 Progressive investment with decision points at every horizon boundary |
| S3: Enterprise-wide intelligence + decentralized culture | -2 Centralized rollout requires mandates, violates decentralized culture | -2 Coordinated enterprise rollout impossible in decentralized structure | +2 Enterprise capabilities through self-initiated country-by-country adoption |
| S4: Incremental delivery (value at every phase) | -1 Value only after full deployment (3-4 years) | -2 No value until complete system deployed (24-36 months) | +2 Value delivered every phase, can stop at any phase with functioning capability |
| S5: Bounded risk (stop any phase, keep value) | -2 All-or-nothing investment, sunk cost if stopped | -2 Cannot stop mid-development without losing entire investment | +2 Progressive de-risking: each phase delivers standalone value |
| S6: Bottom-up adoption (teams discover value) | -2 Requires top-down mandates and standardized training | -2 Mandatory enterprise-wide rollout required for ROI | +2 Self-initiated adoption through peer demonstration and mission framing |
| S7: Customer choice (improved capability, no forced change) | -1 Workflow changes required to use platform capabilities | -1 Custom workflows may require client-facing changes | +2 Capability enhancement only, zero workflow disruption required |
| S8: No vendor dependency (platform agnostic) | -2 Complete vendor lock-in to platform and ecosystem | 0 Platform agnostic but requires external consultants initially | +2 Fully internal, platform-agnostic, no vendor dependencies |
| Primary: Stakeholder (S1-S8) Subtotal: | -14 | -13 | +16 |
CTQ Requirements Framework
Primary CTQs: Direct Stakeholder Requirements (S1-S8)
Stakeholders explicitly articulated their requirements through the Challenge page. These are non-negotiable constraints that any solution MUST satisfy:
| CTQ ID | Critical-To-Quality Requirement | Source (Challenge Page) | Stakeholder Group |
|---|---|---|---|
| S1 | Quarterly results + 5-year strategic optionality | Organizational Dilemma | Board (quarterly) + C-Suite (5-year); cannot sacrifice either |
| S2 | Decisive investment + exit ability at any phase | Organizational Dilemma | CFO (budget commitment) + Board (risk management) |
| S3 | Enterprise-wide intelligence + decentralized culture | Organizational Dilemma | C-Suite (unified capabilities) + Country Directors (autonomy) |
| S4 | Incremental delivery (value at every phase) | Key Requirements | All stakeholders: change-fatigued, need proof before continued investment |
| S5 | Bounded risk (stop any phase, keep value) | Key Requirements | CFO + Board: failed transformation precedent, protect investment |
| S6 | Bottom-up adoption (teams discover value) | Key Requirements | Country Directors + Staff: top-down mandates fail in this culture |
| S7 | Customer choice (improved capability, no forced change) | Key Requirements | Client-facing staff: preserve relationships, avoid workflow disruption |
| S8 | No vendor dependency (platform agnostic) | Key Requirements | CTO + C-Suite: avoid lock-in, preserve competitive flexibility |
Critical Note: These are what stakeholders said they need. Analyses validate WHY these requirements are critical and HOW to achieve them, but they don't replace stakeholder voice.
Supporting CTQs: Analysis-Derived Requirements
Competitive and organizational analyses explain WHY stakeholder requirements are critical and identify ADDITIONAL requirements needed for success:
Competitive CTQs (from Porter's Five Forces) - C1-C4
These requirements validate why stakeholder demands for internal build (S8), quick value (S4), and strategic optionality (S1) are competitively necessary:
| CTQ ID | Critical-To-Quality Requirement | Source Analysis | How It Supports Stakeholder CTQs |
|---|---|---|---|
| C1 | Proprietary capabilities (non-commoditizable) | Porter's: Threat of Substitutes | Validates S8 (no vendor dependency): vendor platforms commoditize the one defensible advantage |
| C2 | Dramatic efficiency gains (outperform lean competitors) | Porter's: Competitive Rivalry | Validates S1 (strategic optionality): must extract more value from knowledge scale advantage |
| C3 | Defensible differentiation (non-substitutable) | Porter's: Threat of New Entrants | Validates S8: need advantages competitors cannot purchase or replicate |
| C4 | Build with existing staff (not external AI talent) | Porter's: Supplier Power | Validates S5 (bounded risk): cannot risk $1.5-3.75M on inaccessible AI talent market |
Analysis Insight: Porter's Five Forces validates stakeholder requirement S8 (no vendor dependency) as competitively necessary, not just a preference. Vendor platforms would commoditize the only defensible competitive advantage.
Organizational CTQs (from McKinsey 7S + SWOT) - O1-O7
These requirements validate why stakeholder demands for decentralized adoption (S6), cultural fit (S3), and bounded investment (S2, S5) are organizationally necessary:
| CTQ ID | Critical-To-Quality Requirement | Source Analysis | How It Supports Stakeholder CTQs |
|---|---|---|---|
| O1 | Total investment <$1M | 7S: Strategy (SWOT Weakness) | Validates S2, S5 (decisive investment + bounded risk): severe budget constraints are absolute |
| O2 | Decentralized self-initiated adoption (no mandates) | 7S: Structure, Style, Shared Values | Validates S3, S6 (enterprise intelligence + decentralized culture, bottom-up adoption): mandates organizationally impossible |
| O3 | Quick value with zero training prerequisites | 7S: Staff, Systems | Validates S4 (incremental delivery): change-fatigued workforce cannot absorb training burden before seeing value |
| O4 | Four-language support from day one | 7S: Staff | Additional requirement: 90% non-native English speakers; English-only excludes majority and violates S6 (bottom-up adoption) |
| O5 | Leverage peer networks and mission framing | 7S: Style, Shared Values | Validates S6 (bottom-up adoption): peer validation more powerful than headquarters directives in this culture |
| O6 | Passive knowledge capture (no expert disruption) | 7S: Skills, Staff | Validates S7 (customer choice): experts won't document; disruption creates resistance and client risk |
| O7 | Respect strongly aligned cultural elements | 7S: All elements | Validates S3 (enterprise + decentralized): cannot change Style-Staff-Structure-Values alignment on transformation timeline |
Analysis Insight: McKinsey 7S validates that stakeholder requirements S3 (enterprise intelligence + decentralized culture) and S6 (bottom-up adoption) aren't preferences - they're organizational constraints. Mandates are impossible in this structure and culture.
CTQ Hierarchy: Primary vs. Supporting
Primary CTQs (S1-S8): Direct stakeholder requirements. Solutions that don't satisfy these fail stakeholder acceptance regardless of analytical merit.
Supporting CTQs (C1-C4, O1-O7): Analysis-derived requirements that:
- Explain WHY primary CTQs are necessary (not just preferences)
- Identify ADDITIONAL requirements for competitive/organizational success
- Provide measurable validation criteria
Critical Insight: Analyses validate stakeholder requirements and add depth, but stakeholder voice is primary. If stakeholders want something not reflected in analysis, we validate it through analysis or acknowledge it as a constraint to work within.
Alternative Solutions Evaluated
Alternative 1: Vendor Platform Approach
Purchase enterprise AI platform from major vendor (e.g., Salesforce Einstein, Microsoft Copilot, ServiceNow AI)
Alternative 2: Custom Big Bang Build
Build custom AI solution with external consultants, deploy enterprise-wide simultaneously
Alternative 3: Phased Internal Build (Our Approach)
Build proprietary AI internally with existing staff, deploy in progressive phases with self-initiated adoption
Why Phased Internal Build Was Selected
The Only Viable Solution
The Pugh Matrix evaluation revealed that Phased Internal Build was not just the best option - it was the only viable option that could satisfy stakeholder requirements while meeting competitive and organizational constraints.
Vendor Platform Approach - Fatal Flaws:
- •Stakeholder rejection: Violates S1 (quarterly results), S2 (exit ability), S3 (decentralized culture), S5 (bounded risk), S6 (bottom-up adoption), S8 (no vendor dependency)
- •Competitive failure: Commoditizes the one defensible advantage (institutional knowledge)
- •Organizational impossibility: Requires $2-5M (exceeds budget 20-50x), mandates (culturally impossible), training prerequisites (violates change fatigue), English-only (excludes 90% of workforce)
Custom Big Bang Approach - Fatal Flaws:
- •Stakeholder rejection: Violates S1 (quarterly results), S2 (exit ability), S3 (decentralized culture), S4 (incremental delivery), S5 (bounded risk), S6 (bottom-up adoption)
- •Competitive failure: Requires AI specialist recruitment (talent market inaccessible; sector cannot compete with private sector compensation)
- •Organizational impossibility: Requires $3-7M investment, centralized coordination (structure prevents), mandates (culture rejects), simultaneous rollout (operationally infeasible across 115 countries)
Phased Internal Build - Why It Works:
Satisfies ALL primary stakeholder CTQs (S1-S8):
- ✓ Quarterly value + 5-year optionality (S1)
- ✓ Decisive investment + exit ability at every phase (S2)
- ✓ Enterprise intelligence + decentralized self-initiated adoption (S3)
- ✓ Incremental delivery with value every phase (S4)
- ✓ Bounded risk with exit optionality (S5)
- ✓ Bottom-up self-initiated adoption through peer demonstration (S6)
- ✓ Customer choice with no forced workflow changes (S7)
- ✓ No vendor dependency, platform agnostic (S8)
Validated by competitive analysis (C1-C4):
- ✓ Proprietary on unique 115-country knowledge
- ✓ Dramatic efficiency through AI-speed knowledge access
- ✓ Defensible differentiation competitors cannot replicate
- ✓ Built with existing staff progressively upskilled
Validated by organizational analysis (O1-O7):
- ✓ $163.1K Direct Investment ($11,100 infrastructure) with bounded risk
- ✓ Self-initiated country-by-country adoption respecting consensus culture
- ✓ Immediate value with embedded learning, no training prerequisites
- ✓ Four languages from day one
- ✓ Peer demonstration and mission framing as adoption mechanism
- ✓ Passive knowledge capture from relational networks without expert disruption
- ✓ Works with strongly aligned cultural elements rather than requiring organizational change
Key Strategic Insights
CTQ-Driven Design Process
The Critical-To-Quality approach ensured rigorous requirements extraction and validation:
- Stakeholders First: Start with what stakeholders explicitly said they need (S1-S8)
- Analytical Validation: Use Porter's and 7S to validate WHY stakeholder needs are real and identify ADDITIONAL requirements (C1-C4, O1-O7)
- Pugh Matrix Evaluation: Score alternatives against all CTQs to find viable solutions
- Selection: Choose solution that satisfies stakeholder voice AND passes analytical validation
Why Alternatives Failed
Both Vendor Platform and Custom Big Bang failed because:
- •Designed for different organizational models (centralized control, mandate authority) than what 7S revealed
- •Assumed different competitive contexts (standardization, external expertise) than what Porter's showed
- •Force organizations to choose which stakeholder groups to disappoint rather than satisfying all simultaneously
The Power of Stakeholder-First CTQ Methodology
Without listening to stakeholder voice first:
- •Might have pursued vendor platform (standard practice, compelling sales pitch)
- •Would have violated what stakeholders explicitly said they need
- •$2-5M investment lost, trust further damaged, transformation failed
With stakeholder-first CTQ methodology:
- •Stakeholder requirements treated as primary constraints (S1-S8)
- •Analyses validate why those requirements are real (C1-C4, O1-O7)
- •Pugh Matrix reveals Phased Internal Build as only viable solution
- •$163.1K Direct Investment, all stakeholder needs satisfied, transformation successful