July 10, 2025 | Career, Product Discovery
Visualize Your Thinking
Visualizing your thinking is a core practice in continuous discovery. It helps you externalize, examine, and communicate what’s often locked away in your mind.
If you can’t see it, you can’t build it , so draw it, map it, share it, and keep it human.
— Kristy Sullivan
Before your trio builds anything, set yourselves up for success. Over and over, I hear the same thing from leaders and stakeholders:
Show your thinking.
Discovery should be visible, not buried in someone’s head or trapped in a random notebook. If what you’ve learned stays hidden, it helps no one. Share it. Show it. Let everyone build on it with you.
Visualizing your thinking is a core practice in continuous discovery. It helps you externalize, examine, and communicate what’s often locked away in your mind. Teresa Torres describes visuals like experience maps, opportunity solution trees, and simple diagrams as “common ground” for a team to build shared understanding.
Let’s break it down.
What it is
Visualizing your thinking is about making the invisible visible. The patterns, decisions, gaps, and ideas that shape your product direction. It doesn’t need to be fancy. Boxes and arrows work fine. So do stick figures.
The point is that if it stays in your head, it remains stuck.
Why this matters:
- Words are too vague. Two people can agree in conversation but leave with very different mental models.
- Visuals force clarity. You have to get specific if you want to draw it.
- We think spatially. Our brains are wired to make sense of things visually. That’s why visuals help us spot contradictions or missing pieces fast.
How to do it
You don’t need to be a designer to sketch your thinking. However, if drawing feels intimidating, consider taking a short sketching course for UX designers on Udemy. I’ve done it myself, and it has helped me share ideas more quickly and clearly in meetings.
Start solo. Then converge.
- Sketch your thoughts individually before aligning with the team. This reduces groupthink and surfaces more perspectives.
Use basic shapes.
- Boxes, arrows, timelines, swim lanes, and that’s enough. You’re not creating a prototype. You’re mapping mental models.
Try an Opportunity Solution Tree (OST).
- Show how your target outcomes connect to customer opportunities, your ideas, and the assumptions you still need to test. This model helps you think in bets instead of binary yes/no decisions.
- Learn how from Teresa Torres
Fun Examples
These are some lightweight ways to bring visuals into your day-to-day work, even if you don’t have a design background:
- Experience maps that show a customer’s journey through frustration or delight
- Story maps that anchor your backlog in customer goals, not screens.
- OSTs for making discovery visible (and tangible)
- Sticky-note timelines from interviews that uncover hidden triggers or delays
- “Now, Next, Later” boards that shift roadmap debates to a shared understanding
Tool Best Practices
Use tools that are simple and accessible:
- Choose something your team can update fast.
- Make sure everyone in the trio has edit access. If not, fix it today.
- Keep it open during working sessions and refer to it often.
Use comments and tags:
- Don’t wait for the next meeting. If you see a new insight or risk, tag your teammates.
- Make it a safe place for honest questions and rough drafts.
Speed it up with templates:
- Interview Snapshots
- Affinity Maps
- Opportunity Solution Trees
- Story Maps
- Assumption Testing
Check out templates from the communities on Figma, FigJam, Miro, and Lucidchart.
Conclusion
If you want to build something meaningful, you have to make your thinking visible. Visuals help your trio align faster, uncover gaps, and make smarter decisions. They keep the customer front and center. They reduce waste. And they create common ground when the pressure is high.
You don’t need to be a visual thinker to start. You just need to start.
Take Action
-
What you can do right now:
- Pick one shared tool and give everyone edit access today.
- Set up a living, breathing Opportunity Solution Tree and review it on a weekly basis.
- Create a shared folder for raw interview notes.
- Block 10 minutes after each customer conversation to jot down what you heard.
- Schedule a quick weekly sync to align on “what we know so far.”
- Tag each other in comments instead of waiting for a meeting.
What to build over time:
- Create a lightweight template library to reuse across projects.
- Put together a short highlight reel for leaders every 4–6 weeks.
- Set up a searchable archive of insights from interviews.
- Add “Now,” “Next,” and “Later” markers to your roadmap or OST.
- Build a ritual to share discoveries with your squad, even 10 minutes during sprint planning helps.
- Train the team to read and contribute to the Opportunity Solution Tree.
