How a consultant can run client delivery without hiding scope in slides

Omar is a fictional 42-year-old independent operations consultant mid-engagement in Dallas, Texas. Omar is six weeks into a warehouse-process project. The original scope was two sites. A sponsor keeps adding a third site in email. The readout is Friday and the working notes are still in three slide decks.

Sponsor email, a shared drive of interviews, and three decks all claim to be the engagement.

A plant manager asked for a recommendation Omar is not ready to make. That ask is currently shaping the slides.

In You.one's Superboard view, Omar can give “Make a dated Friday call that keeps the original two sites honest and treats site three as a priced change or a no” a Board of its own. That Board connects source evidence, unresolved questions, decisions, and accountable judgment; opening “Choose how Friday treats site three” creates a Room for its evidence, discussion, state, and decision.

The mission is specific: Make a dated Friday call that keeps the original two sites honest and treats site three as a priced change or a no.

The consequential choice is not something a board or an AI should quietly make: Whether to keep Friday to two sites, add a thin third-site appendix, or delay Friday to price a change order.

You.one can keep the work, evidence, and “Choose how Friday treats site three” decision visible through its Superboard view. The Owner boundary stays explicit: Omar chooses the scope, talks to the sponsor, and owns every recommendation he is willing to stand behind.

The Two-site delivery Board gives this mission one durable operating picture. Omar can use familiar language instead of translating the situation into project-management jargon. Its four Lists separate the kinds of attention this situation actually requires.

Its Cards deliberately distinguish actions, evidence, and decisions while keeping unsent questions in owned work. A Waiting List would be premature until a named request or outside condition is actually in motion. That separation makes the current choice, evidence, and next move easier to scan.

These Card titles come directly from Omar's situation: “Choose how Friday treats site three” is the live choice, “Site A interview notes” holds evidence, and “Plant manager wants a recommendation now” is still work Omar controls—not a fake Waiting item. The point is recognition, not a perfect taxonomy.

Opening the Card gives the visible item durable depth. Stage can hold Scope brief: Place original scope, remaining interviews, and two-sites / appendix / delay options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Omar will choose Friday’s scope.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Scope brief and this Card Room's visible notes and left “Choose how Friday treats site three” with Omar.”

A useful Card Chat request would be: “Using only the context visible in this Card Room, compare keeping Friday to two sites, adding a thin appendix, and delaying to price a change. Do not email the sponsor or choose for me.” When live AI is configured, current Ava can respond to an explicit Card mention using supported Room context and can make limited reversible changes inside this Card Room after an explicit request. She uses only supported Room context; she cannot summarize the Board, watch other Lists, or act outside this Card Room. She does not gain authority over the decision merely because the context is organized.

Omar's call remains explicit: Omar chooses the scope, talks to the sponsor, and owns every recommendation he is willing to stand behind.

These requests use the visible supported context inside the “Choose how Friday treats site three” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Omar must provide the relevant facts and check the result.

Current Ava can reply in this Room to an explicit Card mention using supported Room context. She cannot summarize the Board, make the choice, represent Omar, watch other Lists, or act outside this Card Room.

Omar owns advice, contracts, and sponsor conversations. Ava does not email the client, write the readout, or expand scope.

A Friday that matches evidence: two sites are the delivery, the third is a change or a no, and a recommendation is not invented to fill a gap.

• Request idea: using only the context visible in this Card Room, compare keeping Friday to two sites, adding a thin appendix, and delaying to price a change. Do not email the sponsor or choose for me.
• Request idea: use only the Scope brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
• Request idea: name which visible Room note could most change the comparison; do not watch other Lists or follow up autonomously

Three slide decks plus sponsor email is enough when scope is stable and evidence is in one place.

It starts to break when a third site and a premature recommendation both try to write Friday.

The Two-site delivery Board earns its place only when the familiar tool—three slide decks plus sponsor email—can no longer keep the reason, Scope brief, conversation, current state, decision, and history connected.

Omar should rename every List or Card that feels artificial. This recipe succeeds when “Choose how Friday treats site three” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.

Later, Ava may help this Board notice when a readout Card outruns the evidence attached to its Site, still leaving every recommendation with Omar.

A future unified You.one experience could carry relevant context from “Choose how Friday treats site three” across guidance and the Superboard view. Broad proactive coordination, cross-surface personalized memory, realtime shared editing, and general external execution are not available today. Any future action would still require the applicable capability, connection, grant, and human authority.

• Omar is fictional and is not a customer, testimonial, research participant, or disguised real person.
• This is not a consulting-result, savings, or performance claim.
• It does not show Ava contacting a client or writing a professional recommendation.
• It is not a measured engagement outcome.