It frustrates me to see how product managers have complicated the simple process of creating a roadmap Believe it or not, a product roadmap is nothing more than a 𝘵𝘰-𝘥𝘰 𝘭𝘪𝘴𝘵, where the items are sequenced based on some logic. For me, creating a roadmap is a simple

Carl Vellotti 🥞 dont ask "how long will this take", instead say "we have X weeks, what can you build in this time?" empower engineers instead of just making them execution slaves

Jackie Bavaro Carl Vellotti 🥞 99% the problem is that time is being wasted on estimating an unknown. Decompose the effort into work that can be completed in a day or two, drive out uncertainty, and stop wasting time on estimates. MinimumCD.org

I know this may make me look stupid to ask, but how do I make this table look better? I do not like the space in the upper left. But, when I move Routines lower, it looks weird, too. #help #tables

When I started learning Product Management, different techniques seemed to be isolated islands. So today: How to combine OKRs with Scrum? Before we dive in, let's note the similarities: - "Radical Focus," which aligns with one of Scrum Values - Emphasis on transparency, which

The PRD is not a static document. It's a living, breathing reflection of the team's progress. The goal of the Product Requirements Document (PRD) is clarity. So at each and every step, aim to increase the resolution of the image. 𝗦𝘁𝗮𝗴𝗲 𝟭 - 𝗣𝗹𝗮𝗻𝗻𝗶𝗻𝗴 For big rocks

⚛️ How to structure and organize a React application ( ) ↓

In 4 minutes, Kurt Vonnegut explained stories better than anyone I’ve ever heard. “The shape of the curve is what matters. Not their origins.” He plots stories on 2 axes: X: Time Y: Good fortune / ill fortune He goes on to say, “Somebody gets into trouble, then gets out of

😅

"Agile" is not a methodology. Read agilemanifesto.org. The only practice that's listed is the retro (i.e., continuous improvement). You can invent a methodology that adheres to the values and principles, but if that's not continuously changing/improving, you're not Agile.

Strategy ⬇️ OKRs ⬇️ Problem statements ⬇️ Solution hypotheses ⬇️ Experiments ⬇️ Evidence ⬇️ Iteration / course correction ⬇️ Agility ⬇️ Customer value

Verifying Estimates

Ambition

Prototypes are the most powerful way to validate product ideas. Here's a complete breakdown of 10 ways to validate your prototypes + save yourself from wasting weeks of time:

Interruption Hell

“Asking product teams to deliver specific features by specific dates is like asking a sales rep to close a specific deal on a specific date or a marketing team to get a set number of leads from a specific campaign.” - Teresa Torres bit.ly/44Xu0kK #prodmgmt #ux

What Product-centric companies are not: - Product Management-led - Product Managers are the boss - Where product makes all the calls - Something that only engineering and product do - Doing 12+ week long discoveries - Do only what our customers want antmurphy.me/newsletter/wha…

Don't confuse the work behind the work with the actual work. - OKRs - Specs - Meetings - Strategy docs - Product review decks These are all intermediate steps that you might take to achieve your end goal. But remember this: Your job is not to craft the perfect OKR, internal

Designers only "hand-off" designs to engineers to build on waterfall teams. On agile teams, it's a constant back and forth between the two, like passing a hot potato. (PMs often help with the passing.)