While frameworks like RICE appear scientific, their inputs are highly subjective. Their primary value isn't for making decisions, but for providing a seemingly objective, data-driven justification to decline stakeholder or management feature requests that don't align with the current strategy.
Instead of relying on subjective scores from frameworks like RICE, use a simple "What and Why" statement for each feature. This narrative approach, which includes a "Why now?" justification, provides clearer strategic alignment and is more persuasive for stakeholders than an abstract number.
A product manager's role extends beyond development. The customer stories and problem statements gathered during discovery are powerful sales assets. Packaging these insights and sharing them with the sales team helps them communicate the product's value more effectively.
To advance in product management, move beyond only solving customer problems. Frame your work in the language of business impact. Articulating how features will affect corporate goals and key metrics is essential for gaining buy-in from senior leadership and progressing your career.
PMs who transition from other professions bring life skills that help them understand diverse perspectives. This real-world experience builds more empathy than academic product management programs, which primarily teach frameworks and a common language.
When a non-designer provides a polished mockup, designers often feel constrained to only refine it. Presenting intentionally rough sketches signals you're communicating an idea's intent, not a proposed execution, freeing designers to reimagine the solution and collaborate more creatively.
At a massive scale like Twitter's, even innocuous features can be weaponized in unforeseen ways. A formal Product Requirements Document (PRD) process, including reviews with teams like Trust & Safety, is vital for identifying and mitigating potential misuse before development begins.