{ "id": "change-request-flow-gates", "schemaVersion": 2, "title": { "ja": "変更管理 — 各段に営業日を与え、否認の行き先まで描く", "en": "Change Control — Business Days on Every Step, and Where a Refusal Goes" }, "summary": { "ja": "受付から反映まで 5 段の流れ。止まる段（判定）だけを塗り、否認したものの行き先を枝として同じ面に描く", "en": "Five steps from intake to change, with the one step that stops filled and the refusal branch drawn on the same page" }, "capturedAt": "2026-09-15", "categories": [ "presentation" ], "tags": [ "minimal", "typography" ], "useCases": [ "change-control", "process" ], "format": "slide-16x9", "density": "medium", "layout": { "kind": "flow", "canvas": { "w": 1920, "h": 1080 }, "margin": { "top": 92, "right": 140, "bottom": 92, "left": 140 }, "columns": { "count": 5, "gap": 34 }, "emphasis": { "column": 3, "via": [ "fill", "rule" ] } }, "type": { "title": { "size": 46, "weight": 700, "tracking": "0.01em", "leading": 1.3 }, "lede": { "size": 19, "weight": 400, "leading": 1.8 }, "days": { "size": 14, "weight": 500, "tracking": "0.14em", "numeric": "tabular" }, "sname": { "size": 28, "weight": 700, "leading": 1.4 }, "who": { "size": 15, "weight": 500 }, "out": { "size": 15, "weight": 400, "leading": 1.7 }, "rname": { "size": 20, "weight": 700 }, "rtext": { "size": 16, "weight": 400, "leading": 1.75 }, "fkey": { "size": 14, "weight": 500, "tracking": "0.14em" }, "fval": { "size": 17, "weight": 500, "leading": 1.65, "numeric": "tabular" } }, "colors": { "ground": "#FFFFFF", "surface": "#F4F6F9", "ink": "#131820", "muted": "#667183", "accent": "#1F5FA8", "rule": "#DBE1E9", "series": [] }, "rules": [ { "ja": "各段に営業日を書く。日数の無いフローは「いつ決まるか」を答えないので、現場は待たずに先に作り始める", "en": "Put business days on every step — a flow with no clock never answers \"when\", so the team starts building before the answer arrives" }, { "ja": "否認の行き先を描く。行き先の無い否認は、同じ要求が翌月また受付に戻ってくる", "en": "Draw where a refusal goes; with nowhere to go, the same request comes back through intake next month" }, { "ja": "判定者を金額や規模で分ける。1 つの会議体に全部持ち込むと、小さな変更が月 1 回の決裁を待つことになる", "en": "Split the judge by size — send everything to one forum and a two-day change waits for a monthly meeting" }, { "ja": "「計画の改訂」を独立した段にする。ここが段になっていないから、小さな変更が工程表に反映されないまま積み上がる", "en": "Make replanning its own step; when it is not a step, small changes accumulate without ever reaching the schedule" }, { "ja": "塗るのは止まる段 1 つだけ。他は作業の段なので、塗ると「どこで待つのか」が読めなくなる", "en": "Fill the one step that stops. The others are work; filling them hides where the waiting happens" }, { "ja": "枝は判定の段の左端から L 字で落とす。渡り線の途中に落とすと、その左に置いた見出しが分岐の出どころに見える", "en": "Drop the branch from the judging step's left edge — landing mid-rule makes the heading to its left look like the source" } ], "cover": "https://design-vault.pages.dev/_astro/cover.B1hRNZh7.png", "assets": [], "shortlist": false, "status": "published", "relations": { "similar": [ "scope-in-out-two-fields", "requirements-response-table", "estimate-breakdown-by-phase" ] }, "license": "Original", "publishedAt": null, "reproduction": { "spec": { "format": "slide-16x9", "density": "medium", "layout": { "kind": "flow", "canvas": { "w": 1920, "h": 1080 }, "margin": { "top": 92, "right": 140, "bottom": 92, "left": 140 }, "columns": { "count": 5, "gap": 34 }, "emphasis": { "column": 3, "via": [ "fill", "rule" ] } }, "type": { "title": { "size": 46, "weight": 700, "tracking": "0.01em", "leading": 1.3 }, "lede": { "size": 19, "weight": 400, "leading": 1.8 }, "days": { "size": 14, "weight": 500, "tracking": "0.14em", "numeric": "tabular" }, "sname": { "size": 28, "weight": 700, "leading": 1.4 }, "who": { "size": 15, "weight": 500 }, "out": { "size": 15, "weight": 400, "leading": 1.7 }, "rname": { "size": 20, "weight": 700 }, "rtext": { "size": 16, "weight": 400, "leading": 1.75 }, "fkey": { "size": 14, "weight": 500, "tracking": "0.14em" }, "fval": { "size": 17, "weight": 500, "leading": 1.65, "numeric": "tabular" } }, "colors": { "ground": "#FFFFFF", "surface": "#F4F6F9", "ink": "#131820", "muted": "#667183", "accent": "#1F5FA8", "rule": "#DBE1E9" }, "rules": [ "Put business days on every step — a flow with no clock never answers \"when\", so the team starts building before the answer arrives", "Draw where a refusal goes; with nowhere to go, the same request comes back through intake next month", "Split the judge by size — send everything to one forum and a two-day change waits for a monthly meeting", "Make replanning its own step; when it is not a step, small changes accumulate without ever reaching the schedule", "Fill the one step that stops. The others are work; filling them hides where the waiting happens", "Drop the branch from the judging step's left edge — landing mid-rule makes the heading to its left look like the source" ] }, "prompt": { "ja": "以下の仕様でスライドを 1 枚作ってください。\n\n- 版面 1920 × 1080\n- 余白 上 92 右 140 下 92 左 140\n- 5 カラム（等分）、間隔 34\n\n## 強調\n3 列目のみ。手段は 塗り + 罫 だけ。ほかは変えない\n\n## 文字（版面 1920px に対する px）\ntitle 46px / 700 / 字間 0.01em / 行送り 1.3\nlede 19px / 400 / 行送り 1.8\ndays 14px / 500 / 字間 0.14em / 等幅数字\nsname 28px / 700 / 行送り 1.4\nwho 15px / 500\nout 15px / 400 / 行送り 1.7\nrname 20px / 700\nrtext 16px / 400 / 行送り 1.75\nfkey 14px / 500 / 字間 0.14em\nfval 17px / 500 / 行送り 1.65 / 等幅数字\n\n## 配色\n地 #FFFFFF / 面 #F4F6F9 / 文字 #131820 / 補助 #667183 / 強調 #1F5FA8 / 罫 #DBE1E9\n\n## 外すと崩れる点\n- 各段に営業日を書く。日数の無いフローは「いつ決まるか」を答えないので、現場は待たずに先に作り始める\n- 否認の行き先を描く。行き先の無い否認は、同じ要求が翌月また受付に戻ってくる\n- 判定者を金額や規模で分ける。1 つの会議体に全部持ち込むと、小さな変更が月 1 回の決裁を待つことになる\n- 「計画の改訂」を独立した段にする。ここが段になっていないから、小さな変更が工程表に反映されないまま積み上がる\n- 塗るのは止まる段 1 つだけ。他は作業の段なので、塗ると「どこで待つのか」が読めなくなる\n- 枝は判定の段の左端から L 字で落とす。渡り線の途中に落とすと、その左に置いた見出しが分岐の出どころに見える\n\n内容は［ここに自分の内容を書く］に置き換えてください。寸法と配色はそのまま守ってください。\n正確に再現する場合は、この HTML をそのまま使ってください: https://design-vault.pages.dev/designs/change-request-flow-gates/pattern.html", "en": "Produce one slide to the following specification.\n\n- Canvas 1920 × 1080\n- Margin top 92 right 140 bottom 92 left 140\n- 5 equal columns, gap 34\n\n## Emphasis\ncolumn 3 only, by fill + rule and nothing else\n\n## Type (px against a 1920px canvas)\ntitle 46px / 700 / tracking 0.01em / leading 1.3\nlede 19px / 400 / leading 1.8\ndays 14px / 500 / tracking 0.14em / tabular numerals\nsname 28px / 700 / leading 1.4\nwho 15px / 500\nout 15px / 400 / leading 1.7\nrname 20px / 700\nrtext 16px / 400 / leading 1.75\nfkey 14px / 500 / tracking 0.14em\nfval 17px / 500 / leading 1.65 / tabular numerals\n\n## Colour\nGround #FFFFFF / Surface #F4F6F9 / Ink #131820 / Muted #667183 / Accent #1F5FA8 / Rule #DBE1E9\n\n## Constraints — dropping these breaks it\n- Put business days on every step — a flow with no clock never answers \"when\", so the team starts building before the answer arrives\n- Draw where a refusal goes; with nowhere to go, the same request comes back through intake next month\n- Split the judge by size — send everything to one forum and a two-day change waits for a monthly meeting\n- Make replanning its own step; when it is not a step, small changes accumulate without ever reaching the schedule\n- Fill the one step that stops. The others are work; filling them hides where the waiting happens\n- Drop the branch from the judging step's left edge — landing mid-rule makes the heading to its left look like the source\n\nReplace the content with [your content]. Keep the measurements and colours as given.\nFor an exact reproduction, use the verbatim HTML at https://design-vault.pages.dev/designs/change-request-flow-gates/pattern.html." }, "code": { "html": "\n\n変更管理 — 各段に営業日を与え、否認の行き先まで描く\n\n\n\n\n
\n
\n
\n

変更要求の扱い

\n

受付から反映まで、各段に営業日を置いています。合計 10 営業日で結論が出ない要求は、そのまま第 2 期の候補に送ります。

\n
\n\n
\n
\n
\n

1 営業日

\n

受付

\n

合同 PMO

\n

要求票に採番し、台帳へ記載

\n
\n
\n
\n

4 営業日

\n

影響評価

\n

開発チーム・基盤チーム

\n

工数・工程・他機能への影響を算定

\n
\n
\n
\n

3 営業日

\n

判定

\n

合同 PMO（20 人日以上はステアリングコミッティ）

\n

承認・否認・保留のいずれかを記録

\n
\n
\n
\n

2 営業日

\n

計画の改訂

\n

合同 PMO

\n

工程表と見積を改訂。版数を上げる

\n
\n
\n
\n

工程に依存

\n

反映

\n

担当チーム

\n

設計書の改訂から実装・試験まで

\n
\n
\n\n
\n
\n
\n

否認・保留のとき

\n

第 2 期の候補一覧へ、判定日と理由を付けて移します。差し戻しはしません —— 行き先の無い否認は、同じ要求が翌月また受付に戻ってくるためです。

\n
\n
\n
\n\n
\n
\n

現在の受付状況

\n

受付 3 件 ／ 評価中 2 件 ／ 判定待ち 1 件

\n
\n
\n

承認済みの累計

\n

7 件 ／ 工期 +3 週・費用 +8,400 千円

\n
\n
\n

この手順を通さない変更

\n

ありません。文言の修正も台帳に載せます

\n
\n
\n
\n
\n", "url": "https://design-vault.pages.dev/designs/change-request-flow-gates/pattern.html", "fonts": [ "https://design-vault.pages.dev/designs/change-request-flow-gates/font.css", "https://design-vault.pages.dev/designs/change-request-flow-gates/font-0.woff2", "https://design-vault.pages.dev/designs/change-request-flow-gates/font-1.woff2", "https://design-vault.pages.dev/designs/change-request-flow-gates/font-2.woff2" ] } }, "urls": { "ja": "https://design-vault.pages.dev/designs/change-request-flow-gates", "en": "https://design-vault.pages.dev/en/designs/change-request-flow-gates" }, "notesMarkdown": "## この構成について / About this pattern\n\nスコープを合意した次に必ず要る、変更要求の扱いを取り決める版。**`pattern.html` が版そのもの**で、\n`cover.png` と frontmatter の寸法はどちらもそこから機械的に出している。編集するのは `pattern.html` だけ。\n\nThe page that always follows a scope agreement: how change requests get handled. `pattern.html` is\nthe artboard itself; both `cover.png` and the measurements come from it, so the three cannot drift apart.\n\n### Techniques\n\n- 5 段を等幅にする。段を大小に振ると、どの段で時間を使うかが幅の話になり、書いた営業日と矛盾する\n- 段の間は 34px の空きトラックにして、そこへ山形を置く。矢印を線で引くと、線の意味を説明する時間が要る\n- 下端に「現在の受付状況」を固定で置く。取り決めだけの紙は運用されず、件数が載ると台帳が更新される\n\n### Apply to\n\n- 要件定義の冒頭で交わす変更管理の取り決め、キックオフ資料\n- 障害対応のエスカレーション手順（段を「受付・切り分け・判断・復旧・報告」に読み替える）" }