Set up project workflow

Set up the Acme Website project workflow on the board: replace Doing with In Progress and split Review into Code Review and Content Review, add a QA Verification list before Done, and create automation that moves a card to Code Review when a Development checklist is complete. Name the workflow stage labels In Progress, Code Review, Content Review, QA, Blocked and attach them to the appropriate lists.

Before I show the workflow to Marcus and Jenna, make it easier for them to know where to drop work. Rename Doing to In Progress, split Review into Code Review and Content Review, add a QA Verification list before Done, and surface who owns each list in the list header. Flag any steps that will slow handoffs, like separate review queues or missing ownership.

I renamed Doing to In Progress and split Review into Code Review and Content Review. Marcus puts code in Code Review but Jenna puts content in Code Review too. I’m not sure whether to force separate cards or explain a rule. What’s the usual diagnosis here and what’s the best single rule to apply so both engineers and writers understand where to drop work?

Across several projects the same stall happens: engineers mark a feature ready but content and QA don’t pick it up for days. That loses velocity and makes deadlines slip. Which habit around list ownership, notifications, or acceptance criteria should I change to keep things moving at each handoff?