Project Name:
Client:
PM:
Diagnostic Date:
Complexity Rating (RYG):
Total Score:
1. BUSINESS OBJECTIVE (What are they actually trying to achieve?)
Summarize in 2–3 sentences.
2. SCOPE OVERVIEW (Plain English)
Top-level description of what we are building or delivering.
3. CRITICAL OUTCOMES (90-Day Success Window)
What must be true 90 days after this project launches?
4. CONSTRAINTS (Budget, Timeline, Access, Internal Limits)
- Budget Range:
- Timeline Expectation:
- Client Resources Provided:
- Technical or Legal Constraints:
5. STAKEHOLDERS & DECISION AUTHORITY
- Decision Maker(s):
- Stakeholders:
- External Vendors / Tools / APIs:
- Known Approval Bottlenecks:
6. COMPLEXITY SCORING (RYG)
Score each category 0 (Green), 1 (Yellow), or 2 (Red).
(PM fills this out inside TeamWork custom fields or inline below.)
| Category | Score | Notes |
|---|---|---|
| Integrations (0–2) | ||
| Requirements Clarity (0–2) | ||
| Content Readiness (0–2) | ||
| Stakeholder Complexity (0–2) | ||
| Technical Risk (0–2) | ||
| Timeline Realism (0–2) | ||
| Budget Alignment (0–2) | ||
| Client Discipline / Reliability (0–2) |
Total Complexity Score:
Complexity Rating: ☐ Green (0–3) ☐ Yellow (4–8) ☐ Red (9+)
7. RISKS & UNKNOWN VARIABLES
Top 3 Risks:
1.
2.
3.
Top 3 Unknowns / Assumptions:
1.
2.
3.
8. REQUIRED PRE-SPRINTS BEFORE PRODUCTION
(Select or add the ones required.)
☐ Content Sprint
☐ Technical Discovery Sprint
☐ Messaging Strategy Sprint
☐ Architecture Sprint
☐ SEO Alignment Sprint
☐ UX/UI Wireframing Sprint
☐ MVP Definition Sprint
☐ Integration Validation Sprint
9. CLIENT READINESS (Checklist)
☐ Single decision maker identified
☐ All stakeholders documented
☐ Content/Assets inventory complete
☐ Access credentials provided (CMS, APIs, hosting, domains)
☐ Brand guidelines available
☐ Client responsibilities communicated
☐ Approval process confirmed
☐ Timeline risks discussed
10. WHAT REQUIRES MATT’S INVOLVEMENT?
☐ None
☐ Diagnostic Review Only
☐ Early Architecture / Strategy
☐ Technical Scoping
☐ High-Risk Oversight
Details:
11. PM SUMMARY (1-Page Executive Explanation)
This is the version Matt skims. It needs to be ruthless, concise, and factual.
- What we’re doing
- Why it matters
- How hard it will be
- Where things will break
- What must happen first
- How the team will run it
- What Matt needs to touch (if anything)
12. NEXT STEPS & TEAM ASSIGNMENTS
Before kickoff:
Team Assignments:
- PM:
- Strategist:
- Developer:
- Designer:
- QA:
Kickoff scheduled:
Pre-sprints scheduled:
Estimated production start: