HouseChalk · What Bothers You

A · The ask

Complaining is easier than specifying. The starters exist because "what bothers you" can freeze people.

The Hollis House · Kitchen

Before we design one

What bothers you about the kitchen you cook in now?

Small things count. Especially the small things.

Talk it through Type

If nothing comes to mind

Think about the last time you cooked a real meal in there.

Where do you put the groceries down? What's always in the way? What do you have to bend or reach for? Where does the mess pile up?

Nobody says "I want good outlet placement." Everybody says "there's nowhere to plug in the mixer."

B · Complaints become constraints

A wish is a preference. A complaint is a requirement, and it is far more durable.

You said

"There's nowhere to plug the mixer in without unplugging the toaster. The pantry is so deep I find expired stuff at the back twice a year. And the trash can is always exactly where I am standing."

What that turns into

Outlets where you actually work This is the single most common regret in every list I have. Now it's a requirement, not an afterthought.

Shallow pantry shelves, or pull-outs Deep is the default and it's why you lose things. Both fixes cost the same as the thing that annoys you.

Trash out of the work triangle Usually a pull-out beside the prep run, not beside the sink.

Two of these travel

Outlets where you work and shallow storage aren't kitchen problems. I applied them to the laundry, the garage and the primary bath.

Anything else bug you?

C · It comes back

Fourteen months later, at the exact moment it can still be fixed. This is the whole return on asking.

The Hollis House · Kitchen

Island electrical

Back in March last year you told me about the mixer.

Nowhere to plug it in without unplugging the toaster. Your electrician roughs this in Thursday, so this is the moment.

Where do you want power on the island?

Pop-ups in the top, near the prep end

Reaches the mixer and the kettle. Nothing visible when it's down.

Outlets in the side panel

The usual default. It's also why cords drape over the edge.

Both

One circuit either way, so the cost is mostly the pop-up hardware.

Side panels only is what you have now

If we do nothing here, the new kitchen has the same problem as the old one.

Ask or tell me anything

Why this question is worth more than the other fifteen

It is retrospective, so it produces constraints instead of wishes. Every other question asks what you want, which is aspiration, which is Pinterest. This one asks about a house you have actually lived in.
It is easier to answer. Complaining costs nothing. Specifying is work. That matters more than it sounds when the alternative is a wall of sixteen tiles.
It reaches things nobody self-reports. Nobody puts "good outlet placement" on a list. Everybody has a mixer story. The viewer research names outlet placement as the single most common regret, and it is not a design preference, it is a lived one.
Frame C is the entire return. A complaint in March 2026, the month the project started, becomes a question in May 2027, at the one moment it can still be fixed for the price of a circuit. Fourteen months is the point: nobody remembers saying it, and the app does. Without that, this is just a nice chat.

And it is the only source of stories that scales

The plan targets around forty lived-experience stories and the sourced pool is roughly seven. Philip's thirty are the seed but they live in one conversation. §3.13 of the viewer avatar is nine lines. The RAG "regret" rows are 124 and entirely LLM-synthetic, so they are not lived experience at all.

Every user arrives carrying twenty years of this about the house they live in now. That is a content engine that grows with the user base instead of with authoring hours, and it costs one question per room.

The boundary from the plan still holds: statistics flow, content does not. "Forty-one users complained about pantry depth" is a signal that a question is missing, and it can auto-surface. One household's words becoming another household's guidance needs a human in the loop.

Two design calls

The starters exist because the question can freeze people. "What bothers you" is broad enough to produce a blank stare. "Where do you put the groceries down" does not.
Scope still gets asked separately. Frame B says outlets and shallow storage travel to three other rooms, and names them. Same rule as everywhere else: never widen silently.

Notes on the drawing

Nothing here is compressed to fit. The page used to carry five overrides whose only job was to shave the shared rhythm: card padding to 13 by 15, callouts to 10 by 12, chat bubbles to a 7px gap. They are gone, the page opts into body.hc-air, and cards sit at 26 by 24 with 24 between them. Frame B now runs past the bottom of the phone, which is the correct outcome rather than a problem to solve.
Frame B's result rows are the shared row primitive. They were three hand-built flex blocks with their own type sizes. They are .row now, with the same hairline between them that every other list in the set uses, on a card. The sage that used to say “settled” here is gone; the rows say when each was answered.
The eyebrow and the sub-line on the green hero are colors now, not transparencies. They were --on-primary mixed toward transparent at 62% and 74%, which is opacity by another spelling and measures 3.62:1 and 4.40:1 on --hero-start. Both fail AA. Mixed 80% toward the hero green instead, they are 4.84:1 and read the same.
No frame carries the nav bar, and the reason is different in each. A and B are the ask itself, opened over the room and closed with the X. C is a real decision screen, but the bottom of it belongs to the composer, and a floating nav pill would land on top of it.

Pattern reference: pillowtalk for a reflective prompt that stays on screen while you answer it, and Navigator for the structured result card landing inside the thread.