Skip to content

Projects

Stop asking how the prototype is going.

A percentage somebody felt was about right. An approval buried in an inbox. A fixture nobody chased until the day of the build. Projects keeps all three on the same record as the part.

  • 12Active cards
  • 4Stuck or idle
  • 7Released this quarter
  • 9.4Avg days in phase

Needs attention

OKA-20020Vex9 Interceptor9d idle
OKD-10021Canopy Latch Bezel6d over
OKD-10009Panel Bracket7d idle
OKA-20013Landing Gear Assembly3d over

Programs

Product Roadmap12 products · 5 phasesOpen board
Product Revision6 products · 3 phasesOpen board
Job Shop4 products · 2 phasesOpen board

You

Scan the board once a week and see which products have stopped moving.

Gauge

Counts idle days and flags every product past its phase goal, so the stalled ones find you.

Drawn screens with demo data. Pick a card on the board to load it into the cockpit.

Three things that go wrong without this

  • The number nobody believes

    A status that reads ninety percent for three weeks is a guess with a decimal point. Here the bar fills from the items actually checked off, and the caption under it is that count, so when somebody asks you can open the thing the number came from.

  • The approval you cannot find

    Name the reviewers on the phase that needs them. Gauge keeps who decided, what they decided and when, one line per approver, so a year later the answer is not somebody's memory of a hallway conversation.

  • The fixture nobody chased

    Tooling, and the parts blocking a release, sit on the project overview. The thing that will stop the build is visible while there is still time to do something about it.

  • You define the phases, per program, from a template you can edit
  • A project's BOM is a tree you can cost, build and release
  • Every part in a project holds its own drawings and files
  • Parts a project holds are locked to it unless another product is linked through a dependency or its tooling

Bring one live program to the demo

Request a demo