A tester logged into IntrynSync last week, stared at the screen, and texted me: "It's not clear what I'm supposed to do. There's a lot of noise."

He's a sharp guy — builds his own software. If he bounced, everyone bounces. So instead of explaining the product to him for the tenth time, I shut up and listened. That conversation rewired the entire thing. Here's the honest version, because that's the only kind worth writing.

What we built vs. what people wanted

IntrynSync started life solving a real but narrow problem: when software and AI agents act on your behalf, you need accountability — memory, audit trails, trust scores, a record of why every decision was made. Genuinely useful. For about 2% of people.

The other 98% don't wake up wanting memory, governance, or a trust score. They wake up wanting an answer to one question:

What needs my attention today?

We had buried that question under a wall of concepts the user had to learn before the product did anything for them. We were asking people to understand IntrynSync before IntrynSync understood them. That's backwards, and the "noise" my tester felt was the sound of it.

The bug behind the feeling

When I actually traced it in the code, it was worse than a vibe. New users were:

  • Filling out a long intake form, then getting asked the same kind of questions again after they logged in — because we'd accidentally built two separate onboarding systems that didn't talk to each other.
  • Landing on a screen full of demo data — sample cards that had nothing to do with their life — instead of their own problem in their own words.
  • Looking at marketing-site navigation bleeding into the app, so it never felt like they'd actually arrived anywhere.

Everything they typed got captured. None of it got shown back. Imagine telling a friend your problem and watching them nod, then hand you a brochure about someone else's problem. That's the experience we shipped.

The metaphor that fixed it: Waze

The unlock came from a dumb-simple analogy. Waze is just a map — like any other map. But the moment you give it a destination, it transforms into something that actively works for you: it plots the route, tells you the next turn, and reroutes the second reality changes.

Here's the part that mattered: you don't need a destination to open Waze. You can just look at the map, see what's around you, and drive. The destination is optional. And when Waze knows you — that you always stop at the same coffee place, get gas at the same spot — it gets quietly, almost spookily, more useful.

That's the product.

  • The map = your default home. Open it and immediately see what needs you today. No setup, no goal required. It works forever this way.
  • The destination = a goal, whenever you decide something matters. Set one and the app starts plotting the route from "someday" down to "the one thing to do today."
  • The memory = it learns how you operate. "You usually finish these on Tuesdays." "This has been stuck for nine days — still want it?" Memory you feel, not a database you visit.
  • Recalculating = the Waze move most goal apps refuse to make. Miss a day? No red streak, no guilt, no "you broke your chain." It just reroutes. The app is never disappointed in you.

Most goal tools stop at aspiration — they're where intentions go to die, the Pinterest board you made in January and never opened again. The difference isn't the picture of the goal. It's the follow-through: the next turn, every day, connected to the thing you actually care about.

Or, the one-liner I keep coming back to: Notion holds your goals. IntrynSync moves them.

What's actually changing

This isn't a tagline swap. We're rebuilding the front door:

  1. Your first screen is yours. You log in and see your problem, in your words, with a clear next step — not a demo, not a tour, not a quiz.
  2. One way in. A single input — "What needs your attention today?" — instead of two onboarding flows fighting each other.
  3. Goals are optional, not a gate. Live in map mode forever if you want. When something genuinely matters and you keep coming back to it, then the app offers to turn it into a route. You're never forced to fill in a five-year plan to get value in the next thirty seconds.
  4. The heavy stuff goes underneath. Memory, accountability, the governance features — they're still there, but they only surface when the stakes actually call for them (a team, real money, clients, agents). The person tracking their kid's college apps never has to see a trust score.

The lesson for anyone building

I didn't need my ego stroked. I needed the gut punch, because gut punches get you to the goal faster. One honest tester saying "WTF am I supposed to do?" was worth more than a hundred polite nods.

If your product needs to be explained before it's useful, the problem isn't your explanation. It's the front door. Build the one where the user sees themselves in the first five seconds — and let the clever architecture earn its place underneath, where it belongs.

More soon. We're building this in the open.