Status buckets help us tag specs in notion for their stage in the lifecycle.

Those emojis are Verbs, think of them as action driving a spec to it’s next stage.

The screenshot below is “left to right” model. This is how teams assist each other to get features out of the door.

Common patterns:

• spikes become outputs: tickets with a level of effort, a simple tech implementation, added to queue, up to project board.
• Product spec (use case, priority, mocks)
• Technical spec [diverge] (poke holes, pseudo code, technical docs, tickets)
• Kickoff [converge] (final blockers, gut checks, and sequencing)

Ticket from product —> tech breakdown —> groom weekly —> ship to release —> proceed to production