AI Product Management Lesson #2 Humanizing AI by Reducing Cognitive Load We all hate taking meeting notes. Or we don’t take them … and forget everything. In most meetings, you’re either (not counting distractions / multitasking): paying attention or writing things down Anyone claiming to do both well is lying (or not listening). This isn’t a productivity issue. It’s biology. The original sin: asking humans to multitask Meetings ask us to: listen think react decide And then we add:“Also, please document this perfectly.” For years, we treated this as a discipline problem. It wasn’t. It was cognitive overload. A brief, slightly embarrassing history of trying to fix this Phase 1: The Moral Phase (pre-2010)“Take better notes.”Translation: try harder to be less human. This gave us notebooks, templates, and the dreaded “note-taker” role. Phase 2: The Tool Phase (2010–2016)Evernote. OneNote. Shared Google Docs. Founders believed better tools would solve the problem. They didn’t.They just made multitasking prettier. Phase 3: The Recording Phase (2016–2019)“Just record the meeting.” We did.And then never watched it again. We didn’t fix memory.We created archives of regret. Phase 4: When AI finally learned to be polite The breakthrough came when a few founders asked a dangerous question: “What if the user shouldn’t do this at all?” That’s when products like Otter and Fireflies clicked. They didn’t say:“Here’s a smarter way to take notes.” They said:“Don’t take notes.” The AI listens.Quietly.Patiently.Like a background character doing the hardest job in the room. That’s humanizing AI. Now here’s where Tell Mel quietly teaches the same lesson At first glance, Tell Mel and meeting-note tools seem unrelated. They’re not. Tell Mel starts with a similar truth:People want to preserve stories … but the moment you ask them to: install an app learn an interface type or navigate You lose them. Especially if they’re elderly. The founders didn’t ask:“How do we make AI smarter?” They asked:“What’s the least demanding way a human already knows how to share stories?” The answer was obvious … and almost no one takes it seriously anymore: A phone call. Just talk. No learning.No remembering.No cognitive strain. Same philosophy, different domain Otter. Fireflies. Tell Mel. Different products.Same product wisdom: Humanizing AI means removing effort, not adding intelligence. Meetings → stop writing Memories → stop typing Stories → stop learning software The AI does the work so the human doesn’t have to. The AI Product Management lesson hiding in plain sight As an AI PM, this is the uncomfortable question you must ask: What task am I asking the user to keep doing, simply because “that’s how it’s always been done”? If your product still requires: attention training constant interaction You may have built a capable system … but not a humane one. A quiet acknowledgment to the founders who got this right It’s worth acknowledging the founders who saw this early: Sam Liang (with Yun Fu and Eli Calderon Morin), founder of Otter AI, for realizing that presence matters more than perfect notes. Krish Ramineni (with Sam Udotong), founder of Fireflies, for letting people participate instead of transcribe And of course, Charlie Graham and Dr. Justin V. Graham, for trusting something as unfashionable … and as human … as a phone call Different journeys. Same instinct. The simple rule that keeps showing up If your AI product demands attention, it’s not humanized yet. The best ones feel boring.Invisible.Almost obvious in hindsight. That’s not a lack of ambition. That’s product maturity. Originally published at https://www.linkedin.com/pulse/ai-pm-masterclass-2-humanizing-reducing-cognitive-load-zztec
The AI Delusion: Tools Don’t Build Products, People Do
Every founder I meet today starts with the same sentence: “We’re building something with AI.” It’s said with pride, as if the presence of machine learning itself guarantees destiny. Like salt, or is it oregano or chaat masala for you – just sprinkle it on your startup and suddenly it tastes like the future. But here’s the thing. Tools don’t build products. People do. And lately, I see too many founders falling for what I call The AI Delusion — the belief that technology will save them from doing the human work: thinking clearly, choosing customers, understanding problems, and making something people actually want. The Founder Dilemma A team once showed me their “AI-powered platform for automating design decisions.” It looked impressive. Slick UI, endless integrations, and a tagline that read like it had been handcrafted by ChatGPT itself. When I asked who their customers were, they said, “Anyone who designs things.” When I asked what problem they solved, they said, “Creative inefficiency.” I nodded politely. Then I asked, “How many designers have paid for this?” Silence Their product wasn’t broken because the model was weak. It was broken because they’d skipped the hard part — talking to real humans long enough to make something worth using. Here is the Deal. AI is a lever, not a ladder. It multiplies direction. If you’re clear about the problem, it makes you faster. If you’re unclear, it just helps you get lost more efficiently. Most founders overestimate what AI can replace and underestimate what judgment can create. A good model can generate code, content, and patterns. But it can’t decide what’s meaningful, valuable, or worth finishing. That’s still your job. Case Study Remember when the world discovered “AI resume builders”? Dozens of them popped up overnight. The tech was solid. The prompts were clean. The UX was identical. A few made millions. Most disappeared. The winners weren’t the ones with the best LLM integration. They were the ones who picked a clear customer — say, job-seekers in tech — and solved a specific pain: writing a resume that beats applicant tracking systems. Narrow focus, strong story, sharp edge. The technology was the same; the intent wasn’t. Fat Tony’s Law: AI amplifies clarity. If you’re confused, it amplifies that too. Let us flip our Mindset. Everyone says “build with AI.” But a better mantra might be “build around AI.” Let’s Ask: What human behavior or pain point stays constant even as tools change? Where does AI reduce friction for real people — not just for your deck? What part of your product still needs a human touch, judgment, or story to feel alive? If your startup needs AI in the first sentence to sound interesting, maybe it’s not. What Not to Do Don’t call it AI because investors do. Don’t outsource customer discovery to your data pipeline. And please, don’t build a dashboard for a problem that doesn’t exist. You don’t need to be an AI founder. You need to be a founder who uses AI intelligently. The Reality Challenge This week, take your favorite AI idea and rewrite it without the word “AI.” Describe what it does for a human, in plain English. If the description still holds power, you’ve got something. If it falls flat, you’re not solving — you’re decorating. Send your rewritten version to help@founderhelpdesk.in with the subject line “Fat Tony — AI Delusion Check.” I’ll share a few sharp ones next week. Most founders chase technology. The great ones chase understanding. Because while AI can mimic intelligence, it can’t replace insight. That still belongs to the people who build, not the tools they use. See you next Sunday. — Fat Tony FounderHelpDesk P.S. You pick next week’s topic. What question about building, funding, or surviving the early stage is living rent-free in your head? Send it — the real one. Not the polished version. help@founderhelpdesk.in Originally published at https://www.linkedin.com/pulse/ai-delusion-tools-dont-build-products-people-do-founderhelpdesk-pnfxc/
Why Most Founders Mistake Planning for Progress
It’s Sunday afternoon. The world is relaxing, scrolling, or napping. And somewhere, a founder is sitting in front of a laptop with twelve open tabs, two productivity tools, and a Notion dashboard titled “Q4 Execution Strategy — Final FINAL (v7).” Zoom out of this scene, and you can see many more founders trying to make their Sunday afternoons more productive. They’re not lazy. They’re thinking. But deep down, they know what this is — another beautifully disguised delay. The mind’s way of feeling productive while quietly avoiding the real, uncomfortable part of building something new. Most founders think planning equals progress. They draw roadmaps, set KPIs, polish slide decks—and call it work. But busy planning is often just a clever way to postpone the one thing that actually matters: finding out if anyone cares. Planning has its place. You need direction. But somewhere along the way, it becomes a comfort zone—clean, structured, and safely removed from risk. You can’t fail on paper. You can only refine. And that illusion feels productive. I’ve seen it a hundred times. A founder spends months mapping the journey, building elaborate projections, hiring consultants to model hypothetical growth curves. Meanwhile, the market moves on. The pattern is familiar. The Mr. “Perpetual Prototyper” building features nobody asked for because they “fit the vision.” The Mr. “Validation Looper” doing endless surveys, meetings, advisory calls that never end with an actual offer. The Mr. “Fund-First Player” waiting for money to fix uncertainty instead of using curiosity to remove it. All of this looks like work. It even feels like work. But it’s motion without momentum. The truth is, most founders would rather polish their assumptions than risk testing them. A few years ago, I watched a young founder build a scheduling app. Beautiful roadmap. Ten integrations. Months of polish. When it finally launched, silence. Not a single sign-up … uh..uh.. unless you want to count family and few beer friends 😉 A competitor – in a related space, who started weeks later, stripped the problem to one use case. Built a rough demo. Talked to ten people. Three paid. A month in, they had traction. Same problem. Same market. Different tolerance for uncertainty. Progress isn’t about working harder. It’s about facing reality sooner. If you want to turn plans into proof, start simple. Write the shortest version of your offer in one line. No jargon, no features, no future vision. Just: “I will do X for Y so they can get Z.” Send it to ten people. Friends, strangers, prospects—anyone who might benefit. Watch what happens. If one person says yes, you’re learning. If ten ignore you, you’re learning faster. Either way, you’re out of theory and into truth. Most of what we call “strategy” is just delayed exposure to feedback. If you can’t sell the idea in one sentence, you’re probably building fiction. Here’s what not to do: Don’t spend another week perfecting your brand before you have a buyer. Don’t design new features because you’re tired of rejection. And don’t wait for the perfect time. The perfect time is the moment you stop hiding behind preparation. Here’s something to try this week: Pause planning for 48 hours. Write your one-line offer. Send it to ten people. See what you learn. Progress is messy. It’s often uncomfortable. But the ones who move fastest aren’t reckless. They just stop pretending clarity will come from another spreadsheet. Ask yourself: are you optimizing your roadmap, or your ability to learn? Clarity beats complexity. Fast learning beats slow planning. If you want a second pair of eyes on your offer, send it to help@founderhelpdesk.in with the subject line “Fat Tony — Sunday Check.” I’ll read a few each week and share the sharp ones. — Fat Tony FounderHelpDesk Next Sunday: Let us know what you like us to brainstorm about – I will mention you if I pick your idea. Originally published: https://www.linkedin.com/pulse/why-most-founders-mistake-planning-progress-founderhelpdesk-9ofvc/
The 24-Hour Validation Sprint — How to test demand before you build anything
It’s surprisingly easy to spend weeks—or months—working on an idea without ever asking the only question that matters: does anyone actually want this? Most founders don’t avoid validation because they’re lazy. They avoid it because it feels exposing. The market is honest in a way your notebook, your mentor, and your imagination will never be. So instead, the mind invents a story: “I just need to refine the product a bit more.” “I’ll validate after I finish the MVP.” “I’ll talk to users once something exists.” But the longer you delay reality, the more fragile the idea becomes. It grows protected, theoretical, precious. Hard to hold up to the light. Clarity doesn’t come from planning. It comes from contact. The Founder Dilemma A founder I spoke with recently had been working on an AI tool for freelancers. Smart idea. Nice thesis. Elegant pitch. He had: a well-structured Notion file polished market research a beautiful Figma prototype He did not have: a single conversation with someone who might buy it He said, “I want it to be strong before I show it to anyone.” But strength doesn’t come from isolation. It comes from pressure. The longer he waited, the harder it became to test. The idea calcified into identity. Core Insight Validation takes courage, not code. You don’t need a product to test demand. You just need an offer someone can say yes or no to. Most founders think validation means surveys, interviews, or complicated UX testing. But markets don’t respond to opinions. They respond to decisions. Validation = A real offer, to a real person, with a real possibility of acceptance. Everything else is noise. The Case Study Remember Airbnb? Their “validation test” wasn’t a website. It was three air mattresses in their own apartment and a simple message: “We’ll host you during the conference.” No platform. No backend. Just a clear offer in the real world. They didn’t ask people if they liked the idea of staying in someone’s home. They offered the stay. People said yes. That was validation. The product came later. The 24-Hour Validation Sprint If you want to know whether your idea has a living pulse, run this—tonight, tomorrow, or the moment you feel yourself drifting into planning-mode again. Write the Offer in One Sentence: Make it embarrassingly simple. “I help X do Y so they can Z.” Send it to 10 Real Prospects: Not friends who will reassure you. Not founders who will critique the concept. People who would actually benefit. Track the Reaction: The answer you’re looking for is not enthusiasm. It’s commitment. “Can we talk?” “How soon?” “Can you do this for me next week?” If you hear silence or polite praise, the idea needs refining. If you get one person leaning forward, you have a foothold. One signal is enough to move. Ten signals are enough to build. Silence is a sign to rethink, not to double down. Fat Tony’s Law: The faster you expose your idea to reality, the stronger it becomes. What Not to Do: Don’t explain the roadmap. Don’t talk about features. Don’t apologize for roughness. You’re not selling the product. You’re testing whether the problem is alive. The Reality Challenge for This Week Write your one-line offer. Send it to ten real people. No landing page. No deck. No logo. Just contact. Let the market answer. If you want a second pair of eyes before you send it, email it here: help@founderhelpdesk.in Subject: Fat Tony — 24-Hour Sprint I’ll reply to a few with direct, sharp adjustments. Progress is not about how much you build. It’s about how quickly you learn. See you next Sunday….hang on for one more sec. What should I write about next? Reply with a topic you actually want clarity on — not the polished question you ask on panels. The real one. The one you’ve been circling in your head. The one you don’t say out loud Send it to: help@founderhelpdesk.in Subject: “Next Sunday” Originally published at https://www.linkedin.com/pulse/24-hour-validation-sprint-how-test-demand-before-you-build-xxzqc