impact-review

name

impact-review

description

Generates a performance review summary of my significant contributions and impact over the past six months, drawing from my Teams chats, emails, meetings, OneDrive files, and SharePoint activity. Use when I ask to "run impact review", "generate my performance review", "what did I accomplish", "draft my impact summary", "contribution review", "what did I do this year", or "draft my connect reflection".

Workflow

Step 1: Gather Data

Search across all of the following for significant contributions since six months ago:

• Teams meeting chats and recordings: Decisions made, things presented, customer conversations, workshops run, outcomes driven.
• Email (sent and received): Threads where I initiated something, drove resolution, received positive acknowledgment, or led a significant effort. Ignore routine scheduling and FYI threads.
• Calendar: Significant meetings I organized or led — workshops, customer engagements, team sessions, reviews.
• OneDrive and SharePoint: Documents, decks, or assets I authored or heavily edited that were shared broadly or used in customer or team engagements.
• Teams channel activity: Posts I authored that got significant reactions, replies, or led to action.

Step 2: Filter for Significance

Only include items that meet at least one of these bars:

• Involved a customer or external stakeholder
• Resulted in a deliverable (deck, document, PoC, proposal, report) that was shared or used
• Received explicit positive feedback, praise, or thanks from peers, leadership, or customers
• Drove a decision, unblocked a team, or accelerated something meaningful
• Was a workshop, training, or enablement session I led
• Required sustained effort over multiple weeks

Exclude: routine 1:1s, recurring standups, read receipts, low-engagement threads, and one-line replies.

Step 3: Write the Review

Generate a performance review summary for me. Write it in first person ("I led...", "I delivered..."). This is intended to be pasted directly into a performance review.

Structure the output as bullet points grouped under 3–5 themes that emerge naturally from the data (examples: "Customer Impact", "Team Enablement", "IP & Thought Leadership", "Strategic Contributions"). Do not force categories — use what the evidence supports.

For each bullet:

• Lead with the outcome or impact, not the activity
• Include specifics: customer names (if findable), dates or timeframes, team names, project names
• If positive feedback or reactions exist, incorporate them as evidence
• Keep each bullet to 1–3 sentences — tight and punchy, not narrative prose

Example bullet style (tone reference only):

Led architecture review and PoC delivery for [Customer], resulting in validated AI adoption path and [outcome]. Received recognition from [person/team] for accelerating the customer's decision timeline.

Step 4: Add Summary

After the bullet themes, add a short paragraph (3–5 sentences) titled "Summary" that serves as an opening statement for the review — the elevator pitch of the past six months.

Tone and Voice

• Professional, confident register appropriate for a corporate performance review
• Active voice throughout
• No hedging ("I think", "possibly", "tried to") — state what happened
• No em-dashes
• Avoid generic filler phrases like "drove alignment" or "synergized across teams" unless backed by a specific example