AI and modern tools make it trivial to ship code in an afternoon. But the real cost comes after: the maintenance, support, and cognitive drag of carrying features nobody actually uses.
Here I share essays on product strategy and offer open 30-minute virtual coffee chats to help founders and PMs pressure-test what to build (and what to cut).
I've spent nearly two decades building products. I've built from scratch, untangled bloated systems, and learned from plenty of mistakes along the way. I value simple solutions, straight talk, and cutting through the noise. Just like every PM, proudly a master of being a jack-of-all-trades. :)
Finding the smallest, sharpest version of an idea before teams burn months building in the wrong direction. Validating real customer problems early, pressure-testing assumptions, and having the discipline to say no.
A working demo takes an afternoon, but a demo is not a product. Getting past the perpetual proof-of-concept phase means tackling the non exciting realities: reliability, data integrity, user habits, and sustainable economics over the long run.
Products fail less from a lack of features but more for carrying too many. I enjoy talking about Product zombies why they exist and how to live with them (or not!)
Product is ultimately about people. I founded and organize ProductTank Heidelberg (a local community of 600+ product builders and founders), and I love coaching early-career PMs to help them build strong product intuition and navigate their careers.
When not thinking about product, I get lost in Ancient Indian civilization. Fun fact: Acharya Pingala discovered the “Fibonacci” sequence roughly 1,400 years before Fibonacci got credit for it.
Observations
Patterns observed repeatedly across startups and scaleups. Solvable early, but increasingly painful the longer they linger.
A working prototype takes an afternoon, so output feels substantial and teams grow attached. The real question, which customer outcome did this move, goes unasked.
Features with ghost-town usage that are too small to matter and too awkward to delete. They eat maintenance, support and screen space while real priorities wait.
Perpetual PoC zombies that are always one model away from perfection, trapping your scarcest AI and data talent without ever reaching customer value.
When adoption slows down, teams default to shipping more capabilities instead of asking why users abandon the existing ones. The result is a bloated product that does twenty things poorly.
Sales leans on it in the pitch, legacy code depends on it, or someone senior built it. Emotion beats data and the zombie survives another quarter.
Founders and PMs often lack a candid, external sounding board. What is missing is an experienced product peer to talk through trade-offs before engineering cycles are spent.
Have you run into these traps in your own teams? How did you navigate or solve them? I am always curious to hear stories from the trenches and how different teams tackle zombie features and AI trade-offs.
Essays
Every mature tech organization has a ghost ship staffed by two dozen engineers. Product zombies thrive inside the protective shelter of the HiPPO, creating an affection trap neither side knows how to escape.
Zombies are tough to kill and they drag us down. Product zombies are no different, except that they very much exist. Here is a practical way to find them, evaluate them and put them down.
Your product portfolio is hiding a secret that is killing innovation: the product zombie. In the age of easy creation, the old framework matters more than ever.
Whether you are an early-stage founder weighing an MVP trade-off, a PM dealing with feature bloat, or just want to chat product, pick an open slot that fits your schedule.
Grab a 30-min virtual coffee