DailyWF / Projects
Project Intake
Capture a proposed project before committing time or budget.
Project use
Use this to decide whether a proposed project deserves commitment, discovery, deferral, or rejection.
- Capture requester, problem, desired outcome, urgency, and affected parties.
- Check strategic fit, risk, cost class, capacity, and dependencies.
- Identify missing information before accepting the work as a project.
- Choose disposition: approve discovery, backlog, reject, merge, or clarify.
- Give the requester the decision and next visible step.
Expected output
A project record that states the decision, owner, boundary, dependency, next checkpoint, and evidence needed to continue.
Common failure mode
Accepting vague requests as projects because saying no feels slower.
Use notes
| Best trigger | Use before a project decision becomes expensive to reverse. |
|---|---|
| Evidence | Keep enough context to explain the decision later without reconstructing conversations. |
| Review point | Review when scope, stakeholder expectation, timing, risk, or ownership changes. |
Related pages
- Milestone ReviewCheck whether a project should continue, adjust, pause, or close.
- Project Intake ChecklistClarify a proposed project before commitment.
- Assumption LogTrack project assumptions before they become invisible sources of risk.
- Discovery BriefDocument early investigation before the project is formally approved.
- Lessons LearnedCapture reusable learning from project execution.
Use this with a tool
Find related documents, copy a checklist, or request a missing workflow.