Communication 101 — The Hussh Way to Communicate
The Hussh cookbook for communication: nine principles, the universal skeleton, length discipline, eleven recipes, email craft, anti-patterns, and the one-page card.
TL;DR: The Hussh Way to Communicate: nine principles, one universal skeleton (context, enumeration, closing reframe), two lengths of message and nothing in between, eleven recipes for the situations that come up every week, the email cut test, the anti-patterns — and the whole book on a one-page card.
Status as of 2026-11-06: see body.
Introduction — Why a Cookbook
Every company writes. Few companies write well, and fewer still write the same way twice — so every message a reader receives from us sounds like it came from a different company, and the reader has to work out, each time, who we are and what we want.
This book ends that. It is the hussh way to communicate: the principles we hold, the shapes we use, and the recipes for the situations that come up every week. It is a cookbook, not an essay. You do not read it once and admire it. You keep it open next to the message you are writing, find the recipe that matches your situation, and follow it.
Three promises about what follows:
- Everything here is usable on day one. Each recipe has a goal, a shape, a worked example, and a checklist. If a page does not change how you write tomorrow, it has failed.
- Everything here is ours. These are the rules we run by, stated in our own words, tested in our own work. Where a rule sounds absolute, it is because we have paid for the exception.
- Brevity is the through-line. Not shortness for its own sake — weight. A message should carry exactly as much as the reader needs to know, decide, or do, and not one sentence more.
How to use the book: read Part I once. It is short, and everything else hangs on it. After that, work from the recipes. When a message matters — a partner, an investor, a hard conversation — run it against the checklists in Part V before you send. When you are in a hurry, the last page is the whole book on one card. Start there if you must; come back for the rest when the stakes rise.
A note on tone throughout: we write the way we would want to be written to. Directly. Without decoration. With respect for the person on the other side, whose attention is the scarcest thing in any room — including the room their inbox is.
Part I — The Principles
Nine laws. Everything in this book is an application of one of them.
1. The reader's attention is the scarcest asset
Before anything else, a message competes for attention against everything else in the reader's day. Most messages lose that competition in the first two lines. So we write as if attention must be earned line by line — because it must.
The subject line carries the ask. The first line is the sharpest true thing we can say. Every line after that earns the next one or gets cut. There is no warm-up, no throat-clearing, no easing in. If the first two lines do not stop the reader, the rest of the message does not exist.
This is not a trick of style. It is respect, stated operationally: the reader's time is worth more than our comfort in writing.
2. Fewest words, maximum weight
The crisp law: every message is written to do its job in the fewest words that carry it fully.
Short is not the goal. Complete is the goal, and complete is usually short. A sentence earns its place only if it changes what the reader knows, decides, or does. A sentence that merely sounds good is waste — and waste is not neutral. Every unnecessary sentence dilutes the necessary ones and taxes the reader for our vanity.
When you finish a draft, read it once more with a single question per line: what does this line do? If the answer is "it sounds professional," delete it.
3. Never echo
Never repeat the other person's message back to them — not their sentences, not a summary of their sentences, not "as you said." They know what they wrote. Echoing reads as filler because it is filler: it moves nothing forward and quietly tells the reader you had nothing of your own to add.
Read their message deeply. Understand what they are actually asking — which is often not the literal question. Then write only what moves things forward: the answer, the decision, the next step, the thing they did not know. A reply that is all forward motion is unmistakable, and rare.
4. Every note is weighed
Write every message as if it travels far and can carry little — because it does, and it can. A note from us may be read on a phone in an airport, forwarded to a partner, screenshotted into a thread we will never see. Each word is weighed before it earns its place on the page.
The practical consequence: nothing casual, nothing throwaway, nothing dashed off. If a message is not worth weighing, it is not worth sending. If it is worth sending, it is worth the ninety seconds of weighing.
5. Structure before sentences
Good messages are built, not written. The shape comes first — what the reader needs first, what follows, what the message lands on — and the sentences fill the shape. Part II gives the one shape we use more than any other.
Structure is what persuasion runs on. Not adjectives, not intensity, not credentials. A message with a clear skeleton and plain words beats a message with brilliant words and no skeleton, every time, because the reader can follow the first and must excavate the second.
6. Candor: the true thing, said plainly
Say what is true, in the plainest words that carry it. Do not soften a fact until it becomes a different fact. Do not inflate a hope until it reads as a promise. Do not bury a "no" inside three paragraphs of context and hope the reader excavates it gently.
Candor is not bluntness toward people. We are unlimited in candor about the work, about decisions, about our own failures and shortcomings. About a person — their worth, their character — we are careful, always. The split is absolute: attack problems at full strength; address people at full respect.
7. If you don't know, ask — never write around the gap
When something is missing — a fact, a number, a decision that is not yours to make — the honest move is to ask. The dishonest move, and the one that feels most like writing, is to compose around the gap: elegant sentences that approach the missing thing from several angles and never touch it.
Readers can tell. Writing around a gap produces the specific texture of fog, and fog destroys trust faster than any bad news. A short message that says "I need one thing before I can answer this properly" is worth ten polished pages of fog.
8. Write to the person, and ask for the meeting
Two rules that travel together.
Write to the person, directly — their actual inbox, their actual name, the message composed for them and nobody else. A message addressed to a desk, a department, or a generic mailbox announces that the reader was not worth finding. Find them.
And when we reach out — to a partner, an investor, a candidate — the ask is a meeting. Not money, not a commitment, not a signature. A meeting is where relationships start; everything else follows from it or it doesn't. One ask, small, easy to say yes to. Prepared material can ride along as information; the ask itself stays a conversation.
9. Slow and steady wins the follow-up
Persistence is a cadence, not a pressure. We follow up because people are busy and inboxes are deep — not because silence means no. A follow-up is a gentle check-in: short, warm, easy to answer, and easier to ignore without guilt than the last one felt. Each touch makes it simpler for the reader to respond, never heavier.
The cadence is measured in days, not hours. The tone never escalates. The tenth touch sounds like the second: here when you need us, no trouble either way. Pressure converts a future yes into a permanent no; patience converts a present silence into a future yes surprisingly often.
The nine laws, on one line each Attention is earned line by line. · Fewest words, maximum weight. · Never echo. · Weigh every note. · Structure before sentences. · Candor about work, care with people. · Ask, don't fog. · To the person; ask for the meeting. · Follow up slow and steady.
Part II — The Universal Skeleton
Almost every message that matters has the same bones:
- Context. How we got here — briefly, and only the part that makes the decision intelligible.
- Enumeration. The options, the reasons, or the facts — laid out in a numbered or clearly separated list, each item eliminable or checkable on its own terms.
- Closing reframe. Not a summary. A final line that changes the reader's posture — states the decision, names the next step, or reframes everything above it in one sentence.
Why it works: context makes the reader a participant instead of an audience. Enumeration does the deciding work — options are eliminated on stated grounds, in the open, so the surviving option arrives with its reasoning attached. And the reframe gives the reader something to carry away: not ten points, but one line that reorganizes the ten.
Rules of the skeleton:
- Context is selected, not complete. Include the history that makes your position look like the continuation of the story. Leave out the history that merely happened.
- Enumerate in threes when you can. Two options read as a corner; four read as indecision. Three reads as a landscape — the reader can see the whole terrain and watch two of the paths close.
- Each enumerated item must stand alone. If item two only makes sense after a paragraph of apology, rewrite item two.
- Put numbers where doubt lives. A claim the reader might question gets a figure, a date, or a name attached — at exactly that point, and nowhere else. Numbers scattered everywhere persuade no one; a number at the point of maximum skepticism settles the question.
- The decision sentence is the shortest sentence in the document. The long build exists to make the short sentence unanswerable. The sentence itself carries no argument — by the time it arrives, the argument is over.
- Never close with a summary. A summary repeats; a reframe advances. If your last line could be deleted without the reader losing their footing, it is a summary. Write the line that changes their footing instead.
Worked example 1 — A partner note
Situation: we are proposing that a wealth platform offer hussh to its clients. The reader is the platform's head of partnerships, who has seen our one-pager and asked, reasonably, "why would our clients want a second place for their information?"
Subject: A meeting about your clients' information
Your clients already trust you with their money. What they don't have — and what they ask your advisors about more every year — is one place where all of their information works for them: accounts, documents, health, home, family. Today that information sits in a dozen inboxes and filing cabinets, working for no one.
As we see it, there are three ways a firm like yours answers that:
- Build it. Two to three years, a team you don't have, and a trust problem money can't solve — clients will not hand their whole lives to a tool their bank built last quarter.
- Wait. The need doesn't wait. Two of your competitors are already piloting answers, and the firm that moves first becomes the default.
- Partner. Your advisors offer hussh under your brand's trust, starting with one client segment, measured in ninety days.
We'd like thirty minutes to show you what the pilot looks like. Tuesday or Thursday afternoon, your office or ours — whichever is easier.
Your clients' information is already an asset. The only question is whose name is on the door when it starts working for them.
Note the bones: context (their clients, their trust, the gap), three options with two eliminated on stated grounds, and a closing line that reframes the whole note — the ask itself is almost an aside, small and easy, because the skeleton did the persuading.
Worked example 2 — An internal decision
Situation: a launch slipped. The team needs to hear what happened, what changes, and what we still believe — in one message, without blame landing on a person.
Subject: The launch moves to March — what changes
We planned to ship in January. We are shipping in March, and the reason is ours: we tried to launch the agent, the vault, and the new onboarding in the same week, and each one made the others slower. That was a sequencing mistake, made at my level, and it cost us six weeks.
Three things change:
- One launch at a time. Onboarding ships February 10. The vault ships February 24. The agent ships March 10. Nothing moves into another item's week.
- Testing gets its own calendar. Two full weeks of real-user testing before each date, owned by one named person, with the authority to stop the line.
- One owner per launch. Priya owns onboarding end to end. Decisions in her area are hers; disagreements come to me the same day, not the same week.
What does not change: the product, and why it matters. We are late because we tried to do everything at once — the fix is to do each thing properly, in order.
By March 10, this will be the launch we meant to have in January — done right instead of done twice.
Context (what happened, owned plainly, process blamed rather than people), enumeration (three concrete changes, each with an owner or a date), reframe (the delay becomes the standard). No summary anywhere.
Worked example 3 — A public explanation
Situation: we are changing how a feature works, and some users will dislike it. The explanation goes to every user.
Subject: Why statements are changing on December 1
When we started, a statement was a simple thing: one account, one page, once a month. Your hussh now holds accounts, documents, policies, and properties — and the old statement had quietly stopped describing your actual financial life.
We considered three ways forward:
- Keep the old statement and add pages. Familiar, but the additions would describe the same asset three times in three places. Longer, not clearer.
- Let everyone design their own. Maximum control, and a part-time job. A statement you have to configure is a statement that has already failed.
- One statement, organized the way you think. Assets together, obligations together, what changed this month first. One page for most households; the detail one tap behind it.
We chose the third. It arrives December 1, with your November statement in both formats so you can compare them side by side.
A statement should answer one question — where do I stand? — in the time it takes to drink a coffee. The new one does.
Same bones, third audience. The skeleton does not care who is reading; it cares that the reader can follow.
Who writes: the final-word rule
In any thread that matters, sequence is part of the message. The person who owns the relationship writes first — updates, preparation, the absorbing of easy questions. The decision-maker writes last, briefly, and only when the moment needs their weight.
This is not ceremony. A short note from the person who can actually decide carries a signal no long note from anyone else can: this is the final rung; the answer you give now is the answer that counts. Spend that signal rarely. A decision-maker who writes every message teaches readers to wait for the second one; a decision-maker who writes once teaches them to answer the first.
Part III — Length Discipline
There are two lengths of message at hussh, and almost nothing in between.
The short form is for asks, answers, decisions, and replies. It runs from one word to one short paragraph. Its job is to move something: get the meeting, give the answer, make the call. If a short-form message needs a second paragraph, it is usually two messages stapled together — unstack them.
The long form is for vision and explanation: the note that must carry a whole argument, teach a whole idea, or change how a reader thinks about something. It is as long as the argument requires — and not one sentence longer. Length is earned by the size of the idea, never by the importance of the writer.
The middle length — the three-paragraph email that is neither a crisp ask nor a real explanation — is where messages go to be ignored. It is too long to answer quickly and too thin to persuade. When you find yourself writing one, decide which of the two forms you actually mean, and write that.
Rules of thumb:
- An answer is one sentence until it must be two. Answer the question asked, in the order it was asked, and stop. Context the reader did not request is a tax.
- The ask appears where the reader can act on it. In short form: the first or last line, never buried in the middle. In long form: after the enumeration, before the reframe.
- If you cannot state your message in one sentence, you do not yet have a message. Find the sentence first — it usually becomes the subject line — then write only what supports it.
- Length signals rank of effort, not rank of person. A one-word reply from a decision-maker ("Approved.") is a complete message with a complete signal. A long reply to a simple question signals the opposite of respect.
- Numbers live in long form; decisions live in short. When a reader needs the reasoning, write the reasoning once, in long form, and let every later message about it be short and point back.
Part IV — The Recipes
Each recipe follows the same format: the goal (what the message must achieve), the shape (its skeleton), a before and after, and a checklist to run before sending.
Recipe 1 — The customer reply
Goal: Answer completely, once, so the customer never has to write twice.
Shape: The answer first. Then the one piece of context that makes the answer trustworthy. Then what happens next, with a date if there is one.
Before:
Hi! Thanks so much for reaching out to us. We really appreciate you taking the time to share your experience. I wanted to let you know that I've looked into this, and it does appear that there may have been an issue on our end with how your statement was generated. I'm going to escalate this to our team and someone will be in touch. Thanks again for your patience and for being a valued customer!
After:
Your October statement double-counted the transfer on the 14th — that's our error, and the corrected statement is in your account now. The refund of the $42 fee it triggered posts Friday. If anything else looks off, reply here and it comes straight to me.
Checklist: — The answer is in the first sentence. — Anything we did wrong is stated plainly, with the remedy and its date. — No sentence exists only to sound warm. — One reply from us ends the matter.
Recipe 2 — The partner note
Goal: A meeting. Not agreement, not signature — a meeting, with a prepared partner who already understands the shape of the idea.
Shape: The universal skeleton (Part II), with the three ways forward enumerated and the meeting as the only ask.
Before:
I hope this message finds you well. I am writing to introduce hussh, a revolutionary platform that is transforming how people manage their personal information. We believe there could be tremendous synergies between our organizations and would love to explore a potential strategic partnership at your convenience. Please find attached our deck, and do let me know if you might be open to a brief introductory call sometime in the coming weeks.
After:
Your advisors hear the same question ours do: where does all my information actually live, and who is it working for? Right now the honest answer, for almost every client, is "a dozen inboxes, and no one."
Three ways a firm like yours answers it: build it (years, and a trust problem), wait (the need doesn't), or partner — your advisors offer hussh to one client segment, measured in ninety days.
Thirty minutes next week to walk through the pilot? Your office or ours.
Checklist: — The note leads with their world, not our product. — Three options, two closed on stated grounds. — The only ask is a meeting, small and specific. — No word claims a partnership that doesn't exist yet.
Recipe 3 — The investor note
Goal: A meeting — the same discipline as the partner note, held harder. We never ask for money in writing. Terms, decks, and prepared materials are information; the ask is a conversation.
Shape: One true line about what we are building and why now. One line of evidence. The meeting ask. Nothing else.
Before:
We are currently raising our seed round and are seeking visionary investors who believe in the future of personal AI. Our total addressable market exceeds $400B and we have built a world-class team. We would be honored if you would consider an investment of $1–5M. Materials attached; happy to jump on a call to discuss terms.
After:
We're building hussh — personal superintelligence owned by the person it serves. The human stays in control; every machine works for them. Our first product is live with its first customers, and the next ninety days decide our distribution.
I'd value thirty minutes with you — what we're building, what the numbers say, where it can go. Thursday or Friday afternoon?
Checklist: — No ask for money, terms, or commitment anywhere in the note. — Every figure in it is one we can stand behind in the room. — The meeting is the only call to action. — Sent to the person, never to a desk.
Recipe 4 — The recruiting note
Goal: Make one specific person feel seen accurately — and curious enough to talk.
Shape: One true line about their work — specific enough that it could be written about no one else. One line about what we're building and why someone of their calibre is the missing piece. The ask: a conversation. Short — this is short-form writing, and every word is weighed.
Before:
I came across your profile and was extremely impressed by your background. We are hiring for several exciting roles at our fast-growing startup and I believe you would be a great fit for our team. Would you be open to a quick chat about opportunities?
After:
Your paper on retrieval under distribution shift is the reason our memory layer works the way it does — we built on it, then spent six months learning where it breaks.
We're hussh: personal superintelligence the person owns outright. The next problem is yours if you want it. Thirty minutes this week?
Checklist: — The true line is verifiable and could fit nobody else. — No flattery that isn't a fact. — The role is named or the problem is — never "opportunities." — Short enough to read in one breath.
Recipe 5 — The internal decision
Goal: Everyone who reads it knows what was decided, why, what changes for them, and what does not change.
Shape: The decision in the subject line. Context, briefly, owned plainly. The changes, enumerated, each with an owner and a date. The reframe: what stays true.
Before:
Team, after careful consideration and lengthy discussion with leadership, we have made the difficult decision to adjust our launch timeline somewhat. We believe this is ultimately in the best interest of the product and the company. More details will follow in due course. Thank you all for your hard work and dedication during this busy period.
After: (Part II, worked example 2, is this recipe executed in full — the launch that moved to March. Study its bones rather than a second example.)
Checklist: — The subject line contains the decision. — Reasons are stated, including our own part in them — process blamed, people never. — Every change has an owner and a date. — What does not change is said out loud.
Recipe 6 — Saying no
Goal: A no that the reader can accept without a second email — clear, kind, and final.
Shape: Thank them in one line, if thanks is true. The no, in one sentence, early. The reason, in one sentence, if a reason helps them. A door that is genuinely open, if one is — otherwise none.
Before:
Thank you so much for thinking of us. This is a really interesting opportunity and we gave it a lot of thought. Unfortunately, due to a variety of factors and our current bandwidth, we're not going to be able to move forward at this time. Perhaps we can revisit at some point in the future when things settle down. Wishing you all the best!
After:
Thanks for bringing this to us. We won't be able to take it on — our next two quarters are committed to the launch, and this deserves more focus than we could give it. If the timing is alive again in the fall, we'd want to hear about it.
Checklist: — The no is findable in the first three lines. — No reason is invented; a vague reason is fog. — Any future door mentioned is a real one. — Nothing in it invites negotiation of the no itself.
Recipe 7 — Declining gracefully (the gracious close-out)
Goal: When someone declines us — an investor, a candidate, a partner — leave them warmer than we found them. A decline handled well is a relationship kept.
Shape: Thank them for the serious look. Accept the decision completely, in one line, with no argument and no re-pitch. One line that keeps the door real. End.
Before:
I'm sorry to hear that. I do want to flag that I think there may be some misunderstanding about our traction, and I'd welcome the chance to share updated numbers that might change the picture. Could we have fifteen minutes before you finalize?
After:
Thank you for the serious look — and for the candour about fit. We'll keep building; if the picture changes on your side, the door here is open, and I'll send the occasional milestone worth your time. Nothing more.
Checklist: — Zero re-pitching. — Their reason is never argued with or echoed back. — The door is stated once, lightly. — This is the last email on the subject from us until a milestone earns another.
Recipe 8 — The apology, with remedy
Goal: When we are wrong: restore trust by owning the failure completely and paying the remedy — while defending the decision, if the decision itself was right.
Shape: What happened, in plain words. That it is ours — no passive voice, no "mistakes were made." What we are doing about it, with the remedy concrete and dated. What changes so it does not recur. If the underlying decision was right, one calm line says so — the apology covers the execution, not the judgment.
Before:
We sincerely regret any inconvenience that may have been experienced. It has come to our attention that some users may have been affected by a technical issue. We take this very seriously and our team is looking into it. We appreciate your understanding.
After:
On Tuesday, statements went out with September's balances. That was our error — a release check we skipped, not a system that failed. Corrected statements are in your account now, and any fee the wrong balance triggered is refunded, no claim needed.
The check we skipped is now automated and blocking: no statement ships without it. The decision to move statements to the first of the month stands — it's the right rhythm — but its execution this week was not worthy of your trust, and we've fixed the part that broke.
Checklist: — Active voice; a named failure, not "an issue occurred." — The remedy is concrete, dated, and requires nothing of the reader. — The fix is systemic, not a promise to try harder. — Decision and execution are apologised for separately, each at the right strength.
Recipe 9 — The three-choices close
Goal: End a negotiation, a proposal, or a second-touch note by handing the reader a landscape instead of a corner.
Shape: Three genuine options, each stated fairly, each with its real consequence. Our preference visible through the honesty of the framing, never through rigging the other two. The reader chooses; any of the three is one we can honour.
Before:
Given the constraints, we really only see one viable path forward, which is option A. Please confirm so we can proceed.
After:
Three ways we can run the pilot:
- Your top twenty advisors, ninety days. Fast signal, small blast radius, results we can both publish internally.
- One region, all advisors. Slower, but the answer covers your whole model, not a selected slice.
- Wait for the spring release. The strongest product story; the cost is a quarter of learning we won't get back.
Our instinct is the first — it earns the second. But it's your client base; we'll run whichever you choose, properly.
Checklist: — All three options are real — we can honour any of them. — Consequences stated for each, including ours. — A preference may be named, once, with its reason. — Never two options (a corner) or four (indecision).
Recipe 10 — The gentle follow-up
Goal: Stay present without becoming pressure. Silence usually means busy, not no.
Shape: Shorter than the message it follows. One new true thing — a milestone, a relevant fact, a reason today is a good day to talk — or simply the standing invitation, restated lightly. Easier to answer than the original: a smaller ask is a gift.
Before:
Just following up on my previous email (see below). I haven't heard back and wanted to make sure it didn't get buried. This is time-sensitive on our end, so I'd appreciate a response at your earliest convenience. Bumping this to the top of your inbox!
After:
A short update since my note: the pilot I mentioned is now live with its first firm, and the first month's numbers are better than the ones I quoted you. The offer stands — thirty minutes, your office or ours, whenever it suits. No reply needed if the timing's wrong; I'll check back in the spring.
Checklist: — No reference to their silence, our waiting, or the message "below." — One new true thing, or a graceful standing invitation. — The exit costs them nothing — "no reply needed" is said and meant. — Cadence in days, tone identical to the first touch.
Recipe 11 — The hard conversation
Goal: Say the difficult true thing in a way the other person can hear, act on, and still respect — and be respected after.
Shape: The fact, plainly, first — never after three paragraphs of cushioning that teach the reader to dread our openings. The evidence, briefly. What it means and what happens next. Then space: the message ends; the person responds in their own time.
Before:
First of all, I want to say how much we value your contributions and how great it's been working together. There have been a few small things that have come up recently that I wanted to chat about, nothing major, just some areas where there might be some room for alignment going forward…
After:
I need to tell you plainly: the last two releases shipped with defects our customers found before we did. That's the fact, and it sits with the review process you own.
Here's what I propose: you take the release checklist redesign — yours to shape — and we look at the next two releases together before they go. If they're clean, this conversation becomes a footnote. I believe they will be; that's why I'm having it with you and not about you.
Checklist: — Candour about the work at full strength; care for the person at full strength. — Facts and evidence, not character judgements. — A concrete path forward that the person can actually walk. — Nothing in it is a surprise ambush about anything never raised before.
Part V — Email Craft
The recipes assume these mechanics. They are not optional garnish; they are most of why the recipes work.
The subject line carries the ask. Not a topic — the ask. "Thirty minutes next week" outperforms "Introduction" and "Partnership opportunity" because the reader can decide before opening. If the message asks for a decision, the subject names the decision. If it carries news, the subject is the news.
The first line is the sharpest true thing. Not the warmest, not the cleverest — the truest thing that makes the reader need the second line. Test: if the reader stopped after line one, would they still have received something of value? They should.
Every line earns the next. Read the draft as the reader: at each line, ask whether you'd continue. The line where you'd stop is the line to cut or move.
The cut test. Before sending, read the final draft once, line by line. For each sentence ask: does this change what the reader knows, decides, or does? If not, delete it. Not shorten — delete. The sentences that survive this test, in this order, are the message.
Cut list — phrases that almost always fail the test:
- "I hope this email finds you well" and every day-relative greeting.
- "Just following up" / "bumping this up" / "circling back."
- "Please don't hesitate to reach out."
- "As previously mentioned" (if it was mentioned, trust it; if it matters, say it again as fact).
- "In today's fast-paced world" and all scene-setting about the era.
- Superlatives about ourselves ("world-class", "revolutionary", "cutting-edge"). Claims about ourselves are made by evidence or not made.
- "Synergy", "leverage" as a verb, "touch base", "loop in" — fog words; each hides a concrete verb. Find the verb.
Closings. Short and human. "Thank you" when thanks is true. A name. Nothing stacked: no quote, no slogan, no four-line signature block with three logos. The signature exists so the reader can reach us — name, role, one phone, one link. That is all it is for.
Reply discipline. Reply to the message that was sent, not the one you wish had been. Answer its actual question first (Principle 3: never echo it back — answer it). If the real question hides under the literal one, answer both, real one first.
Length. Short form by default (Part III). If a reply passes five lines, check whether it is doing explanation work that deserves long form — or whether it is two short messages stapled.
Part VI — Anti-Patterns
The failure modes. Each one feels like writing; each one costs trust.
- Echoing. Restating the sender's message as a summary before answering. It reads as a machine clearing its throat, because that is what it is. Answer; don't recap.
- Throat-clearing. "I wanted to reach out because…", "So, basically…", three sentences of weather before the point. The point is the opening. Move it up.
- Flattery. Praise that isn't a specific, verifiable fact. Readers can price generic praise at its true value instantly, and they apply the discount to everything after it. Specific admiration is research; generic admiration is noise.
- The buried ask. The request in paragraph four, wrapped in context, deniable. It reads as either fear or manipulation. Asks go where readers can act on them.
- Writing around the gap. Elegant fog where a fact is missing (Principle 7). The reader feels the missing fact like a missing stair. Ask for it instead.
- Performing smartness. Vocabulary chosen to impress, structures chosen to display. Writing is for the reader's clarity, not the writer's reputation. The smartest message in the thread is usually the plainest.
- The summary close. Ending by repeating the message in miniature. It trains readers to read only endings. Close with the reframe or the ask — something that moves.
- Escalation theatre. Deadlines we invented, urgency we don't feel, "time-sensitive" on things that aren't. Spent once, it devalues every true deadline after.
- The hedge stack. "Might potentially perhaps be somewhat…" One hedge is honesty; four is fog. Say the thing at the strength you believe it.
- Sending the first draft. The first draft is where you find out what you think. The message is the rewrite. Nobody outside this building ever sees the first one.
Part VII — The One-Page Card
Print this page. Keep it next to the keyboard.
THE HUSSH WAY TO COMMUNICATE
The nine laws
- Attention is earned line by line.
- Fewest words, maximum weight.
- Never echo.
- Weigh every note.
- Structure before sentences.
- Candour about work; care with people.
- Ask — never write around the gap.
- To the person; ask for the meeting.
- Follow up slow and steady.
The skeleton Context, briefly → the enumeration, in threes → the closing reframe. Never a summary.
The two lengths Short for asks, answers, decisions. Long only for vision and explanation. Nothing in between.
Before you send
- Subject carries the ask?
- First line the sharpest true thing?
- Every sentence passes the cut test — changes what the reader knows, decides, or does?
- The ask findable in three seconds?
- No echo, no fog, no flattery, no invented urgency?
- If we're wrong somewhere in it — is it owned, with the remedy and its date?
- Would this read well forwarded to someone we never expected?
The whole book in one line: Say the true thing, in the fewest words that carry it fully, structured so a busy person can act on it — and make every line earn the next.
Sources
- First published on the Hussh Wiki on November 6, 2026. Canonical PDF edition held in the Hussh Library (Communication 101 — The Hussh Way to Communicate, 42 pages).