Brittle and risky both flag a problem, but one is far more actionable than the other. Use "brittle" when you can name the exact structural dependency that would break something; use "risky" only when you genuinely mean broad, unspecified uncertainty -- "brittle" is the more precise, more actionable claim.
The test: can you name the exact dependency?
"Risky" tells a stakeholder something could go wrong without saying what or why; "brittle" names the exact dependency that would need to fail for the plan to break, which is the difference between a vague warning and an actionable diagnosis.
"The release process is risky because only Maya knows how to recover a failed deployment" becomes more precise as "The release process is brittle because recovery depends on one person's deployment knowledge" -- naming the exact mechanism instead of a generic risk label.
"Risky because adoption targets are hard to predict" is vaguer than "brittle because missing that adoption rate would break the whole plan."
The common mistake: settling for the vaguer word
"Risky" tells a stakeholder something could go wrong without saying what or why; "brittle" names the exact dependency that would need to fail for the plan to break -- the difference between a vague warning and an actionable diagnosis.
Want to learn "Brittle" in depth?
Lyra Practice teaches advanced non-native professionals the nuance of high-value expressions like this one, then has you practice using them in realistic work scenarios.
Start learning for free →Before writing "risky," it's worth asking whether you can actually name the dependency. If you can, "brittle" gives the reader something to act on. If you genuinely can't -- the uncertainty really is broad and unspecified -- then "risky" is the honest word, not a downgrade.
Practice scenarios
Practice using brittle in situations like:
- upgrading a vague "risky" claim into a named, actionable "brittle" diagnosis
- naming the exact person, assumption, or step a plan depends on before calling it brittle
- deciding whether a genuinely unspecified uncertainty should stay "risky" rather than forced into "brittle"
Useful practice phrases:
- "[X] is risky because..." -> "[X] is brittle because it depends on [specific dependency]."
- "Risky" tells you something could go wrong; "brittle" tells you what and why."
- "If I can't name the dependency, it's risky, not brittle."