AI-Led Development Made Features Cheap. Your Users Still Can't Find Them.

AI-Led Development Made Features Cheap. Your Users Still Can't Find Them.

I had a client who built real-time co-editing, which is basically Google Docs but for their data workflows, because users kept asking for it. It took them three months' time, and let's say it was very close to 100,000 US dollars, and six months later 8% of users had touched it.And the funny part is that people kept asking for it after it was live. They didn't have any support, so basically people just submitted ideas, or submitted issues on GitHub or whatever, about 47 a month. Most of those people had been paying for it, but on different plans, because there were people who had been on a starter plan and asking for most of the features, but not the power users. They are almost always silent. That was before AI. Now something like this takes two, three weeks' time, and it ends up in the same place. ⸻ Four clicks to a toggle Where was it? Settings, then Workspace, then Collaboration, then a toggle called "Enable real-time editing". Nothing in onboarding. Why was it there? They hid the feature because on the landing page they had everything about this real-time collaboration, absolutely everything was about this collaboration feature. But unfortunately, when you are a free user, you are allowed to use only basic functionality. And so that was the reason. The founder told me: "It's a premium feature. We don't want to confuse free users by showing it if they can't use it." It's a nice thought, but 64% of their users were on paid plans. I tracked it, not for long, I think for 20 days, 25 days. 8% found the toggle in Settings by accident. 12% asked and got told where it was. 3% read the changelog. The other 77% never found it. ⸻ The fix was almost embarrassing I changed three things, and none was a redesign. Onboarding got one line, about 10 seconds: you can collaborate in real time, click any document to invite teammates. If you opened a document alone, you got a small prompt: working solo? Invite teammates. And the toggle moved out of Settings and became a Collaboration button in the header of every document. In 30 days 81% of users had found it. Usage on paid plans went from 8% to 47%. The requests went from 47 a month to 11. Nothing in the feature itself changed. Three months of engineering, and what saved it was a button and one sentence. ⸻ Now the same thing happens in three weeks Now it goes differently. A person sees something on X.com, saying that someone requests something like this, a product similar. So they get an idea. They ask the opinion of 25 to 40 people. They say, yeah, yeah, yeah, this is a very nice idea, and you would be like the next Elon Musk and everything. This person thinks that this is so nice, this is a very nice thing. And so they just start to build all the shit, and it takes two, three weeks' time of absolutely vibe-coded experience, and it costs them like 10 grand. But most importantly, this thing costs them their health and mental well-being, because all these people, they're developing all their products vibe coding, without the basic... okay, fine, forget about basic, but without even some advanced understanding. They are growing dependent on their AI. They just say, okay, I will build one more feature, which actually means AI will build one more feature, and I'll just sit there and check what's what. And nobody in that process asks where the feature goes. So it goes to Settings. ⸻ What Settings actually tells people Settings would say that this is some advanced stuff, and if you would love to just fuck around, you just could break the product. Unfortunately, there are some people that would say you have basic settings and advanced settings, which says we couldn't decide, so you decide. I would say that if this is a feature and it's more than two clicks away, it says that this is vibe-coded shit that wouldn't help you at all. It's not like bad UX, it's AI UX, which is always shite. ⸻ The four mistakes I see again and again The first one is how paid features are shown. Some of them are hidden, like the toggle. Some of them are on the first panel in the settings, and they try to say that if you want to activate, just pay right now, without even giving people some basic time to just try it out. The second one is Settings as a dump. Settings is for time zones, notifications and passwords, but every feature the team couldn't place ends up there. And again, there are some people who would say, like, advanced settings and basic settings. It's absolutely, absolutely crazy. The third one is the launch. My client still had a changelog, and 3% read it. I don't think people do those changelogs anymore. I think they have websites and they have emails sent to potential users. Because some people would say this is, like, a killer feature, and we release it, and then ask AI to produce some short five-second video of how this feature works, completely forgetting that they have built another three, four features that should grab some attention as well. And the fourth one is new. On their landing pages, on their website, they promise too much and do too little. So this is one of those things that they promise somewhere, somehow, and then they just ask Claude Code to build it for them. So no designer, no planning meeting where someone would ask where people will actually see it, and that's why they all have this mistake. ⸻ So before anyone opens Claude Code for the next feature, read last month's requests and count how many ask for something you already have. AI will build you a feature by Thursday. It has no idea where to put it. ⸻

Original Source

Read the full article at Hackernoon →

KhanList aggregates and links to publicly available news content. We do not host full articles from third-party sources. Always verify important information with original sources.