Tasks

Due dates should represent a commitment to a decision point or deliverable, not a vague aspiration. If every date is “ASAP”, the system trains people to ignore dates entirely.

Tie due dates to client-visible milestones where possible: IC dates, data room opens, exclusivity windows, and regulatory filing cut-offs.

Reserve “urgent” language for material risk or client-blocking items. Chronic over-labelling erodes attention when a real emergency appears.

Review weekly for tasks that slipped more than once — often the scope is wrong, not the owner’s intent.

When parallel tracks exist (legal, tax, model), make dependencies explicit in descriptions so owners know what can move independently and what must wait.

Surface cross-team dependencies in pipeline review so leadership sees systemic stalls, not isolated overdue rows.

Desk leads should scan overdue tasks in deal context, not as a global dump. Context tells you whether a slip is benign or a precursor to a client miss.