MC 16.17 Team meetings

Page 1

MC 1617 Team meetings

AIESEC Slovensko | Ĺ tĂşrova 3, 811 02 Bratislava | www.aiesec.sk | tomas.susedik@aiesec.sk


1. Introduction This document provides clear insights into the meetings structure of the MC 1617. The types of meetings are following:

Performance

Development

The structure and purpose of the meetings might change throughout the term.

2 AIESEC Slovensko | Ĺ tĂşrova 3, 811 02 Bratislava | www.aiesec.sk | tomas.susedik@aiesec.sk


2. Performance meetings The purpose of Performance meetings is to evaluate and adjust the MC team plan and performance.

Operational Tactic Strategic The meetings are adjusted according to scope and periodicity: 1. Strategic - evaluation of the last Q (achievements, learnings), defining steps for the next Q and the implementation. 2. Tactic - evaluation of the last month (achievements, learnings), defining steps for the next month and the implementation. 3. Operational - problem solving, defining short-term priorities.

3 AIESEC Slovensko | Štúrova 3, 811 02 Bratislava | www.aiesec.sk | tomas.susedik@aiesec.sk


2.1. Performance meetings - Strategic MC Days: • Periodicity: • 4 times a year, first week of each Q • Attendees: • MC team • Duration: • maximum 3 days • Agenda: • MC team building • LC reality check • projects reality check • area reality check • consolidation of inputs, identifying key issues • brainstorming solutions • defining next steps for LCs, projects and areas • Inputs: • LC reports, • project reports, • area reports. • Outcomes: • LC next steps • updated project plan • updated area plan • updated budget

4 AIESEC Slovensko | Štúrova 3, 811 02 Bratislava | www.aiesec.sk | tomas.susedik@aiesec.sk


2.2. Performance meetings - Tactic Monthly Review: • Periodicity: • last week of each month (except months with Q review) • Attendees: • MC team • Duration: • maximum 1 day • Agenda: • LC reality check • projects reality check • area reality check • consolidation of inputs, identifying key issues • brainstorming solutions • defining next steps for LCs, projects and areas • Inputs: • LC reports, • project reports, • area reports. • Outcomes: • inputs for LC monthly review • project monthly priorities • area monthly priorities • updated budget

5 AIESEC Slovensko | Štúrova 3, 811 02 Bratislava | www.aiesec.sk | tomas.susedik@aiesec.sk


2.3. Performance meetings - Operational Monday Meeting: • Periodicity: • weekly on Tuesday at 9:00 • Attendees: • MC team • Duration: • maximum 2 hours • Agenda: • identifying key improvement areas, discussing solutions and defining next steps • appreciation time • Inputs: • individual performance reports • Outcomes: • tasks, responsibilities, deadlines • previous week priorities evaluated • next week priorities defined

6 AIESEC Slovensko | Štúrova 3, 811 02 Bratislava | www.aiesec.sk | tomas.susedik@aiesec.sk


3. Development meetings The purpose of Development meetings is to focus on personal and professional development experience of each MC team member, connecting it with the individual contribution towards the MC plan.

Team building

Team coaching

1on1 coaching

The structure and purpose of the meetings might change throughout the term.

7 AIESEC Slovensko | Ĺ tĂşrova 3, 811 02 Bratislava | www.aiesec.sk | tomas.susedik@aiesec.sk


3.1. Development meetings - Team coaching MC Days: • Periodicity: • 4 times a year, first week of each Q • Attendees: • MC team • Duration: • maximum 1 day (together with Team building) • Description: • evaluation of current state of team dynamics • defining needs for team dynamics improvement • Inputs: • MC team members’ feedback • 1on1 coaching • Outcomes: • inputs and needs for team dynamics evolution • reviewed team manifesto • reviewed working standards

8 AIESEC Slovensko | Štúrova 3, 811 02 Bratislava | www.aiesec.sk | tomas.susedik@aiesec.sk


3.2. Development meetings - Team building MC Days: • Periodicity: • 4 times a year, first week of each Q • Attendees: • MC team • Duration: • maximum 1 day (together with Team coaching) • Description: • delivering the “social part” of the team experience, ensuring personal interaction of the MC team members • Inputs: • MC team members’ feedback • 1on1 coaching • Outcomes: • group hugs

9 AIESEC Slovensko | Štúrova 3, 811 02 Bratislava | www.aiesec.sk | tomas.susedik@aiesec.sk


3.3. Development meetings - 1on1 coaching Coaching meeting: • Periodicity: • monthly • Attendees: • MCP and MC team member • Duration: • maximum 90 minutes • Description: • assessment of individual aspects of the MC team experience (MC, functional and sub-team roles) • defining development activities for the next month • the content of the coaching meetings will vary based on the timeline of the term - mostly on MC team plan and current state of team dynamics • Inputs: • individual scorecard • MC team timeline • Outcomes: • action steps towards improving the team experience • learning activities for the next month

10 AIESEC Slovensko | Štúrova 3, 811 02 Bratislava | www.aiesec.sk | tomas.susedik@aiesec.sk


3.4. Development meetings - other Team dinners: • Periodicity: • weekly • Attendees: • who’s available • Description: • 2 different people every week prepare an international dinner Other activities: • Sports, BBQ, movies, anything else - not regularly scheduled

11 AIESEC Slovensko | Štúrova 3, 811 02 Bratislava | www.aiesec.sk | tomas.susedik@aiesec.sk


Turn static files into dynamic content formats.

Create a flipbook
Issuu converts static files into: digital portfolios, online yearbooks, online catalogs, digital photo albums and more. Sign up and create your flipbook.