Generative research and a checkpoint where you get to know users and their context. This is where you define problem & opportunities and analyze and synthesize (see patterns, gain insights) understanding. Understanding could come from our communities, Community Liaisons, internal Product Audiences, Design Research, Research & Data, Partnerships and Communications.
|Communities and communication checklist - Understand|
- The investigation to define a problem is documented in public
- Relevant stakeholders have been invited to participate in the discussion
- If there is prior discussion, it has been reviewed
- Discussion is facilitated/mediated as needed
- Participate in the determinization of results
- Impact on user workflow has been researched
- These results have been discussed with those it would impact
New feature proposals and submissions for current problems or new ideas. These items could involve or be generated from areas like general discovery or ideation, research, technical debt and/or strategy. Submissions could come from our communities, Community Liaisons, internal Product Audiences, Design Research, Research & Data, Partnerships and Communications.
|Communities and communication checklist - Concept|
- This solution has been presented for discussion
- This solution takes into account its shortcomings and explains them
- This solution takes into account its benefits and explains them
Planning and prioritization involve defining the inputs (people, forecasting, resources), outputs (tasks), outcomes (metrics), defining milestones, dependencies and maintenance tasks. These tasks are driven by Product Managers, Engineering and User Experience and may include participation, validation or checkins with Communications, Team Practices, Security, Community Liaisons, API/Services, Release Engineering and Legal teams.
|Communities and communication checklist - Plan|
- Initial roadmap is determined, published, and communicated
- Have a rollback/revert plan - as simple as "We are willing to"
Backend and front-end development takes place and carry the selected concept forward to implementation. Quality and performance are important checks. If any issues or bugs are found the feature may roll back to Design depending on the severity of issues found. Testing via labs, prototyping, a/b tests, surveys, flow analysis, user sessions, and community validation of progress. The tasks are driven by Product Managers, Engineering and User Experience and could include participation, validation or checkins with Research & Data, Architecture and Operations, Data Analyst, Community Liaisons, Operations, Team Practices, API and Services, Performance and Architecture. Bugs, analysis and feedback in this round can send features back to the design phase.
|Communities and communication checklist - Develop|
- The product accounts for community moderation tools (+sysop, oversight, checkuser, abuse filter, etc.)
- Wireframes and/or prototypes have been communicated
- Bugs identified as blockers before by CLs and/or communities are discussed and fixed
- Performance and quality notes are taken and communicated
- Translators are contacted about system messages
Reviews by dependent stakeholders from the concept stage to validate concept completion. Community review and initial feedback on the development may influence release & rollout timing. Teams will be analyzing performance and adoption. If any issues or bugs are found the feature may roll back a stage or two depending on the severity of issues found. Announcements or events may also be created around releases. These tasks could apply to alpha, beta and production level feature releases. The tasks are driven by Product Managers, Communications, Community Liaisons, Release Engineering and could include participation, validation or checkins with Operations, Legal, and Security. Bugs, analysis and feedback in this round can send features back to the build phase.
|Communities and communication checklist - Release|
- Concept and resulting product are reviewed for completeness
- This review is documented
- Including translations
- Each stage of release has a feedback loop (alpha, beta, production)
- Determine order of release (which wikis on which dates)
After a feature is released ongoing maintenance is measured through feedback loops and analysis, retrospectives, metrics and impact reviews and identification of improvements. Community review and feedback on real usage and interaction is measured and teams will be analyzing performance and adoption. Improvements or new features restart the process and planning and milestones will be created. The tasks are driven by Product Managers, Performance, Data Analysts, Design Research, Research & Data, Community Liaisons and Security. Any iterations to the product will result in the process restarting.
|Communities and communication checklist - Maintain|
- Document clear ownership of maintenance, even if that means documenting something is unmaintained/abandoned