Clarity in collaboration: Describe a bicycle exercise
The power of detailed communication and shared vision in team dynamics
When people create something, like software or a product, what they make is not the perfect version of what they want. Instead, they are making something close to, but not exactly, the ideal version in their mind. This ideal version is based on what experts think, what customers want, and what is needed for the business.
The problem is that everyone involved might have a slightly different idea of what this perfect version should be. Also, there are limits like time, money, and the tools they use, which affect how close the final product can be to this ideal version.
As the project goes on, the team learns more and adjusts their work and gets closer to this ideal version. They constantly (consciously or unconsciously) refine their understanding and the product, based on new information and feedback.
This journey towards a vision is littered with challenges one of which is ensuring that everyone on the team shares a similar understanding of the goal. However, do we truly appreciate how different our individual interpretations of a common concept can be?
While thinking about how to combat this issue of individual interpretations, I realised that the first thing that needs to be tackled is awareness of the issue. So, I came up with the ‘Describe a Bicycle’ exercise. It’s an exploration into how each member interprets a simple concept like a ‘bicycle’ in varied and unique ways.
The essence of this activity lies in its ability to showcase the importance of clear, detailed communication. It demonstrates that even when we agree on a general concept, the specifics can vary greatly from person to person. But it’s this understanding which is crucial in project development, where details matter and the alignment of these details among team members can significantly impact the outcome.
This exercise reveals the difference between a basic theoretical grasp of a concept and the ability to turn that concept into a detailed, tangible description ready for creation. It highlights how each individual’s interpretation of a simple idea can evolve into unique, detailed descriptions. If these interpretations are misaligned, it can lead to inconsistencies in the final creation, underscoring the need for continuous alignment and communication within the team.
“Ideas scatter when details don’t matter”
Describe a bicycle exercise
Purpose of the Exercise:
This activity is designed to highlight the importance of alignment and detailed understanding within a team working on a product. It emphasises the need for clear, specific communication and understanding of a common goal by showing that while everyone may agree on a broad concept, their interpretations of the details can vary significantly.
Materials Needed:
- Pen and paper for each team member.
- Timer.
Duration:
Approximately 15–20 minutes.
Activity Brief:
- Ask the team to imagine a bicycle.
- Explain that each member will need to describe their imagined bicycle in detail as if it were physically present.
- Emphasise the need for specifics — the description should be unique enough to distinguish their bicycle from others.
Individual Description (5 min):
- Set a timer for 5 minutes.
- Each team member writes indivually a detailed description of their imagined bicycle.
Sharing Descriptions:
- Go around the room, allowing each member to share their description.
- Listen to each description attentively.
Debrief and Discussion:
- Explain that the exercise was more than just describing bicycles; it was about understanding how different perceptions can affect a team project.
- Highlight that each person’s unique description reflects how varied interpretations of a simple concept like a bicycle can be.
- Invite the team to imagine what the bicycle would look like if it were created using elements from everyone’s descriptions.
- Reflect on how this ‘composite bicycle’ might be impractical or illogical, illustrating the challenges of unclear or misaligned visions.
- Discuss the importance of clear and detailed communication in product development.
- Emphasise how different perceptions, if not aligned, could lead to a final product that doesn’t meet the intended purpose or user needs.
- Conclude by stressing the need for regular check-ins and clarifications among team members to ensure everyone is aligned with the project’s goals and requirements.
Note: Ensure that the team does not become aware of the real purpose of the exercise until the debrief, to maintain the authenticity of their responses.
Example Script:
“Hello everyone, let’s gather for a quick team exercise. Today, we’re going to do a simple but revealing activity. I want each of you to imagine a Bicycle. Think about its appearance, its function, how and when it’s used, its user, and any distinctive features. Now, write a description of this bike. Be as detailed as possible — imagine you’re describing it so someone could pick it out from a large bike rack. You have 5 minutes for this.
[After 5 minutes]
Let’s hear your descriptions. [Proceed with sharing]
Thank you for your participation. The aim of this exercise was to demonstrate that even with a common understanding of a concept — like a bicycle — each of us has a unique interpretation. In our work, when we talk about our product or project goals, it’s crucial to be as specific as possible to ensure we are all aligned and working towards the same detailed vision. This is why constant checking for understanding and alignment is essential in our team.”
Further Activity: Identifying and Combating Vagueness in Team Communication
Extend the exercise:
After completing the ‘Describe a bicycle’ exercise, the team can extend the activity to address common issues of vagueness and lack of detail in team communication. This part of the exercise focuses on identifying and overcoming ‘dark patterns’ of communication, where important details are often overlooked or not clearly expressed.
Discussion on Vagueness:
The team discusses examples of vague communication they have encountered and its impact on project work.
Identifying Indicators:
Develop a list of ‘red flags’ that indicate when communication is becoming too vague or details are being skipped.
Strategy Development:
Collaboratively come up with methods and practices to improve focus and clarity. This could include setting standards for communication, using specific project management tools, or regular check-ins to ensure clarity.
Implementation Plan:
Decide how these strategies will be implemented in day-to-day work.
The ‘Describe a bicycle’ exercise, aims to give a team a deeper appreciation for the necessity of concise communication and the vital role of collective understanding in collaborative projects. This activity serves as a metaphor for the challenges we face in product development, where each team member’s unique perspective and expertise contribute to shaping the outcome. It reinforces the idea that while we may share a common goal, the path to achieving it is paved with diverse interpretations and ideas. By ensuring detailed, clear communication and continually testing and refining our visions, we can work more effectively towards creating products that not only meet but exceed our collective expectations. Remember, the strength of our team lies in our ability to understand, respect, and integrate our varied perspectives into a cohesive and successful product.
