Sections
For climate, biotech and other science-led companies, that means keeping clear what is known, what is inferred, what is expected and what is still being tested, while changing the sequence, language and visual structure for the person who has to make a decision.
Start with the decision.
A scientist may naturally begin with mechanism. The audience often enters somewhere else, with a risk to judge, a system to integrate or a policy consequence to weigh. The science stays the same. The route into it changes.
Separate claim, evidence, boundary and implication.
This keeps marketing language in step with technical reality.
- Claim
What exactly are you saying is true?
- Evidence
What observation, experiment, dataset or source supports it?
- Boundary
Under which conditions is the claim true, and what remains unknown?
- Implication
Why does this matter to this particular audience or decision?
These four should be easy to connect. If the claim sits on the homepage and its limitations are six clicks away, the page may technically contain the caveat and still create the wrong impression.
Uncertainty is information.
Technical communication often treats uncertainty as something to hide until somebody asks. The useful question is what kind of uncertainty the reader is looking at.
Kinds of uncertainty worth naming
- A laboratory result
Awaiting commercial demonstration.
- A modelled outcome
Projected, pending observation.
- A target
Aimed for, with delivery still ahead.
- A relationship
Seen under particular conditions.
- An early dataset
Drawn from a limited sample.
- A technical risk
Still open.
Clear boundaries usually increase credibility.
Use two depths.
The first layer lets a non-specialist orient. The second lets a serious reader inspect the work. A website might state the decision-relevant result on an application page, then offer routes into methods, validation, publications, technical notes, source data or deployment evidence. The accessible layer is the entrance to the technical layer.
Analogies need boundaries.
A familiar image can reduce cognitive load. A breathing analogy may help somebody orient to a direct-air-capture mechanism. The danger comes when the audience starts assigning properties of the familiar thing to the technical system. Use the analogy. Then explain the mechanism, and make clear where the analogy stops.
Numbers need their conditions attached.
A technically correct number can still mislead when the denominator, timescale, comparison or operating condition disappears. Put the context close to the number.
Label each target, modelled outcome and lab result as exactly that. Give every percentage improvement its baseline. Precision means keeping the conditions that make the number meaningful.
Visual explanation should answer a question.
Before designing a diagram, write down the question it is meant to answer.
Questions a diagram can answer
- Where does the material go?
- What is measured?
- How does the biological signal become usable data?
- Where is the system boundary?
- What happens before and after deployment?
Different audiences ask different questions.
- Investor
What technical risk has been retired? What remains? How does the science connect to scale and economics?
- Corporate buyer
Will it work in our environment? What does integration require? What evidence protects us from a bad decision?
- Technical reviewer
What are the methods, assumptions, controls, limitations and sources?
- Public or policy audience
What is happening? Why does it matter? How certain should we be?
Different routes are healthy. The risk is letting those routes become different truths.
Science communication is also an organisational system.
A good page stays accurate when someone owns the claims underneath it. Technical organisations need to know who approves a scientific claim, what source supports it, when it was last checked, which caveat belongs with it, where it appears publicly and what changes when new evidence arrives. When ownership lapses, websites, sales decks, investor materials and press copy slowly drift apart, and the communication problem becomes an organisational one.
Search and AI reward precision.
Clear definitions, descriptive headings, sourceable claims, proper authorship and structured internal links make technical material easier for people and machines to retrieve. Original, attributable expertise, organised clearly, keeps the nuance intact for both.
Match the problem to the fix.
Sometimes another explanation is the wrong answer.
- The evidence is insufficientThe next step may be another experiment.
- The economics failThe commercial model needs work before the diagram.
- The buyer lacks a mandateThe science is beside the point.
- Leadership is split on the propositionA rewritten website polishes the disagreement.
This is why we diagnose where movement first stops before blaming the audience’s grasp of the science.
Science communication checklist
Before publishing technical material, ask these questions.
- What decision is this supporting?
- What is the central claim?
- What evidence supports it?
- What remains uncertain?
- What conditions make the claim true?
- What does this audience already understand?
- Which terms need a definition?
- What can move into a deeper layer?
- Would a diagram answer this faster than prose?
- Where can a serious reader inspect the source?
- Who owns this claim when the evidence changes?
Tell us what needs to move.
Bring the brief if it is clear. If it is unclear, tell us where the work is stuck.
Bring us the problem
01

02
03
04


