Meeting planning

game-design.md

📝 Pre meeting checklist:

• You thought through the situation and believe a meeting a necessary. If not, think about why you need this meeting in the first place.

• You need outside input to make progress. If not, schedule time for doing this work.

• Moving forward requires a real-time conversation If not, send an email or use Slack.

🗓️ Game Design Meeting

We're going to meet for an hour every week to go over active and new game ideas. We'll spend the first half of the meeting on new ideas and the rest of the time on existing ideas. Bring new games!

❓ Purpose

• Alignment - we will use this time to align on game mechanics and target audiences
• Update - we will use this time to share updates about the green light framework status of current pitches
• Creative Exploration - we will use this time to conduct a creative exploration of new game ideas
• Prioritize - we are using this time to prioritize existing and new ideas in the pipeline

🎯 Expected Outcomes

• Alignment on the types of games we're building and for whom
• Deliverables: One pagers and 2-minute pitches commited to blockchain-ideas
• Plan for development and production for new games

👨👩 Owner

@mackflavelle

📖 Resources

• blockchain-ideas repo
• google drive folder

👥 Participants:

• 🎤 Facilitator - @mackflavelle
• 👨‍💻 Note taker - @tessa
• 🙋‍ Required Members: @richard @raf @alan @santiago @abhi @sam @mackflavelle
• 🤷‍ Optional Members: @mitch @howard

📆 Cadence and Duration - 1 hour

• twice a week

Meeting Norms

• 🎮This is a game design meeting so bring new game ideas. It's not mandatory but highly encouraged!
• 👨‍💻There will be a note taker present at the meeting
• 💬 The primary communication channel for this meeting will be over Slack #actual-game-designers
• 📵 No laptops / devices during the meeting
• 🏢 In person meeting
• 🌎 Remote attendees in the meeting
• 📚 Agendas and resources will be sent a day ahead of the meeting
• 👁️ Attendees are expected to review material before the meeting
• ✅ Check-ins / Check-outs - sentence
• 🚘 Parking lot rule - you can ask for a tangential discussions to be taken to the parking lot
• 🏢 Disagree and commit
• 🔎 We will review the necessity and format of this meeting in 1 month

🎩 Which hat to wear?

Knowing which hat(s) to wear to a meeting can be important, especially when making decisions. Use this section to pick which you should wear to the meeting, or tag individual team members to ask them to wear a specific hat!

• Green Hat: Complete creativity. This is where you develop creative solutions to a problem. It is a freewheeling way of thinking, in which there is little criticism of ideas.
• Blue Hat: @mackflavelle This hat represents process control. It's often the hat worn by people chairing and facilitating as they help to guide the general flow discussion by helping people wear different hats.
• Red Hat: Use your intuition, gut reaction, and emotion. Think how others could react emotionally. Try to understand the responses of people who do not fully know your reasoning.
• Yellow Hat: Think positively. Use the optimistic viewpoint to help you to see all the benefits of the decision and the value in it.

meeting-template.md

---

Meeting Planner

Planning and running good meetings takes work. Use this tool to help you plan and communicate for your meetings. Each meeting is different but the common feature of all good ones is good groundwork and mutual understanding of well set expectations and norms. Pick and the parts of the template that describe your meeting best. This tool will help you to:

• Establish norms and groundwork
• Assess that you actually need a meeting and keep track of them over time

You can start to use this as a way to organize your most important meetings, or most frequently occurring ones

Six Thinking Hats - Looking at a Decision From All Points of View

Disagree and Commit - A Management Principle for Highly Functioning Teams

Running an Effective Staff Meeting - Claire Hughes Johnson

---

📝 Pre meeting checklist:

• You thought through the situation and believe a meeting a necessary. If not, think about why you need this meeting in the first place.

• You need outside input to make progress. If not, schedule time for doing this work.

• Moving forward requires a real-time conversation If not, send an email or use Slack.

🗓️ Your Awesome Meeting Title

Describe your meeting in a few words. Good things to think about are: How will participants spend time in this meeting? What will the interaction look like? We will you use your time for in the meeting? What is the reason for this group to exist?

---

❓ Purpose

• Alignment - We will use this time to align on ...
• Update - we will use this time to share updates about ...
• Decision Making - We will come to a decision about ...
• Planning - We will create a plan for ...
• Creative Exploration - we will use this time to conduct a creative exploration on ...
• Prioritize - We are using this time to set priorities for ...
• Work session - We will use this tile to work on ...

---

🎯 Expected Outcomes

• Alignment on ...
• Deliverable for ...
• Plan for ...
• Decision for ...
• Creative exploration on ...

---

👨👩 Owner

Tag the meeting owner here. There can only be 1️⃣

📖 Resources

• Add any relevant slides, documents and links
• Repositories, Drive folders, ZenHub boards

👥 Participants:

• 🎤 Facilitator - Who will be facilitating this meeting? This is usually the owner.
• 🙋‍ Required Members: Tag the people who need to be at the meeting.
• 🤷‍ Optional Members: Tag the optional attendees.
• 👨‍💻 Note taker - Who will be taking notes?

📆 Cadence and Duration - 15 minutes / 30 minutes / 1 hour

• when scheduled by the owner
• daily / weekly / monthly
• when requested by a participant

Meeting Norms

• 👨‍💻There will be a note taker present at the meeting
• 💬 The primary communication channel for this meeting will be over (Slack / Email )
• 📵 No (laptops / devices) during the meeting
• 💻 Laptops okay during the meeting
• 🏢 In person meeting
• 🌎 Remote attendees in the meeting
• 📚 Agendas and resources will be sent a (day / week / month) ahead of the meeting
• 👁️ Attendees are expected to review material before the meeting
• ✅ Check-ins / Check-outs (word / sentence / paragraph)
• 🤝 Decisions will be made by a (decision owner / consensus / committee)
• 💡 No un-discussables - any idea or topic can be discussed during the meeting
• 🚘 Parking lot rule - you can ask for a tangential discussions to be taken to the parking lot
• 🏢 Disagree and commit
• 🔎 We will review the necessity and format of this meeting in a (week / month / quarter)

🎩 Which hat to wear?

Knowing which hat to wear to a meeting can be important, especially when making decisions. Use this section to pick which you should wear to the meeting, or tag individual team members to ask them to wear a specific hat!

• White Hat - Focus on the available data. Look at the information that you have, analyze past trends, and see what you can learn from it. Look for gaps in your knowledge, and try to either fill them or take account of them.

• Red Hat: Use your intuition, gut reaction, and emotion. Think how others could react emotionally. Try to understand the responses of people who do not fully know your reasoning.

• Black Hat: Look at a decision defensively and think about potentially negative outcomes. Try to see why it might not work. Highlight the weak points in a plan. Build strategies to eliminate them, alter them, or prepare contingency plans to counter them.

• Yellow Hat: Think positively. Use the optimistic viewpoint to help you to see all the benefits of the decision and the value in it. Yellow Hat thinking helps you to keep going when everything looks gloomy and difficult.

• Green Hat: Complete creativity. This is where you develop creative solutions to a problem. It is a freewheeling way of thinking, in which there is little criticism of ideas.

• Blue Hat: This hat represents process control. It's often the hat worn by people chairing and facilitating as they help to guide the general flow discussion by helping people wear different hats.