💡

InsightHunt

Hunt the Insights

M

Maggie Crowley

Vice President of Product

Toast

🚀 Career & Leadership (1)🎯 Product Strategy (1)⚡ Execution (1)

Key Takeaways

  • 1.Great PMs simplify complexity: find the one thing that matters and stick with it.
  • 2.Follow up on results: check metrics 2 weeks, 1 month, and 6 months post-launch.
  • 3."Carry the water": PMs must do the unglamorous work (QA, support, sales calls) to fill gaps.
  • 4.A product strategy doc is primarily for the PM to ensure their own logic is sound.
  • 5.When writing specs/PRDs, the most important question is "Why does this matter NOW?"
  • 6.Being overly "data-driven" can be a red flag for a lack of product intuition.
  • 7.Avoid rewrites/redesigns; they almost always take longer than expected and fail.

Methodologies(3)

🚀 Career & Leadership

Three specific behaviors that define top-tier PMs: the ability to cut through noise to find the single priority, the discipline to close the loop on outcomes, and the willingness to do whatever unglamorous work is needed to ship.

Core Principles

  • 1.Simplify relentlessly: Identify the single most important task amidst chaos and stick to it until completion.
  • 2.Follow up on results: Set calendar reminders (2 weeks, 1 month, 6 months) to check if the feature actually moved the metric, and report back.
  • 3.Carry the water: Adopt a "no job is beneath me" attitude. Do QA, write copy, hop on sales calls, or manage projects if that's what is needed to ship.

"If you ever find yourself saying something like, 'that's not my job,' that's probably a thing you should do."

#high-performance#triad#career
View Deep Dive →
🎯 Product Strategy

A comprehensive document structure that forces the PM to rigorously assess the landscape and internal state before proposing solutions. It serves as 'homework' for the PM to ensure they aren't missing critical context.

Core Principles

  • 1.Landscape & Context: Mission, goals, competitive SWOT, and market POV.
  • 2.Honest Accounting: What is the brutal truth about the current product state? User feedback, tech debt, and what isn't working.
  • 3.Opportunity & Logic: Where can we win? What must be true for this to work? Then, and only then, propose the solution (max 3 bullets) and plan.
  • +1 more...

"I put in... an honest accounting of the current state of your product... What works, what doesn't work? What are your customers saying? ... What are your technical hurdles?"

#'honest#accounting'#strategy
View Deep Dive →
The 'Why Now' One-Pager

by Maggie Crowley

⚡ Execution

A simplified spec document that prioritizes the context and timing over the feature list. It centers the team around the problem rather than the solution details.

Core Principles

  • 1.Start with Context: Define the background clearly.
  • 2.The Two Critical Whys: Explicitly answer 'Why does this problem matter?' AND 'Why does it matter NOW?' (Urgency).
  • 3.Record Decisions: Use the doc to log decisions made and what is strictly out of scope.
  • +1 more...

"What is the problem, why does it matter, and why does it matter now?"

#one-pager#execution#process
View Deep Dive →