How will that feel?

Three scenes from the intended future of working with SDD. They are not fiction about a distant system: each scene ends with an honest note naming what already works today and what is still being built or discussed. The names and settings come from a digital-agency world, because that is where our first partners work; the pattern in each scene belongs to any team that decides together.

The product owner

Jana runs a relaunch project for a retail client at her agency. Tuesday morning, the client’s marketing lead sends an email: legal now requires a cookie-less analytics setup, and the go-live date cannot move.

In the old workflow this email would start a chain: forward it to the tech lead, write a ticket from memory, schedule a meeting to find out what it actually means. Instead, the email arrives in the project’s shared record as a candidate. An assistant has already read it, connected it to the analytics decision from June and to the go-live commitment, and written down what it thinks the email changes, and what it isn’t sure about. Nothing is final; the candidate waits for a person.

Jana opens a short dialogue over her first coffee. The assistant lays out the connection: the June decision assumed the current analytics tool, and the email contradicts that assumption. Together they settle what this is. A new constraint, recorded with the client’s exact words and a link to the email. And an open question for the tech lead: which cookie-less options fit the budget? Five minutes. The record has grown, and the tension between the new constraint and the June decision is now visible to everyone, not just to Jana.

The client’s own issue tracker doesn’t go away. The client team lives in it, so the agreed follow-up appears there as a ticket, generated from the recorded question, carrying a plain-language summary rather than the whole reasoning. When the ticket closes, its status flows back. The tracker stays what it is for the client: their familiar surface. The shared record stays what it is for the project: the place where the reasoning lives.

The same scene plays out wherever outside requirements land in somebody’s inbox: a supplier’s price change, a new regulation, a customer request.

The project lead

Marek leads a team working three streams of a client project at once. His morning starts without a standup. He opens his briefing, shaped to him: what moved in his streams since yesterday, which decisions landed, and where something waits on his answer. A designer carried the onboarding flow forward; an agent finished a data migration overnight and recorded exactly what it did and why; one decision needs his read before the eleven o’clock call. Nobody recites yesterday. Nobody waits for a sprint boundary. The work moves as many small loops, each closing when it closes, and the shared record keeps them coherent instead of a ceremony.

When Marek checks what to push next, the priorities carry their why. The payment flow doesn’t just say “high”: it says the contract carries a penalty date, and links the reasoning. Yesterday a developer had to choose between two tasks and chose right without asking him, because the why was readable.

At eleven, the client meeting. Beforehand, the record prepared the ground: the two decisions that need the client’s sign-off and three open questions only they can answer, in plain words, no internal vocabulary. The meeting is short. Afterwards Marek drops the notes in; a short dialogue sorts them. Two answers close their questions, one new wish becomes an observation for the design stream, and one misunderstanding is recorded as exactly that. He confirms each item once, so what lands stays true to what was said. Nothing gets typed into three systems.

The same morning exists for anyone coordinating people who decide: a head of operations, a clinic manager, a restaurant owner.

The UX designer

Carla runs a usability test on the checkout redesign. While packing up, she speaks her findings into her assistant the way she would tell a colleague: three of five participants missed the save action; two described the new wizard as “filling in a form, not being guided”. A short dialogue later, both observations sit in the shared record, connected to the checkout decisions they touch, in her words, with the test session as their source.

Weeks later, someone proposes trimming the confirmation step down to an icon-only button. The proposal gets flagged before it lands: it contradicts Carla’s recorded finding that participants missed icon-only actions. The tension surfaces to Carla and the proposer together, both entries side by side. Not as a rejection, but as a conversation that has to happen. They talk; the proposal changes shape. Nobody had to remember the finding. The record did.

The same week, Carla joins a second project mid-flight. The navigation is a side drawer, and her instinct says tabs. Instead of asking around (who decided this? was it deliberate?), she reads the decision: what was tried in the first round, why tabs broke on the seller dashboard, which customer feedback grounded the call. Her instinct updates in ten minutes, and her next question is a better one: has the seller dashboard constraint survived the latest redesign? She records it as an open question, and it finds the person who knows.

The same protection exists for any team whose hard-won observations must outlive the moment they were made: field research, customer interviews, clinical practice.