# Writing is a product skill

> Clear writing ships faster products. I treat every sentence like a UI decision. Cut the fluff, name the tradeoff, make the next step obvious.

- Author: Kevin Dalvi
- Published: 2026-05-05
- Read time: 7 minutes
- Tags: writing, product, founding
- Canonical: https://www.kevindalvi.com/blog/writing-as-product-skill

I used to think writing was marketing’s job. Then I watched a brilliant engineer lose a week because the PRD said “make it smarter” and nobody agreed what smarter meant. The product didn’t stall on code. It stalled on language.

Writing is how product decisions travel. Specs, changelogs, investor notes, landing pages, Slack threads. If the words are mushy, the team builds mush. If the words are sharp, people move in the same direction without a meeting.

## Treat sentences like interface

A good product sentence does one job: it removes ambiguity. Same bar I use for UI. If a user has to guess, the design failed. If a teammate has to ping you for clarification, the writing failed.

I write the outcome first, then the constraint, then the non goal. Outcome: “New users complete onboarding without asking support.” Constraint: “Under three screens.” Non goal: “We are not rebuilding auth.” That structure alone has saved me more calendar time than any AI tool.

> If you can’t say it in one plain sentence, you don’t understand it well enough to build it.

## What I actually rewrite

I don’t polish for tone. I polish for decisions. Vague verbs get replaced with verbs that imply a measurement. “Improve retention” becomes “raise week 2 return rate from 22% to 30%.” “Delight users” becomes “cut time to first value under 60 seconds.”

- Name the user and the moment. Who is stuck, where, and why it matters now
- State the tradeoff you’re accepting so debate is about taste, not confusion
- End with the next concrete action someone can take without you in the room

## Writing compounds like code

Early on I rewrote the same explanation in five places. Pitch deck, website, hiring post, onboarding email. Now I keep a short “truth doc” for each product: what it is, who it’s for, what we refuse to build. Everything else is a remix of that source.

Founders who write well don’t sound literary. They sound decisive. That’s the skill. Ship the sentence that makes the next build step unavoidable. Then get out of the way.