{
  "schema_version": "core-reviewed-term-ai-handoff-v2",
  "version": "core-reviewed-term-ai-handoff-v2",
  "compat": {
    "backward_compatible_schema_versions": [
      "core-reviewed-term-ai-handoff-v1"
    ],
    "v1_fields_preserved": true
  },
  "contract_status": "preview",
  "distribution": "per_term_read_only_ai_handoff",
  "no_write_operations": true,
  "content_tier": "db_backed",
  "canonical": {
    "url": "https://core.yogoq.com/ko-KR/core/pdca",
    "slug": "pdca",
    "locale": "ko-KR"
  },
  "summary": {
    "schema_version": "core-reviewed-term-summary-v1",
    "term_id": "a1e5bf28-8a36-58e4-911d-98653b5c6bd7",
    "canonical_slug": "pdca",
    "canonical_url": "https://core.yogoq.com/ko-KR/core/pdca",
    "locale": "ko-KR",
    "display_name": "PDCAサイクル",
    "english_name": "PDCA Cycle",
    "abbreviation": "PDCA",
    "short_definition": "PDCA Cycle is a decision tool for turning learning velocity into a concrete continuous improvement loop.",
    "content_tier": "db_backed",
    "quality": "reviewed",
    "publication_status": "published_reviewed",
    "version": "core-reviewed-term-summary-v1",
    "last_reviewed_at": "2026-05-14T00:00:00.000Z",
    "sources_count": 2,
    "limitations_key": "core-trust-policy-v1-2026-06-22"
  },
  "aliases": [
    {
      "text": "PDCAサイクル",
      "type": "display_name",
      "locale": "ko-KR"
    },
    {
      "text": "PDCA Cycle",
      "type": "english_name",
      "locale": "en-US"
    },
    {
      "text": "PDCA",
      "type": "abbreviation",
      "locale": null
    },
    {
      "text": "ピーディーシーエー・サイクル",
      "type": "katakana",
      "locale": "ko-KR"
    },
    {
      "text": "PDCAサイクル",
      "type": "localized_title",
      "locale": "ja-JP"
    }
  ],
  "content": {
    "definition": {
      "key": "definition",
      "title": "一言でいうと",
      "text": "PDCA Cycle is a decision tool for turning learning velocity into a concrete continuous improvement loop.",
      "items": []
    },
    "formula": null,
    "boundary": null,
    "usage": [
      {
        "key": "meaning",
        "title": "意味",
        "text": "PDCA Cycle defines the working structure used when a process improvement should be planned, tested, checked, and standardized through a repeatable learning loop. In PDCA Cycle, the important work is not the template itself; the page states the decision boundary, required evidence, owner, and review cadence. Used well, PDCA Cycle turns vague discussion into an auditable management choice and exposes trade-offs before resources are committed.",
        "items": []
      },
      {
        "key": "usage",
        "title": "役立つ場面",
        "text": "PDCA Cycle changes decisions by making learning velocity visible before commitments are made. It helps leaders decide whether to start, stop, resize, or resequence work based on evidence rather than meeting momentum. It reduces rework because assumptions, owners, and review points are explicit enough to challenge.",
        "items": [
          "PDCA Cycle changes decisions by making learning velocity visible before commitments are made.",
          "It helps leaders decide whether to start, stop, resize, or resequence work based on evidence rather than meeting momentum.",
          "It reduces rework because assumptions, owners, and review points are explicit enough to challenge."
        ]
      },
      {
        "key": "usage",
        "title": "使い方のポイント",
        "text": null,
        "items": [
          "Define the decision, owner, and time horizon before filling in the continuous improvement loop.",
          "Separate evidence from opinion so the tool supports judgment instead of decorating a preferred answer.",
          "Record assumptions and review dates because learning velocity changes as the operating context changes.",
          "Use the output to choose a management action, not merely to produce a document.",
          "Retire or revise the tool when the decision boundary no longer matches the work."
        ]
      }
    ],
    "misunderstandings": [
      {
        "key": "misunderstandings",
        "title": "判断するときの注意点",
        "text": "The main risk is false precision: a neat continuous improvement loop can hide weak evidence or political assumptions. Check whether the tool is describing reality or merely rationalizing a decision that has already been made. If the output does not change a priority, owner, resource level, or review date, the analysis is probably too soft.",
        "items": [
          "The main risk is false precision: a neat continuous improvement loop can hide weak evidence or political assumptions.",
          "Check whether the tool is describing reality or merely rationalizing a decision that has already been made.",
          "If the output does not change a priority, owner, resource level, or review date, the analysis is probably too soft."
        ]
      },
      {
        "key": "misunderstandings",
        "title": "よくある誤解 / 落とし穴",
        "text": null,
        "items": [
          "PDCA Cycle is not the decision itself; it is a structure for making and reviewing the decision.",
          "More detail is not automatically better. For PDCA Cycle, the useful level is the one that changes a management action.",
          "A one-time workshop is not enough; the value comes from keeping the artifact current while the decision is live."
        ]
      }
    ],
    "examples": [
      {
        "key": "examples",
        "title": "最小例",
        "text": "A leadership team uses PDCA Cycle because a process improvement should be planned, tested, checked, and standardized through a repeatable learning loop. They draft the continuous improvement loop, name one accountable owner, and list the evidence that would change the recommendation. During the PDCA Cycle review, one assumption proves weak, so the team narrows the scope and schedules a follow-up review. The PDCA Cycle decision record now shows the action taken, the risk accepted, and the signal that would trigger a change.",
        "items": []
      }
    ],
    "comparisons": [
      {
        "key": "comparisons",
        "title": "似ている言葉との違い",
        "text": "A/B test | Compares alternatives under controlled conditions | PDCA manages the broader improvement cycle around the test Project plan | Coordinates deliverables | PDCA focuses on learning and standardizing improvement Retrospective | Reflects after work | PDCA includes planning and action before and after reflection",
        "items": [
          "A/B test | Compares alternatives under controlled conditions | PDCA manages the broader improvement cycle around the test",
          "Project plan | Coordinates deliverables | PDCA focuses on learning and standardizing improvement",
          "Retrospective | Reflects after work | PDCA includes planning and action before and after reflection"
        ]
      }
    ],
    "faq": [
      {
        "question": "What decision should PDCA Cycle support?",
        "answer": "PDCA Cycle should support a specific management choice: what to do, who owns it, what trade-off is accepted, and when the choice will be reviewed."
      },
      {
        "question": "How detailed should the continuous improvement loop be?",
        "answer": "PDCA Cycle should be detailed enough to expose assumptions, ownership, and evidence gaps, but not so detailed that the team stops making decisions."
      },
      {
        "question": "How often should PDCA Cycle be updated?",
        "answer": "Update PDCA Cycle when material evidence changes, when ownership changes, or when the review cadence says the decision must be revisited."
      }
    ]
  },
  "source_refs": [
    "concept:pdca:en-US",
    "concept:pdca:ja-JP",
    "concept:pdca-2:en-US",
    "concept:pdca-2:ja-JP",
    "concept:pdca-3:en-US",
    "concept:pdca-3:ja-JP",
    "manual_merge_map:numeric-suffix-2026-04-28"
  ],
  "sources": {
    "source_refs": [
      "concept:pdca:en-US",
      "concept:pdca:ja-JP",
      "concept:pdca-2:en-US",
      "concept:pdca-2:ja-JP",
      "concept:pdca-3:en-US",
      "concept:pdca-3:ja-JP",
      "manual_merge_map:numeric-suffix-2026-04-28"
    ],
    "visible_sources": [
      {
        "label": "Principles of Management (OpenStax)",
        "url": "https://openstax.org/details/books/principles-of-management",
        "kind": "tier_s"
      },
      {
        "label": "Wikipedia reference: PDCA Cycle",
        "url": "https://en.wikipedia.org/wiki/PDCA",
        "kind": "supplemental"
      }
    ]
  },
  "related_terms": [
    {
      "topic_id": "0a61b3e0-9651-5d4e-aafe-1045319955af",
      "canonical_slug": "priority",
      "canonical_url": "https://core.yogoq.com/ko-KR/core/priority",
      "title": "優先順位",
      "relation_type": "used_together"
    },
    {
      "topic_id": "04977a76-1418-5883-be32-c0c37e58ac32",
      "canonical_slug": "scope",
      "canonical_url": "https://core.yogoq.com/ko-KR/core/scope",
      "title": "スコープ",
      "relation_type": "used_together"
    },
    {
      "topic_id": "0d2f83cf-0cfa-5e83-976d-e7d6919d6ff5",
      "canonical_slug": "project",
      "canonical_url": "https://core.yogoq.com/ko-KR/core/project",
      "title": "プロジェクト",
      "relation_type": "related"
    }
  ],
  "relations": [
    {
      "term_id": "0a61b3e0-9651-5d4e-aafe-1045319955af",
      "canonical_slug": "priority",
      "canonical_url": "https://core.yogoq.com/ko-KR/core/priority",
      "display_name": "優先順位",
      "relation_type": "related",
      "source_relation_type": "used_together"
    },
    {
      "term_id": "04977a76-1418-5883-be32-c0c37e58ac32",
      "canonical_slug": "scope",
      "canonical_url": "https://core.yogoq.com/ko-KR/core/scope",
      "display_name": "スコープ",
      "relation_type": "related",
      "source_relation_type": "used_together"
    },
    {
      "term_id": "0d2f83cf-0cfa-5e83-976d-e7d6919d6ff5",
      "canonical_slug": "project",
      "canonical_url": "https://core.yogoq.com/ko-KR/core/project",
      "display_name": "プロジェクト",
      "relation_type": "related",
      "source_relation_type": "related"
    }
  ],
  "chunk_ids": [
    "core:chunk:pdca:ko-KR:definition:5acb38ce772d7194",
    "core:chunk:pdca:ko-KR:meaning:4cf03a3f26e0f960",
    "core:chunk:pdca:ko-KR:usage:272925821b465f93",
    "core:chunk:pdca:ko-KR:usage:b2f59aec5bf1863c",
    "core:chunk:pdca:ko-KR:misunderstandings:2e119dc4284daf0d",
    "core:chunk:pdca:ko-KR:misunderstandings:f4b868ab790e1425",
    "core:chunk:pdca:ko-KR:examples:76d76315b91f3193",
    "core:chunk:pdca:ko-KR:comparisons:3e22565d9aa46f46",
    "core:chunk:pdca:ko-KR:faq:b721d0080249877b",
    "core:chunk:pdca:ko-KR:faq:3eaf4d51ecd09352",
    "core:chunk:pdca:ko-KR:faq:c3cc93da3a744a66"
  ],
  "chunks": [
    {
      "chunk_id": "core:chunk:pdca:ko-KR:definition:5acb38ce772d7194",
      "section_key": "definition",
      "heading": "一言でいうと",
      "text": "PDCA Cycle is a decision tool for turning learning velocity into a concrete continuous improvement loop.",
      "source_refs": [
        "concept:pdca:en-US",
        "concept:pdca:ja-JP",
        "concept:pdca-2:en-US",
        "concept:pdca-2:ja-JP",
        "concept:pdca-3:en-US",
        "concept:pdca-3:ja-JP",
        "manual_merge_map:numeric-suffix-2026-04-28"
      ],
      "content_hash": "5acb38ce772d719485de5506f6dc6e8cd5532c4fa10dec917ec7a9fc6283bb6e"
    },
    {
      "chunk_id": "core:chunk:pdca:ko-KR:meaning:4cf03a3f26e0f960",
      "section_key": "meaning",
      "heading": "意味",
      "text": "PDCA Cycle defines the working structure used when a process improvement should be planned, tested, checked, and standardized through a repeatable learning loop. In PDCA Cycle, the important work is not the template itself; the page states the decision boundary, required evidence, owner, and review cadence. Used well, PDCA Cycle turns vague discussion into an auditable management choice and exposes trade-offs before resources are committed.",
      "source_refs": [
        "concept:pdca:en-US",
        "concept:pdca:ja-JP",
        "concept:pdca-2:en-US",
        "concept:pdca-2:ja-JP",
        "concept:pdca-3:en-US",
        "concept:pdca-3:ja-JP",
        "manual_merge_map:numeric-suffix-2026-04-28"
      ],
      "content_hash": "4cf03a3f26e0f96029c7e639d6023f78f5fd70b78f9207f4deb316f182a2f581"
    },
    {
      "chunk_id": "core:chunk:pdca:ko-KR:usage:272925821b465f93",
      "section_key": "usage",
      "heading": "役立つ場面",
      "text": "PDCA Cycle changes decisions by making learning velocity visible before commitments are made. It helps leaders decide whether to start, stop, resize, or resequence work based on evidence rather than meeting momentum. It reduces rework because assumptions, owners, and review points are explicit enough to challenge. PDCA Cycle changes decisions by making learning velocity visible before commitments are made. It helps leaders decide whether to start, stop, resize, or resequence work based on evidence rather than meeting momentum. It reduces rework because assumptions, owners, and review points are explicit enough to challenge.",
      "source_refs": [
        "concept:pdca:en-US",
        "concept:pdca:ja-JP",
        "concept:pdca-2:en-US",
        "concept:pdca-2:ja-JP",
        "concept:pdca-3:en-US",
        "concept:pdca-3:ja-JP",
        "manual_merge_map:numeric-suffix-2026-04-28"
      ],
      "content_hash": "272925821b465f932289846f0e83f986b3cdc30bbf729764b52ceec87c608171"
    },
    {
      "chunk_id": "core:chunk:pdca:ko-KR:usage:b2f59aec5bf1863c",
      "section_key": "usage",
      "heading": "使い方のポイント",
      "text": "Define the decision, owner, and time horizon before filling in the continuous improvement loop. Separate evidence from opinion so the tool supports judgment instead of decorating a preferred answer. Record assumptions and review dates because learning velocity changes as the operating context changes. Use the output to choose a management action, not merely to produce a document. Retire or revise the tool when the decision boundary no longer matches the work.",
      "source_refs": [
        "concept:pdca:en-US",
        "concept:pdca:ja-JP",
        "concept:pdca-2:en-US",
        "concept:pdca-2:ja-JP",
        "concept:pdca-3:en-US",
        "concept:pdca-3:ja-JP",
        "manual_merge_map:numeric-suffix-2026-04-28"
      ],
      "content_hash": "b2f59aec5bf1863c2386e78463a179d4b13d9cfd3d654d964698cde3cbc04326"
    },
    {
      "chunk_id": "core:chunk:pdca:ko-KR:misunderstandings:2e119dc4284daf0d",
      "section_key": "misunderstandings",
      "heading": "判断するときの注意点",
      "text": "The main risk is false precision: a neat continuous improvement loop can hide weak evidence or political assumptions. Check whether the tool is describing reality or merely rationalizing a decision that has already been made. If the output does not change a priority, owner, resource level, or review date, the analysis is probably too soft. The main risk is false precision: a neat continuous improvement loop can hide weak evidence or political assumptions. Check whether the tool is describing reality or merely rationalizing a decision that has already been made. If the output does not change a priority, owner, resource level, or review date, the analysis is probably too soft.",
      "source_refs": [
        "concept:pdca:en-US",
        "concept:pdca:ja-JP",
        "concept:pdca-2:en-US",
        "concept:pdca-2:ja-JP",
        "concept:pdca-3:en-US",
        "concept:pdca-3:ja-JP",
        "manual_merge_map:numeric-suffix-2026-04-28"
      ],
      "content_hash": "2e119dc4284daf0d872fa4daec94a70c380727e1d163945371911c3819a29b8f"
    },
    {
      "chunk_id": "core:chunk:pdca:ko-KR:misunderstandings:f4b868ab790e1425",
      "section_key": "misunderstandings",
      "heading": "よくある誤解 / 落とし穴",
      "text": "PDCA Cycle is not the decision itself; it is a structure for making and reviewing the decision. More detail is not automatically better. For PDCA Cycle, the useful level is the one that changes a management action. A one-time workshop is not enough; the value comes from keeping the artifact current while the decision is live.",
      "source_refs": [
        "concept:pdca:en-US",
        "concept:pdca:ja-JP",
        "concept:pdca-2:en-US",
        "concept:pdca-2:ja-JP",
        "concept:pdca-3:en-US",
        "concept:pdca-3:ja-JP",
        "manual_merge_map:numeric-suffix-2026-04-28"
      ],
      "content_hash": "f4b868ab790e1425cc82be2734d3c3b1ebf5cb4f24ed8427e096e3ef9ef28b8f"
    },
    {
      "chunk_id": "core:chunk:pdca:ko-KR:examples:76d76315b91f3193",
      "section_key": "examples",
      "heading": "最小例",
      "text": "A leadership team uses PDCA Cycle because a process improvement should be planned, tested, checked, and standardized through a repeatable learning loop. They draft the continuous improvement loop, name one accountable owner, and list the evidence that would change the recommendation. During the PDCA Cycle review, one assumption proves weak, so the team narrows the scope and schedules a follow-up review. The PDCA Cycle decision record now shows the action taken, the risk accepted, and the signal that would trigger a change.",
      "source_refs": [
        "concept:pdca:en-US",
        "concept:pdca:ja-JP",
        "concept:pdca-2:en-US",
        "concept:pdca-2:ja-JP",
        "concept:pdca-3:en-US",
        "concept:pdca-3:ja-JP",
        "manual_merge_map:numeric-suffix-2026-04-28"
      ],
      "content_hash": "76d76315b91f3193881b9cd73360169d62f33ddfbefc0823a9305fbc20dd5b92"
    },
    {
      "chunk_id": "core:chunk:pdca:ko-KR:comparisons:3e22565d9aa46f46",
      "section_key": "comparisons",
      "heading": "似ている言葉との違い",
      "text": "A/B test | Compares alternatives under controlled conditions | PDCA manages the broader improvement cycle around the test Project plan | Coordinates deliverables | PDCA focuses on learning and standardizing improvement Retrospective | Reflects after work | PDCA includes planning and action before and after reflection A/B test | Compares alternatives under controlled conditions | PDCA manages the broader improvement cycle around the test Project plan | Coordinates deliverables | PDCA focuses on learning and standardizing improvement Retrospective | Reflects after work | PDCA includes planning and action before and after reflection",
      "source_refs": [
        "concept:pdca:en-US",
        "concept:pdca:ja-JP",
        "concept:pdca-2:en-US",
        "concept:pdca-2:ja-JP",
        "concept:pdca-3:en-US",
        "concept:pdca-3:ja-JP",
        "manual_merge_map:numeric-suffix-2026-04-28"
      ],
      "content_hash": "3e22565d9aa46f46d5e6662d3c8284f687d58e3325c94d90600aac06ec41ffc5"
    },
    {
      "chunk_id": "core:chunk:pdca:ko-KR:faq:b721d0080249877b",
      "section_key": "faq",
      "heading": "What decision should PDCA Cycle support?",
      "text": "What decision should PDCA Cycle support? PDCA Cycle should support a specific management choice: what to do, who owns it, what trade-off is accepted, and when the choice will be reviewed.",
      "source_refs": [
        "concept:pdca:en-US",
        "concept:pdca:ja-JP",
        "concept:pdca-2:en-US",
        "concept:pdca-2:ja-JP",
        "concept:pdca-3:en-US",
        "concept:pdca-3:ja-JP",
        "manual_merge_map:numeric-suffix-2026-04-28"
      ],
      "content_hash": "b721d0080249877b62d86a6a76a1f12fe3346a411e3aeed87b1f424d591f6a93"
    },
    {
      "chunk_id": "core:chunk:pdca:ko-KR:faq:3eaf4d51ecd09352",
      "section_key": "faq",
      "heading": "How detailed should the continuous improvement loop be?",
      "text": "How detailed should the continuous improvement loop be? PDCA Cycle should be detailed enough to expose assumptions, ownership, and evidence gaps, but not so detailed that the team stops making decisions.",
      "source_refs": [
        "concept:pdca:en-US",
        "concept:pdca:ja-JP",
        "concept:pdca-2:en-US",
        "concept:pdca-2:ja-JP",
        "concept:pdca-3:en-US",
        "concept:pdca-3:ja-JP",
        "manual_merge_map:numeric-suffix-2026-04-28"
      ],
      "content_hash": "3eaf4d51ecd0935257b41d5856d5cba3b21f69da3c24c1fcb22f8990ae4064ce"
    },
    {
      "chunk_id": "core:chunk:pdca:ko-KR:faq:c3cc93da3a744a66",
      "section_key": "faq",
      "heading": "How often should PDCA Cycle be updated?",
      "text": "How often should PDCA Cycle be updated? Update PDCA Cycle when material evidence changes, when ownership changes, or when the review cadence says the decision must be revisited.",
      "source_refs": [
        "concept:pdca:en-US",
        "concept:pdca:ja-JP",
        "concept:pdca-2:en-US",
        "concept:pdca-2:ja-JP",
        "concept:pdca-3:en-US",
        "concept:pdca-3:ja-JP",
        "manual_merge_map:numeric-suffix-2026-04-28"
      ],
      "content_hash": "c3cc93da3a744a6654db6369981508e2ca3c31b842dc929f7b2559989a7649d7"
    }
  ],
  "content_hash": "ebc16a882ab6dacad74ac41a0eae8ecea7c8744c5c93bfd7b484fea0e70fb64d",
  "hash_algorithm": "sha256",
  "rag": {
    "chunk_id_policy": "core:chunk:{canonical_slug}:{locale}:{section_key}:{sha256_16}",
    "content_hash_policy": "sha256_stable_json",
    "source_refs_precision": "source_object_ref_or_source_key_current_snapshot"
  },
  "quality": {
    "content_tier": "db_backed",
    "quality": "reviewed",
    "publication_status": "published_reviewed",
    "source_count": 2,
    "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": "이 페이지는 조사와 학습을 위한 참조 정보입니다. 회계, 법무, 금융, 의료, 보안 등 개별 판단은 1차 출처나 전문가 확인을 우선하세요.",
    "items": [
      "공개 페이지는 일반 이해와 실무 맥락을 돕는 자료이며, 개별 사안의 전문 조언이 아닙니다.",
      "제도, 가격, 규제, 회계 기준, 제품 사양처럼 빠르게 변하는 정보는 최종 판단 전에 1차 출처를 확인해야 합니다.",
      "AI 지원 제작·감사 흐름을 사용하더라도 공개 여부는 품질 게이트와 사람이 읽을 수 있는 증거에 기반해 다룹니다."
    ]
  }
}