Assessing red flags
Use this checklist during project reviews, at the end of each sprint, or whenever something feels off. The goal isn't to catastrophise — it's to surface issues early when they're still manageable.
Scope & requirements
- [ ] Is the scope clearly documented and signed off?
- [ ] Have there been any undocumented additions or changes?
- [ ] Do all team members have the same understanding of what's in and out of scope?
- [ ] Are there any requirements that are still undefined or unclear?
Timeline & delivery
- [ ] Are we on track against the project plan?
- [ ] Have any milestones been missed or are at risk?
- [ ] Is there sufficient buffer in the schedule?
- [ ] Are all external dependencies on track?
Budget & resources
- [ ] Are we tracking within budget?
- [ ] Are there any unplanned expenses or resource needs?
- [ ] Is the team appropriately resourced for upcoming work?
- [ ] Are any team members overloaded or under-utilized?
Client & stakeholder health
- [ ] Is the client responsive and engaged?
- [ ] Are approvals happening in a timely manner?
- [ ] Is there any ambiguity about who has sign-off authority?
- [ ] Are stakeholder expectations aligned with what we're delivering?
Team health
- [ ] Is the team communicating openly?
- [ ] Are any team members showing signs of burnout or disengagement?
- [ ] Are blockers being surfaced and resolved quickly?
- [ ] Is there psychological safety to raise concerns?
Technical & quality
- [ ] Is the technical approach still sound?
- [ ] Are there any unresolved technical risks?
- [ ] Is QA keeping pace with development?
- [ ] Are there any integration or dependency issues?
Newsletter
Get more like this in your inbox
Sharp opinions on operations, systems, and the psychology of how work gets done. No fluff. Unsubscribe anytime.
