In the last two weeks, I initiated the Discovery process for a new feature in the product I’m working on for my client. After completing the initial deliveries, which were:
- Gathering all the documents from previous discoveries.
- Creating a CAQ matrix (you can read my article about the benefits of creating this matrix at the beginning of your project).
- Designing the user flow and the complete journey.
Even with all the data documented and discussed with the squad, I still felt that we couldn’t convey all the ideas that were emerging. That’s why, in some conversations with my Lead (Alan, if you’re reading this, thank you very much for the tips!), I thought about conducting an Ideation Workshop. But how did this Workshop work?
The preparation and implementation were fast. The most complex part was analyzing the insights (there were many of them) because the team was very excited about the dynamic (they called it “an hour as designers”).
- Preparation
- To prepare, I researched some articles on Medium to understand the best way to conduct an Ideation Workshop, as this would be the first one I would do with this team.
- I also searched for some Canva or Miro board templates, as Miro is the platform they are most familiar with. It’s essential to use a tool they are comfortable with so that the focus is on the dynamics and not on how it will be conducted.
- To help, I created a step-by-step guide to be followed, specifying the time we would spend, adding our ideas and discussing them one by one.
- I also left an example in Miro to stimulate creativity and generate various initial ideas and questions that could be answered by stakeholders.
- I created a description, always emphasizing that they could let their ideas flow and didn’t need to focus solely on the delivery, allowing them to separate into MVP (Minimum Viable Product) and versions (v1, v2, v3). Always keeping in mind the idea of “thinking outside the box.”
2. Application
We reached the implementation phase! But, Ana, how did you manage to do it in just one hour?
The team consisted of 1 Product Designer (me!), 1 Product Manager, 1 Product Owner, 1 Agile Master, and 1 Agronomy Specialist. How do you conduct ideation with people with such different profiles?
- Since we already had a weekly meeting scheduled, I proposed that we conduct it within that one-hour timebox, and if any insights were missing, they could be added throughout the week.
- Since we were 5 people, I gave two options to my squad: 1. Perform the activities as a single general group, or 2. Split into two groups, and I would assist by alternating between their conversations.
- They chose to split into two groups, and they started creating flows, adding post-its, and even wireframes on Miro.
- In total, there were thirty-five minutes of ideation for the two groups. We then returned to the initial room, and I asked how the process and experience went. One of the feedbacks was as follows:
“I never imagined it would be so complicated to bring our ideas to ‘paper,’ but if I already valued the Designer profession before, now I value it even more.” (Agile Master)
3. Analysis
- When we returned to the initial room, I requested permission from everyone and began recording to analyze all the data later and also understand how I would put into practice all the data collected from that ideation session.
- Then, I asked the first group to present what they came up with, cleared some doubts, and had some discussions even before the second group presented.
- When the second group presented, we realized that the ideas were interconnected, even filling in certain points that the previous group had doubts about (some technical aspects that the second group explored further).
4. Insights obtained and next steps
- As mentioned above, the next steps will involve creating flows, wireframes, prototypes, and an overall more comprehensive deliverable, with a stronger technical foundation and better alignment with the business.
- We’ve kept everyone in the squad involved since the beginning of the project, emphasizing the importance of the design process.
- The Workshop will also help reduce rework and enhance the connection with the technology team (developers) and the entire design team. I’ll bring up the topic for discussion in the coming week.
If I helped you, feel free to message me on LinkedIn to chat about design or any other subject you find interesting! 👍
