--- title: "The client email is not a ticket" subtitle: "Unnamed work looks official. That is how it stays." principle: "Done or dated" date: "2026-09-05T14:35:14.786Z" author: "Mikko Atienza" canonical: "https://ciel.codes/showcase/blog/the-client-email-is-not-a-ticket" edition: "2026-09-05" source: "https://ciel.codes/showcase/pulse/2026-09-05" abstract: "Monday, four cards still say some version of “client wants.” Two have sat since last month. Nobody can say what would make them done. Hours get booked anyway, because a card on a board looks like a job." cite: "Atienza, M. (2026). Done or dated. Pulse." citations: - handle: "@levelsio" url: "https://x.com/levelsio/status/2096177854270550097" - handle: "@poetengineer__" url: "https://x.com/poetengineer__/status/2095976143232827763" - handle: "@hnshah" url: "https://x.com/hnshah/status/2095989719452750237" --- Monday, four cards still say some version of “client wants.” Two have sat since last month. Nobody can say what would make them done. Hours get booked anyway, because a card on a board looks like a job. A fuzzy request is not a ticket. Putting it on the board does not name done. It only makes the shrug look staffed. ## The request that is not a job yet A client writes “can we look at X.” A salesperson forwards it with a shrug. Someone on the floor turns it into a card because leaving it in the inbox feels rude. By Wednesday three people have touched it. By Friday nobody can close it, because close was never written down. Fuzzy is not a failure of the client. It is what new work sounds like before anyone has lived with it. Kat Zhang (@poetengineer__), an engineer who spends her time on work that does not arrive with a spec, put the trap in one line. > For anyone making something new, they can’t articulate their intention — otherwise the work would have been done already. > > Kat Zhang Read that as an operator, not as a theory of creativity. If the person asking cannot yet say what done looks like, they are not handing you execution. They are handing you a question. A ticket is a promise that someone will finish a named thing. Putting the question on the board does not make it named. It only makes it look staffed. Your job this week is not to get better at guessing. It is to stop treating a guess as a commitment. ## Two doors off the inbox Hold the next vague thread in the inbox until it can walk one of two doors. Not three. Not “park it and we’ll see.” Two. Door one: the owner can write a finish line in one sentence. Who is happy, with what, by when. That sentence gets signed. Then it becomes a ticket. The coordinator may break it into tasks. They may not invent the finish. Door two: nobody can write that sentence yet. Then it is not a ticket. It is a short, dated look. An owner, a Friday, and a question to answer. The look exists to make done namable, or to prove it is not worth naming. It does not exist to keep a card warm. ```mermaid flowchart TD A["Coordinator reads the client mail"] --> B{"Owner: can we name done?"} B -->|Yes| C["Owner signs the finish line"] C --> D["Coordinator puts a ticket on the board"] B -->|No| E["Owner dates a look to Friday"] E --> F{"Owner: is done namable now?"} F -->|Yes| C F -->|No| G["Coordinator sends it back or kills it"] style A fill:#1e1b4b,color:#e0e7ff,stroke:#312e81 style B fill:#4c1d95,color:#ede9fe,stroke:#6d28d9 style C fill:#064e3b,color:#d1fae5,stroke:#047857 style D fill:#064e3b,color:#d1fae5,stroke:#047857 style E fill:#1e1b4b,color:#e0e7ff,stroke:#312e81 style F fill:#4c1d95,color:#ede9fe,stroke:#6d28d9 style G fill:#1e1b4b,color:#e0e7ff,stroke:#312e81 ``` The coordinator owns the door. The owner owns the sentence or the date. If those two people are the same person in a shop of twenty, write both hats down anyway. Otherwise the mail still slides onto the board because it felt urgent at 9:40. What you send back can be two options, not a novel. “We can do A by this date, or B if you mean the other thing. Which one is done?” If they cannot pick, you did not fail the client. You refused to staff a shrug. ## The ideas column is last quarter's maybe Look at the other side of the board. The column you call ideas, later, research, or “when we have time.” Half of it is last quarter’s maybe. It feels cheaper than a fake ticket. It is the same shrug in nicer clothes. You tell yourself you are being careful. You are waiting until the intent is clear. Clear intent is what done already looks like. Waiting for it is how a look becomes a permanent resident. Hiten Shah (@hnshah), who has watched a lot of small software companies, keeps a note to himself that is shorter than most status updates: ship the experiments. He is not telling you to dump half-built work on customers. He is telling you to stop storing the experiment in planning. A dated look is how you ship it without lying. It has an owner. It has a Friday. On Friday it either earns a finish line and becomes a ticket, or it comes off. An undated look is not caution. It is a card that cannot fail, so it cannot finish. If you are the person who hates killing work, write the kill rule before the week starts. Anything still unnamed on Friday was never a job. You are not cancelling real work. You are admitting it never arrived. ## You already know what a cheap filter does Think about the noisy channel you already regret. A customer group. A lead Slack. A “just add them” list that anyone can join. You have watched people spend mornings on junk that never should have entered the room. Pieter Levels (@levelsio), who has run a paid community for a decade, dropped the signup to a dollar. Not because a dollar is a business model. Because a dollar is a filter. Free meant hours of spam. A tiny fee meant the people who showed up meant to be there. He still has to moderate. He still has to decide what support quality he will protect. The fee only stops the door from being infinite. Your board needs that kind of cheap gate. Not a charge to the client. A finish sentence. If they cannot name done, they have not paid the dollar. You can still help them. You help them through the dated look, or you send two options back. You do not help them by staffing a card that cannot close. A team this size cannot afford an open board. Ten unnamed cards will eat the week of the three people who actually finish things. You will feel busy. You will not be able to say what got done. ## A Wednesday tally Nobody has a credible figure for how many hours vanish into unnamed tickets. Count your own board. Do it in one pass, with the person who owns the clients sitting next to you. | Measure | Count | |---|---| | Open tickets with no one-sentence finish written on the card | | | Looks, spikes, or “research” cards with no end date | | | Mail threads that became cards this month without either a finish line or a Friday | | Write the three numbers on a sticky. That is the whole dashboard. If the first number is ugly, do not open new work on Thursday. You already have more promises than finish lines. If the second number is ugly, your ideas column is a parking lot. If the third is ugly, the leak is still in the inbox, which means the board will refill by Monday. > **Aside.** Do not average them. Do not turn them into a percentage. The count is the point. You are trying to see how much of the board is theater. ## Run the board cut by Friday Run the cut with the same two people who own the doors. Coordinator and owner. One hour. Cards only, not feelings about cards. - [ ] For each open ticket, write a one-sentence finish or move it to a look with a Friday - [ ] For each undated look, give it Friday this week or take it off - [ ] For each thread that skipped both doors, send two options back and remove the card Put the sticky numbers next to the board after the cut. If a card comes back next week, it comes back through a door. It does not come back because someone was embarrassed to kill it. Walk the inbox the same afternoon. The next vague “can we look at X” stays in mail until an owner names done or dates a look. That is the whole practice. You can run it without a new tool, and without waiting for the client to become a better writer.