← Voices /

The Space Between

The gap between the key moments — the part seldom paid attention to. What happened before the discovery ever began.

🎤 hear it in his voice
The Space Between — Venky’s version, Part 2
About 17 minutes. A cancelled workshop, a vulnerable admission, two brands at different speeds, and an airport phone call.
87 87 / 100 · faithful to the recording How close is this page to what Venky actually said? See the breakdown →
The Whisperer’s reply to The Loud Fight · in three parts The Dreamer shared The Loud Fight first — the fourth voice in his own run. Hearing it set off a chain of thoughts in The Whisperer, who answered with this three-part reply. So although these read as Parts 1–3, they were penned after the Loud Fight, in response to it — his version of the same journey, told his way and shaped for the page. The memories don’t always line up. That, more than anything, is the point. Part 1 · Prologue  ·  Part 2 · The Space Between  ·  Part 3 · The Workshop

Built from a voice recording, then shaped for the page — the way you’d tell a story to a friend. Part real, part retelling: the moments are true, the names are protected. Memory is imperfect and voices are interpreted. If this caused any discomfort, we're sorry.

Every good story skips the boring middle. This is the boring middle. It’s also where the real work happened.

March 2025. We had a workshop on the calendar. We cancelled it.

That sounds like nothing. It didn’t feel like nothing. Sri, The Dreamer and I had one of those conversations that quietly rearranges the furniture in your head, and at the end of it Sri said: cancel the workshop. Focus on AI and Artemis tech — the part that’s actually within our control.

And then he said the thing I keep coming back to:

I haven’t earned the right to coach others on AI yet. I should do it inside one team first. Truth hurts — but that’s where I stand today.
Today's conversation was truly eye-opening, guys. I realize I haven't gained enough experience to coach others on how to utilize AI effectively. I should implement this at least in one team first, truth hurts, but I guess it's the reality of where I stand today.

A leader, voluntarily saying not yet, not me, not until I’ve done it myself. That’s rarer than any model release. And it set the tone for everything after: we would earn the workshop before we sold it.


By May, Voice IQ had done its quiet work. The business had seen it. The Champion believed in it — and belief travels in both directions; she inspired the business and the business inspired her right back. Then she brought us the next thing:

our sales sponsor and I are fleshing out AI proposal generation. Take a call transcript, auto-generate an itinerary for the consultant to review. The leadership is very excited.
James and I are fleshing out another AI project on AI proposal generation. This is something the ET SLD are very excited about. It's taking those call transcripts and based on that auto-generating an itinerary for the TC to review.

She was honest about the weight of it: “The goal feels aggressive to me. But I trust you — you’ve lived with these AI projects longer than we have.” The Bold One was the one pushing to go big and bold. The Champion was the one carrying the risk. Both true at once.

The seed had actually been planted a year earlier. The Spark floated it back in 2024: take the last few hundred sold proposals for a destination, train the AI on them, hand it to the consultants. Ideas like that don’t die. They marinate. This one had sat in the room for a year, waiting for the rest of us to catch up.


By June we were prioritising, and The Wanderer framed the problem so cleanly it never needed reframing:

A consultant spends most of the day building proposals from scratch. If AI halves that, they get the other half back — for customers, and for selling.
TC spends more time creating proposals from scratch. Is there an opportunity to reduce this time by 50% using AI so that the TC can devote time to relationship building and more sales?

Around the same time I was running the same play with the the sister brand team — The Catalyst and The Steward — on their own proposal automation. Same blueprint: start small, show a sliver of improvement at every step, keep the business close, and move slowly from do-it-yourself toward do-it-for-me.

And then the two brands started moving at very different speeds — which taught me something I didn’t want to learn.

the sister brand flew. Within a couple of weeks their sales team was pulling a transcript and weaving real first-draft proposals, even feeding the AI draft back into their own tooling to finish it. the brand did not fly. And that wasn’t a knock on the brand — just the opposite. the brand is a complex, niche, deeply experiential business, with a team that is fiercely opinionated for all the right reasons, and real skin in how things get built. the sister brand’s users were happy to be handed a tool and told “go.” the brand’s users wanted to argue with it first. That isn’t friction. That’s care.

But from the outside, it just looked like one brand was winning. The execs noticed. The First Dreamer and The Bold One started pushing: the sister brand is galloping — why not the brand? Why aren’t we just copying what works?

And we got defensive. I’ll own that. We wrote canvases explaining why the two businesses weren’t the same, why one size wouldn’t fit both. But underneath the defensiveness sat a principle I still believe:

When you’re doing blue-sky work, the cookie-cutter is the enemy. What works in one brand is a hypothesis in the next — not a template.
When we are innovating and when we are actually having a blue sky thinking, let's not follow a cookie cutter model. Something is working in EE, doesn't mean it will work in ET — let's do this discovery from scratch.

So we held the line: the brand would get its own discovery, from scratch, not a tracing of the sister brand. And that turned out to be exactly right — because what “good” meant for an the brand customer was a completely different shape than for the sister brand.


Before the real pressure hit, we ran a small discovery call — our sales sponsor, The Dreamer, Sri, The Champion, The Builder, The Believer, me. Sri asked one question that stopped the room:

Do you want an evolution, or a revolution?
We were talking about this concept of evolution versus revolution. She asked this question — what do you guys want to do, an evolution or a revolution? — and everybody was stunned. Evolution is incremental changes to remove admin and planning tasks from the TC's workflow. The revolution is completely anchored on proposals by AI.

Evolution: shave the admin and planning off the consultant’s day. Revolution: anchor the whole thing on AI-generated proposals and be willing to change how people work — probably with a new cohort who carry none of the old muscle memory. Just naming the choice out loud changed every conversation that came after. I think I even opened a Slack channel for it. The description was a dare: Can we script history together?


July. The pressure arrives. On the 16th I told the team we were starting the engineering foundation — daily pairing with The Ghost, building a platform so we’d have something real to play with during the workshop, not after it.

This came from a heresy I’d been muttering for months, and that Sri and The Dreamer and I kept throwing at each other: if AI is going to rip up how we build software, why is discovery still a five-day slideshow? Why can’t discovery be AI-first? Why can’t we walk out of it holding a working prototype instead of a wall of sticky notes?

So my job, as I saw it, was to cut the noise. Stop explaining, stop defending. Build. We already had Voice IQ — so we plumbed its transcripts into a small new platform, fed in a knowledge base of past proposals, and let an LLM take a swing at sample itineraries. Not to present as the answer. Just to make the possible visible.


Meanwhile the weight was landing squarely on The Dreamer. The Champion had spun up a workshop channel, expectations were set, and the brand was openly impatient with our old ways. The Bold One said it to our faces:

We’re not fans of your discovery workshops. Five days, and all we get is a hypothesis. We think we can do this ourselves.
We are not a big fans of your discovery workshop. You guys take five days and at the end of the five days, we have some hypothesis or some convergence on what could be the real outcome. And I think we can do this ourselves and we will tell you what needs to be done.

And instead of bristling, we did something better — we agreed with the discomfort. We said: fair. And honestly, we don’t fully know what a new kind of discovery looks like either. Let’s find out together.

That openness cost The Dreamer something, though. One evening he sent me a message — just to me — that I won’t forget:

I’m a bit lost, The Whisperer. I wanted an inception with the whole team. Now there’s a tech inception that’s already happened, two meetings scheduled, and I feel the one thing that matters — giving people the space to understand the ask — is being sacrificed to “bias for action.”
I'm a bit lost, Venky. I want an inception with the full team. Now suddenly we see that there is a tech inception that has happened, Devika has scheduled two meetings — I somehow feel that the fundamental technique of giving enough space and time for the teams to discuss and understand the ask better is lost in the name of bias for action. And just wanted to share it in private.

Sri and I were at the airport, on our way to visit a partner. I read it and stepped away. “Sri, give me a minute — The Dreamer needs a call.”

The real knot was simple. The Champion was anxious because The Dreamer couldn’t hand her a tidy agenda and a guaranteed outcome. And The Dreamer, being a true product person, refused to pretend he could:

I know what I know, and I know what I don’t. I can’t tell you the exact outcome — arriving at it is the work.
Rajesh in his own product thinking says, I know what I know, I don't know what I don't know. I really can't tell you what we will do at what point in time and what will be the outcome — because this is to arrive at the outcome.

We talked it through on that airport call. He went back to The Champion, had the long, hard conversation, and came out the other side with eight points of alignment. The two tracks were finally official. The anxiety had done its job — it had squeezed out clarity.


That’s the space between. No demo landed here. Nothing shipped. It’s the chapter you’d normally cut.

But this is where a cancelled workshop, a leader’s honesty, two brands at different speeds, and one vulnerable message at an airport quietly decided whether the next part would work at all.

Then we walked into the room.

Part 3 — The Discovery Workshop: Three weeks of 4:30 p.m. calls. A “room before the room.” A tit-for-tat between The Whisperer and The Dreamer that made our sales sponsor wonder if the team was toxic — until he saw the coffee afterwards. And a first booking that landed on a birthday.
Read Part 3 →
← back to Part 1
about the author
The Whisperer is most interested in the parts other people skip — the cancelled workshop, the private message, the airport phone call. This is Part 2 of his three-part reply to The Dreamer’s Loud Fight. Spoken, not written.

Have your own AI story? WhatsApp Sree →  ·  or email →