Skip to content

Instantly share code, notes, and snippets.

@zhowzeng
Last active May 17, 2024 19:09
Show Gist options
  • Save zhowzeng/7e551e9062a13d4e2b0fe7be964e9db9 to your computer and use it in GitHub Desktop.
Save zhowzeng/7e551e9062a13d4e2b0fe7be964e9db9 to your computer and use it in GitHub Desktop.

[Strategy] Initiative Name

This is a generic doc for any directional discussion. You can mold it to your use case (e.g. major eng initiative, team strategy, partnership alignment, etc)

Problem Context

Where are we today? Explain relevant context for the reader to understand the problem or opportunity you’re going after.

North Star

Where do we want to be? Give a high level statement explaining what winning would look like. This is often something that is directionally correct but perhaps not immediately attainable. Here are some examples:

  • “Google users always find what they’re looking for in the top result” (potentially from some search relevance team/project)
  • “TikTok users never fail to create videos in app” (potentially from some creation reliability team/project)
  • “Amazon users never see inauthentic reviews” (potentially from some amazon reviews team/project)

High-Level Plan

[optional] How will we get there? What major initiatives will we invest in to get us closer to the North Star? Note that for some strategy docs, you might leave the concrete plan out initially to get buy-in on the direction first.

Success Measurement

How do we know we’re making progress? How will we measure success? Talk about the milestones & metrics that you’ll use to track this initiative.

Appendix

Use this section for details you want to refer to but not inline in the doc since they’re too verbose or not necessary for the reader to understand the strategy.

  • Link/table/diagram/etc
  • Link/table/diagram/etc
  • Link/table/diagram/etc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment