Publish clear VSP north star and vision

[rroueche]

• Responsible: Rachael and Kevin
• Accountable: all

---

Problem statement: teams don't have what they need today to understand overall platform vision and priorities, or initiatives across other platform teams and how they fit together as a greater whole. This makes it hard for teams to coordinate/prioritize dependencies, or make calls on trade-offs. It often feels as if we are a bunch of teams working on a bunch of stuff, rather than a cohesive set of teams all contributing toward a shared vision.

Goal: publish and present content to all of VSP (and externally as a next priority) that:

• Inspires and motivates
• Illustrates the experience and outcomes we seek for VA, VFS Teams, and VA.gov users
• Clarifies what success looks like
• Has repeatable messaging
• Allows VSP teams and individuals to see themselves in the platform’s purpose and journey

Development check list:

Artifacts

• [x] Artifact: Short and sweet high level strategy document
• [x] Vision Letter (Andrew Gunsch author)
• [ ] Team mission clarity
• [ ] Principles
• [ ] How vision connects to the near term
• [ ] What is the scope of platform? What should fall under it?
• [ ] KPIs / how we measure success
• [ ] Deck w/short and sweet messaging about all of the above

Other tasks

• [x] Initial Presentation to full team
• [ ] Docs shared w/full team and pinned in Slack
• [ ] Slackbot updated w/auto-responses based on keywords
• [ ] Plaster vision and mission everywhere, in all the ways we communicate (use mission statement on the newsletter!), other docs updated or retired to point to canonical docs
• [x] 2 way communication path - specifically for this content - exists (knowing that we want to launch this w/o waiting on a final overall communication plan)

Stretch

• [ ] Incorporate any definitions into C&IA's word list (Vision, Mission, Platform, Customer (what else?))

---

Release plan:

1. 5/29: Kevin posts his Friday message sharing our high level strategy document, setting expectations about additional strategy info to come, and linking to rolling questions and feedback doc.
2. 6/2: Andrew shares vision letter with more detail and clarity, but without team-specific details
3. 6/5: Kevin shares Friday post tying the two vision docs together
4. 6/10: We answer Q&A from the document, and promise when we'll share the next draft
5. After that enter written answers to the questions

Goal is that going into Q3, this is no longer a draft

[rroueche]

Activities to consider doing as a part of visioning:

• "vision" brainstorm
• "success" brainstorm
• team mission survey
• "north star" or "kpis" voting
• priority voting on vsp principles and tenets
• vision map (vision -> teams -> this year's objectives -> this quarter's work)

Ideas for communication

• share written materials in advance, and ask each team to appoint someone to collect and ask questions at the presentation.

[rroueche]

Working with @KevinMHoffmanUSDS to rubber stamp the "blue" content for a short and sweet one pager, and to start communication process.

Nutshell communication plan:

• Share the high level one pager (the blue content) in week 1 as a part of the Friday post
• Share more detail about the vision, team missions, and how this vision connects to the quarterly roadmaps in week 2
• Give a presentation w/Q&A of that content in week 3 using pre-existing meeting like End of Sprint Demos

To do

• [x] RR: pop the blue content into a google doc one pager
• [x] RR: get the approved content into the deck so it's ready for review in our daily standups
• [x] KH: format and brand one pager (if needed), and make sure leads are OK with it
• [x] RR: set target dates for written comms + preso
• [ ] Full leads team: Sync up on the deck
• [ ] KH: draft content for sharing one pager in the Friday post (set expectations w/this content around the element of "there's more info to come")
• [x] RR: coordinate with Nancy so we can use the AMA doc for people to track their questions
• [ ] RR: send activity for team missions work
• [ ] RR: schedule time w/Kevin to outline the 6/5 post

[andreahewitt-odd]

Should this just be VSP or all of DEPO platform? Something we should explore in discovery.