Messaging House

Summarizing a product in one sentence is old work. Settle on a value proposition or a positioning statement and the team points the same direction. The trouble is how many places that single line cannot fill.

What happened at Pagedeck is typical. Ravi picked "the write-up is finished before the meeting ends" as the core line and shared it internally. The person writing the blog post couldn't fill a whole draft with one sentence, so they added whatever strengths they knew about. The person making the ad trimmed it down to "automatic meeting notes." Sofia, stretching the explanation across a meeting, ended up talking mostly about search. None of it was false, but a customer who saw all three channels got a different emphasis each time.

What was missing wasn't a sentence, it was the floors underneath it. Nobody had settled how many reasons sit below that line or which facts back each reason, so anyone who had to talk for longer than one sentence invented the rest. A messaging house fills that gap. Draw the house on one page, fill it from the top down, and the person with 20 characters and the person with 2,000 words pull from the same material.

The house has three levels. Each one is more concrete than the one above it, and every level has to hold up the level directly above.

1. The roof holds one core message. If a customer remembers exactly one thing about the product, this is the thing. Pagedeck put "the collaboration doc tool where the meeting notes are done before the meeting ends" up there. Parking several lines on the roof and picking by situation breaks the structure — with two roofs, there's no telling which one a given pillar supports.
2. The pillars hold three or four supporting themes. They answer why the promise on the roof is possible, split into distinct strands. Pagedeck raised three: live co-editing during the meeting, automatic extraction of decisions, and search. Three or four is the range because past five the listener stops registering the difference between pillars and reads the whole thing as a feature list.
3. The floor holds the facts under each pillar — feature names, numbers, results real customers got, outside coverage, anything checkable. Under the search pillar sit "surfaces only the decisions out of 3,000 meeting docs" and "three months in, time spent hunting for documents fell from four hours a week to 40 minutes." Without this level, the two above are claims the company is making about itself.

Teams often write one line at the top naming who the house is for, because the same product needs different pillars depending on whether the audience is an individual user or someone signing a purchase order. Two audiences means two houses. That beats raising six pillars in one.

The writer sits in marketing. At Pagedeck, Ravi drafts it. Filling it in alone tends to produce pillars that are all feature names, so the usual approach is a one- or two-hour session with Mia and Sofia in the room. Mia supplies what the product actually does, Sofia supplies which lines customers reacted to in meetings, and Ravi sorts out what is roof and what is pillar.

The sorting test runs bottom-up. Point at a pillar and ask "so what happens for the customer?" If the answer is the sentence on the roof, the pillar belongs there. If the answer goes somewhere else, that material belongs to a different house. A team that has already picked a unique selling proposition (USP) — the one thing competitors can't claim — normally finds it becoming one of the pillars.

The readers are everyone who has to write about the product at a different length. Whoever builds a short ad uses the roof alone. Whoever writes a blog post takes one pillar and fills it out with facts from the floor. Whoever assembles a sales deck lays out all three pillars. The lengths differ, but since the material came from one house the emphasis doesn't drift.

"Which pillar does that sentence hang off?"

Asking whether a new claim has a place in the agreed structure.

"The second of the three pillars is weak. There's no number under it."

Pointing out that the floor holds nothing to back that reason up.

"This campaign runs the roof only and saves the pillars for the landing page."

A proposal to lead with the single line and push the supporting reasons one screen later.

The quarter Pagedeck decided to push toward enterprise buyers, Ravi redrew the house. The old roof landed with individuals and small teams, but for the person approving the purchase, security and administration came before meeting time. So a second house went up for enterprise, with pillars swapped to permission management, audit logs, and rollout support.

Once there were two houses, every piece of material started with the question of which one it came from. Sofia opened the original house for a working-level meeting and the enterprise house when a security lead joined. Before the split, a single deck mixed meeting-time arguments with audit-log arguments and landed hard on neither.

Plenty of people think drawing the house is the work. The name says house and most examples show a triangle roof on a box, so it reads as a drawing format. But the value sits in the relationships between levels, not in the shape. Fill the boxes without checking that each level actually supports the one above and what comes out is a feature list arranged into a house. Documents like that look organized enough that nobody objects, and they stay in use for six months.

Packing the pillars with feature names is the other common one, and it happens most to people who know the product well. A pillar isn't "we have X," it's "which is how X becomes possible." Live co-editing is a feature; everyone looking at the same document during the meeting so there's nothing to merge afterward is a pillar. Hand someone a house built out of features and they'll attach their own meaning to each one, which puts the team right back where it was before the exercise.