One Month PM - The Fullstack PM Academy

I bet you're biased. I'm biased. Your team is completely biased. Your CEO is 100% biased. Every single time I've screwed up in a product decision, it was connected with NOT identifying someone's biases (including my own). So let's explore them, in a way PMs get them: 1. Confirmation Bias You only read the user feedback that says your product is awesome. The rest? “Users are dumb”. 2. Anchoring Bias The first estimate is always the right estimate. New information that says “this will take longer” doesn’t matter. 3. Availability Heuristic Last week's bug is all you can think about, so you declare it "top priority". Meanwhile, other bugs rule the backlog. 4. Hindsight Bias After the product launch, you’re like, “Oh, I *knew* that feature would be a hit... even though I almost cut it three times.” 5. Self-Serving Bias If the product succeeds, it’s because of your brilliant strategy. If it fails, it’s because the dev team didn’t “understand the vision.” 6. Dunning-Kruger Effect After one sprint, you’re pretty sure you could code the whole app yourself... even though you don’t even have a GitHub account. 7. Fundamental Attribution Error When sales miss their targets, it’s because they’re lazy. When you miss a deadline, it’s because the requirements weren’t clear. 8. Ingroup Bias The product team’s ideas are always superior—especially when you’re presenting them as your own in the leadership meeting. 9. Optimism Bias “This release is going to be a walk in the park!”—you say, knowing deep down that you’re going to be pulling an all-nighter on launch day. 10. Sunk Cost Fallacy You keep pushing a doomed feature because “we’ve already spent too much time on this to quit now!”. 11. Overconfidence Bias You assure everyone the integration will take “two weeks, max.” Three months later, you’re still “confident” it’ll be done soon. 12. Negativity Bias That one piece of negative feedback keeping you up at night, while all positive comments gather digital dust. 13. Bandwagon Effect “Everyone’s adding AI to their product! We should too!”—even though you’re still not sure what AI actually stands for. 14. Framing Effect You rephrase “cutting features” as “prioritizing core functionality,” and suddenly everyone’s on board. 15. Loss Aversion You’d rather keep a broken feature than remove it, because, well, what if someone actually *likes* it? 16. Recency Bias The last customer demo went well, so you decide the whole product is ready for launch, ignoring that crash from two minutes ago. 17. Survivorship Bias You point to your one successful product as proof your strategy works, conveniently forgetting the five that didn’t make it. 18. Gambler’s Fallacy “We’ve had three successful sprints in a row—there’s no way this one can go wrong!” Spoiler: It can, and it will. This can save your product, team and career.

I’ve deleted my entire backlog. Literally gone. All tickets and issues, bye bye. I do it (almost) every quarter. Jira tickets. Linear issues. To-do items. I used to do this with some teams. Talk about temporary chaos. We did it over summer and winter. Press delete, woosh, awesome feeling. You might be thinking “that’s insane, that’s my roadmap”. Let’s be honest... How often do you end up with an endless backlog of stuff that just drag along from one roadmap to the other? How often do you have issues that got in and out of a sprint, and just linger? How often have tickets been on boards and nobody even remembers where they came from? Go to your backlog right now. I bet you can spot a few.. That’s why summer and winter cleaning matters. It’s a do over. “But there is important stuff there.. if I delete it, we’ll forget the requirements.” First: No, there isn’t. If it was important, you would’ve done it by now. Second: if it is important, it will come back again. That’s how you know you need to tackle it. Third: the same way you figured it out the first time, you'll figure it out again. Chill.. I’ve observed a few things from teams with heavy backlogs:  1. they're usually slower and less productive.  2. PMs spend the most time writing tickets with less customer-facing time.  3. there's less clarity about strategy.  4. there's a larger % of roadmap with “past stuff”. Less forward thinking. Backlog cleaning helped these teams clear their minds, focus, rethink what customer want, reframe competitive offering. Try it out. Redesign your next year, this quarter. PS: if you’re skeptical, take a screenshot or export the issues. Then delete everything and if you’re freaking out, just import them back or recreate them. I'm looking for tomorrow's Product Managers, and turning them into Fullstacks. How? Through my Membership, join me and hundreds at onemonthpm.com

Here's what I would be obsessively learning if I was a non-technical product manager: - Zapier, how to build workflows and automations, how to connect with other APIs - OpenAI/Anthropic API, how to integrate it with Zapier, how it works and costs - Claude Artifacts, how to build small apps that do stuff on my behalf - Proper prompting, and going deeper on how chaining works - Cutting scopes to ship faster (yes this is a skill), creating your library of "the best in the game to like this" - How AI agents work, the principles behind and experimenting (will write about this) - Automation thinking (also a skill), or how to outsource tasks to agents/bots (also, which agents exist out there that you can use) - New GTM practices, being comfortable with the stack (stuff like Clay, Amplemarket, Listkit, Apollo, 11x, Warmly, RB2B, Champify) - Verticalized/niche influencer marketing strategies & driving/growing communities (ads are dying, long live "advertising") - Fast DIY design, using tools like Canva, freeing yourself from product/marketing designers And yes, all of this matters for a product manager. I'll write more extensively on each, but I have been building my company/products as a solopreneur on top of this stack, and it feels like I have a whole team behind me. The product game is evolving. — If you want to evolve as well, join our Membership at onemonthpm.com lots of ☝️is covered in our live programs. We’re looking for the next Fullstack PMs.

Andre Albuquerque asked if I could speak about Go-To-Market strategies or in my own words "How to sell your average product assumption" at One Month PM - The Fullstack PM Academy. If you have any material I should read before Thursday, please help! Otherwise 👇 Join the Membership to participate: onemonthpm.com/membership

🎉 I just completed the AI Prompt Engineering Nano Bootcamp from One Month PM - The Fullstack PM Academy. The course provided valuable insights into optimizing AI prompts and improving model performance through structured and creative techniques. Thank you Andre Albuquerque, the founder, for opening up this free spot to the community! For anyone interested, check out the upcoming bootcamps—they're a great way to sharpen your skills! 🚀

I’m happy to share that I’ve obtained a new certification: Prototyping Foundations from One Month PM - The Fullstack PM Academy! Thank you Karin Garcia Moreno and Bernardo Domingues for all the insights shared!

I'm happy to share that I received a new certification: Prototyping Foundations from the company One Month PM - The Fullstack PM Academy!

I’m happy to share that I’ve obtained a new certification: Product Manager Foundations from One Month PM - The Fullstack PM Academy! Thank you for amazing course Andre Albuquerque

Sharing product marketing knowledge today with the team at One Month PM - The Fullstack PM Academy! I'll be leading my own masterclass with insights from my experience working with Google AdSense. Thank you Andre Albuquerque and António "Tojal" Rocha for the invite and opportunity to connect with future PMs. Watch my masterclass and others at https://lnkd.in/dyhzrHJ9. #productmarketing

I'm thrilled to announce I'm hosting a Live Masterclass Q&A on Product Management happening on October 24th, 6 PM CET, hosted by One Month PM - The Fullstack PM Academy. Don't miss out! Join the Membership to get access: onemonthpm.com/membership I've been working with virtual assistants and automations for the past 7 years, and I'm excited to share all the knowledge and Insights I've gathered about Product Management with future PMs