Brittle and unstable can both describe a risky system. Yet they point to different flaws. Use "unstable" when something lacks steadiness or may change without control. Use "brittle" when something may break instead of adapting under stress. A system can have either flaw or both.
Quick check
Erratic output or sharp load failure?
You know "Brittle" well.
Keep going with the full learning path — more workplace contexts, related expressions, and practice using it yourself with feedback.
Continue with "Brittle" →There's more to "Brittle" than it seems.
You've got part of it, but the full learning path goes deeper into its nuances, workplace contexts, and when it sounds natural — then gives you practice using it yourself.
Learn "Brittle" in depth →The test: unsteady behavior, or failure under stress?
Something brittle may look "stable" in normal use. Stress can expose its weak ability to adapt. An unstable system may already swing, fail, or change in ways the team cannot control. However, "unstable" does not always mean constant or random change. "Brittle" also does not promise one clear breaking point.
A warehouse system works at 1,000 orders a day but deadlocks at 1,050. Call it "brittle" if the point is that it cannot adapt to added load. Call it "unstable" if its behavior or output also becomes hard to control. The evidence, not the number alone, decides the label.
Calling every load-related failure "unstable" may imply unsteady behavior that the evidence does not show. Calling it "brittle" may be more exact when a small stress causes a sharp failure.
The common mistake: treating the risks as opposites
The common mistake is to treat the words as exact opposites. A repeatable load failure is good evidence of "brittleness," but the threshold need not be single or easy to find. "Instability" is also wider than continuous fluctuation. It can mean that a state, service, or result is not secure or steady.
The choice affects the next question, but it does not prescribe "one fix." An unstable service may need monitoring, diagnosis, or control work. A brittle service may need load tests, design changes, or safer fallbacks. One test or fix may not be enough. State the observed behavior before you recommend action.
Try it yourself
Describe Mosaic's fragile sensor parser
Practice scenarios
Practice using brittle in situations like:
- deciding whether evidence shows unsteady behavior ("unstable") or poor adaptation under stress ("brittle")
- checking whether "unstable" overstates a repeatable load failure
- describing a system that's calm in normal use but breaks under added load
Useful practice phrases:
- "That's brittle, not unstable -- it stays steady in normal use, then fails under added load."
- "It's not fluctuating, it's brittle -- stress exposes its weak ability to adapt."
- "The system may be unstable; let's document the changes before we choose a fix."
Want to actually use "Brittle" naturally at work?
Understanding it is one thing. Practice its nuances, see how it works in real workplace situations, and use it yourself with feedback.
Start the "Brittle" learning path →"Unstable" describes a lack of steadiness or control. "Brittle" describes a tendency to break under stress.
The risks can overlap, so describe the evidence and avoid promising a simple fix.