nahisaho Framework Library (PWC)
6 PwC-specific framework definitions.
Use This Skill When
- Looking up a PWC-specific framework definition.
- Comparing PWC frameworks for a business question.
- Selecting the best framework from PWC candidates.
Framework Index
| Framework | Primary Trigger | Category |
|---|---|---|
| Fit for Growth | fit for growth | cost |
| Strategy& (Capability-Driven) | strategy | strategy |
| BXT (Business Experience Technology) | BXT | transformation |
| TIMM (Total Impact) | TIMM | impact |
| Deal Value Creation | M&A | deal |
| Risk & Regulation | risk | risk |
Recommended Workflow Patterns
Strategy & Cost
Strategy& (Capability-Driven) → Fit for Growth
Digital Transformation
BXT (Business Experience Technology) → Strategy& (Capability-Driven) → Fit for Growth
M&A / Deal
Deal Value Creation → Fit for Growth → Risk & Regulation
ESG / Impact
TIMM (Total Impact) → Strategy& (Capability-Driven) → Risk & Regulation
Selection Principles
- Choose the PWC framework that directly answers the core question.
- Prefer simpler frameworks when data is limited.
- Maximum 3 frameworks per analysis.
- PWC frameworks take priority over generic frameworks when applicable.
- Read detailed definitions in
references/pwc-frameworks.mdwhen applying a specific framework.
Quality Gates
- Framework definition is accurate and complete.
- Selection rationale matches the business objective.
- Recommended frameworks do not exceed 3.
- Detailed reference is conditionally referenced (not loaded unconditionally).
If any gate fails: identify the specific failing check, fix the issue, and re-validate before proceeding.
Gotchas
- PWCフレームワークは「考える道具」であって「答え」ではない。フレームワークを埋めることが目的になってはならない
- 汎用フレームワーク（SWOT, 3C等）とPWCフレームワークは併用可能だが、PWC固有の視点を主軸にすること
- フレームワーク間の推奨ワークフロー順序を無視して適用すると、前提となるデータが不足する
Validation Loop
- フレームワーク情報を提供
- チェック: 定義が正確か、選択理由が目的と合致しているか
- 不合格なら修正