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—two programs, 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.

Nathan is willing to make the case. He is not willing to inflate it. The current pile cannot tell him which claims have a source, which are still a feeling, and which belong to a team rather than to him.

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.

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

That distinction matters. Superboard can make the work, evidence, waiting, and decision visible. Nathan still owns the purpose, tradeoff, and final call.

A useful Board gives this mission one durable operating picture. Nathan does not have to convert life into project-management jargon or decide the perfect taxonomy first. Lists separate kinds of attention; Cards keep each meaningful item visible and movable.

The Cards are deliberately mixed. Some are tasks, some are decisions, some hold a person or promise, and some are reference points. Current Superboard supports that flexibility without flattening the mission into one long to-do list.

A Board becomes useful when the Card titles sound like the actual situation. These are not generic placeholders; they show what Nathan would need to see to run this mission without carrying every open loop in memory.

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 Waiting for Nathan to choose which story the packet leads with. Activity preserves the attributable Card record supported by the current product.

A useful Card Chat request would be: “Using only this Board, 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 context and can make limited reversible product changes. She does not deeply reason over the whole Board by default, and 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 are useful requests to adapt, not claims that current Ava automatically surveys the whole Board, prepares every comparison, or follows up on her own. The relevant facts must be present in supported Board/Card context, and the human still checks the result.

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.

The modest outcome is not that Ava lives Nathan's life. The modest outcome is a packet with a chosen lead and a source rule: unlabeled screenshots are work, not proof, and team credit stays visible.

• Request idea: summarize evidence, stories, and waiting verifications already on the Board
• Request idea: compare lead-story options using what is sourced versus still unchecked
• Request idea: help keep unlabeled artifacts out of the ready pile

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

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

Superboard earns a place only when the responsibility needs a durable picture around the list: the reason, artifact, conversation, current state, decision, and history.

Use the names that already make sense in Nathan's world. The recipe is successful when the Board reduces remembering and exposes the real decision—not when every Card is perfectly categorized.

Later, Ava may help this Board notice when a story Card still depends on Waiting verification, still leaving every claim with Nathan.

The unified You.one and Superboard runtime, cross-product personalized Memory Spine, broad proactive coordination, realtime shared editing, and general external execution are not available today. Future actions 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.