The Rant that Reshaped Our Product
How me with no context turned public frustration into a product breakthrough
The Moment
An engineer stood up mid-conversation. Uninvited. Unfiltered.
"You know what? The Orchestration Builder doesn't even solve a basic problem."
He wasn't asking a question. He was making a statement. Loud enough for the room to hear it. Pointed enough that everyone knew who it was directed at. Me. The design team.
"It's not useful. You should have solved the basic issues first."
The room went quiet. The kind of quiet that makes you hear your own heartbeat.
The Honest Part
Here's what I didn't tell anyone in that moment.
I didn't have a plan for this. There was no section in any design playbook that said: "When an engineer publicly tells you your work is useless, do this."
I'm a Lead Product Designer at an AGI company. I'd been working on AGI platform. A complex, ambitious platform that was trying to make agentic AI workflows accessible. My job that week was simple: run a UX evaluation in the Orchestration Builder staging environment. Understand the pain points. Talk to the dev team. Gather insights.
Simple, right?
I'd been asking around. Trying to schedule time with the engineering team. A few polite emails. A couple of Teams messages. The usual dance of calendar coordination that every designer knows too well.
And then, instead of a scheduled meeting with structured questions and polite observations, I got a rant.
What Nobody Saw
Here's what the room didn't see.
While the engineer was venting, my hand was moving. I was writing. Every word. Every complaint. Every frustrated observation that came out of his mouth.
Not because I was building a case against him. But because I recognized something in his frustration that most people in that room missed.
He was a user. And he was giving me raw, unfiltered feedback
The kind of feedback you can't get from a structured interview. The kind that product teams pay research firms thousands for. The kind that reveals the gap between what we *think* we built and what people *actually* experience.
He wasn't being professional about it. But he was being honest.
And honesty, even when it arrives rudely, is the most expensive currency in product development.
The Conversation Behind the Conversation
A product manager walked over to me afterwards. He looked more upset than I was.
"This is coming from top leadership," he said. "I can understand the frustration, but this is not the correct way to talk to someone."
He was right. It wasn't.
But here's what I told him:
"I'm a UX person. I know how these things go. But I saw that as an opportunity to reshape our product. I've noted everything. And I'm going to present it to the Product Director tomorrow."
He looked at me like I was either brave or slightly unhinged. Maybe both.
What I Did Next
I went home that evening and did something that most people wouldn't expect from someone who just got publicly called out.
I built.
I took every complaint, every frustrated observation, every "this doesn't work" from that rant, and I turned them into structured UX research findings. I created prototypes. Quick, functional prototypes using Claude that addressed the core issues the engineer had raised. I documented the gaps. I mapped the pain points to potential solutions. I wrote a research document that didn't just list problems. It reframed them as design opportunities.
The next day, I walked into the room with the Product Director and presented the research.
Not as a defense. Not as a response to criticism. But as a new direction.
What Changed
The research revealed what many of us had felt but couldn't articulate.
The Process Builder had been built with capability in mind, not usability. It could do powerful things, but the foundational experience, the basic, day-to-day interactions, had gaps that frustrated the very people who needed to use it most.
The prototypes I built weren't perfect. They were fast. But they were *clear.* They showed the team: here's what's broken, here's why it's broken, and here's what "fixed" could look like.
The reaction wasn't just positive. It was energized.
People who had been quietly frustrated suddenly had a shared language. Engineers who had complaints now had prototypes to react to. Product managers who had been caught between teams now had a research artifact to rally around.
One rant became a roadmap.
The Uncomfortable Truth About Design Leadership
Nobody prepares you for this part of design.
They teach you about wireframes, user flows, design systems, and accessibility patterns. They teach you how to present work, how to defend decisions, and how to run usability tests.
But they don't teach you what to do when someone stands up in a room and tells you, to your face, that your work isn't solving the problem.
Here's what 10 years of design experience has taught me: the most important design decisions happen outside of Figma.
They happen in the moments when you choose to listen instead of defend. When you choose to document instead of dismiss. When you choose to see frustration as data, not disrespect.
What I'd Tell Every Designer Reading This
You will have a moment like this.
Maybe not as loud. Maybe not as public. But there will be a moment when someone tells you that the thing you poured months into isn't working. And everything in you will want to explain, justify, or push back.
Don't.
Write it down. All of it. The messy, unstructured, emotionally charged feedback that nobody would dare put in a Jira ticket.
Then go build something with it.
Because the gap between criticism and innovation isn't courage or talent. It's simply the willingness to treat every voice, even the angry ones, as a user voice.
The Takeaway Nobody Talks About
That engineer? He wasn't wrong.
He was rude. He was unprofessional. But he wasn't wrong.
And the fact that I didn't have a context for that moment? That turned out to be the advantage. Because when you don't have a script, you can't hide behind one. You have to actually listen. You have to actually respond. Not with a template, but with work.
The Orchestration Builder is better today because of that rant.
And I'm a better designer because I chose to sit in the discomfort instead of walking away from it.