Mostly about building products, healthcare tech, and lessons learned along the way.
Loading articles
The Death of Institutional Memory: Why I'm Building Atlas (And Why It Matters) — Clint Johnson
The Death of Institutional Memory: Why I'm Building Atlas (And Why It Matters)
Every resignation takes a piece of the organization nobody wrote down. Org charts capture hierarchy, not the relationship networks that keep things running. A different approach to preserving institutional knowledge before it walks out the door.
Documentation fails for tribal knowledge because the knowledge is relational, contextual and always changing, so manuals and SharePoint sites go stale.
Map the dependencies behind a process, like who must finish before whom and who has backup access, because those relationships are what break when someone leaves.
Capture knowledge through conversation, the brain dump someone gives when training a replacement, instead of asking people to write process docs.
Business knowledge is mostly relationships, exceptions and intuition built over years of doing the work. Process manuals go unread, SharePoint sites go stale once published, and training videos capture steps but miss the nuance.
What is Atlas by Clint Johnson?
Atlas is software that maps the relationship networks behind how a business runs. People explain how their work happens in conversation, and Atlas turns that into a living map of steps, owners, dependencies and what breaks when key people are unavailable.
How does tribal knowledge loss differ between startups and enterprises?
At startups, one person leaving can paralyze entire functions. At enterprises the damage is quieter: processes slow down, quality drops, and new hires take months to become productive.
What does mapping institutional knowledge look like for month-end close?
It records dependencies, not only tasks. For example, inventory has to finish before depreciation can run, a variance over $10K triggers a call to a specific bank contact, and only two people have backup access to reconciliation when the usual owner is out.
I've spent my career working in tech, product, strategy, and combinations of those. I've helped build startups, and I've worked inside very large enterprise organizations. No matter the variables, one thing stays constant: the battle with tribal knowledge.
At a 50-person startup, it was the founder who knew which server would crash under load and the exact sequence of commands to restart it. At a Fortune 500 company, it was the accounts payable clerk who knew which vendors would accept late payments without penalty. Different scale, same problem.
The knowledge that runs businesses lives in people's heads. When those people leave, chaos follows.
When your key employee says "I quit" and takes 15 years of undocumented processes with them
The Pattern Across Every Organization
Last month, I watched a CFO nearly break down during our demo call. "My controller just gave notice," she said. "Fifteen years with us. Everything about our month-end process lives in her head, and I have no idea how we're going to manage without her."
I've heard variations of this story dozens of times now. The details change — manufacturing, healthcare, professional services — but the crisis is identical. The shortcuts, the relationships, the "call Mike when the system breaks" wisdom exists only as tribal knowledge that was never captured anywhere.
What's interesting is how this problem scales. At startups, one person leaving can paralyze entire functions. At enterprise companies, it's more subtle: processes slow down, quality drops, new hires struggle for months to become productive. The fundamental issue is the same. Critical knowledge is trapped in individual minds.
Why Documentation Never Works
Every organization I've worked with has tried the obvious solution: document everything. Process manuals that nobody reads. SharePoint sites that go stale the moment you publish them. Training videos that capture the steps but miss the nuance.
Business knowledge isn't really about processes. It's about relationships, exceptions, and intuition developed over months or years of doing the work.
How do you document the fact that Jennifer in AP has a contact at the bank who can expedite critical payments? How do you write down "Sarah's the only one who really understands intercompany eliminations"? How do you capture the dozen unofficial workarounds that everyone uses but nobody talks about?
You can't. That knowledge is relational, contextual, and constantly evolving. Documentation captures snapshots, but businesses are movies.
The Network Insight
The breakthrough came from watching patterns across all these organizations. I started seeing businesses differently — not as hierarchies or processes, but as networks.
Complex webs of relationships between people, systems, information, and outcomes that constantly shift and evolve. The org chart shows who reports to whom, but the real work happens through invisible connections that span departments, roles, and systems.
Take something as simple as month-end close. On paper, it's a sequence of tasks. In reality, it's a complex dance of dependencies:
Tom needs to finish inventory before Sarah can run depreciation
AP rushes final invoices while accounting pulls GL data
If the variance exceeds $10K, Jennifer needs to call her contact for an emergency transfer
When Mike's out, only two other people have backup access to the reconciliation system
These aren't process steps. They're relationships. Relationships can't be documented; they can only be mapped.
The Realization That Changed Everything
After my last company, I planned to take time off. Maybe do some consulting. Instead, I kept encountering the same crisis everywhere I looked.
A manufacturing company where the production scheduler's vacation could shut down operations. A family business where the founder's knowledge was the single point of failure. A tech company spending hundreds of thousands on AI tools that couldn't answer basic questions about their own operations.
The pattern was clear: successful businesses were becoming victims of their own knowledge distribution. The specialization that made them efficient was making them fragile.
We needed a fundamentally different approach. Not better documentation or project management, but a way to capture and preserve the network of relationships that runs businesses.
Building Atlas
Atlas started from a simple insight: what if we could map these invisible networks? Not with complex diagrams that nobody maintains, but with something as intuitive as explaining how your day works.
Instead of asking people to document their processes, we ask them to explain how things really work. Through conversation. Through the kind of brain dump that happens when someone's training their replacement with two days' notice.
"Our month-end close starts when IT runs the extract. Then accounting pulls the GL data while AP rushes final invoices. Sarah handles intercompany stuff — she's the only one who really gets it — while Tom deals with accruals. If anything's off, we call Mike because he built half these reports..."
The software converts that stream of consciousness into something different: a living map of how your business operates. Not just the steps, but the connections. Not just what happens, but who does it, when it depends on something else, and what breaks when key people are unavailable.
Beyond Process Documentation
What excites me about this approach isn't just solving knowledge transfer — though that's significant. It's what becomes possible when businesses can see how they work.
Imagine onboarding that doesn't take months because new hires can see exactly how they fit into the network of relationships. Imagine bottlenecks that become visible before they cause delays. Imagine AI that helps with your work because it understands your specific context, not just generic best practices.
Imagine businesses that get stronger instead of more fragile as they grow.
The Great Knowledge Transfer
We're living through the largest knowledge transfer in business history. Boomers retiring with decades of institutional wisdom. Job tenure dropping to under four years. Remote work breaking the casual conversations where real learning happened.
The organizations that figure out how to capture and preserve knowledge networks will have an enormous advantage. The ones that don't will keep losing ground with every resignation, every promotion, every unexpected absence.
From my experience across startups and enterprises, scale doesn't matter. The fundamentals are the same: businesses run on relationships and tribal knowledge. The question is whether you can see those networks, understand them, and strengthen them before critical knowledge walks out the door.
What This Really Means
This isn't just about efficiency or risk management. It's about human potential.
In every organization I've worked with, I've watched brilliant people spend huge chunks of their time hunting for information, recreating knowledge that exists somewhere in the company, or waiting for the one person who knows how something works.
When that friction disappears — when knowledge flows efficiently, when relationships are visible, when expertise is accessible — people can focus on what humans do best: creative problem-solving, innovation, and building something meaningful.
That's not just better business; it's better work.
The Network Effect
What's particularly exciting is how this approach creates compound benefits. As more businesses build their knowledge graphs, patterns emerge. Best practices become shareable as templates. Industry insights become possible. The collective intelligence grows.
It starts with individual organizations recognizing a fundamental truth: businesses are networks, not hierarchies. Networks can be mapped, understood, and optimized.
The question isn't whether this will happen — the pressure from knowledge loss is too great, and the technology is already here. The question is whether your organization will be early to recognize how work gets done, or whether you'll keep losing critical knowledge until you're forced to change.
The companies that figure out how to see and strengthen their knowledge networks will compound their advantages for decades. The ones that don't will keep hemorrhaging wisdom with every resignation.
When people aren't constantly hunting for information or recreating knowledge that already exists somewhere in the organization, they can focus on what humans do best: creative problem-solving, relationship building, and pushing boundaries.
