Hi there,

​

Most people work hard but leave no clear record of the value they create. That means performance reviews rely on memory, and interviews feel like guesswork. You can fix this by saving small artifacts and writing short summaries that make your impact obvious. Today you will pick outcomes, collect proofs, write one-pagers, publish everything in a single hub, and use it in reviews and interviews.

The Playbook

Step 1: Choose outcomes to prove

How to do it: Write three outcomes your role should drive, such as faster delivery, better quality, or happier customers. Attach one simple metric to each outcome so progress is easy to see.

​

Proof: You can point to a short list of outcomes, each with a matching metric, and your manager agrees they fit your role.

Step 2: Collect small artifacts weekly

How to do it: Save before-and-after screenshots, tiny charts, short clips, or stakeholder quotes in a dated folder. Name files clearly so anyone can tell what they show and when.

​

Proof: Your folder fills with weekly evidence that a reviewer can scan in minutes and understand without extra context.

Step 3: Write one-page project summaries

How to do it: For any work that mattered, create a one-pager with Title, Goal, Role, Actions, Results, and Links to artifacts. Keep sentences short and end with one visible number that moved.

​

Proof: People can read your impact in under two minutes and repeat the result in their own words.

Step 4: Publish everything in one hub

How to do it: Use a single location such as a Notion page or a cloud drive folder with a clean index. Group proofs by outcome and pin your top five.

​

Proof: Reviewers stop asking for scattered links and share your hub in threads as the source of truth.

Step 5: Use proofs in conversations

How to do it: Bring two one-pagers to 1:1s and performance reviews. In interviews, answer with a short story and share an artifact link so the proof speaks for you.

​

Proof: Decisions move faster because your examples are concrete and easy to verify.

Skill Focus

Skill 1: Evidence writing

Why it matters: Clear, brief writing turns activity into impact that others can see. It reduces debate and makes your work easier to sponsor.

​

Practice this week: Rewrite one long project note into a one-pager using Title, Goal, Role, Actions, Results, and Links. Remove fluff and keep verbs strong and simple.

​

Apply at work: Share the one-pager in your project channel and in your 1:1. Ask whether the result line is clear and which number matters most to the team.

​

Proof to show: Your manager reuses your wording in their update, and the result line appears in a planning deck.

Skill 2: : Metric selection

Why it matters: The right number turns a story into direction. Consistent metrics build trust and protect you from opinion-based debates.

​

Practice this week: For one outcome, pick a single KPI with the formula, time window, and exclusions written in one line. Test it on last week’s data and validate it with a peer.

​

Apply at work: Put the rule above your chart and keep the time window consistent. Note only what changed and why it matters to your plan.

​

Proof to show: Two people calculate the same value and get the same result. Reviewers quote your KPI when discussing next steps.

Skill 3: Interview storytelling

Why it matters: Good stories compress months of work into a clear arc that shows judgment and results. They help you stand out without hype.

​

Practice this week: Use a simple frame: Situation, Task, Actions, Results, Proof link. Keep each part to one or two sentences.

​

Apply at work: Practice two stories out loud and attach an artifact link at the end. Use the same stories in reviews and external interviews.

​

Proof to show: Listeners can retell your story accurately and ask deeper questions about your choices, not basic facts.

Case study

Thomas was a mid-level analyst who delivered solid work but struggled to show impact during reviews. His updates were text-heavy, and artifacts were scattered across chats and folders, so results were hard to verify. He picked three outcomes with matching metrics, saved weekly artifacts in a dated folder, and wrote one-pagers for two projects that moved key numbers.

​

He published a single hub with a simple index and pinned five top proofs. In his next review, he opened with the index and walked through two stories supported by before-and-after charts. The conversation shifted from defending effort to planning bigger scope. Three months later, he used the same proofs in an external interview and received an offer at a higher level.

Action steps

Lock the habit with small, visible moves. Build your first hub this week so evidence starts compounding.

• List three outcomes your role should prove, and write one metric rule for each.
• Create a dated folder and save two artifacts from this week with clear file names.
• Turn one recent project into a one-page summary with links to artifacts.
• Build a simple hub page and group items by outcome, with your top five pinned.
• Bring two one-pagers to your next 1:1 and ask which proof matters most for the team’s goals.

These steps make your impact easy to see and easy to sponsor. Repeat the loop weekly so your portfolio grows with every small win, and you never walk into a review or interview empty-handed.