𝙏𝙤𝙤 𝙈𝙪𝙘𝙝, 𝙏𝙤𝙤 𝙎𝙤𝙤𝙣? 𝘼𝙧𝙚 𝙋𝙈𝙨 𝙗𝙚𝙞𝙣𝙜 𝙨𝙩𝙧𝙚𝙩𝙘𝙝𝙚𝙙 𝙩𝙤𝙤 𝙩𝙝𝙞𝙣?

Lately, I’ve seen more and more Product Managers diving headfirst into Vibe coding, spending most of their time learning and using low-code or no-code tools, developing, and deploying their “production-ready” builds.

At the same time, some mid to large-sized companies are cutting engineering or design roles and expecting PMs (assuming with the help of AI-enabled tools) to do it all, going from requirements to release, solo.

This might work in a startup or simple products, but it rarely scales well in complex or mature products. At least not yet.

To my fellow PMs rushing to learn Vibe coding as their primary goal: Exploring tools can spark creativity and speed up prototyping, and all good with that!

Let’s only remember, as Product Managers, your core mission is to define the 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝘆, prioritise the 𝗿𝗼𝗮𝗱𝗺𝗮𝗽, and work closely with customers to build the right 𝘃𝗮𝗹𝘂𝗮𝗯𝗹𝗲 thing.

Tools and tech stacks are there to support that mission, not replace it. 𝗙𝗼𝗰𝘂𝘀 on what matters most and 𝗱𝗲𝗹𝗲𝗴𝗮𝘁𝗲 the rest to the right people or automated processes.

To companies leaning on PMs to fill engineering or design gaps: I’m all for cost-effective solutions that improve ROI and increase accessibility.

Let’s only remember that cutting corners might get you to market faster, but poor code quality and unscalable builds will cost far more down the track.

𝘎𝘳𝘦𝘢𝘵 𝘱𝘳𝘰𝘥𝘶𝘤𝘵𝘴 𝘴𝘵𝘪𝘭𝘭 𝘯𝘦𝘦𝘥 𝘴𝘬𝘪𝘭𝘭𝘦𝘥 𝙚𝙣𝙜𝙞𝙣𝙚𝙚𝙧𝙨, 𝘳𝘪𝘨𝘰𝘳𝘰𝘶𝘴 𝙩𝙚𝙨𝙩𝙞𝙣𝙜, 𝘢𝘯𝘥 𝘢 𝘧𝘭𝘦𝘹𝘪𝘣𝘭𝘦 𝘥𝘦𝘭𝘪𝘷𝘦𝘳𝘺 𝙥𝙧𝙤𝙘𝙚𝙨𝙨, 𝘴𝘶𝘱𝘱𝘰𝘳𝘵𝘦𝘥 𝘣𝘺 𝙘𝙪𝙧𝙞𝙤𝙪𝙨 𝙋𝙈𝙨 𝘸𝘩𝘰 𝘴𝘵𝘢𝘺 𝘧𝘰𝘤𝘶𝘴𝘦𝘥 𝘰𝘯 𝘷𝘪𝘴𝘪𝘰𝘯 𝘢𝘯𝘥 𝘪𝘮𝘱𝘢𝘤𝘵.

You can launch 100 features that flop, or one that truly hits the mark.

Focus matters. Don’t lose yours.