Compass content strategy gameplan
0. Kickoff
Stage | Description and deliverables | Dates | Contributors |
---|---|---|---|
Literature review |
Understand, summarize, and make plain the work done up to this point by contributors prior to our involvement
|
Prior to kickoff | Sam Irons |
Kickoff workshop |
Define vision statement, drivers, decision model, project scope, trade-off sliders, early ideas for success, and stakeholder engagement model
|
31 Mar 2021 | Core team members and senior stakeholders |
1. Wonder - 07 Apr – 23 Apr 2021
Stage | Description and deliverables | Dates | Contributors |
---|---|---|---|
Success metrics |
Outline the goals, signals, and measures we’ll use to judge success of Compass content
|
07 Apr 2021 | Core team members and senior stakeholders |
Competitor analysis |
Investigate best practices and market trends
|
29 Mar – 09 Apr 2021 | Content team |
User behaviors |
Review analytics & qualitative feedback to identify opportunities and define user mindsets
|
29 Mar – 09 Apr 2021 | Content team |
Author journeys |
Define current authoring journey for Atlassian content
|
12 Apr – 23 Apr 2021 | Sam Irons |
Jobs to be done |
Based on what we know of the user problems and opportunities, define jobs stories
|
12 Apr – 23 Apr 2021 | Core team and senior stakeholders |
1.1 Wonder playback and pulse check
Host a playback of vision, archetypes, success metrics, and prioritized job stories with wider Compass team.
Host a checkpoint meeting with core team and senior stakeholder to decide if we're ready to move into the Explore phase.
Explore – 05 May – 29 May 2021
Stage | Description and deliverables | Dates | Contributors |
---|---|---|---|
Current state mapping |
Map out the workflows for our key journeys as they are currently
|
13 May 2021 | Core team members and product team representatives |
Begin core documentation execution 17 May | |||
Ideation |
Use divergent thinking to imagine the future and explore ideas to satisfy pain points and opportunities in our key journeys
|
19 May 2021 | Core team members and product team representatives |
Future state experience |
Map out the future-state end-to-end content experience based on our key identified journeys
|
24 May 2021 | Sam Irons |
Vision |
Visualize the ideal experience and provide indicative screens/mocks to direct future iterations
|
24 May – 04 June 2021 | Sam Irons |
Platforms |
Evaluate the publishing platforms and channels we’ll use to deliver the experience
|
17 May – 26 May 2021 | Sam Irons |
Delivery |
Document the resources required and current gaps for delivering on our vision
|
31 May – 04 June 2021 | Sam Irons |
Indicative content creation |
Create examples of indicative content journey for 1 key journey
|
17 May – 04 June 2021 | Core team members |
Concept testing |
Test lo-fi content concepts for usability with internal stakeholders
|
17 May – 04 June 2021 | Content team |
2.1 Exploration playback and pulse check
Host an Explore checkpoint meeting with core team and have a go/no-go discussion to move into our Make phase
Host a playback of explorations and a walk through of our vision.
3. Make - 07 June - 25 June 2021
Stage | Description and deliverables | Dates | Contributors |
---|---|---|---|
Documentation roadmap |
Generate a roadmap of prioritized content deliverables
|
17 May - 28 May 2021 | Content team |
Content creation |
Write and polish all in-product and support content needed to support open beta goals
|
17 May 2021 + | Content team |
Content strategy |
Coalesce and define content strategy to guide content creation
|
31 May - 11 June 2021 | Sam Irons |
Documentation IA |
Outline the structure of developer and end-user documentation
|
31 May - 11 June 2021 | Content team |
Stage and blitz |
Publish content to staging environments and bug bash
|
25 June 2021 + | Content team |
3.1 Make playback and pulse check
Host a go/no-go decision for publishing content and making it available to customers.
Impact - 25 June 2021 and ongoing
Stage | Description and deliverables | Dates | Contributors |
---|---|---|---|
Content health |
Periodically assess and address the health of our content
|
Fortnightly | Content team |
Experience quality |
Periodically review and file UI/UX bugs for content and development teams to polish our experiences
|
Fortnightly | Content team |
4.1 Impact and health metrics
Host a quarterly retrospective with leadership regarding content implementation and team health.
Host fortnightly content team retrospectives.