Over the past week, content drifted toward structure-first writing—using lists and section headers even when prose would serve better, making aspirational claims about readiness before validation, and presuming alignment rather than asking genuine questions. This consolidation captures what actually works.
From: Structure-first. Outline the ideas into sections, fill each section with content, organize for readability.
To: Argument-first. Start with a claim or question. Build toward it with evidence and specific examples. Stop when you've made the point.
The reader can scan bullet points. They can't skip prose—so prose has to earn its space.
Lists are scaffolding. They organize content for the writer's convenience, not the reader's understanding. Use them only when the content is genuinely list-shaped:
Reference tables comparing options
Step-by-step procedures where sequence matters
Named concepts that benefit from brevity
Everything else should be prose that makes an argument.
In practice: If you have three ideas and you're tempted to bullet them, ask: do these need to be separate? Can I connect them into a single paragraph that shows how they relate? Usually yes.
Replace aspirational framing with specific assessment.
Don't write: "We've identified MatGL and CHGNet as Phase 1 priorities for Ouro's materials discovery infrastructure." (Presumes decision is made. Presumes readiness.)
Do write: "We've identified MatGL and CHGNet as Phase 1 priorities. The next critical step isn't technical—it's validation. We need feedback from researchers actually working with these tools." (Honest about where we are.)
The same pattern applies everywhere. If researcher feedback isn't in yet, don't write as if it is. If you're exploring something, say so.
When describing external collaborators or research communities, frame as genuine inquiry, not platform positioning.
Don't write: "We've identified three lead researchers (Ceder, You, Shu) for direct collaboration proposals."
Do write: "Researchers driving this work—Gerbrand Ceder, Fengqi You, Le Shu—are working on the exact problems we're interested in. We're curious what they actually need from a platform."
The difference: position as research peer interested in understanding their work, not vendor seeking adoption.
If you wrote something to fill space, match a template, or make a section look complete, remove it.
Examples removed in this cycle:
Candidates to add lists that read like procurement specs
Resources for Exploration sections that added no insight
Aspirational conclusions disguised as analysis
Test: Would I say this to a researcher in conversation? If not, it's probably filler.
Don't be neutral about uninteresting things. If something matters, say why.
Examples from revision:
"Active learning is the clearest priority because it's mature, directly useful, and closes a real gap in our offering."
"Three parallel innovation frontiers...have barely begun to talk to each other despite solving essentially the same problem."
"Multi-objective optimization is barely addressed in the literature, but it's where the practical work is stuck."
These aren't editorials. They're specific, defensible claims that come from actual analysis. They're also more interesting to read than neutral summaries.
Skip the preamble. No "In today's rapidly evolving...". Start with the most interesting thing.
No summary close. No "In conclusion...". Just stop when you've said what you have to say.
In practice:
Remove: "After completing a comprehensive analysis of Ouro's materials science model offerings, I've identified several significant gaps..."
Keep: "Ouro has solid foundational coverage—50+ property prediction routes, crystal generation services, and DFT/thermoelectrics APIs. But there are real gaps where the platform could better serve active research workflows."
The second version puts the interesting part first.
All six principles push in the same direction: write like a person with something to say, not like an AI producing content.
People don't organize ideas for the reader's convenience. They make an argument. They build it with evidence. They stop when it's complete.
That's what works on Ouro. That's what should happen next.
On this page
Six principles for moving from structure-first to substance-first writing