A Think Big is designed to create a shared understanding of purpose and goals with all members of a stage group. Everyone in the stage group is invited to participate in a facilitated discussion around vision, roadmap, user research, design, and delivery of upcoming product features.
Think Big's are meetings that drive knowledge-sharing across the organization at the stage group and section levels. Participants are given the opportunity to review and ensure short-term activities are aligned with long-term goals.
Watch past recordings in the GitLab Unfiltered YouTube channel.
Think Big meetings occur once a milestone (once a month).
Having a synchronous meeting with a large number of individuals may feel like it goes against GitLab's Values and culture. It is essential to evaluate the Think Big meetings regularly to ensure they are valuable to the team. Some questions to ask could include:
If any of the above questions are answered with a "No" it is a sign to reevaluate the topics, discussions, and structure of Think Big and iterate to ensure the team gets the most value out of the meeting as possible.
Think Bigin Google Drive.
After completing Problem or Solution Validation, Product Managers and Product Designers walk away with robust data about our customers and their needs. The Think Big meeting is a perfect forum for sharing the plan, process, and results of those research efforts.
Upcoming research discussions involve the entire team and give everyone involved in creating a product or feature an opportunity to raise questions to ask the users.
Reviewing past research initiatives and discovered UX-Research Insights with the whole team helps everyone understand what our users need and how the features being built will help them.
Reviewing a new epic with the whole team helps everyone understand the large scale vision and the logical breakdown formed. Having this conversation opens opportunities for the team to collaborate on how to break down large work into MVC deliverables in a logical and efficient order.
Remember, the goal is to capture a quantity of specific feedback. While it may be tempting to start discussions around the design choices and feedback, this activity doesn't make for a proper forum. The designer will follow up with reviews asynchronously afterward in the issue(s) to start discussions and conversations around the feedback.
A think big meeting may be accompanied by a think small meeting. While the think big focuses on divergent thinking about a problem and the solution space, the think small portion focuses on convergent thinking to help define the smallest step that the team can take today.
At GitLab, a great outcome of a Think Small meeting is having a small issue that solves a customer problem and gets them closer to the larger outcome discussed in the Think Big.