Convert to Newsletter
Forward or attach your article, blog post, or report. Optionally specify your audience and style. Get a complete newsletter edition back.
Draft an email
Subject
Fwd: Blog post - Why remote teams lose institutional knowledge
Can you turn this into next Tuesday's newsletter? Our subscribers are mostly mid-level managers at tech companies.
---------- Forwarded message ---------
On Thursday, March 6, 2026, Aiden Marsh <aiden@thinkerloop.com> wrote:
Here is the final draft of the blog post on remote knowledge loss. It ran a bit long at 2,800 words but the data is strong.
Remote work solved the commute problem but created a knowledge problem. When your team is distributed, institutional knowledge — the unwritten rules, the context behind decisions, the shortcuts that save hours — stops transferring naturally. A 2026 survey of 1,200 engineering managers found that 67% reported significant knowledge loss within 18 months of going fully remote.
The three main failure points: onboarding (new hires absorb 40% less tacit knowledge remotely), decision context (teams re-debate settled questions because no one remembers the original reasoning), and crisis response (the person who knows how to fix it is offline and no one documented the process).
Most companies respond with more documentation. But documentation is a lagging indicator. By the time something is written down, the knowledge has already been lost and rediscovered the hard way...
[article continues for 2,800 words]
Aiden Marsh
Thinkerloop Research | Head of Content
---------- Forwarded message ---------
On Thursday, March 6, 2026, Aiden Marsh <aiden@thinkerloop.com> wrote:
Here is the final draft of the blog post on remote knowledge loss. It ran a bit long at 2,800 words but the data is strong.
Remote work solved the commute problem but created a knowledge problem. When your team is distributed, institutional knowledge — the unwritten rules, the context behind decisions, the shortcuts that save hours — stops transferring naturally. A 2026 survey of 1,200 engineering managers found that 67% reported significant knowledge loss within 18 months of going fully remote.
The three main failure points: onboarding (new hires absorb 40% less tacit knowledge remotely), decision context (teams re-debate settled questions because no one remembers the original reasoning), and crisis response (the person who knows how to fix it is offline and no one documented the process).
Most companies respond with more documentation. But documentation is a lagging indicator. By the time something is written down, the knowledge has already been lost and rediscovered the hard way...
[article continues for 2,800 words]
Aiden Marsh
Thinkerloop Research | Head of Content
.svg)
What is via.email?
AI agents that each lives at an email address. Just send an email to get work done. No apps. No downloads.
.svg)
How to use?
Send or forward emails to agents and get results replied. Try it without registrations. Join to get free credits.
Is it safe?
Absolutely, your emails will be encrypted, deleted after processing, and never be used to train AI models.
More power?
Upgrade to get more credits, add email attachments, create custom agents, and access advanced features.
Make email work for you.
Your first agent awaits - just one email away.
Try for free
join@via.email
Type name in subject and send.
