What does a brittle strategic or operational dependency look like? It makes a plan easy to disrupt and hard to restore. One vendor, analyst, tool, or approval may carry too much weight. Yet one weak link is only one possible cause.
Quick check
Is the backup actually independent?
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 shape: a chain with one weak link
One weak link is a common shape. A plan may rely on one supplier for a key part. A control may rely on one analyst and one spreadsheet. If that link fails, work may stop or become unreliable. The impact depends on timing, demand, and recovery options. Another supplier or reviewer can help, but both may share the same weakness.
A launch plan depends on one vendor for a custom part. There is no approved substitute. A late delivery could delay the launch, but the result depends on stock, timing, and other recovery options.
A compliance control requires one analyst to update a spreadsheet each Friday. The risk may involve access, review, documentation, or absence. Seniority and a weekly schedule do not create the weakness by themselves.
The common mistake: misdiagnosing what the actual dependency is
The main mistake is naming a cause too soon. A manual task is not always brittle. One person may also be enough for a low-impact task. Risk depends on likely failures, their effects, and recovery time. Calling it "volatile because it happens every Friday" confuses frequency with change. The schedule may still matter if a missed run delays a required report.
First, map the people, tools, data, suppliers, and approvals involved. Then test what happens when each part fails. Check whether backups are truly independent and ready to use. A second vendor may use the same factory. A second reviewer may lack access. The right response may include prevention, detection, recovery, or risk acceptance.
Try it yourself
Map Rowan's Friday compliance control
Practice scenarios
Practice using brittle in situations like:
- spotting a dependency that could cause major delay or weak recovery
- naming the person, vendor, tool, approval, or shared source at risk
- testing backups before proposing a vendor, reviewer, or process change
Useful practice phrases:
- "This plan depends on one [vendor/analyst/reviewer], and recovery may take two weeks."
- "The concern is not seniority or frequency; it is the impact of a missed step."
- "We should test whether a second [vendor/reviewer] can provide a real backup."
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 →A brittle dependency can be a weak link, but it can also be a weak system.
Name the failure, its impact, and the recovery path before choosing a fix.