Vague Project Brief Warning Signs¶
Use this page when the project exists mostly as loose intent, not clearly defined work.
This is a precheck for projects where ambiguity is already shaping the risk profile before pricing or kickoff.
What This Risk Usually Looks Like¶
Broad goals without a concrete deliverable¶
Success described as direction rather than outcome¶
Missing dependencies, assets, or operating assumptions¶
Major details deferred until after agreement¶
Why This Becomes Dangerous Before Commitment¶
Estimation becomes fiction¶
A vague brief pushes you to commit to cost or time before the work can be judged cleanly.
Scope expands through clarification debt¶
The missing definition does not disappear. It reappears later as rework, debate, or loss.
What Not to Do Next¶
- do not convert ambiguity into false certainty
- do not treat urgency as proof that the project is ready
- do not assume you can stabilize scope after fixed commitments are made