How to keep a promotion evidence file without turning the year into a brag list

Nathan is a fictional 38-year-old senior analyst preparing a promotion packet in Atlanta, Georgia. Nathan’s manager asked for a packet in six weeks. The work is real—a forecasting program, a messy vendor recovery, and a junior colleague he coached—but the evidence is in slide decks, Slack praise, and a memory of numbers he has not re-checked.

A dashboard screenshot from March is unlabeled. A peer’s thank-you lives in a chat that may be gone next quarter.

The vendor recovery involved four people. Writing “I led” without naming the others would be easier and less true.

In You.one's Superboard view, Nathan can give “Build a promotion packet of dated, sourced evidence that distinguishes Nathan’s work from team work without inflating either” a Board of its own. That Board connects unlabeled screenshots, praise that may vanish, shared vendor credit, verification work, and the six-week packet clock; opening “Choose the lead story” creates a Room for its evidence, discussion, state, and decision.

The mission is specific: Build a promotion packet of dated, sourced evidence that distinguishes Nathan’s work from team work without inflating either.

The consequential choice is not something a board or an AI should quietly make: Whether the lead story is the vendor recovery, the forecasting program, or the coaching record, given what can actually be sourced in six weeks.

You.one can keep the work, evidence, live dependency, and “Choose the lead story” decision visible through its Superboard view. The Owner boundary stays explicit: Nathan chooses the lead story, verifies numbers, asks people for examples, and owns every sentence in the packet.

The Promotion packet Board gives this mission one durable operating picture. Nathan can use familiar language instead of translating the situation into project-management jargon. Its six Lists separate the kinds of attention this situation actually requires.

Its Cards deliberately distinguish actions, evidence, a live dependency, and decisions. A Waiting List is useful here only because a named request or outside condition is already in motion. That separation makes the current choice, evidence, and next move easier to scan.

These Card titles come directly from Nathan's situation: “Choose the lead story” is the live choice, “March dashboard screenshot” holds evidence, and “Priya coaching example requested” names something genuinely in motion outside Nathan's control. The point is recognition, not a perfect taxonomy.

Opening the Card gives the visible item durable depth. Stage can hold Lead-story comparison: Place sourced versus unsourced evidence beside the three candidate stories and the six-week date. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Nathan will choose which story the packet leads with.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Lead-story comparison and this Card Room's visible notes and left “Choose the lead story” with Nathan.”

A useful Card Chat request would be: “Using only the context visible in this Card Room, compare the three lead stories on what is already sourced versus still waiting. Do not write the packet 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.

Nathan's call remains explicit: Nathan chooses the lead story, verifies numbers, asks people for examples, and owns every sentence in the packet.

These requests use the visible supported context inside the “Choose the lead story” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Nathan 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 Nathan, watch other Lists, or act outside this Card Room.

Nathan owns the claims, the numbers, and every conversation with his manager and peers. Ava does not invent impact, contact people, or submit the packet.

A packet with a chosen lead and a source rule: unlabeled screenshots are work, not proof, and team credit stays visible.

• Request idea: using only the context visible in this Card Room, compare the three lead stories on what is already sourced versus still waiting. Do not write the packet or choose for me.
• Request idea: use only the Lead-story comparison 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

A folder of old slides is enough when there is one project and a manager who already remembers it.

It starts to break when six weeks remain and the strongest memory is still unlabeled.

The Promotion packet Board earns its place only when the familiar tool—a folder of old slides—can no longer keep the reason, Lead-story comparison, conversation, current state, decision, and history connected.

Nathan should rename every List or Card that feels artificial. This recipe succeeds when “Choose the lead story” 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 story Card still depends on Waiting verification, still leaving every claim with Nathan.

A future unified You.one experience could carry relevant context from “Choose the lead story” 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.

• Nathan is fictional and is not a customer, testimonial, research participant, or disguised real person.
• This is not HR advice, a promotion guarantee, or a claim Superboard accessed company systems.
• It does not show Ava writing the packet, verifying payroll, or contacting peers.
• It is not a measured compensation or title result.