The job of this console
Open the pending gate, review the packet, decide, and only then spawn a Project if the process says build.
Projects · NPD
NPD Gates
Stage-gate decisions on NPD items — process decisions, not leave approval and not project governance RAG.
Scroll to Flowcharts. Scenario: Pass or hold an NPD gate.
Stage decisions
Pass, hold, or kill — not a leave inbox
NPD gates are product-process decisions on ideas. They are not timesheet approval and not delivery governance RAG.
Projects → NPD gates
Route
/npd/gates
Org flag npdEnabled
Project Manager · Executive · Admin
Seat at the table
Executives and PMs. Employees do not vote here unless invited as reviewers.
The working rhythm
Queue of pending gates, decide, write the outcome on the NPD record.
Moments that bring you here
Stage-gate meeting. Funding hold. Kill a zombie idea. Pass to launch.
ⓘ
Different approval family
My Approvals is leave/time/access. Project governance is RAID. This is NPD process.
Flowcharts
1 — Decide a gate
Review the packet, pass/hold/kill.
flowchart TD
A[Open NPD gates] --> B[Open pending]
B --> C[Review packet]
C --> D{Decision}
D -->|Pass| E[Next stage / launch / Project]
D -->|Hold| F[Return to idea]
D -->|Kill| G[Close idea]
- 1OpenProjects → NPD gates.
- 2ReviewIdea packet.
- 3DecidePass, hold, kill.
- 4NextLaunch or Project.
Overview
Gates are NPD process. Universal approvals are HR/time domains. Project governance is delivery RAID.
How to use
1. Packet on the idea
Do not decide only in email.
2. Kill cleanly
So the tower does not show zombies.
3. Build
Project list after pass-to-build.