Information Design
Why Important Information Shouldn't Have to Go Viral
We live in a paradox. We are more connected to the world than ever before, yet it has become incredibly difficult to reliably distribute a simple piece of local information to the people who actually need it.
A municipal announcement affecting 300 residents doesn't need 30,000 views. It needs the correct 300 people.
The Attention Economy's Blind Spot
On traditional social media platforms, all information is treated as "content." A meme, a celebrity update, a political debate, and a local flood warning are all thrown into the same arena, forced to compete for the same resource: attention.
Algorithms are designed to maximize engagement. They boost posts that trigger strong emotions—outrage, joy, awe, or humor. But vital local information is rarely emotionally engaging. A notice about a scheduled power outage isn't going to get thousands of likes, shares, and comments.
Therefore, the algorithm decides it isn't "relevant," and buries it.
The Flawed Funnel of Social Distribution:
- A local government posts an important update on their Page.
- The algorithm shows it to a tiny fraction of their followers.
- Because it doesn't receive immediate engagement, distribution halts.
- Residents who actively need that information never see it in their feeds.
Relevance Over Reach
The solution isn't to hack the algorithm. The solution is to change the architecture entirely. We need to shift from an attention-distribution system to an intentional information-distribution system.
When a local organization issues a Notice, its success shouldn't be measured by its "reach" or "impressions." It should be measured by whether it reached the specific audience it was intended for.
Algorithmic Platforms
Information must be entertaining or polarizing to survive. Reach is based on popularity and engagement.
Contextual Platforms
Information is routed by metadata: Geography, Community, and Persona. Delivery is based on explicit necessity.
Designing for Intent
This is why Duruha separates standard posts from Notices and Alerts. It's why we use Geography as structural metadata rather than just a suggestion engine. It's why Communities and Personas are explicitly defined by the user.
If there is a water interruption in Barangay X tomorrow, the system doesn't need to ask, "Will people click on this?" The system simply needs to know: "Who lives in Barangay X?"
Important information shouldn't have to win a popularity contest to be seen. It's time to build a network that knows exactly who information is for.