Skip to content
You.one

Join the You.one waitlist

Already joined? Find your link

Example

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

Omar has to decide whether Friday stays with the contracted two sites, includes a deliberately thin appendix, or moves while he prices the third site. Sponsor enthusiasm cannot quietly turn an extra location into finished scope.

You.one · Superboard viewTwo-site delivery

Make a dated Friday call that keeps the original two sites honest and treats site three as a priced change or a no

Mission2

Original scope, Friday, and the change-order rule

Original contracted scope is two sites; site three is a priced change or a no

Keep hours and the change-order rule visible beside sponsor enthusiasm

Choose how Friday treats site three

Compare two-sites-only, thin appendix, and delay-to-price options

Sites2

Each location’s evidence and remaining questions

Site A interview notes

Attach evidence to the location it belongs to

Missing Site B night-shift interview

Keep Site B’s evidence gap attached to the location instead of filling it with confidence in slides

Readout1

What Friday will actually claim

Plant manager wants a recommendation now

Mark a claim Friday is not yet able to make

Change asks1

Extras from email that are not yet work

Sponsor email: add site C

Hold the extra as an ask, not as silent scope

An illustrative Board built from this fictional scenario. Adapt the Lists and Cards to your own mission.
Structured Board artifact for consulting delivery: contracted two-site scope, a third-site email request, missing night-shift evidence, and Friday's readout beside three scope paths.
The scope picture separates contracted work from a new ask and keeps unsupported Friday claims visible before Omar chooses the delivery posture.
01

The Two-site delivery Board keeps original scope, site evidence, claims Friday can support, and extra asks in distinct plain-language Lists.

02

The Scope Room compares two-sites-only, thin-appendix, and delay-to-price paths beside the missing Site B interview and Site C request.

03

Ava can organize the visible scope evidence. Omar owns the client recommendation, pricing, claims, timing, and every sponsor conversation.

A third site in email is not scope until it is priced and dated

This Board has one job: Make a dated Friday call that keeps the original two sites honest and treats site three as a priced change or a no.

The decision still belongs to Omar: 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. Authority does not move to the software: Omar chooses the scope, talks to the sponsor, and owns every recommendation he is willing to stand behind.

Available today

Two-site delivery: one place for the mission

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.

The Board is not a master task list. It keeps the live choice, the facts that could change it, and any reply or outside event already in motion visible without pretending every uncertainty is work in progress.

Swipe or scroll sideways to see every column.

Two-site delivery Board shape
ListWhat belongs here
MissionOriginal scope, Friday, and the change-order rule
SitesEach location’s evidence and remaining questions
ReadoutWhat Friday will actually claim
Change asksExtras from email that are not yet work

Available today

Cards that sound like the real work

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 something already awaiting another person. The point is recognition, not a perfect taxonomy.

Swipe or scroll sideways to see every column.

Example Cards for Omar
CardListJob
Original contracted scope is two sites; site three is a priced change or a noMissionKeep hours and the change-order rule visible beside sponsor enthusiasm
Choose how Friday treats site threeMissionCompare two-sites-only, thin appendix, and delay-to-price options
Site A interview notesSitesAttach evidence to the location it belongs to
Sponsor email: add site CChange asksHold the extra as an ask, not as silent scope
Plant manager wants a recommendation nowReadoutMark a claim Friday is not yet able to make
Missing Site B night-shift interviewSitesKeep Site B’s evidence gap attached to the location instead of filling it with confidence in slides

Available today

Keep the evidence with “Choose how Friday treats site three”

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.”

A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Choose how Friday treats site three” from the visible evidence. Ava can work from the context Omar deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.

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

Swipe or scroll sideways to see every column.

Inside the Choose how Friday treats site three Room
SurfaceJob in this example
StageScope brief: Place original scope, remaining interviews, and two-sites / appendix / delay options on one page
ChatKeep Omar's request and Ava's attributed response with the work
PulseOpen decision: Omar will choose Friday’s scope

Start small and rename what feels artificial

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.

Swipe or scroll sideways to see every column.

Start with the Two-site delivery Board
StepAction
1. Restate original scopeSites and Friday on the Mission Card
2. Attach evidence to sitesNotes are not a pile
3. Park email extrasChange asks are not work
4. Mark claims Friday cannot makeGaps stay visible
5. Choose how Friday treats site threeOpen a Room before the deck lies

Three slide decks plus sponsor email can remain part of the system

Three slide decks plus sponsor email can be enough while the situation stays simple: 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.

Where this example stops

  • This is a fictional example, not a customer story.
  • 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.

Keep the third site an explicit choice before the deck turns it into scope.

See how Superboard works