{
  "schema_version": "core-reviewed-term-ai-handoff-v1",
  "version": "core-reviewed-term-ai-handoff-v1",
  "contract_status": "preview",
  "distribution": "per_term_read_only_ai_handoff",
  "no_write_operations": true,
  "canonical": {
    "url": "https://core.yogoq.com/en-US/core/business-framework-0084",
    "slug": "business-framework-0084",
    "locale": "en-US"
  },
  "summary": {
    "schema_version": "core-reviewed-term-summary-v1",
    "term_id": "b9af64c0-fb58-52e1-8895-d09c5a0e727a",
    "canonical_slug": "business-framework-0084",
    "canonical_url": "https://core.yogoq.com/en-US/core/business-framework-0084",
    "locale": "en-US",
    "display_name": "Change Readiness Deep-Dive Checklist",
    "english_name": null,
    "abbreviation": null,
    "short_definition": "Change Readiness Assessment Framework guides assessing organizational readiness for change by structuring readiness score, stakeholder alignment, and change fatigue index and making the trade-off between speed of change…",
    "quality": "reviewed",
    "publication_status": "published_reviewed",
    "version": "core-reviewed-term-summary-v1",
    "last_reviewed_at": "2026-05-14T00:00:00.000Z",
    "sources_count": 3,
    "limitations_key": "core-trust-policy-v1-2026-06-22"
  },
  "content": {
    "definition": {
      "key": "definition",
      "title": "一言でいうと",
      "text": "Change Readiness Assessment Framework guides assessing organizational readiness for change by structuring readiness score, stakeholder alignment, and change fatigue index and making the trade-off between speed of change versus stability explicit. It keeps assumptions visible for assessing organizational readiness for change and produces a reusable decision record.",
      "items": []
    },
    "formula": null,
    "boundary": null,
    "usage": [
      {
        "key": "meaning",
        "title": "意味",
        "text": "Add stakeholder heatmap and dependency risk scan before go-live.",
        "items": []
      },
      {
        "key": "usage",
        "title": "役立つ場面",
        "text": "Use this framework when assessing organizational readiness for change and teams disagree on survey results, leadership sponsorship, and training readiness. It fits decisions that need cross-functional alignment, numeric justification, and a written rationale. Apply it when reversal costs are high or when data sources are fragmented across systems.",
        "items": [
          "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"
        ]
      },
      {
        "key": "usage",
        "title": "使い方のポイント",
        "text": "Define scope, horizon, and success metrics (readiness score, stakeholder alignment, and change fatigue index); confirm baseline data quality and key assumptions. Collect inputs (survey results, leadership sponsorship, and training readiness) for each option and normalize units, timing, and ownership so comparisons are consistent. Run scenario and sensitivity checks to see how speed of change versus stability shifts; note thresholds that change the recommendation. Select a preferred option, record decision criteria, and list constraints or approvals required before execution. Set monitoring cadence, owners, and triggers for revisit; store the decision log and update when evidence changes. Template: 1) Background and objective 2) Scope and time horizon 3) Success metrics (readiness score, stakeholder alignment, and change fatigue index) 4) Key assumptions (survey results, leadership sponsorship, and training readiness) 5) Options A/B/C 6) Scenario ranges 7) Trade-off summary (speed of change versus stability) 8) Risks and mitigations 9) Decision criteria 10) Recommendation 11) Owner and timeline 12) Review triggers. Include data sources, document confidence levels, and flag variables that change outcomes materially. Use Change Readiness Deep-Dive Checklist 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.",
        "items": [
          "Define scope, horizon, and success metrics (readiness score, stakeholder alignment, and change fatigue index); confirm baseline data quality and key assumptions.",
          "Collect inputs (survey results, leadership sponsorship, and training readiness) for each option and normalize units, timing, and ownership so comparisons are consistent.",
          "Run scenario and sensitivity checks to see how speed of change versus stability shifts; note thresholds that change the recommendation.",
          "Select a preferred option, record decision criteria, and list constraints or approvals required before execution.",
          "Set monitoring cadence, owners, and triggers for revisit; store the decision log and update when evidence changes.",
          "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."
        ]
      }
    ],
    "misunderstandings": [
      {
        "key": "misunderstandings",
        "title": "判断するときの注意点",
        "text": "Use Change Readiness Deep-Dive Checklist 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.",
        "items": [
          "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."
        ]
      },
      {
        "key": "misunderstandings",
        "title": "よくある誤解 / 落とし穴",
        "text": null,
        "items": [
          "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",
          "Using inconsistent units or timing across options makes comparisons misleading and erodes trust in the output.",
          "Ignoring the speed of change versus stability in stakeholder discussions invites later reversals when priorities shift.",
          "Failing to record assumptions and data sources causes rework when results are challenged or audited."
        ]
      }
    ],
    "examples": [
      {
        "key": "examples",
        "title": "最小例",
        "text": "A team discussing Change Readiness Deep-Dive Checklist 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.",
        "items": []
      }
    ],
    "comparisons": [
      {
        "key": "comparisons",
        "title": "似ている言葉との違い",
        "text": "Compare Change Readiness Deep-Dive Checklist with adjacent concepts before deciding. Change Readiness Deep-Dive Checklist | 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",
        "items": [
          "Change Readiness Deep-Dive Checklist | 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"
        ]
      }
    ],
    "faq": [
      {
        "question": "When should I use Change Readiness Deep-Dive Checklist?",
        "answer": "Use it when the team needs to decide scope, priority, owner, or trade-off, not when it only needs a short definition."
      },
      {
        "question": "What makes Change Readiness Deep-Dive Checklist useful in practice?",
        "answer": "It becomes useful when it is tied to evidence, a decision owner, and a concrete next operating choice."
      },
      {
        "question": "What should I avoid?",
        "answer": "Avoid using the term as a label without clarifying assumptions, boundaries, and how success will be judged."
      }
    ]
  },
  "sources": {
    "source_refs": [
      "framework:business-framework-0084:en-US",
      "framework:business-framework-0084:ja-JP",
      "core-term-page-500:framework:business-framework-0084"
    ],
    "visible_sources": [
      {
        "label": "Principles of Management (OpenStax)",
        "url": "https://openstax.org/details/books/principles-of-management",
        "kind": null
      },
      {
        "label": "Principles of Marketing (Open Textbook Library)",
        "url": "https://open.umn.edu/opentextbooks/textbooks/principles-of-marketing",
        "kind": "tier_s"
      },
      {
        "label": "Principles of Management (OpenStax)",
        "url": "https://openstax.org/details/books/principles-management",
        "kind": "tier_s"
      }
    ]
  },
  "related_terms": [
    {
      "topic_id": "381210fb-8137-5f73-a388-80d4307fdc5e",
      "canonical_slug": "business-framework-0087",
      "canonical_url": "https://core.yogoq.com/en-US/core/business-framework-0087",
      "title": "Supplier Resilience Scoring Framework",
      "relation_type": "next"
    },
    {
      "topic_id": "3f8add05-d665-5336-b348-b152c932349d",
      "canonical_slug": "customer-support-load-balancing-framework",
      "canonical_url": "https://core.yogoq.com/en-US/core/customer-support-load-balancing-framework",
      "title": "Customer Support Load Balancing Framework",
      "relation_type": "used_together"
    },
    {
      "topic_id": "73d54971-cf3a-51c5-b3be-f2b31cf7f816",
      "canonical_slug": "finance-concept-0136",
      "canonical_url": "https://core.yogoq.com/en-US/core/finance-concept-0136",
      "title": "Project Discount Rate Selection",
      "relation_type": "used_together"
    },
    {
      "topic_id": "15549854-6bfc-50a6-a01e-43d3a2becc44",
      "canonical_slug": "finance-concept-0175",
      "canonical_url": "https://core.yogoq.com/en-US/core/finance-concept-0175",
      "title": "Investment Hurdle Rate Selection",
      "relation_type": "used_together"
    }
  ],
  "quality": {
    "quality": "reviewed",
    "publication_status": "published_reviewed",
    "source_count": 3,
    "last_reviewed_at": "2026-05-14T00:00:00.000Z",
    "trust_policy_version": "core-trust-policy-v1-2026-06-22"
  },
  "limitations": {
    "policy_version": "core-trust-policy-v1-2026-06-22",
    "professional_advice_boundary": "reference_only_not_professional_advice",
    "text": "This page is reference information for research and learning. For accounting, legal, finance, health, security, or other individual decisions, confirm against primary sources or qualified professionals.",
    "items": [
      "Public pages support general understanding and practical context; they are not professional advice for individual cases.",
      "Fast-changing information such as regulations, accounting standards, prices, product specs, and legal requirements should be checked against primary sources before final decisions.",
      "Even when AI-assisted drafting or audit is used, publication relies on quality gates and human-readable evidence."
    ]
  }
}
