{
  "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/process-bottleneck-mapping",
    "slug": "process-bottleneck-mapping",
    "locale": "en-US"
  },
  "summary": {
    "schema_version": "core-reviewed-term-summary-v1",
    "term_id": "b72b2cc0-ffad-5a64-9e04-1c0e4f73fe4b",
    "canonical_slug": "process-bottleneck-mapping",
    "canonical_url": "https://core.yogoq.com/en-US/core/process-bottleneck-mapping",
    "locale": "en-US",
    "display_name": "Process Bottleneck Mapping",
    "english_name": null,
    "abbreviation": null,
    "short_definition": "Process Bottleneck Mapping is a constraint map of the flow used for choosing the highest-leverage improvement point before redesigning a process.",
    "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"
  },
  "content": {
    "definition": {
      "key": "definition",
      "title": "一言でいうと",
      "text": "Process Bottleneck Mapping is a constraint map of the flow used for choosing the highest-leverage improvement point before redesigning a process.",
      "items": []
    },
    "formula": null,
    "boundary": null,
    "usage": [
      {
        "key": "meaning",
        "title": "意味",
        "text": "Process Bottleneck Mapping is a method for tracing a process end to end and identifying where queues, rework, handoffs, or policy constraints limit flow. In practice it is used for choosing the highest-leverage improvement point before redesigning a process by making owners, boundaries, evidence, and review triggers explicit.",
        "items": []
      },
      {
        "key": "usage",
        "title": "役立つ場面",
        "text": "Process Bottleneck Mapping changes decisions by making the owner, boundary, required evidence, and review trigger explicit before work proceeds. Process Bottleneck Mapping helps teams decide whether to start, stop, resize, or resequence work using evidence rather than meeting momentum. Process Bottleneck Mapping reduces rework because assumptions, unresolved questions, and follow-up responsibilities are visible enough to challenge.",
        "items": [
          "Process Bottleneck Mapping changes decisions by making the owner, boundary, required evidence, and review trigger explicit before work proceeds.",
          "Process Bottleneck Mapping helps teams decide whether to start, stop, resize, or resequence work using evidence rather than meeting momentum.",
          "Process Bottleneck Mapping 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 Process Bottleneck Mapping as an operating artifact.",
          "Separate evidence from opinion so Process Bottleneck Mapping supports judgment instead of decorating a preferred answer.",
          "Record what was accepted, what was deferred, and what signal would cause a future change in Process Bottleneck Mapping.",
          "Use Process Bottleneck Mapping to choose a management action, not merely to produce a tidy document or status label.",
          "Revise or retire Process Bottleneck Mapping when the boundary, owner, evidence, or operating context changes materially."
        ]
      }
    ],
    "misunderstandings": [
      {
        "key": "misunderstandings",
        "title": "判断するときの注意点",
        "text": "Process Bottleneck Mapping will not speed execution when ownership remains ambiguous. Process Bottleneck Mapping becomes storage instead of a decision aid when it is too long to use. Process Bottleneck Mapping needs change history or teams cannot reconstruct why the decision moved.",
        "items": [
          "Process Bottleneck Mapping will not speed execution when ownership remains ambiguous.",
          "Process Bottleneck Mapping becomes storage instead of a decision aid when it is too long to use.",
          "Process Bottleneck Mapping needs change history or teams cannot reconstruct why the decision moved."
        ]
      },
      {
        "key": "misunderstandings",
        "title": "よくある誤解 / 落とし穴",
        "text": null,
        "items": [
          "Process Bottleneck Mapping 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 Process Bottleneck Mapping; the useful level is the one that clarifies ownership and review.",
          "Process Bottleneck Mapping 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 Process Bottleneck Mapping after noticing that discussion keeps producing activity without a clear management decision. For Process Bottleneck Mapping, the team defines the intended outcome, names one accountable owner, and lists the evidence that would change the decision. During the Process Bottleneck Mapping review, the team compares current evidence with the recorded boundary, adjusts the scope, and assigns follow-through work. The Process Bottleneck Mapping 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. Bottleneck | Names the limiting point | Mapping is the evidence process used to find it Process improvement | Changes the work | Mapping chooses what to change first Process standardization | Stabilizes the baseline | Mapping reveals where the baseline breaks",
        "items": [
          "Bottleneck | Names the limiting point | Mapping is the evidence process used to find it",
          "Process improvement | Changes the work | Mapping chooses what to change first",
          "Process standardization | Stabilizes the baseline | Mapping reveals where the baseline breaks"
        ]
      }
    ],
    "faq": [
      {
        "question": "What data is needed?",
        "answer": "Use timestamps, queue age, rework counts, handoff counts, and owner interviews."
      },
      {
        "question": "How detailed should the map be?",
        "answer": "Detailed enough to identify the constraint and decision owner, not every minor motion."
      },
      {
        "question": "What is the first output?",
        "answer": "A ranked constraint list with evidence and a proposed test."
      }
    ]
  },
  "sources": {
    "source_refs": [
      "concept:business-concept-0183:en-US",
      "concept:business-concept-0183:ja-JP",
      "manual_promotion_packet:synthetic-business-concepts-batch3-2026-04-28"
    ],
    "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/en-US/core/cycle-time-reduction",
      "title": "Cycle Time Reduction",
      "relation_type": "used_together"
    },
    {
      "topic_id": "ed9364f3-d42d-552f-bf81-674b1f0d1528",
      "canonical_slug": "process-improvement",
      "canonical_url": "https://core.yogoq.com/en-US/core/process-improvement",
      "title": "Process Improvement",
      "relation_type": "used_together"
    },
    {
      "topic_id": "674dec80-baec-539f-9eb0-629dff182ffa",
      "canonical_slug": "bottleneck",
      "canonical_url": "https://core.yogoq.com/en-US/core/bottleneck",
      "title": "Bottleneck",
      "relation_type": "related"
    }
  ],
  "quality": {
    "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": "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."
    ]
  }
}