A team. Call it a group, squad, bunch, company, party, crew, troupe, absolutely anything – one thing is certain. Each person brings their own unique talent, thoughts/ideas, skill sets and understanding to the team. Because they all have different facets, having them work together in a team is interesting as well as challenging at the same time. It is like machinery – each part, each team member needs to be in sync with the others to make things happen
That was also the game we played in one of the continuous learning sessions. The game called “Playing in Sync” was led by Jahir Mallik who works as a UI Developer. Jahir is known to be very persistent in his team and passionately trustworthy. He loves watching movies, bike-riding and spending time with his family. He is also a foodie who loves trying new food.
The rules of the game seemed pretty confusing at first, but as we got into the game, it was easy to follow. Two teams were created with 6 members in each team. It was an activity game – one team commanded/instructed as to what was to be done, while the other had to perform. The team that was to command had to give 2 commands and they had the liberty to switch the commands as they wished. The team that was performing had to switch the activity as soon as the command was given. It is easy, isn’t it? Except that the switching was done without any prior notice. So they would say “jog” and then say “stop” and then would reverse the commands as they wished. 2 more commands were added in later. As if this was not complicated enough, the team commanding could go on to make the commands “temple” and the team performing had to touch the floor as in a temple or say “stand on one leg” and then the next one would be “jump.” Team #1 also brought in some innovation – like the temple command and another which said “bird” and they had to jump the word was commanded. Or using the word “day” for a walk and the word “night” for stopping.
Points for the game were counted in terms fouls committed. So every time a team member faulted in following a command it was counted as 1 foul. At the same time, when 2 team members faulted and it was counted as 2 fouls. Team #1 had 14 fouls and Team #2 had 17 fouls. The team with fewer fouls was declared the winner.
The game came with many lessons – about how everyone was in sync with performing the commands and at another level, how the command was perceived. There were funny moments when someone or the other forgot what the commands meant and had to look at others to get back in with the team. Most of the lessons were team lessons – how to conquer challenges, strategizing better so that the commands can be followed with minimum fouls as one team did – they performed the activity in a circle so that even if someone misses out or forgets the commands, they could easily look at others and do the activity. Or by keeping the command strategy a secret and within the team so that the opposing team doesn’t get an idea as to what the next command would be.
As the game ended, each one of us had an example that fit in well with their own tasks and gave them a better understanding of working as a team. That is one of best things about our continuous learning sessions – after each session, we find that we see our team members and teamwork in a new light and that brings us closer as a team as in this case.