The best feedback I've ever gotten came in slightly annoyed, over a phone call, from a physiotherapist named Yukta.
Yukta is one of the real ones -- a paying customer on the old PHP version. She's been running her practice's bookings through my software for a while now, which means when she talks, I don't get defensive, I get a notebook. People who pay you and keep paying you have earned the right to tell you you're wrong. And today she told me I was wrong.
"Your reschedule thing," she said. "It's built wrong."
Now, I'd just been rebuilding reschedule for the new version, and I was quietly proud of it. A guest wants to move their booking to a different time? The host can do that. Clean, simple, works. So I asked her what she meant.
"A patient asked to move their slot," she said. "So I moved it. Your system just... let me. Changed the booking to the new time. And I assumed they'd see it, that they knew, that it was settled. They didn't. They showed up at the old time. I had an empty room at the new one and a confused patient at the old one. Awkward for both of us."
And I felt that one land in my stomach, because the instant she described it, I saw exactly what I'd done.
I had built reschedule as if the host is god. The host decides, the host moves it, done -- the system treats the host's action as the final word. But that's not how the world actually works. Yukta doesn't control her patients' calendars. When she moves a booking, that's not a decision, it's a request. The patient has a life, a schedule, other plans at the new time. Moving their booking without their explicit yes isn't helpful -- it's the software silently overriding a person's day and hoping they noticed.
"I'm not god," Yukta said, and honestly that should be printed on a wall somewhere. "My patients have their own lives. When I move something, they have to agree to the new time. Not me deciding it for them."
She was completely, obviously right, and I'd been completely, un-obviously wrong -- un-obvious because on my screen, as the developer, the feature worked perfectly. I moved a booking, the booking moved. Success! I never felt the gap, because I was never the patient standing in an empty room. You cannot see this bug from inside the code. You can only see it from inside someone's actual practice.
So I changed it. Reschedules are no longer a done deal the moment a host clicks. Now a reschedule is a proposed new time that waits for the guest to acknowledge before it becomes final. The host suggests, the guest confirms, and only then does the booking actually move. Until the guest says yes, the change is pending -- visible, honest, not silently pretending everyone's on the same page. It meant reworking the booking's states to carry that in-between "waiting for you to confirm" status, but that's a small price for the software telling the truth about what's actually been agreed.
Here's the thing I keep coming back to, and it's kind of the whole philosophy of why I even rebuilt this product: one sentence from a real customer beat a week of my own thinking. I could have sat in a room for days designing reschedule flows and I'd have designed the same wrong one, because I don't have patients, I don't run a physio practice, I've never stood in an empty room at 4 PM. Yukta has. Her lived reality is worth more than my cleverest assumption.
This is exactly why the PHP version wasn't a waste -- it's why I keep calling it "expensive market research." It put my software into real lives, and real lives push back. Yukta pushing back made the new version more honest than I could have made it alone.
Early customers are worth more than any analytics dashboard I'll ever build. A dashboard tells you what happened. Yukta tells you why, and what to do about it, in one annoyed sentence. I'll take the annoyed sentence every time.
Tomorrow: Google Calendar, and a Meet link that stubbornly refused to be born.
Explore more from Shubham — discover curated reads at BookASloth, or check out Rajmudra Media for media & marketing solutions.
Explore more from Shubham — discover curated reads at Book AS loth, or check out Rajmudra Media for media & marketing solutions.