Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Meeting Sections

Group Norms

  • John Towns - Based on 2024 Feb Quarterly Meeting - Lead the effort of creating group norms

This is one of the outcomes that was requested for this session. Normally this groundwork is laid at the beginning of a meeting/session. This is how to set up some norms.

Activity; Think, Pair, Share

Think: 

What group behaviors would help the team be the best they can be? What should 6 or 7 norms be for how teams interact going forward?

  • For meetings: we will always have agendas and notes in a place where people can find it in a well known/searchable location.

  • Minimum bar - team has a folder and everyone uses it and there is a known and used way to document things

    • There is in internal reporting obligation/standard and people use it

  • Track norms: Determine how much visibility should Tracks have to other Tracks stuff

    • How do we share what is going on - and what is shared

    • More than private internal and fully public

  • Specify how the teams work together in an interpersonal, non-technical way - how do we engage as humans?

  • Create a process for vetting requirements and sharing requirements

Other teams - are these team norms? Group norm can be an action - Group Culture Norms and Logistics/Process Norms (how) 

  • Access wide staff onboarding

  • Skillset roster - who to contact for certain things

  • Access wide newsletter - when have individual track meetings - have first 5 mins to summarize what all other tracks are doing and what are the opinions on what is going on

    • Everyone should be reading the newsletter

    • In group meetings - talk about the newsletter and what all other teams are doing

  • We are collaborative - AND what all is involved in that

  • Team should document decisions and plans - tell everyone about things and not live in the silo

  • Visibility of all plans of others so you can figure out what you are doing is consistent with your team AND project plans

  • Decisions we make in each meeting are connected somehow to overall program goals

  • Everyone is heard - responsibility to make yourself heard

  • Establishing trust - expressed as I trust you to help me and I hope you trust me to help you

  • Individual norms

    • Believe your contribution matters

    • Take advantage of opportunities

    • Speak up

    • Make space for new people and new ideas - can be heard

    • Less pride - more moving forward

    • May not be able to find Win-Win - but Win Lose and Lose Lose are highly collaborative

    • Following through on responsibilities

    • Ask for help if you need it

  • Linking Code of Conduct to some of the behaviors in meetings

    • Code of Conduct has actions - should find and read - at the bottom of every access web page

  • Revisit the vision for ACCESS

  • Step back and take a long term view - don’t focus on little things

  • Responsiveness

  • Preparation for meetings

  • Clarity of communication

  • Accountability - and a way to push back on decisions

  • Delegation - ask for help is OK

  • Workload expectation management - no one is 100% on Access

  • Hold EC accountable

  • Working Groups should be clear on what they are empowered to do

    • What is their specific relation to the EC

  • Meetings should be deliberate and directed back to the agenda if they get off agenda

  • Talk with everyone in the meeting

  • Collaboration for all

  • Mechanisms to push decisions down as far as possible so all people are involved in making it happen

  • Agendas solve problems of the moment

  • All members should discuss - not just give updates

  • Respect and compassion for each other

  • Connect with the person before you connect with problem

  • We each have different work cultures - even within the team

  • Don’t interrupt each other - let people finish  

  • Shared objectives

  • In person interaction as much as possible

  • Validate others ideas when in discussions

  • Should we collect and assess conflicts that we know about? And make this a regular intentional thing.

  • We commit to using the tools we are learning here today.

Consultants will consolidate this list and send it to us along with a full report.

There will be action items needed to implement the group norms - the EC has the power to make this happen.

Outreach and Associated Working Groups

  • Shawn Strande - Based on 2024 - Feb Quarterly Meeting - Create a new metric - based on potential users and outreach goals - if people fill out engagement spreadsheet with how many people attented their session - we could get a good data point

New Metric - a gap we currently have is potential users and outreach - if everyone who went to a meeting would put entry in spreadsheet - and count how many people attended their session it would be a good data point

To Do: suggestion for Engagement Tracker - trigger or alert - people get notified when people make entries for future dates - comms reaches out to support the person who is going  

To Do: Can we ask during requesting allocation - how did you hear about us?

To Do: Make a list of everyplace you go in a year - you would be surprised at how many people you contact - look over 2023 and enter your list into the tracker - it would be helpful for us to use for evaluation

From Tom: To Do: make a cheat sheet that says if you talk to this “persona” you should relay this info - and outreach can turn to listening.

From Tom: Planting opportunities with advocates who run carpentry workshops - if we can partner with trusted agents like that it could help.

To Do:  Rather than trying to project where we might go - should we put a note on the web site for “where should ACCESS go?” “invite ACCESS to come here” - this is $0 investment and could be beneficial.

  • No labels