Assign action items

Assign action items from last week’s design review to specific people. Put the color contrast fixes on Raj, the icon updates to Mei, and the prototype polishing to Carlos. Add due dates: contrast fixes by Wednesday, icons by Friday, prototype by next Monday. Notify the assignees and the product manager, Hannah, and mark tasks as high priority only if they block the upcoming demo.

Before I assign these action items, make them easy to complete. For each task, add the exact file link, the acceptance criteria, and the person who must approve the change. Surface any dependencies—like engineering time—and flag anything that will block the demo. That way assignees know whether to do the work or escalate.

After I assigned action items with due dates, Raj and Mei acknowledged them but haven’t started and the demo is in five days. I’m worried they think the tasks are low priority or unclear. What are the likely causes and what immediate move gets the work started without escalating to a meeting?

We routinely see action items accepted after reviews but not completed before demos, which damages credibility with product and customers. Where are we losing time or ownership—assignment clarity, workload balancing, or follow-up—and what two changes to our assignment routine will stop these slips within the next two demos?