The instant you copy a document and paste it, the information starts going stale. The source changes, the copies don't. Today we unpack the 'component' principle that keeps knowledge alive.
If you've ever shared a document at work, you know this scene. You send a file by email. A few days later one number changes. You send an updated version. Now half the team is on v1, half on v2, and the first five minutes of the next meeting get burned asking, "which one is current?" This tiny chaos repeats in almost every office, almost every day.
Let's slowly unpack the cause and the fix. This isn't about one specific product. I want to give you a principle that will keep working no matter which collaboration tool shows up in the next 10 years.
Start here. The instant you copy information and paste it somewhere, that information begins to rot. There is no connection between the original and the copy. You can change the original, the copy won't know. The copy is a snapshot from that one moment. Time passes, the original evolves, the copy stays frozen. That is how knowledge quietly dies.
The problem hides when it's one document. It shows up when documents grow to 20, 50. The same table is sitting in four places, and nobody knows which copy holds the real latest number. From that point on, half of every meeting gets eaten by "which one is right?"
We already know this principle everywhere else in life. Your bank app shows your balance in real time. When a friend updates their chat profile photo, yours refreshes automatically. Map apps pick up a new road closure and reflect it on your screen within 10 minutes. The sense that "when the source changes, my view changes" is already built into us.
But somehow, in front of work documents, that sense vanishes. We still copy, attach, paste. The reason is that our document tools were designed long ago. Word, Hangul, Excel, email — they all run on "files." A file is, by definition, a thing that gets copied.
One recent product tackles this head-on. Microsoft Loop, launched November 2021. It looks like Notion at first, but the core idea is different. The word Loop keeps pushing is component.
A component is just "a small piece of information that stays connected." A table, a checklist, a paragraph. Make one inside Loop, then paste it into a Teams chat, an Outlook email body, and a Word document. But the key point is that this isn't a copy. Those four places hold the same table, and each of them is a window onto one original.
If someone edits the table inside the email, the chat version and the Word version change immediately too. Edit it inside the Word document, the other three refresh at once. One edit, four simultaneous updates. The real latest is in all four places at once.
Think of a neighborhood restaurant. The pasta price is changing. A master menu hangs on the kitchen wall, and four paper menus sit on the tables outside. The chef edits the master, but the four paper menus stay the same. Somebody has to walk around and rewrite each one by hand. Four manual updates. Miss one, and the customer orders at the old price, and the register becomes a fight.
Now replace those paper menus with small tablets. The chef changes the master once. All four tablets update at the same instant. One edit, four updates. The manual work vanishes.
Loop's component is exactly that tablet menu. It looks like the same table appears in four places, but each one is only a screen reflecting one original.
Let's compare three ways of sharing the same "quarterly revenue table" with four teammates.
| Method | Updates per change | Chance of broken sync | Where's the real latest |
|---|---|---|---|
| Email attachment (file copy) | 4 per change | 70% | Nobody knows |
| Shared link (same document) | 1 per change | 20% | One place |
| Component (Loop-style) | 1 per change | near 0% | All four, at once |
Email-attach mode creates 4x the work every time someone edits. Sync risk climbs to 70%. Pile this up for a year and the team has no idea which number is real. The component approach edits once and auto-refreshes all four, with near-zero drift.
We have spent way too much of our working lives managing copies.
This is the aha moment of today's essay. The time to copy, the time to hunt for the latest version, the time wasted asking "which one is right?" — all of that disappears.
So what should you change? Switching tools is fine, but first make one question a habit.
"Should this information also change on other people's screens when it changes?"
If the answer is yes, this is a component. Don't copy-paste it. If the answer is "no, a frozen record is enough," then a copy is fine. Training yourself to split these two is the whole of component thinking.
Concrete example. I run a project with a 20-item to-do list.
Old way: I make a Word file called "project plan.docx" with 20 checklist lines. I email it to 5 teammates. When one of them finishes an item, my document doesn't know. Every Monday, 5 people email me "mine is done," and I retype updates into the master. 30 minutes of manual work per week.
New way: I build the checklist as a Loop component and paste it into the team chat. I paste the same component into the project Word document. When a teammate taps a checkbox in chat, the checkbox in the Word document flips too. I do nothing, and the master stays current. 0 minutes per week.
Those 30 minutes become 2 hours per month, 24 hours per year. But the bigger win isn't the time. It's that the question "where is the real state?" just disappears.
You don't need Loop specifically. Notion has something similar. Google Docs has "smart chips" that behave the same. Tools change, principle holds.
1. When making new info, ask: "frozen record, or living info?"
2. If living info, make it a component (or a link, or a smart block)
3. When placing it elsewhere, use "embed/link," not "copy"
4. Keep one original location; the rest are just "windows onto it"
5. Once a week, sweep for stale copies and delete them
Five lines, that's all. Especially steps 2 and 3 — if they become habit, life changes. Since I've held this rule, I almost never get asked "where is the latest version?" by teammates anymore.
One sentence summary: Copies go stale. Components grow with you. Changing your unit of information from "file" to "component" is the core of knowledge management for the next 10 years.
The tool names will keep changing. Microsoft Loop may disappear. Notion may fade. But whatever shows up next will carry the same principle, because this isn't a tool problem — it's the nature of information. Living information lives in one place and is seen from many. Copying it in many places kills it. Tools change. Principles don't.
Three words to remember — One source. Many windows. Auto sync.