✌️ hii! i recently stepped into a new role @microsoft.com to lead design operations and reimagine the future of how we build.

that’s me shooting hoops with my dad at the redmond campus 🏀

SoCal vibes (can’t tell if it’s fog or smog in the background) 🌊

Wisdom: a farm-to-table journey.

After the planning cycle, I ran a 1-min survey in Slack (love that feature!) to see how the process landed our PMs, designers and EMs. People also sent DMs of gratitude!

Average NPS = 9, with tons of great feedback on how to make planning even better for next time.

8. Review & Feedback Loop

When teams are ready to share their 1-pager, they just hit a button.

That populates a Slack channel with a link to their doc, tagging execs with next steps. A feedback table at the bottom of each 1-pager facilitates async Q&A between execs and teams.

7. Team Dependencies

I set up an automated master table in Coda so each team has:

- outbound view of asks for other teams
- inbound view of all requests coming in
- description of ask; target delivery date; P1/P2/P3
- status tracker (needs confirmation, confirmed, blocker)

5. Roadmap

Teams embed their roadmaps, wherever that may live (e.g. Coda, Jira, ProductBoard, FigJam etc.). No commentary required.

4. Delivery

These are the other deliverables by work streams, planned for the half.

- 1-sentence description of the work stream and why it matters
- Include screenshots/visuals/prototypes wherever possible!
- Optional: 1-2 stretch goals

3. Launch Moments & Milestones

Most companies have that one "big-bang" event every year where they show off big and exciting product updates.

- Call out launch-related milestones w/ target dates so execs & stakeholders can see what teams plan to ship for prime time

2. Goals

Goals can be audacious, but they should be clear and measurable where possible.

- Two columns, with the team's top 3-4 goals for each quarter and any key metrics
- Goals are (naturally) higher-fidelity for the upcoming quarter vs. 2 quarters out

1. TLDR

This section frontloads the most important tagline a team wants exec stakeholders to know. It includes:

- Plain language outcome statement: "We will affect X towards X bet/initiative by doing X"
- 5-min Loom voiceover on what you plan to deliver

What joy on a wall looks like 🥲

👋 Helloo world! I’m Aletheia—a globetrotting pizza enthusiast, Design/ProductOps leader and Calgary mama.

I worked at the UN, European Commission, French Prime Minister’s Office & Government of Canada, before falling into tech.

I have 2 main vibes: mountain Mama & ice cream pro. Stoked to be here!