There is a kind of work whose value becomes difficult to see when we measure it by how far it travels.
A conversation may matter enormously to one person and produce nothing that can be counted afterward. An editor can spend an hour helping a writer understand why something isn't working and have no additional artifact to show for the hour. A reporter can spend years becoming familiar with a community before that accumulated context becomes important to a particular story.
None of this means the work is somehow purer because it remained small. It means reach and value aren't measuring the same thing.
I've become interested in that distinction because so much of modern work is organized around multiplication. If something is useful, we naturally ask how to make more of it, distribute it farther, automate it or reduce the amount of labor required for each additional person served.
Often that's exactly the right question.
Printing allowed one person's writing to reach people they would never meet. Radio extended a voice across a region. Software lets the same capability be used thousands or millions of times without rebuilding it for each person. A newspaper would be a strange institution if it regarded reaching more readers as evidence that something had gone wrong.
Scale can be extraordinarily useful.
It just doesn't scale everything.
Suppose I write an article and ten thousand people read it. The artifact scaled beautifully. Whatever relationship each reader forms with the article still happens individually. One person recognizes something useful in it, another disagrees, another misunderstands it, another skims the first two paragraphs and leaves, and most may never think about it again.
Increasing distribution multiplies encounters.
It doesn't make the encounters identical.
This becomes easier to see in work that depends heavily on context. A teacher can reuse a lesson, but the moment when a particular student finally understands something may depend on noticing exactly where that student is stuck. A physician can rely on knowledge developed across millions of cases while still needing to determine what is happening with the person in the room. A reporter can publish one story to an entire community while building the relationships that made the reporting possible through hundreds of conversations that never became stories themselves.
The scalable part and the non-scalable part can belong to the same work.
That changes the question. Instead of deciding that something either scales or doesn't, we can ask what scales cheaply, what scales with additional cost and what changes character when we try to multiply it.
Sometimes the answer is surprising.
Software can make a process available to thousands of people, but understanding an unusual failure may still require somebody to look closely at one case. A community directory can publish thousands of records through the same interface, while keeping those records trustworthy may depend on individual organizations noticing changes and telling us about them. A newspaper can distribute an edition widely, but the local knowledge contained in it accumulates through encounters that can't simply be duplicated by increasing server capacity.
The infrastructure scales differently from the relationships that feed it.
This is where optimization can become misleading. Once we've found something valuable, we tend to look for the repeated operation and remove whatever appears to prevent repetition. Sometimes that reveals unnecessary friction. Other times the apparent friction is where important information enters.
A conversation takes too long because the situation is genuinely ambiguous.
An editor asks another question because the first answer changed their understanding.
A customer doesn't fit the workflow because the workflow doesn't represent something about the customer.
A reporter keeps talking after obtaining the quote because the quote isn't the only reason for the co