Projects · NPD
Route /npd/dashboard Flag npdEnabled

NPD

New product development tower — ideas, gates, launch — on NPD records that still respect Project when delivery starts.

Scroll to Flowcharts. Scenario: Scan NPD pipeline and open a gate.

Product process

Ideas to gates to launch — then a project

NPD is the product-development tower. When you start building, Project (and PO when used) becomes the delivery source.

Projects → NPD Route /npd/dashboard Org flag npdEnabled Project Manager · Executive · Admin

The job of this console

See pipeline health, open the stage that is stuck, and only then spawn delivery on a real project.

Seat at the table

PMs, executives, admins with npdEnabled. Delivery teams join after a project exists.

The working rhythm

Scan tower, drill a stage, decide, create Project when approved to build.

Moments that bring you here

Portfolio of products. A stuck gate. Launch week. After an idea is funded.

ⓘ
NPD is not Task
Ideas and gates are process records. Hours and capacity need Project / Employee.

Flowcharts

1 — Tower then stage

Read NPD health, open ideas or gates.

flowchart TD
  A[Open NPD] --> B[Read pipeline]
  B --> C[Ideas / gates / launch]
  C --> D{Approved to build?}
  D -->|Yes| E[Project / PO chain]
  D -->|No| F[Stay in NPD]
            
  1. 1
    OpenProjects → NPD.
  2. 2
    ScanPipeline KPIs.
  3. 3
    DrillIdeas, gates, launch.
  4. 4
    BuildProject when delivery starts.

Overview

NPD is product process. Delivery execution is Project → Task. Do not run timesheets on an idea id.

How to use

1. Stage first
Do not skip gates in a side deck as source.
2. Delivery later
Project list is execution.
3. Exec
Launch screen is go-to-market, not payroll publish.