Productivity Slowdown Diagnosis Framework
プロダクティビティ・スローダウン・ダイアグノーシス・フレームワーク
Productivity Slowdown Diagnosis Framework guides teams to evaluate diagnosing drivers of productivity slowdowns using TFP growth, capital deepening, R and D intensity and investment rate, diffusion lag, skills availability, keeping short-term cost versus long-term growth trade offs visible and repeatable. It creates a concise decision record.
What it means
Productivity Slowdown Diagnosis Framework describes a practical concept that helps teams frame a situation, compare options, and decide the next operating move. The value is not the label itself; it is the discipline of defining scope, evidence, owner, and decision consequence before the team acts.
How to design it
Productivity Slowdown Diagnosis Framework should be turned into an explicit decision sequence before it is used. Frame | Write the decision, owner, and time horizon | Prevents the framework from becoming a discussion label Compare | List options, constraints, evidence, and trade-offs | Makes the choice testable Commit | Record the selected path, review date, and reversal signal | Keeps execution accountable
- Frame | Write the decision, owner, and time horizon | Prevents the framework from becoming a discussion label
- Compare | List options, constraints, evidence, and trade-offs | Makes the choice testable
- Commit | Record the selected path, review date, and reversal signal | Keeps execution accountable
- Confirm scope and horizon; lock metric definitions for TFP growth, capital deepening, R and D intensity so comparisons are consistent.
- Collect and normalize investment rate, diffusion lag, skills availability; document ownership and refresh cadence.
- Run scenarios to see when short-term cost versus long-term growth flips; record thresholds and triggers.
- Select the preferred option, list constraints and approvals, and document the decision logic.
- Define monitoring cadence, owners, and review triggers to keep the decision current.
How to run it
Productivity Slowdown Diagnosis Framework works best when the review cadence is fixed before execution starts. Initial review | Confirm inputs and assumptions before the first decision Operating review | Recheck evidence and execution drift on a fixed rhythm Post-review | Decide whether to continue, adapt, or stop based on observed signals
- Initial review | Confirm inputs and assumptions before the first decision
- Operating review | Recheck evidence and execution drift on a fixed rhythm
- Post-review | Decide whether to continue, adapt, or stop based on observed signals
When it helps
Apply this when leaders must decide despite uncertainty in investment rate, diffusion lag, skills availability. It sets shared definitions for TFP growth, capital deepening, R and D intensity and clarifies how short-term cost versus long-term growth priorities will be weighted.
- Priority | Clarifies what matters now | Prevents scattered execution
- Ownership | Makes the responsible team explicit | Reduces handoff ambiguity
- Evidence | Connects the concept to observable facts | Keeps decisions from becoming opinion-driven
When not to use it
Do not use Productivity Slowdown Diagnosis Framework when the decision context is too unstable or too shallow. No owner | The decision owner is unclear | The framework will not change execution No evidence | Inputs are guesses only | The output will look precise but remain fragile No choice | The team is not willing to change action | The framework becomes documentation theater
- No owner | The decision owner is unclear | The framework will not change execution
- No evidence | Inputs are guesses only | The output will look precise but remain fragile
- No choice | The team is not willing to change action | The framework becomes documentation theater
How to use it
Confirm scope and horizon; lock metric definitions for TFP growth, capital deepening, R and D intensity so comparisons are consistent. Collect and normalize investment rate, diffusion lag, skills availability; document ownership and refresh cadence. Run scenarios to see when short-term cost versus long-term growth flips; record thresholds and triggers. Select the preferred option, list constraints and approvals, and document the decision logic. Define monitoring cadence, owners, and review triggers to keep the decision current. Template: Objective; Scope and horizon; Success metrics (TFP growth, capital deepening, R and D intensity); Key assumptions (investment rate, diffusion lag, skills availability); Options A/B/C; Scenario ranges; Trade off summary (short-term cost versus long-term growth); Risks and mitigations; Decision criteria; Recommendation; Owner and timeline; Review triggers. Use Productivity Slowdown Diagnosis Framework with a clear context and decision owner. Define the scope before comparing alternatives. Separate facts, assumptions, and open questions. Tie the concept to a decision, not only to a vocabulary explanation. Review the definition when the customer, market, or operating context changes.
- Confirm scope and horizon; lock metric definitions for TFP growth, capital deepening, R and D intensity so comparisons are consistent.
- Collect and normalize investment rate, diffusion lag, skills availability; document ownership and refresh cadence.
- Run scenarios to see when short-term cost versus long-term growth flips; record thresholds and triggers.
- Select the preferred option, list constraints and approvals, and document the decision logic.
- Define monitoring cadence, owners, and review triggers to keep the decision current.
- Define the scope before comparing alternatives.
- Separate facts, assumptions, and open questions.
- Tie the concept to a decision, not only to a vocabulary explanation.
- Review the definition when the customer, market, or operating context changes.
Decision cautions
Use Productivity Slowdown Diagnosis Framework as a decision aid, not as a substitute for judgment. Do not hide weak evidence behind a clean framework. Do not compare options with inconsistent assumptions. Do not keep using the framework after the market, customer, or operating constraint changes.
- Do not hide weak evidence behind a clean framework.
- Do not compare options with inconsistent assumptions.
- Do not keep using the framework after the market, customer, or operating constraint changes.
Decision checklist
Decision: Select Option B. Validate TFP growth, capital deepening, R and D intensity early, revisit if investment rate, diffusion lag, skills availability change materially, and document stop conditions. Rationale: Option B balances short-term cost versus long-term growth and allows learning before full commitment. It protects the organization from misreading TFP growth, capital deepening, R and D intensity when investment rate, diffusion lag, skills availability are volatile. Next: Assign owners, finalize baselines for TFP growth, capital deepening, R and D intensity, and record investment rate, diffusion lag, skills availability with update rules. Schedule the first review and define escalation triggers.
- Option A: Maintain the current approach to minimize disruption while accepting limited improvement.
- Option B: Pilot changes in stages, validate against metrics, and scale only after thresholds are met.
- Option C: Redesign the approach end to end to pursue larger gains with higher execution risk.
- Poor data quality can obscure shifts in TFP growth, capital deepening, R and D intensity and delay corrective action.
- Slow execution can deepen the downside of short-term cost versus long-term growth and reduce credibility in governance reviews.
Example
A team discussing Productivity Slowdown Diagnosis Framework first writes the decision it needs to make, the evidence it has, and the trade-off it is willing to accept. After that, the team compares options and records why one path is better for the current quarter. This makes the term useful in planning, review, and handoff conversations.
Compare with
Compare Productivity Slowdown Diagnosis Framework with adjacent concepts before deciding. Productivity Slowdown Diagnosis Framework | Current concept | Use when the team needs the primary decision lens Adjacent metric or framework | Supporting lens | Use when the team needs evidence or process detail General vocabulary | Broad explanation | Use only for orientation, not final decision-making
| Metric | Difference | Why read together |
|---|---|---|
| Productivity Slowdown Diagnosis Framework | Current concept | Use when the team needs the primary decision lens |
| Adjacent metric or framework | Supporting lens | Use when the team needs evidence or process detail |
| General vocabulary | Broad explanation | Use only for orientation, not final decision-making |
Common mistakes
- Misconception | It is only a dictionary term | In practice it should change a decision or operating behavior
- Misconception | Everyone means the same thing | Teams should write the scope and assumptions
- Misconception | It is always positive | The term can reveal constraints, risks, or reasons not to act
- Misconception: assuming TFP growth, capital deepening, R and D intensity alone prove success without validating investment rate, diffusion lag, skills availability leads to false confidence.
- Treating short-term cost versus long-term growth as fixed ignores context shifts and causes later reversals.
- If investment rate, diffusion lag, skills availability are stale or unaudited, the decision will fail governance checks.
Frequently asked questions
When should I use Productivity Slowdown Diagnosis Framework?
Use it when the team needs to decide scope, priority, owner, or trade-off, not when it only needs a short definition.
What makes Productivity Slowdown Diagnosis Framework useful in practice?
It becomes useful when it is tied to evidence, a decision owner, and a concrete next operating choice.
What should I avoid?
Avoid using the term as a label without clarifying assumptions, boundaries, and how success will be judged.