Product Management & Design Workflows

Streamline product planning, design handoffs, and launch processes with automated checklists and gates.

Definition of Ready (DoR) Checklist

Ensure every story meets quality standards before development begins. Place this checklist at the top of every story ticket.

Workflow Structure:

  1. Title: "Definition of Ready"
  2. Required Checkboxes:
    • Designs approved ✓
    • Acceptance criteria written ✓
    • API contract signed off ✓
    • Dependencies identified ✓
    • Story points estimated ✓
    • Technical approach reviewed ✓
  3. Blocker Trigger - Only then does the dev section unlock
  4. Notify Trigger - Tells #product-triage "Story is now ready for refinement/grooming"
  5. Change Assignee Trigger - Auto-assigns to development team lead

🎯 Quality Gate: Prevents incomplete stories from entering development, reducing rework and delays.

User Story → Sub-tasks Auto-creation

Product managers write high-level acceptance criteria as checklist items, which automatically convert into proper dev sub-tasks.

Workflow Structure:

  1. Product Manager Creates Checklist
    • Each acceptance criterion as a checklist item
    • Can include nested items for complex criteria
  2. Convert to Separate Issue - Each line can be converted
    • Turns into proper dev sub-task
    • Accurate summary and description auto-populated
    • Linked to parent story
    • Auto-assigned to appropriate developer
  3. Blocker on Parent - Story can't be closed until all sub-tasks are complete

Launch Checklist (Go/No-Go)

Comprehensive pre-launch verification ensuring nothing is missed before going live.

Workflow Structure:

  1. Nested Launch Checklist:
    • Feature flags on ✓
    • Rollback plan reviewed ✓
    • Monitoring dashboards ready ✓
    • Comms sent ✓
    • Support team briefed ✓
    • Documentation updated ✓
    • Legal/compliance approved ✓
  2. Blocker Between Sections - Ensures proper sequencing
  3. Final Notify Trigger - Posts launch announcement in #announce with one click
  4. Change Assignee Trigger - Transfers ownership to support team post-launch

🚀 Launch Confidence: Never miss a critical launch step with this comprehensive checklist.

Feature Planning & Refinement

Structure your feature planning process with clear gates and automated notifications.

Workflow Structure:

  1. Discovery Phase
    • User research completed
    • Market analysis done
    • Competitive analysis reviewed
  2. Blocker → Design Phase
    • Wireframes created
    • Mockups approved
    • Design system compliance verified
  3. Blocker → Development Planning
    • Technical approach defined
    • Story breakdown complete
    • Dependencies mapped
  4. Notify Triggers - Keep stakeholders informed at each phase

Best Practices

  • Always start stories with a Definition of Ready checklist to ensure quality
  • Use convert to separate issue to break down large stories into manageable sub-tasks
  • Implement blockers between planning phases to prevent premature progression
  • Configure notify triggers to keep all stakeholders informed throughout the planning process
  • Use launch checklists as templates that can be customized per feature
  • Leverage change assignee triggers to hand off work between product, design, and development teams