Google Opus
They wanted to transform both business processes and software systems with a new product suite called Opus that would make work more efficient and agile.
They wanted to transform both business processes and software systems with a new product suite called Opus that would make work more efficient and agile.
innovation
Find innovative ways of transforming both processes and tooling, to allow operations teams to meet team work order goals.
productivity
Create a product suite that boosts overall happiness and operation teams’ productivity
They were also using software tools to gather relevant information for the same project, which showed that software systems were another area for potential growth.
The Google Opus team wanted to create a new product suite that would:
before the sprint
Rootstrap team members worked with Google Opus to define their goals and consider possible deliverables.
While a traditional design sprint would be five days, due to scheduling constraints they had only two days. The goal was to rapidly generate actionable ideas that could be completed in a more leisurely timeframe afterwards.
day one
On day one, the team dove into lightning talks to better understand the product goals, the design evolution of the existing software tools, current user journeys, pain points, and technological opportunities. They selected the main personas for this project and mapped the user journeys from start to finish. From there, they further narrowed the main target area for the sprint and moved into sketching.
day two
Day two was dedicated to expanding each participant’s ideas into presentable solution sketches that they would share with the rest of the team. The group discussed each sketch and highlighted the best features, ultimately voting on the best solution to prototype.
During the final discussion of the sprint, Opus needed to test the new solutions they had developed to gather feedback from their core users and understand how to truly improve their daily workflow.
Through the initial brainstorming, it became clear that internal communications and processes within the Google Opus team needed to be codified. Solutions included the introduction of collaboration tools, documentation, and a set engagement model.
