Skip to content
You.one

Join the You.one waitlist

Already joined? Find your link

Example

How to plan a block party when a permit is not a community

Rita’s event wishlist is growing faster than ownership. The useful decision is whether to keep the potluck, hire one vendor, or shorten the event before music and activity ideas become promises nobody agreed to carry.

Superboard exampleStreet together

Host a simple street gathering with shade, seating, food clarity, and responsibilities neighbors actually choose

Neighbor promise1

The promise and limits Rita is protecting

Street together

Hold the mission and boundary: host a simple street gathering with shade, seating, food clarity, and responsibilities neighbors actually choose

Event next4

Choices and actions Rita can move without pretending every fact or outside wait is owned work

Potluck, vendor, or simpler

Hold the live choice—whether to keep a potluck, hire one food vendor, or make the event shorter and simpler—so Rita can decide from the evidence in this Room

Inventory shade, seating, food, and sound setup needs

Prepare the next owned move without treating a draft, check, or test as evidence that anyone has agreed

Check current permit status

Check the official permit page and record the current status, any approval if present, the applicable window, and stated limits without implying a person must reply

Ask each volunteer which setup job they are willing to own

Use the result of the first owned action to update the Party-shape brief; record the finding, not merely the effort

Participation evidence1

Source facts, observations, and artifacts that can change “Potluck, vendor, or simpler”

Four setup volunteers

Supply the evidence for the Party-shape brief: place volunteers, access, food, seating, sound, and permit limits together. Live choice: Whether to keep a potluck, hire one food vendor, or make the event shorter and simpler.

An illustrative Board built from this fictional scenario. Adapt the Lists and Cards to your own mission.
Decision diagram for a neighborhood block party: actual volunteers, shade, seating, food, and permit evidence beside three event-shape choices.
01

The Street together Board keeps the neighbor promise, next event work, participation evidence, and permit status in one view.

02

The party-shape Room compares potluck, vendor, and simpler-event paths while asking each volunteer which setup job they will actually own.

03

Ava can prepare the options from visible evidence. Rita and the neighbors make the commitments, handle permits and food choices, and decide the event.

Street together has one live choice: Potluck, vendor, or simpler

This Board has one job: Host a simple street gathering with shade, seating, food clarity, and responsibilities neighbors actually choose.

The decision still belongs to Rita: Whether to keep a potluck, hire one food vendor, or make the event shorter and simpler.

You.one can keep the work, evidence, and “Potluck, vendor, or simpler” decision visible through its Superboard view. Authority does not move to the software: Rita, as the resident organizing her street's first block party, owns the preparation and the decision about whether to keep a potluck, hire one food vendor, or make the event shorter and simpler.

Available today

Street together: one place for the mission

The Street together Board gives this mission one durable operating picture. Rita can use familiar language instead of translating the situation into project-management jargon. Its three 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.

Street together Board shape
ListWhat belongs here
Neighbor promiseThe promise and limits Rita is protecting
Event nextChoices and actions Rita can move without pretending every fact or outside wait is owned work
Participation evidenceSource facts, observations, and artifacts that can change “Potluck, vendor, or simpler”

Available today

Cards that sound like the real work

These Card titles come directly from Rita's situation: “Potluck, vendor, or simpler” is the live choice, “Four setup volunteers” holds evidence, and “Check current permit status” is still work Rita 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 Rita
CardListJob
Street togetherNeighbor promiseHold the mission and boundary: host a simple street gathering with shade, seating, food clarity, and responsibilities neighbors actually choose
Potluck, vendor, or simplerEvent nextHold the live choice—whether to keep a potluck, hire one food vendor, or make the event shorter and simpler—so Rita can decide from the evidence in this Room
Four setup volunteersParticipation evidenceSupply the evidence for the Party-shape brief: place volunteers, access, food, seating, sound, and permit limits together. Live choice: Whether to keep a potluck, hire one food vendor, or make the event shorter and simpler.
Inventory shade, seating, food, and sound setup needsEvent nextPrepare the next owned move without treating a draft, check, or test as evidence that anyone has agreed
Check current permit statusEvent nextCheck the official permit page and record the current status, any approval if present, the applicable window, and stated limits without implying a person must reply
Ask each volunteer which setup job they are willing to ownEvent nextUse the result of the first owned action to update the Party-shape brief; record the finding, not merely the effort

Available today

Keep the evidence with “Potluck, vendor, or simpler”

Opening the Card gives the visible item durable depth. Stage can hold Party-shape brief: Place volunteers, access, food, seating, sound, and permit limits together. Live choice: Whether to keep a potluck, hire one food vendor, or make the event shorter and simpler. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Rita will decide whether to keep a potluck, hire one food vendor, or make the event shorter and simpler.”

A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Potluck, vendor, or simpler” from the visible evidence. Ava can work from the context Rita deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.

Rita's call remains explicit: Rita, as the resident organizing her street's first block party, owns the preparation and the decision about whether to keep a potluck, hire one food vendor, or make the event shorter and simpler.

Swipe or scroll sideways to see every column.

Inside the Potluck, vendor, or simpler Room
SurfaceJob in this example
StageParty-shape brief: Place volunteers, access, food, seating, sound, and permit limits together. Live choice: Whether to keep a potluck, hire one food vendor, or make the event shorter and simpler
ChatKeep Rita's request and Ava's attributed response with the work
PulseOpen decision: Rita will decide whether to keep a potluck, hire one food vendor, or make the event shorter and simpler

Start small and rename what feels artificial

Rita should rename every List or Card that feels artificial. This recipe succeeds when “Potluck, vendor, or simpler” 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 Street together Board
StepAction
1. Write the missionHost a simple street gathering with shade, seating, food clarity, and responsibilities neighbors actually choose
2. Open the live choicePut “Potluck, vendor, or simpler” in a Room of its own
3. Attach the evidenceParty-shape brief: Place volunteers, access, food, seating, sound, and permit limits together. Live choice: Whether to keep a potluck, hire one food vendor, or make the event shorter and simpler.
4. Keep the work ownedKeep “Check current permit status” in owned work and name the next visible move
5. Take the first owned actionAsk each volunteer which setup job they are willing to own

A neighborhood email thread can remain part of the system

A neighborhood email thread can be enough while the situation stays simple: “Inventory shade, seating, food, and sound setup needs” and “Check current permit status” no longer change the “Potluck, vendor, or simpler” choice.

It starts to break when “Four setup volunteers” and “Check current permit status” must inform the same choice.

The Street together Board earns its place only when the familiar tool—a neighborhood email thread—can no longer keep the reason, Party-shape brief, conversation, current state, decision, and history connected.

Where this example stops

  • This is a fictional example, not a customer story.
  • This fictional example is not permit, traffic, food-safety, accessibility, child-safeguarding, insurance, or public-event advice; neighbors and responsible authorities own the real gathering.
  • It does not show Ava completing external actions or contacting anyone for Rita.
  • It does not report a measured result, and this Board is a starting shape to adapt—not a universal prescription.

Build the gathering from volunteered ownership, not a wishlist.

See how Superboard works