Carve to Connect: Why Subtraction Is the Most Radical Act in Science and Tech Design

Hatched by Media Science Tech Foundation

Apr 16, 2026

9 min read

5 views

85%

Question: what if the way to make your technology more persuasive is to remove everything you think matters

The reflex in science and advanced technology is to add. More data, more features, more nuance, more caveats. The story of any new instrument, therapy, or platform often arrives burdened with complexity: methods sections, feature lists, hedged claims, and a glossary. Those elements feel necessary. They are proof that the work is serious. And yet the people you need to convince have a simpler requirement: they need to see, in an instant, what changes for them.

This essay argues that the highest form of design for science and technology is not accumulation but surgical subtraction. The bold approach is to treat clarity as an outcome of disciplined removal, not polished accumulation. When done correctly, subtraction is not an act of impoverishment. It is a way to reveal the essential leverage the technology gives to investors, partners, talent, and users. This is not mere rhetoric. It is a replicable process with clear steps, cultural rules, and measurable benefits.

The paradox: why adding things makes your message worse

Engineers, scientists, and founders share a paradox: each new piece of evidence or feature reduces the listener's ability to choose. A dense slide deck signals rigor, but it also produces decision fatigue. A product with a long onboarding script supposedly educates users, but it also increases churn. A website with every dataset available feels transparent, but it buries the single claim that would win a partnership.

Two instincts collide here. The first is the responsibility instinct: the developer wants to honor the complexity of the work. The second is the attention economy instinct: human decision makers operate on a narrow bandwidth of meaningful signals. These instincts are both valid. The synthesis is that clarity does not come from omission in service of deception. It comes from organizing complexity so the right people see the right constraint, at the right time, in the right form.

This is where subtraction becomes a design method, not a rhetoric trick. It requires asking: what problem are we solving, and who are we solving it for? Once that is clear, you can treat everything else as optional cargo to be jettisoned until the value proposition sails cleanly.

The anatomy of subtraction: five moves that turn complexity into clarity

Subtraction is not chaos. It is an ordered practice with tactical moves and cultural disciplines. Apply these to narratives, product flows, and organizational processes.

Specify the problem with brutal fidelity

Start by stating the single problem you will solve, at an order-of-magnitude scale. Small improvements are easy to make, but hard to sell. If your goal is marginal speed or marginal precision, you will be tempted to list every nuance. If your goal is to reduce time to decision by an order of magnitude, you have permission to simplify aggressively.

Analogy: a surgeon does not aim to reduce pain by 10 percent. They aim to remove the tumor. When the problem is stated as a tumor removal, every step that does not serve that goal becomes suspect.

Map the entire audience journey

Expand your focus beyond the product touchpoint. Who are the investors, talent, or partners and what are their micro-decisions? Where do they pause, doubt, or ask for proof? Map each pause as a potential barrier to the outcome you specified.

Concrete tactic: spreadsheet the journey. Line by line, write every action, every document, every call. If you cannot observe it, embed in the front lines until you can. Managers should spend active time experiencing the process as the customer does. This is not a one-off exercise. It is the heartbeat of subtraction.

Delete everything that does not create customer value

Once you have the journey in view, identify which steps add discretionary value and which exist for internal comfort. Every requirement except legal and physical constraints should be questioned. Remove steps in waves, intentionally leaving open the option to add them back if evidence requires it.

Rule of thumb: assume you will remove at least half the steps, and be prepared to reintroduce up to 10 percent as necessary. This is not wasteful. It is iterative efficiency.

Optimize for speed and expose weaknesses

Speed is a diagnostic. When you accelerate cycles, weaknesses become visible quickly. Short cycles create more opportunities to learn, and they compress the time between claim and verification.

Metric to watch: attention velocity. In financial products the metric is cash velocity. For narratives and recruitment it is the pace at which interest converts to action. Higher attention velocity forces clarity because ambiguity becomes costly.

Automate only after the process is repeatable

Automation is seductive because it promises scale. But automating a flawed, complex process is amplifying dysfunction. Automate once you have a repeatable, optimized flow. Automation is the final polish, not the initial sculpt.

Subtraction is not a shortcut to laziness. It is the discipline of choosing what stays because it is the lever, not because it feels important.

SCALP: a mnemonic for carving clarity from complexity

To make these moves operational, use a simple framework I call SCALP. Think of it as a surgical checklist for communication and product design.

S: Specify the problem at order-of-magnitude scale. If you cannot state it in one sentence that implies a tenfold improvement, you have not specified the right problem.

C: Chart the journey for each stakeholder. Map each interaction, emotion, and decision point in a spreadsheet and annotate which steps add value.

A: Abolish optional steps. Start with everything except legal and physical constraints. Remove until the story or process still functions.

L: Lean optimize the remaining steps. Simplify language, shorten processes, and shave time where it matters. Iterate with real customers and front-line observations.

P: Package and automate only when repeatability is proven. Standardize what is consistent, and then build for scale.

This model is not linear. It is recursive. After you package and automate, you return to specifying the problem again because the landscape has shifted. That loop is the engine of durable clarity.

Concrete example: fund raising for a biotech

A common failure mode is the 30-slide deck that attempts to do everything. Using SCALP, the founders start by specifying the problem with surgical clarity: our therapy reduces hospital readmissions from X to Y within 90 days. Next they chart the investor journey: initial curiosity, technical due diligence, regulatory questions, clinical trial timelines, valuation assumptions. They delete everything investors do not need at stage one: exhaustive assay validation, full trial protocol, and all secondary endpoints. They lean optimize by creating a one-page visual that aligns mechanisms to outcomes and a three-minute demo of the assay. They accelerate cycles by pitching and iterating based on investor feedback at demo days, and only after repeatable investor interest is proven do they automate the outreach sequence with templated materials and a CRM workflow.

Result: fewer slides, faster decisions, clearer expectations.

Cultural rules that make subtraction sustainable

Processes alone do not sustain clarity. They require cultural habits that enforce candidness and urgency.

Experience the product like your customer

When teams use their product as customers do, they uncover friction that never appears in design reviews. Eating your own dog food is not vanity. It is research. Put leaders on the front lines and give them time budgets to learn from real interactions.

Focus on two or three company priorities

Urgency is the engine of elimination. When you identify the two or three things that matter right now, you create permission to ignore everything else. This reduces the impulse to add features or messages for future hypotheticals.

Measure the right cadence

Choose metrics that reflect velocity of decision and adoption. For product teams this might be time-to-first-success. For communicators, this might be time-to-intent to invest or time-to-reply from a partner. Use these metrics to judge which steps are baggage.

Make deletion reversible and accountable

Treat deletions as experiments. If removing a step increases friction in unexpected ways, you can add it back. But every restoration requires evidence and senior sign off. That accountability prevents creeping complexity.

Real world analogies that make subtraction intuitive

Michelangelo supposedly said that his sculptures were already present in the marble and his job was to remove what was not needed. This is the creative moral for modern makers: reveal the form by removing the excess.

Consider the chef who strips a recipe to its essence. Removing an ingredient reveals another flavor. The dish becomes clearer, not weaker. In the hands of an amateur, subtraction becomes bland. In the hands of a master, removal produces contrast and focus.

Think of the onboarding flow for a lab instrument. A complex manual full of caveats may express respect for safety and complexity. A minimalist checklist that puts the first experiment in front of the user in five steps does more: it demonstrates the instrument is usable. The manual remains available for compliance, but it is no longer the front door.

Key Takeaways

Specify one audacious problem to solve. If your improvement is not at least an order-of-magnitude, simplify the goal or risk inching toward irrelevance.
Map the entire customer journey as a spreadsheet and question every step except legal and physics constraints. Delete ruthlessly, and be willing to add back a maximum of 10 percent if evidence requires it.
Use speed as a diagnostic tool. Short cycles expose friction faster than committees do. Measure attention velocity or time-to-first-success rather than vanity metrics.
Automate only after the process is repeatable. Automation should amplify what works, not hide what is broken.
Make leaders spend time on the front lines. Firsthand experience translates abstract decisions into specific deletions.

A closing reframing: subtraction is the craft of connection

The cultural myth is that convincing people requires more information. The counterintuitive truth is that convincing often requires less. The aim is not to omit truth but to order it so that the right truth meets the right person at the right moment.

When you adopt subtraction as design practice, three things happen: your message gains clarity, your processes become faster, and your product becomes more humane. You will find that the act of removing is not impoverishment but revelation. By removing the noise you reveal the lever.

So here is a final prescription: choose a messy artifact from your organization today. It could be a pitch, an onboarding flow, a website, or an internal approval chain. Apply SCALP to it for one week. Delete. Speed test. Reintroduce only if the data demands it. Observe the difference in decisions and attention.

The radical act is not to throw things away. The radical act is to choose what stays because it is meaningfully useful. Clarity, like elegance, is a construction by subtraction. The most persuasive technologies do not shout all they can do. They show one meaningful thing in a way that the right people can act on immediately.

What would you choose to carve away today?