{ "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/bottleneck", "slug": "bottleneck", "locale": "ko-KR" }, "summary": { "schema_version": "core-reviewed-term-summary-v1", "term_id": "674dec80-baec-539f-9eb0-629dff182ffa", "canonical_slug": "bottleneck", "canonical_url": "https://core.yogoq.com/ko-KR/core/bottleneck", "locale": "ko-KR", "display_name": "ボトルネック", "english_name": "Bottleneck", "abbreviation": null, "short_definition": "Bottleneck is a system constraint point used for deciding where improvement work should focus first.", "content_tier": "db_backed", "quality": "reviewed", "publication_status": "published_reviewed", "version": "core-reviewed-term-summary-v1", "last_reviewed_at": "2026-05-22T00:00:00.000Z", "sources_count": 2, "limitations_key": "core-trust-policy-v1-2026-06-22" }, "aliases": [ { "text": "ボトルネック", "type": "display_name", "locale": "ko-KR" }, { "text": "Bottleneck", "type": "english_name", "locale": "en-US" }, { "text": "ボトルネック", "type": "localized_title", "locale": "ja-JP" } ], "content": { "definition": { "key": "definition", "title": "一言でいうと", "text": "Bottleneck is a system constraint point used for deciding where improvement work should focus first.", "items": [] }, "formula": null, "boundary": null, "usage": [ { "key": "meaning", "title": "意味", "text": "Bottleneck is the point in a workflow, market motion, or operating system that limits total throughput or decision speed. In practice it is used for deciding where improvement work should focus first by making owners, boundaries, evidence, and review triggers explicit.", "items": [] }, { "key": "usage", "title": "役立つ場面", "text": "Bottleneck changes decisions by making the owner, boundary, required evidence, and review trigger explicit before work proceeds. Bottleneck helps teams decide whether to start, stop, resize, or resequence work using evidence rather than meeting momentum. Bottleneck reduces rework because assumptions, unresolved questions, and follow-up responsibilities are visible enough to challenge.", "items": [ "Bottleneck changes decisions by making the owner, boundary, required evidence, and review trigger explicit before work proceeds.", "Bottleneck helps teams decide whether to start, stop, resize, or resequence work using evidence rather than meeting momentum.", "Bottleneck reduces rework because assumptions, unresolved questions, and follow-up responsibilities are visible enough to challenge." ] }, { "key": "usage", "title": "使い方のポイント", "text": null, "items": [ "Define the decision question, accountable owner, and time horizon before using Bottleneck as an operating artifact.", "Separate evidence from opinion so Bottleneck supports judgment instead of decorating a preferred answer.", "Record what was accepted, what was deferred, and what signal would cause a future change in Bottleneck.", "Use Bottleneck to choose a management action, not merely to produce a tidy document or status label.", "Revise or retire Bottleneck when the boundary, owner, evidence, or operating context changes materially." ] } ], "misunderstandings": [ { "key": "misunderstandings", "title": "判断するときの注意点", "text": "Bottleneck will not speed execution when ownership remains ambiguous. Bottleneck becomes storage instead of a decision aid when it is too long to use. Bottleneck needs change history or teams cannot reconstruct why the decision moved.", "items": [ "Bottleneck will not speed execution when ownership remains ambiguous.", "Bottleneck becomes storage instead of a decision aid when it is too long to use.", "Bottleneck needs change history or teams cannot reconstruct why the decision moved." ] }, { "key": "misunderstandings", "title": "よくある誤解 / 落とし穴", "text": null, "items": [ "Bottleneck is not valuable because the label exists; it is valuable only when it changes a decision or execution behavior.", "More detail is not automatically better for Bottleneck; the useful level is the one that clarifies ownership and review.", "Bottleneck is not a one-time workshop output because the artifact must stay current while the decision remains live." ] } ], "examples": [ { "key": "examples", "title": "最小例", "text": "A team uses Bottleneck after noticing that discussion keeps producing activity without a clear management decision. For Bottleneck, the team defines the intended outcome, names one accountable owner, and lists the evidence that would change the decision. During the Bottleneck review, the team compares current evidence with the recorded boundary, adjusts the scope, and assigns follow-through work. The Bottleneck record now helps people see why the action was chosen, what risk was accepted, and when the decision should be revisited.", "items": [] } ], "comparisons": [ { "key": "comparisons", "title": "似ている言葉との違い", "text": "Separate nearby terms by the decision each one supports. Process bottleneck mapping | Locates constraints systematically | Bottleneck names the constraint itself Cycle time reduction | Reduces elapsed time | Bottleneck work targets the limiting point first Operational efficiency | Improves resource use | Bottleneck analysis prevents local efficiency from hurting total flow", "items": [ "Process bottleneck mapping | Locates constraints systematically | Bottleneck names the constraint itself", "Cycle time reduction | Reduces elapsed time | Bottleneck work targets the limiting point first", "Operational efficiency | Improves resource use | Bottleneck analysis prevents local efficiency from hurting total flow" ] } ], "faq": [ { "question": "Can there be multiple bottlenecks?", "answer": "There can be several pain points, but one usually limits the system most at a given moment." }, { "question": "Should we add people first?", "answer": "Not until the constraint is confirmed and low-value work has been removed from it." }, { "question": "What happens after it is fixed?", "answer": "The constraint usually moves, so the review must continue." } ] }, "source_refs": [ "concept:bottleneck:en-US", "concept:bottleneck:ja-JP", "catalog:concept:F-01-10" ], "sources": { "source_refs": [ "concept:bottleneck:en-US", "concept:bottleneck:ja-JP", "catalog:concept:F-01-10" ], "visible_sources": [ { "label": "Principles of Management (Open Textbook Library)", "url": "https://open.umn.edu/opentextbooks/textbooks/principles-of-management", "kind": "tier_s" }, { "label": "Wikipedia reference: Business Process Management", "url": "https://en.wikipedia.org/wiki/Business_process_management", "kind": "supplemental" } ] }, "related_terms": [ { "topic_id": "e1c8190b-64bf-5f85-b270-1acc27a2ace4", "canonical_slug": "cycle-time-reduction", "canonical_url": "https://core.yogoq.com/ko-KR/core/cycle-time-reduction", "title": "サイクルタイム短縮", "relation_type": "used_together" }, { "topic_id": "99f8864b-7bc8-5751-b0d1-40161ad0dee7", "canonical_slug": "operational-efficiency", "canonical_url": "https://core.yogoq.com/ko-KR/core/operational-efficiency", "title": "オペレーション効率", "relation_type": "used_together" }, { "topic_id": "b72b2cc0-ffad-5a64-9e04-1c0e4f73fe4b", "canonical_slug": "process-bottleneck-mapping", "canonical_url": "https://core.yogoq.com/ko-KR/core/process-bottleneck-mapping", "title": "プロセスのボトルネック把握", "relation_type": "related" } ], "relations": [ { "term_id": "e1c8190b-64bf-5f85-b270-1acc27a2ace4", "canonical_slug": "cycle-time-reduction", "canonical_url": "https://core.yogoq.com/ko-KR/core/cycle-time-reduction", "display_name": "サイクルタイム短縮", "relation_type": "related", "source_relation_type": "used_together" }, { "term_id": "99f8864b-7bc8-5751-b0d1-40161ad0dee7", "canonical_slug": "operational-efficiency", "canonical_url": "https://core.yogoq.com/ko-KR/core/operational-efficiency", "display_name": "オペレーション効率", "relation_type": "related", "source_relation_type": "used_together" }, { "term_id": "b72b2cc0-ffad-5a64-9e04-1c0e4f73fe4b", "canonical_slug": "process-bottleneck-mapping", "canonical_url": "https://core.yogoq.com/ko-KR/core/process-bottleneck-mapping", "display_name": "プロセスのボトルネック把握", "relation_type": "related", "source_relation_type": "related" } ], "chunk_ids": [ "core:chunk:bottleneck:ko-KR:definition:e18a58388a77ead3", "core:chunk:bottleneck:ko-KR:meaning:414d8a01f1d7754e", "core:chunk:bottleneck:ko-KR:usage:f42cb8add368e617", "core:chunk:bottleneck:ko-KR:usage:08830d4adbd2d01a", "core:chunk:bottleneck:ko-KR:misunderstandings:6f11a5f23bca94b1", "core:chunk:bottleneck:ko-KR:misunderstandings:659704d143b60c38", "core:chunk:bottleneck:ko-KR:examples:7bf7e2df7d596144", "core:chunk:bottleneck:ko-KR:comparisons:84033895f434c7ab", "core:chunk:bottleneck:ko-KR:faq:3504a62da9d09a09", "core:chunk:bottleneck:ko-KR:faq:34b581f14a25d52a", "core:chunk:bottleneck:ko-KR:faq:3dc0c844f73575e2" ], "chunks": [ { "chunk_id": "core:chunk:bottleneck:ko-KR:definition:e18a58388a77ead3", "section_key": "definition", "heading": "一言でいうと", "text": "Bottleneck is a system constraint point used for deciding where improvement work should focus first.", "source_refs": [ "concept:bottleneck:en-US", "concept:bottleneck:ja-JP", "catalog:concept:F-01-10" ], "content_hash": "e18a58388a77ead374a5ab570b8cb64a10eb58827ae2497ec8ebaf0187ad7a77" }, { "chunk_id": "core:chunk:bottleneck:ko-KR:meaning:414d8a01f1d7754e", "section_key": "meaning", "heading": "意味", "text": "Bottleneck is the point in a workflow, market motion, or operating system that limits total throughput or decision speed. In practice it is used for deciding where improvement work should focus first by making owners, boundaries, evidence, and review triggers explicit.", "source_refs": [ "concept:bottleneck:en-US", "concept:bottleneck:ja-JP", "catalog:concept:F-01-10" ], "content_hash": "414d8a01f1d7754e9b453547bb02a798fd2d030deada3370db373438ff6427be" }, { "chunk_id": "core:chunk:bottleneck:ko-KR:usage:f42cb8add368e617", "section_key": "usage", "heading": "役立つ場面", "text": "Bottleneck changes decisions by making the owner, boundary, required evidence, and review trigger explicit before work proceeds. Bottleneck helps teams decide whether to start, stop, resize, or resequence work using evidence rather than meeting momentum. Bottleneck reduces rework because assumptions, unresolved questions, and follow-up responsibilities are visible enough to challenge. Bottleneck changes decisions by making the owner, boundary, required evidence, and review trigger explicit before work proceeds. Bottleneck helps teams decide whether to start, stop, resize, or resequence work using evidence rather than meeting momentum. Bottleneck reduces rework because assumptions, unresolved questions, and follow-up responsibilities are visible enough to challenge.", "source_refs": [ "concept:bottleneck:en-US", "concept:bottleneck:ja-JP", "catalog:concept:F-01-10" ], "content_hash": "f42cb8add368e6173420ca94c2bdfdc105985e66c2eb9611130904f01323b5de" }, { "chunk_id": "core:chunk:bottleneck:ko-KR:usage:08830d4adbd2d01a", "section_key": "usage", "heading": "使い方のポイント", "text": "Define the decision question, accountable owner, and time horizon before using Bottleneck as an operating artifact. Separate evidence from opinion so Bottleneck supports judgment instead of decorating a preferred answer. Record what was accepted, what was deferred, and what signal would cause a future change in Bottleneck. Use Bottleneck to choose a management action, not merely to produce a tidy document or status label. Revise or retire Bottleneck when the boundary, owner, evidence, or operating context changes materially.", "source_refs": [ "concept:bottleneck:en-US", "concept:bottleneck:ja-JP", "catalog:concept:F-01-10" ], "content_hash": "08830d4adbd2d01af45045cbe37d9d62dfd9ae26591a99d7f2515b26def90b8a" }, { "chunk_id": "core:chunk:bottleneck:ko-KR:misunderstandings:6f11a5f23bca94b1", "section_key": "misunderstandings", "heading": "判断するときの注意点", "text": "Bottleneck will not speed execution when ownership remains ambiguous. Bottleneck becomes storage instead of a decision aid when it is too long to use. Bottleneck needs change history or teams cannot reconstruct why the decision moved. Bottleneck will not speed execution when ownership remains ambiguous. Bottleneck becomes storage instead of a decision aid when it is too long to use. Bottleneck needs change history or teams cannot reconstruct why the decision moved.", "source_refs": [ "concept:bottleneck:en-US", "concept:bottleneck:ja-JP", "catalog:concept:F-01-10" ], "content_hash": "6f11a5f23bca94b1bb2e67f97e8b006f778092b46c083df4ff0cfde68c9da977" }, { "chunk_id": "core:chunk:bottleneck:ko-KR:misunderstandings:659704d143b60c38", "section_key": "misunderstandings", "heading": "よくある誤解 / 落とし穴", "text": "Bottleneck is not valuable because the label exists; it is valuable only when it changes a decision or execution behavior. More detail is not automatically better for Bottleneck; the useful level is the one that clarifies ownership and review. Bottleneck is not a one-time workshop output because the artifact must stay current while the decision remains live.", "source_refs": [ "concept:bottleneck:en-US", "concept:bottleneck:ja-JP", "catalog:concept:F-01-10" ], "content_hash": "659704d143b60c38836637c7d68d1ff9ccea769820400c7fc92739425404ba8e" }, { "chunk_id": "core:chunk:bottleneck:ko-KR:examples:7bf7e2df7d596144", "section_key": "examples", "heading": "最小例", "text": "A team uses Bottleneck after noticing that discussion keeps producing activity without a clear management decision. For Bottleneck, the team defines the intended outcome, names one accountable owner, and lists the evidence that would change the decision. During the Bottleneck review, the team compares current evidence with the recorded boundary, adjusts the scope, and assigns follow-through work. The Bottleneck record now helps people see why the action was chosen, what risk was accepted, and when the decision should be revisited.", "source_refs": [ "concept:bottleneck:en-US", "concept:bottleneck:ja-JP", "catalog:concept:F-01-10" ], "content_hash": "7bf7e2df7d59614451fa6b810d1027a9834440ddd80ba2c4ad68b4713a4fd642" }, { "chunk_id": "core:chunk:bottleneck:ko-KR:comparisons:84033895f434c7ab", "section_key": "comparisons", "heading": "似ている言葉との違い", "text": "Separate nearby terms by the decision each one supports. Process bottleneck mapping | Locates constraints systematically | Bottleneck names the constraint itself Cycle time reduction | Reduces elapsed time | Bottleneck work targets the limiting point first Operational efficiency | Improves resource use | Bottleneck analysis prevents local efficiency from hurting total flow Process bottleneck mapping | Locates constraints systematically | Bottleneck names the constraint itself Cycle time reduction | Reduces elapsed time | Bottleneck work targets the limiting point first Operational efficiency | Improves resource use | Bottleneck analysis prevents local efficiency from hurting total flow", "source_refs": [ "concept:bottleneck:en-US", "concept:bottleneck:ja-JP", "catalog:concept:F-01-10" ], "content_hash": "84033895f434c7abf0186f7257cb74afbc48660aad2c3a92b7d7c1f94113bc9e" }, { "chunk_id": "core:chunk:bottleneck:ko-KR:faq:3504a62da9d09a09", "section_key": "faq", "heading": "Can there be multiple bottlenecks?", "text": "Can there be multiple bottlenecks? There can be several pain points, but one usually limits the system most at a given moment.", "source_refs": [ "concept:bottleneck:en-US", "concept:bottleneck:ja-JP", "catalog:concept:F-01-10" ], "content_hash": "3504a62da9d09a097760bbd96092d1eeabf89b7b2a4e17d2272989ebb78cba6e" }, { "chunk_id": "core:chunk:bottleneck:ko-KR:faq:34b581f14a25d52a", "section_key": "faq", "heading": "Should we add people first?", "text": "Should we add people first? Not until the constraint is confirmed and low-value work has been removed from it.", "source_refs": [ "concept:bottleneck:en-US", "concept:bottleneck:ja-JP", "catalog:concept:F-01-10" ], "content_hash": "34b581f14a25d52a73f09ff1d4dd2b5cf316d36982fd6050fdc81b3de792f5d0" }, { "chunk_id": "core:chunk:bottleneck:ko-KR:faq:3dc0c844f73575e2", "section_key": "faq", "heading": "What happens after it is fixed?", "text": "What happens after it is fixed? The constraint usually moves, so the review must continue.", "source_refs": [ "concept:bottleneck:en-US", "concept:bottleneck:ja-JP", "catalog:concept:F-01-10" ], "content_hash": "3dc0c844f73575e2e34029002a3d1a423904997693ae2a78bc0adc67f80af8ba" } ], "content_hash": "8e65a6bb35db765147f1f0c1fbb6ad1ccfdbeb95d1d6f4d48f93024214be857d", "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-22T00: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 지원 제작·감사 흐름을 사용하더라도 공개 여부는 품질 게이트와 사람이 읽을 수 있는 증거에 기반해 다룹니다." ] } }