Designing for Signal

Over the past few months, Founding Fuel has refreshed its platform. In this conversation, Charles Assisi speaks with Shrinath V, who led the rebuild, about what changed—and why.

Charles Assisi: When we began this process, what problem were we really trying to solve?

Shrinath V: I think the model was always coherent. What wasn’t working was how that coherence showed up in the platform.

Founding Fuel rests on three reinforcing elements—open, reader-supported publishing, immersive learning, and curated convenings. These were already informing one another in practice, but the platform didn’t make those relationships easy to see or navigate.

What we did was reorganise navigation, page structure, and linking so these strands now surface as connected parts of a single system rather than separate sections.

Charles: So this wasn’t about aesthetics.

Shrinath: I wouldn’t look at it that way. Design here had to make the system legible.

The platform now reflects how Founding Fuel actually operates. Contributors, institutions, and readers are surfaced more explicitly in the structure. Content is positioned within a broader network of ideas rather than as isolated pieces.

That required changes to how pages are composed, how relationships are shown, and how readers move across the system.

Charles: What changed most in the rebuild?

Shrinath: If I had to pick one thing, it would be hierarchy and flow.

We simplified navigation so primary paths are clearer and secondary elements don’t compete for attention. Pages now guide reading instead of fragmenting it. Relationships between essays, learning modules, and convenings are visible within the experience itself.

The effect is that readers spend less time figuring out where to go and more time engaging with what’s there.

Charles: Did the conventional design playbook feel inadequate for what we were trying to do?

Shrinath: I think it assumes a different kind of product.

Most redesigns work toward a single release after a long cycle. That approach doesn’t sit well with something that keeps evolving.

We worked in smaller iterations—making changes, observing how they behaved, and refining them. That allowed the structure to develop alongside editorial thinking instead of being locked in early.

Charles: What did we consciously resist?

Shrinath: I think the strongest pull was toward speed-driven patterns.

A lot of media platforms optimise for continuous consumption—more surfaces, more prompts, more movement. That works if volume is the goal.

Here, the priority is depth. So we removed elements that interrupted reading, avoided unnecessary prompts, and allowed long-form work to hold attention.

The interface became quieter, and that helps the content do more of the work.

Charles: What does this rebuild signal about where Founding Fuel is headed?

Shrinath: I’d say it signals greater structural clarity.

The platform now expresses more directly how ideas move—from publishing to learning to shared discussion. That alignment makes it easier to extend the system without having to rethink the basics each time.

Charles: So this wasn’t a redesign. It was a reconfiguration.

Shrinath: That’s closer to how I’d describe it.

The structure now matches how the institution actually operates. That alignment is what allows the experience to feel consistent.

Charles: If I’m a regular reader, what will I actually notice?

Shrinath: You’ll probably notice that moving through the platform feels more natural.

It’s easier to move between related essays, explore connected themes, and access learning or convening formats without having to look for them. Long-form pieces are easier to navigate, and the surrounding context is clearer.

Those changes reduce friction and make the experience feel more continuous.

Founding Fuel has always stood for signal over noise. The platform now supports that more directly through its structure.

What’s Changed

• Clearer articulation of our three-part model
• A more visible contributor network
• Simplified navigation and reduced visual noise
• Stronger hierarchy for long-form essays

P.S: Shrinath has written separately about the technical architecture and backend rebuild on his personal blog for those interested in the engineering and structural details. To read, click here.