The last time most of us met in session #5, we discussed our theme and progress to-date and pointed out the latest research
made available to us by the movement direction work.
Leading into session #6, the coordinating team decided that jumping from an impact theme to projects was probably not constrained enough, so we took a stab at identifying project groupings, which we are calling "outcomes", and then narrowing down that list. This way, teams have a lot more focus when they sit down to identify what it is they should work on. By the end of session #6, we had cut that group of themes from 9 into 4. We also did a fair bit of work in refining the overall goal to explicitly answer some of the questions raised in Session #5. The attached preso
is one that we walked through in session #6, but I have modified it a bit to show the outcomes and explain why. Our notes
from the session might also be helpful if you want to understand a particular bit of context.
Coming out of that meeting, we have a draft of the strategy we hope will provide significant guidance as we plan specifics for the coming year.
elaborates on what we think the theme means as well as what each of the 'output' groupings mean. It is definitely a living document, and subject to modification. Please review and comment or suggest changes. The document gets particularly sparse at the bottom of this tree, where the ideas are not as well fleshed out.
The next steps are to identify what the highest priority projects are for each grouping, carve out a subset for 2018-2019 and then align them with resources. As part of due diligence, we will need engineering to weigh in on feasibility and bandwidth and to figure out how we plan on measuring success for each project. Everyone in the coordinating group felt that this was probably best done at the team-level.
However, there will be some coordinating oversight necessary to ensure, for instance, that shared resources like technology team support and community appetite for change are not oversubscribed. There might also potential conflicts or disagreements. For instance, if the mobile web team and the editing team both choose VE on mobile web as a project they want to tackle. For this reason, I suggest each team comes up with >1 set of projects they would be interested in, in case there is a conflict.
- 1 annual plan of X projects with 1-2 alternatives for each project proposed.
- For each project, please:
- explain theory of how it best leads to outcome and impact (taking into account constraints)
- explain how you would measure success
- identify assumptions/risks
Please reach out on or off-list if you have any concerns or suggestions about any of this.
All Hands Week Opportunities
- Many of you are meeting with your teams on Monday - feel free to share this outcome with your teams if you feel comfortable doing so and starting to think about projects. I am also around on Monday if you'd like me to come provide context, answer questions or bounce ideas around.
- On Tuesday we will have product day. In the afternoon, we have 2 hours devoted to moving forward on these next steps.
- We will be presenting this process/outcome and a few other related things at the all-audiences meeting on Wednesday.
- On Wednesday there will be time in the Reading afternoon meeting (60-90 minutes) and (I believe) in the Contributors meeting to discuss further with your teams.
Again, your feedback, communication outward, and help filling in the blanks here is really, really welcome. See you all next week!