Email Was Better Than We Remember
For a long time, email was the place where serious discussions happened. Proposals, technical discussions, project updates, introductions, decisions — all of it lived in email.
And as a service, email was not an anachronism — it kept evolving and while a lot of my younger readers may associate email mainly with Gmail, I, as a person who remembers The Bat and Pine, can confirm — email kept changing to remain relevant.
But we wanted more. We wanted live communication. We wanted some dedicated place where companies could communicate. Workplace messaging apps arrived looking faster, simpler, and more human. And in many ways, they were.
But while replacing email, we may have also thrown away some of the things it did best.
Email made people slow down
Writing an email usually required at least a small amount of thought.
You had to decide what the message was about. You had to write a subject. You had to choose who should receive it. Then you had to explain the situation well enough for someone else to understand it without standing next to you and you knew that once sent, you wouldn’t be able to edit or delete it.
That friction was useful. It encouraged people to provide context. Longer replies were normal. Disagreements could be explained instead of compressed into three sentences, five reactions, and a GIF.
Email was asynchronous, but it did not feel disposable. You could send a detailed message, continue working, and expect the other person to read it when they had time to think. There was no expectation that every message needed an immediate response. That is very different from modern workplace chat, where even when nobody says a response is urgent, the little green dot next to the avatar quietly suggests otherwise.
Email threads gave conversations a shape
Email threads were imperfect, but they gave discussions a basic structure.
There was a subject. There was an original message. There were replies. There was a visible history of how the conversation developed.
When someone joined the discussion later, they could usually read the earlier messages and understand what had happened. Not always easily, but the context was there.
This mattered because workplace conversations are rarely just about the latest message. A decision may depend on something mentioned three days ago. A technical choice may only make sense when you understand the original limitation. A disagreement may look irrational until you see the earlier assumptions.
Email threads preserved that history better than we tend to remember. They also created a durable record. Months later, you could search for a person, subject, phrase, or attachment and often find the full conversation.
Again, it was not elegant. But it worked.
Of course, email had real problems
People did not abandon email for no reason. Adding someone to an existing discussion was awkward. Removing someone was even stranger. Someone could reply to the previous email and the thread would split silently.
Then there was quoting
information
way to consume
a very convenient
And that was not
Eventually the message looked like an archaeological dig where every previous civilization had left another layer of angle brackets behind. Some email clients helped a bit, but it was not enough.
And the biggest issue of all — inboxes became dumping grounds for everything. Real conversations sat next to marketing emails, password resets, automated reports, calendar notifications, shipping updates, receipts, and messages from systems that should never have been allowed to send email in the first place.
Email was not just a communication tool anymore. It became the universal output tray of the internet. That made it exhausting.
Chat apps solved the most visible problems
Slack, Teams, and similar tools felt like a relief. You did not need a formal subject. You did not need to think carefully about recipients. You could drop a message into a channel, tag someone, and move on.
Quick questions became genuinely quick. Conversations felt more casual. Images, links, reactions, files, and short updates all fit naturally into the same interface.
For day-to-day coordination, this was clearly better. The problem is that the same tools also became the default place for serious discussions. A conversation about an important product decision now looks almost identical to a conversation about where to order lunch.
Chat reduced the cost of starting a conversation, but it also reduced the pressure to finish one properly.
We replaced correspondence with a stream
Email treated communication as correspondence. Chat treats communication as activity. That difference matters.
In email, a message was usually written as a complete thought. In chat, communication happens in fragments. John writes a sentence. Emily replies while the John is still typing. Victor adds a side question and a Tyler answers that question instead. Then the original topic returns twenty messages later, after two jokes, a screenshot, and a discussion that should probably have been in another channel.
This feels natural in the moment. It feels active. People are communicating. But when someone tries to understand the discussion later, the experience is very different. They are not reading a conversation. They are reconstructing one.
But what if part of the discussion was in Slack, another part happened on a call, someone sent an email afterward, a decision was mentioned in a meeting, but the meeting notes only say “discussed next steps”? Then six months later, everyone wonders why nobody can explain what was decided.
The problem was not the basic idea of email
Email became unpleasant, but its core model was not necessarily wrong. The basic idea was simple:
- A conversation has a topic.
- It has participants.
- It has a visible history.
- People can respond thoughtfully and asynchronously.
- The discussion remains available later.
Those are good qualities. The weaknesses were mostly in the mechanics around that model. Participant management was awkward. Quoting was ugly. Threads became difficult to navigate. Inbox organization was primitive. Important discussions were mixed with endless automated noise.
Instead of improving those parts, workplace communication largely moved toward systems built around speed and immediacy. That solved one set of problems and created another. Now we have tools that are excellent at delivering messages, but not always very good at preserving the value of the conversation.
Not every conversation should feel like chat
Chat is useful. I am not arguing that companies should return to sending emails for every quick question. But some conversations need more structure. Discussions about strategy, architecture, product direction, hiring, policies, customer problems, or major decisions often need time, context, and clear participation. They should not be forced into the same format as quick coordination.
A useful communication system should make it easy to distinguish between “Can someone check this?” and “We need to think this through”. Those are different types of conversations, but most workplace tools treat them almost the same.
What I wanted to preserve in VOSTORQ
When I started building VOSTORQ, I kept coming back to the strengths of email threads.
A serious discussion had a topic. It could be addressed to a defined group of people or broadcast across the whole company or one of its departments. Everyone could see the history. People had enough space to explain their thinking instead of constantly reacting to the latest message.
I did not want to recreate email, but I did want to preserve the idea that an important company conversation should have structure. It should be easy to add the right people. The context should remain clear. Replies should connect naturally to the point being discussed. The conversation should stay useful after everyone stops actively participating in it. And most importantly, it should become part of the company’s knowledge instead of disappearing into a stream of messages.
Email was far from perfect. But it understood something that modern communication tools sometimes forget:
The value of a good conversation should outlive the conversation itself.