Is Your Content Like a Fungus?
When bad content gets in the way of good information architecture
I’m doing some Information Architecture (IA) work for a few different websites right now, and grabbed my copy of Communicating Design by Dan M. Brown to skim the chapter on content inventories. And I came across this quote:
Regardless of how tight a rein the content managers keep, sites tend to grow organically, and content springs up like a fungus.
It’s true. It’s so ridiculously true I can’t even express it properly. Because that is my life right now: to prune and prune and prune and prune and then step back and discover that while you were culling old content, three more pieces of bizarre content have spring up in their place.
I’m just brainstorming loosely, but I do think content doesn’t merely grow like a fungus; it itself can be fungal as well.
Here’s what I mean.
Good content can be described as useful, unique, and specific.*
- Useful: Does it actually say anything of relevance?
- Unique: Is the reader learning something new from it?
- Specific: Does the reader gain enough knowledge to solve their problem, or at least figure out their next step?
Now, I’m painting incredibly broad strokes there. There’s a case for repetition of certain key phrases, for example. But if there is such a thing as good, healthy content, there must be bad, fungal content as well.
Get Lisa Eldred’s stories in your inbox
Join Medium for free to get updates from this writer.
For the sake of the metaphor, good content is a farmer’s well-ordered fields. Fungal content is a lazy farmer’s fields, overtaken by mold and mushrooms. Fungal content kills the crops and thrives on the decay.
Fungal content is:
- Toxic: Not only is it useless, but it may actually impede understanding as well.
- Cloneish/clustered: Nearly identical content may appear in very similar formats in very close proximity.
- Sprawling: The content may be so generic that it defies a single taxonomy.
Now obviously, there’s a lot to be said about writing and editing in here (e.g. “Don’t write bad, repetitive content!”), but it’s also relevant to information architects: your work may be impeded by fungal content.
As a case in point, several of my colleagues and I recently ran a few card sorts on some existing content on our company’s website. As a content manager, I pride myself in keeping a tight rein on the content that gets published, and while I was grateful to see some of my assumptions confirmed, I was also humbled to see where quite a bit of content broke down and defied sensible categorization, or where incredibly outdated content led to user biases in sorting. Did we gain valuable insights from these card sorts? Yes, absolutely. Do we feel confidence in our results? Not even remotely.
Here’s my point, represented via a horrible misapplication of a quote from Jesus:
A bad tree cannot bear good fruit; nor can bad information be used to create a good taxonomy.
Or, in slightly less heretical terms:
If you are trying to force existing content into a new architecture, and the existing content is defying sane categorization, it might be time to burn the old, toxic fields down.





