Natural Collocations for Brittle at Work

Brittle describes something that may fail under stress: it may work now but break when a condition changes. Three language moves help make the claim clear: name the thing, the reason, and its degree.

Slot one: the noun -- what's brittle

Brittle often describes things that can fail under stress. Process nouns include workflow, handoff, and approval flow. Technical nouns include system, integration, automation, and test suite. It can also describe a plan, assumption, forecast, business case, or trust.

"The approval process is brittle because only one reviewer knows the exception rules."

In each case, the thing may need to hold up as working conditions change.

Slot two: the reason -- naming the dependency or the stressor

A clear reason names the exact dependency: "brittle because it depends on..." You can also name the stress condition. Common forms include brittle under pressure, under load, under stress, or brittle when demand spikes.

"The integration works fine in testing, but it's brittle under real traffic, because the retry logic was never load-tested."

Note the pattern. "Brittle under" pairs with a noun such as pressure, load, or stress. "Brittle to" and "brittle of" usually sound unnatural in this pattern.

Slot three: the grade -- how brittle, compared to what

Brittle works with degree phrases such as less brittle, more brittle, and too brittle to scale. The noun brittleness is generally uncountable. It often appears in analysis: "there's some brittleness in the process."

"The workaround is brittle -- it works today, but it's getting more brittle as traffic grows, so it needs to become less brittle before the next launch."

What doesn't collocate

Do not stretch "brittle" to any weak or poor thing. A meeting, salary figure, idea, or report may not have a failure structure. "The status meeting was brittle because half the team joined late" sounds unnatural. Lateness caused trouble, but it did not reveal this kind of failure point, and brittle is not the same as rigid. A process that rejects all exceptions may be rigid. A brittle process is at risk of failing under a condition.

Practice scenarios

Practice using brittle in situations like:

• naming a system, plan, or process and the exact dependency that makes it brittle
• describing a stress condition with "under" or "when," not "to" or "of"
• grading brittleness over time -- less brittle, more brittle -- instead of treating it as fixed

Useful practice phrases:

• "[X] is brittle because it depends on [dependency]."
• "[X] is brittle under [pressure/load/stress]."
• "[X] is getting more/less brittle as [condition changes]."

A claim about brittleness is more useful when you name what may fail, why, and by how much.

Without a reason, it may sound like a complaint, while a grade can show whether the risk is changing.