My frustration with product tooling

When Nathan and I started Adora, it began with a vision of the product visibility I longed for during my time leading Product Growth at Canva.

I kept running into the same problem in a hundred different forms: data lived everywhere, but clarity lived nowhere.

I could see pieces of the story in different tools. But I couldn’t see a live, end-to-end view of what was actually happening across a journey, for each variation of customer.

The tools were all there: analytics dashboards, session replay, feedback platforms. But they didn’t connect. You’d get fragments, not the full picture.

So Adora was born from a simple question:

What if you could see every user journey in your product, end to end, as it actually happens?

We started with journeys

The first thing we built was journey mapping: real, live, end-to-end maps of how users move through your product. Not the kind you sketch on a whiteboard in a workshop. The kind that updates continuously, because it’s grounded in what users are actually doing.

In the early days, we spoke to hundreds of product teams. The pain was universal, and it ran deep. Teams didn’t just want journey maps, they needed them. They were tired of stitching together five different tools to understand a single flow. They were tired of running workshops to produce maps that were outdated the moment the sticky notes went up.

So we built it. Teams started using it. And then we heard the same request over and over.

“Just tell me what I need to fix”

Once teams could see their journeys clearly, the next ask was immediate: “I don’t want to go hunting for problems. Just tell me where they are in this journey.”

They wanted Adora to surface the issues, show the evidence, and point to what matters most.

And honestly, they were right to ask for it.

This is the same pain point I felt throughout my entire product carer.

A dashboard can tell you something changed. It rarely tells you why it changed, or what a real customer experienced in the moment.

At Adora, we already had the ingredients that made this possible.

We capture live screenshots that update continuously. We have full session replay. And we have end-to-end journey mapping that ties it all together.

That combination put us in a unique position to build something genuinely new.

A new era of visual analytics

That’s how AI Insights was born.

Not as a feature we dreamed up in a roadmap session. As the thing our users kept asking us to build, because they could see Adora was the only product that could do it properly.

AI Insights scans your product continuously and detects frustrations, issues, and missed opportunities as they happen. It groups them, labels them, and ranks them by impact.

Here’s what makes it different from any alerting or anomaly detection you’ve used before: every insight is tied to real session replays and real journeys.

You’re not looking at a chart that says “conversion dropped 5%.” You’re looking at the journey where users got stuck, with:

• a screenshot of the moment something went wrong
• a session replay that shows the friction
• a recommendation for what to fix

And when you’re ready to act, you can push that insight straight into a Linear ticket, with the context and next steps attached, so your team can move quickly.

How teams are using AI Insights today

The most rewarding part for me has been watching how quickly AI Insights has become part of our early users’ weekly rhythm.

This isn’t a tool people check once a month. It’s becoming the place teams start their week.

• Sprint planning. Product managers start the sprint by pulling the top-ranked insights for their product, or a specific journey. Instead of debating priorities based on gut feel or outdated reports, they walk into planning with an evidence-backed list of issues that will have the most impact.
• Bug hunting. Engineering teams use insights to catch issues that would otherwise take days or weeks to surface through support tickets. Because every insight comes with a session replay and a screenshot, the time from “we found a bug” to “we understand the bug” has collapsed.
• Release validation. After shipping a change, teams monitor the real-time impact. Did the update introduce friction? Are users getting stuck somewhere new? You see it immediately.
• Localisation. Teams with international products spot journey-level issues that are specific to certain markets or languages. These are problems that are almost impossible to catch by staring at aggregate dashboards.

Our early beta testers are sharing insights with their teams daily or weekly. It’s become part of how they build.

The product we always wanted to build

AI Insights isn’t just a feature we’re launching. It’s the natural evolution of what Adora was always meant to be.

We started by giving teams the ability to see their journeys. Now we’re giving them the ability to understand them automatically, continuously, and with the evidence they need to act.

Having insights overlaid directly on your journeys has elevated Adora into the product Nathan and I always wanted to build. It’s the tool I wish I’d had.

If you’re a product team swimming in data but struggling to know where to focus, we built this for you.

AI Insights is available now. See it in action →