Recording: (Accidentally exited recording while screen sharing so it’s in two)
Part 1: https://drive.google.com/file/d/1-ZKJbjnmx-QgO31WCZ5sj2nq5WuYjD9K/view?usp=share_link
Part 2: https://drive.google.com/file/d/1BRN9-7ppxQKjcWzsXVjg5dDJVtTsj5uR/view?usp=sharing
Attendees: Shelby, Louie, Ange, Abbey
Agenda
Notes
- In getting feedback for the Design Exercise:
- Need to further describe what it means to be an “Owner” and “Participant”
- Ownership: Creating the process, Collecting input from participants
- Participant: Giving input
- The design exercise should surface contributor feedback on key questions
- There are few functions that are new
- Should we be showing one as an example
- Feedback on the functions themselves
- Feedback on the proposed mapping (it’s key that we describe these as proposed, not assigned as a final. Words like thumbs up/Agree or Disagree may contribute to it being more seen as final)
- What would make most impact in terms of helping CTs?
- How detailed should we get?: Aside from proposing owners, would it be helpful if we focused on facilitating one more functions and working with them all the way though (ie. Technical Development - a governance process for how they would come to agreement or disagreement?)
Takeaways
- 4/4 Agreed it would be better to create some prototypes and ask for feedback in the context of the prototype.
- We can show a few prototypes so they can compare / ask questions
- Include option to design their own, or communicate their ideas
- If we decide to work on the prototype before presenting the open exercise with contributors, we would wait until after the Sprint, slated for (Nov 28-Dec 5).
- @Louie to share mtg recording/notes with @Matty or walk him through it and get his feedback and thoughts