IC — delivery standards

Purpose: Minimum bar for how ICs show up in delivery. Team-wide behavioral bar and growth levels: delivery team charter and delivery performance rubric. Also see good vs bad exemplars.


Linear hygiene

  • One Issue = one clear outcome; single assignee.
  • Link Issue → Project; use Project milestones for client-visible bundles.
  • Update status when blocked; don’t let Issues sit “In Progress” with no movement without a comment.
  • Prefer async updates that let CSO/SL cancel unnecessary meetings.

Communication

  • Internal: Clear, timestamped notes on Issues (what changed, what’s next, what you need).
  • Client-facing: Do not commit dates or scope in client channels without CSO alignment.

Quality

  • Follow SL / team review norms; fix root causes when the same defect class repeats.
  • Use AI to accelerate execution; don’t ship unreviewed or generic output as client-ready.

Canonical detail: Add or restore linear hygiene when a dedicated file exists.


Last updated: 2026-03-23