zhukang
1c7abd81d1
- 310 registry:skill items, 1528 files, 7 categories (hub tags) - registry.json generated by @kortix/registry buildRegistry - nested SKILL.md in sn-da-* renamed SUBSKILL.md (no phantom skills) - provenance + licenses: SOURCES.md
26 KiB
Writing Product Requirement Documents - All Guest Insights
14 sources, 38 insights
Bob Baxley
Insight: A successful design brief provides clear constraints and context while leaving the visual solution entirely to the designer.
Tactical advice:
- Focus the brief on the future state you want to create rather than the specific features to build.
- Wait as long as possible to draw pictures to ensure the problem space is fully defined first.
Source: 35 years of product design wisdom from Apple, Disney, Pinterest, and beyond | Bob Baxley @ 01:01:53
Insight: Prematurely creating high-fidelity prototypes can anchor a team to a suboptimal solution before they have fully explored the problem space.
Tactical advice:
- Wait as long as possible to create a prototype or draw a picture of your idea.
- Prioritize verbal and conceptual alignment on the desired outcome before moving to visual design.
Source: 35 years of product design wisdom from Apple, Disney, Pinterest, and beyond | Bob Baxley @ 01:09:04
Claire Vo
Insight: Leveraging AI to automate the synthesis and formatting of requirements allows PMs to pivot their time toward high-level strategy and alignment.
Tactical advice:
- Experiment with AI tools to handle the clerical parts of product requirement generation.
- Focus on refining the strategic 'why' of a product while letting AI manage the functional 'what.'
- Stay ahead of the curve by identifying which PM skills will be complemented or replaced by AI shifts.
Source: Bending the universe in your favor | Claire Vo (LaunchDarkly, Color, Optimizely, ChatPRD) @ 00:54:06
Jenny Wen
"We used to go off and make this two-year, five-year, 10-year vision even. Now it becomes a vision that's three to six months out, and isn't necessarily creating this beautiful deck, sometimes just creating a prototype that points people in the right direction."
Insight: The speed of AI-driven engineering requires design to shift from static, long-term theoretical planning to short-term functional prototyping and real-time execution support.
Tactical advice:
- Replace multi-year vision decks with three-to-six-month directional prototypes.
- Reduce time spent on high-fidelity mocks to prioritize supporting engineers with 'last mile' implementation and polish.
- Test functional prototypes with actual models to account for the non-deterministic nature of AI behavior.
Source: Jenny Wen @ 00:04:59
Julie Zhuo
Insight:
Source: Julie Zhuo on accelerating your career, impostor syndrome, writing, building product sense, using intuition vs. data, hiring designers, and moving into management @ 00:54:52
Katie Dill
Insight: Physical proximity and shared goals between disciplines prevent silos and ensure design intent is maintained during execution.
Tactical advice:
- Seat designers, engineers, and product managers together to facilitate spontaneous 'shoulder-look' feedback.
- Establish shared goals across disciplines to ensure the entire team is aligned on the same outcome.
- Balance cross-disciplinary pods with regular functional meetups to foster community and maintain craft excellence.
Source: Building beautiful products with Stripe’s Head of Design | Katie Dill (Stripe, Airbnb, Lyft) @ 01:01:59
Kevin Yien
Insight: The role of a product manager is to maximize the team's output by providing the necessary direction and decision-making that builders may not have the capacity to handle alone.
Tactical advice:
- Step in to define constraints when a product space becomes too complex for builders to manage alone.
- Delegate PM activities to engineers or designers when they are the target customers for the product.
- Focus on minimizing the loss of value when converting team effort into customer benefits.
Source: Unorthodox PM wisdom: Automating user insights, unselling job candidates, logging every decision, more | Kevin Yien (Stripe, Square, Mutiny) @ 00:19:10
Lenny Rachitsky
Insight: Continuously returning to the defined problem and success metrics serves as a filter to reject features that don't directly serve the project's goal.
Tactical advice:
- Keep coming back to the original problem statement during every phase of development.
- Evaluate every proposed feature by asking if it increases the likelihood of hitting your defined success metric.
- Cut any scope that does not directly contribute to solving the core problem.
Source: A Three-Step Framework For Solving Problems 👌
"Problem-oriented: They crystallize the problem being solved in a few strong sentences—ideally near the top of the document—to focus the brainpower of every teammate in the same direction."
Insight: An effective PRD centers on a clearly defined problem and specific success metrics to ensure the team remains aligned on the 'why' before debating the 'how'.
Tactical advice:
- Crystallize the problem being solved in a few strong sentences near the top of the document.
- Define super-specifically what success looks like to help the team make tradeoff decisions throughout the project.
- Include a clear proposed timeline for review and shipping to maintain urgency and prevent scope explosion.
Source: Examples and templates of 1-Pagers and PRDs
"Design crits are intended to be very generative, and are explicitly not about making decisions. Designers share a file (often on FigJam), and we spend 10 minutes heads-down silently leaving stickies and comments to give feedback on the designs before discussing live."
Insight: Separating generative feedback from decision-making ensures more diverse input and prevents the loudest voices from prematurely narrowing the creative process.
Tactical advice:
- Dedicate at least 5-10 minutes of every critique for silent, written feedback before speaking.
- Structure crits around technology pillars or product areas with regular standing slots.
- Invite 'observers' from across the company to participate and understand the design culture.
Source: How Figma builds product
"A week before a product review, Snowflake product managers share a six-page document for the topic with meeting attendees that outlines the customer problem, proposed solution, risks, and other key data points around a specific product investment."
Insight: Use a comprehensive six-page narrative to facilitate deep asynchronous feedback from leadership before the actual review meeting.
Tactical advice:
- Distribute the review document to attendees at least one week before the meeting.
- Include an executive summary, problem statement, use cases, risks, and an FAQ section.
- Invite leadership to provide feedback via comments directly in the document before the session.
Source: How Snowflake builds product
"A reminder of how valuable it is to keep these to one page, at least to start"
Insight: Keeping initial project documents to a single page forces clarity and ensures the team stays focused on core problems and goals before increasing complexity.
Tactical advice:
- Keep initial PRDs or initiative documents to a single page to maintain focus.
- Include a "Non-Goals" section to clearly establish project boundaries.
- Use a problem statement framework to anchor the project's purpose.
Source: My favorite product management templates
Insight: High-performing PM and design partnerships rely on the PM acting as a facilitator who trusts design expertise and aligns the team through shared context rather than control.
Tactical advice:
- Trust the designer’s expertise in creative schedules and the need for uninterrupted maker-time.
- Act as a conductor by clarifying context and facilitating communication rather than dictating every detail.
- Ensure team alignment on the core problems, mission, and goals to leverage each expert's unique superpowers.
Source: The PM 🤝 Design Partnership
Insight: To improve a product spec, audit it for clarity of the problem statement, concrete feature details, and overall readability.
Tactical advice:
- Study 1-Pagers from past successful projects at your company to understand what 'great' looks like in your specific context.
- Verify that the document provides 'just enough' direction without eliminating the opportunity for teammates to find better solutions.
- Clean up formatting and resolve comments regularly to ensure the document remains readable and usable.
Source: Examples and templates of 1-Pagers and PRDs
"In the end, if you want this document to be used, it needs to be readable. So keep it brief (that’s why I like the term 1-Pager), clean up formatting and comments anytime it starts to get messy, and put additional context into an appendix at the end."
Insight: Choose a template that enforces brevity and focuses on essential structural elements like problem statements and success criteria rather than exhaustive documentation.
Tactical advice:
- Select a '1-Pager' style template to ensure the document remains brief enough for the team to actually read and use.
- Use templates that include 'Non-Goals' or 'Acceptance Tests' to explicitly define project boundaries and technical requirements.
- For hardware products, utilize specialized templates that account for the unique constraints of physical manufacturing.
Source: Examples and templates of 1-Pagers and PRDs
"There’s a fine line between articulating the important details of a project spec and spending three pages explaining one button. This annoying habit can apply to both the beginning of a project, telling designers and engineers exactly how a feature needs to work, and also at the end when you spec out each feature for days."
Insight: Over-specifying features stifles the creative input of designers and engineers and can make the team feel micromanaged.
Tactical advice:
- Prioritize verbal conversation over exhaustive written documentation.
- Check if teammates are actually using your documents or if they are feeling micromanaged by the length of your specs.
- Narrow in on which nuances actually require written clarification versus those that are better handled via discussion.
Source: Five habits of highly annoying product managers
"Instead of suggesting something will be quick, ask, “What would need to be true for this to be doable in the next x days?” It’s totally OK to suggest something will be quick occasionally, but if you’re finding that the majority of your asks should take “just” a few hours, you’re probably annoying the sh*t out of your team."
Insight: Assuming technical tasks are "quick" undermines the expertise of your engineers and risks burning them out on unrealistic promises.
Tactical advice:
- Eliminate the word "just" when describing the expected duration of an engineering task.
- Frame requests by asking what resources or conditions are needed to meet a specific timeline.
- Listen for engineering pushback on estimates as a signal that you are underestimating technical complexity.
Source: Five habits of highly annoying product managers
"Describe what you want in human language, get an 80% complete draft, refine it, and then ship. This is already happening with tools like ChatPRD."
Insight: AI can automate the bulk of technical writing tasks, allowing PMs to focus their energy on the final refinement and nuance of product specs.
Tactical advice:
- Use natural language descriptions to generate 80% complete PRD drafts using AI tools.
- Refine AI-generated specs to ensure they include necessary nuance and team context.
- Explore specialized tools like ChatPRD or WriteMyPRD for faster feature documentation.
Source: How AI will impact product management
Insight: Maintaining product simplicity and delight remains a uniquely human responsibility and a key competitive advantage in an AI-commoditized market.
Tactical advice:
- Personally review designs and prototypes to ensure the user experience is cohesive and simple.
- Use AI to identify common UX challenges and verify that designs follow industry best practices.
- Leverage human judgment to refine AI suggestions into truly delightful product experiences.
Source: How AI will impact product management
Insight: Use AI to overcome the 'blank page' problem by generating initial drafts of technical documentation and user requirements.
Tactical advice:
- Prompt the AI to create a v1 PRD or Jira ticket based on a feature idea.
- Use the tool to write specific user stories and acceptance criteria.
- Identify potential drag metrics that could impact your feature's success.
Source: How to use ChatGPT in your PM work
Insight: AI platforms designed for product management can transform disorganized notes into standardized, professional documentation that integrates directly with development workflows.
Tactical advice:
- Convert messy initial notes into clear, structured PRDs automatically.
- Connect documentation to Linear to break down work into actionable sub-issues.
- Mention AI agents in comments to get immediate feedback or improve task descriptions.
Source: Part 2 of how to get the most out of your product pass—and welcome, Stripe Atlas, to the bundle!
"I know it can be hard to add yet another person to the room, but the benefit outweighs the risk. A good example is during planning. I have known plenty of PMs that were eager to rush ahead with a list of features they thought the team should build. However, I have seen these same PMs sing a very different tune after including designers in the planning process."
Insight: Including designers in early product planning avoids the inefficiencies of waterfall handoffs and leverages their ability to catalyze innovation and advocate for the user.
Tactical advice:
- Bring designers into the planning process early to gain a skillful facilitator, user advocate, and storyteller.
- Avoid waterfall handoffs by having designers inform conversations with a salient voice of the user from the start.
- Use visual prototypes and creative ideas during planning to catalyze conversations and drive more thoughtful solutions.
Source: The PM 🤝 Design Partnership
Insight: A clear problem statement must be concise, focused on a single need, and strictly agnostic of any potential solutions.
Tactical advice:
- Aim for a single sentence to describe the actual problem.
- Reference a user or business need that is currently unfulfilled.
- List examples of what specific problems the project is not intended to solve.
Source: A Three-Step Framework For Solving Problems 👌
Insight: A structured one-pager forces teams to document the problem, evidence, and success criteria before diving into design or engineering.
Tactical advice:
- Complete a 1-pager answering description, problem, why, success, audience, and what.
- Assign a single person, usually the PM, to take the first pass at the document.
- Use the 'Why' section to collect evidence that justifies the team's time investment.
Source: A Three-Step Framework For Solving Problems 👌
Insight: Modern product managers must leverage AI and automation to handle increasing output expectations with fewer resources.
Tactical advice:
- Use AI tools to get more done with fewer management layers and resources.
- Hone productivity practices that provide leverage beyond what is traditionally expected of individual contributors.
Source: Product manager is an unfair role. So work unfairly.
Insight: Aligning the team on a precise problem statement is the most critical step to ensure efficient execution and avoid project churn.
Tactical advice:
- Use a one-pager template to crystallize the problem and opportunity for all stakeholders.
- Apply the situation-complication-resolution framework to communicate the project's story.
- Utilize the jobs-to-be-done framework to ensure solutions address actual customer needs.
Source: What Seven Years at Airbnb Taught Me About Building a Business
Insight: Technical knowledge allows PMs to account for implementation constraints and architectural trade-offs during the planning and design phases of product development.
Tactical advice:
- Ask engineers about the database requirements for new features early in the planning stage to avoid late-stage storage issues.
- Factor in time for testing phases like integration and end-to-end tests when setting project timelines.
- Define the specific data needed from API endpoints within your requirements to ensure technical feasibility.
Source: Become a more technical product manager
Insight: High-fidelity interactive prototypes drive better discovery conversations and help teams identify technical edge cases far faster than static text or wireframes.
Tactical advice:
- Use tools like v0 or Bolt to build interactive flows that can be demonstrated during discovery.
- Focus prototyping efforts on specific elements being tested to keep discussions focused.
- Maintain a repository of reusable components to quickly assemble interactive mocks for new projects.
Source: How to get your entire team prototyping with AI
Maggie Crowley
Insight:
Source: Mastering product strategy and growing as a PM | Maggie Crowley (Toast, Drift, Tripadvisor) @ 00:49:52
Melanie Perkins
"So we have this concept of chaos to clarity and every idea starts in the chaos side, and then you have to work all the way to the other side, which is clarity. And so chaos can be an idea, it can be a problem, it can be a philosophy or a belief."
Insight: Transform amorphous concepts into actionable projects by systematically moving them from the 'chaos' of an idea to the 'clarity' of a documented plan.
Tactical advice:
- Add clarity to every abstract idea by forcing yourself to write it down as the very first step.
- Develop a visual vision deck for every new project to make the intended outcome visible to the team.
- Iterate through designs and prototypes to refine the concept before seeking mastery or total answers.
Source: The woman behind Canva shares how she built a $42B company from nothing | Melanie Perkins @ 00:11:49
Nickey Skarstad
Insight: Analyze the downstream effects of optimizing for immediate conversion to prevent creating a low-quality ecosystem that hurts user behavior in the long run.
Tactical advice:
- Look beyond immediate conversion rates to see how changes affect user success days or weeks later.
- Measure the emotional impact of early wins, as these are critical motivators for long-term retention.
- Evaluate if 'success' at the start of a funnel actually translates to a sustainable behavior later in the journey.
Source: Nickey Skarstad (Airbnb, Etsy, Shopify, Duolingo) on translating vision into goals, operationalizing product quality, second-order decisions, brainstorming, influence, and much more @ 00:42:29
Ryan Singer
"What we need to do in a shaping session is we come out with some kind of diagram where engineers, product and design, they're saying, "We understand that." So the first thing is we are not going to start something unless we can see the end from the beginning."
Insight: Use intense shaping sessions with engineering, product, and design to create a shared, concrete understanding of a project's boundaries before development begins.
Tactical advice:
- Gather product, design, and senior engineering leads for short, high-intensity collaborative sessions.
- Create diagrams that represent the core concept without getting bogged down in high-fidelity details.
- Verify technical feasibility early to avoid drastic changes in cost or time during the build.
Source: A better way to plan, build, and ship products | Ryan Singer (creator of “Shape Up,” early employee at 37signals) @ 00:33:19
Insight: Successful projects require aggressive sharpening of ideas into a specific, bounded concept to prevent waste and ensure the team reaches the finish line.
Tactical advice:
- Narrow down fuzzy requests into specific problems that can be solved within a fixed cycle.
- Ensure the project concept is bounded so the team can see the end from the beginning.
- Filter out "big things" that haven't been distilled into actionable, small-scale work.
Source: A better way to plan, build, and ship products | Ryan Singer (creator of “Shape Up,” early employee at 37signals) @ 00:19:10
Insight: Empower builders by handing off a shaped concept that defines the boundaries but leaves the specific implementation details to the team.
Tactical advice:
- Provide a shaped diagram rather than a long, rigid PRD to allow for builder ownership.
- Allow the build team to translate the concept into their own implementation tasks.
- Ensure the team understands the "end from the beginning" during the project handoff.
Source: A better way to plan, build, and ship products | Ryan Singer (creator of “Shape Up,” early employee at 37signals) @ 01:04:22
Scott Belsky
Insight: Superior products result from collapsing the artificial boundaries between functions so the entire team can focus on the user's perception of the technology.
Tactical advice:
- Break down artificial and constraining boundaries between product, design, and engineering.
- Align the entire cross-functional team around shipping better end-to-end user experiences.
- Review designs across the entire company to raise the bar for the total experience being shipped.
Source: Lessons on building product sense, navigating AI, optimizing the first mile, and making it through the messy middle | Scott Belsky (Adobe, Behance) @ 00:35:18
Shweta Shriva
Insight:
Source: Product lessons from Waymo | Shweta Shrivastava (Waymo, Amazon, Cisco) @ 00:25:40
Vijay
"And if you're shipping features that quick leads, you don't have time to stop and think, where does this go, and how does this fit into our overall system architecture? And what started to happen was that we were hitting diminishing returns with some of these features. And not considering the holistic design and consistency meant the reach of every feature was low."
Insight: High-velocity feature shipping eventually hits a wall of diminishing returns unless the product is anchored by a consistent system architecture and design building blocks.
Tactical advice:
- Identify the minimal number of core building blocks required for your product's system architecture.
- Pivot to a design-led initiative to ensure consistency once high-velocity shipping begins to fragment the user experience.
- Establish design as a key differentiator to improve feature discoverability and reach across the platform.
Source: An inside look at Mixpanel’s product journey | Vijay Iyengar (Head of Product) @ 00:12:09
Insight: Traditional estimation should be replaced by appetite-based scoping to optimize for speed and clarity in execution.
Tactical advice:
- Define the 'appetite' or time box for a project before deciding on the specific features to build.
- Explore how project requirements change when given different time constraints (e.g., two weeks versus two months).
- Focus on the problems you are trying to solve rather than precise hour-based technical estimates.
Source: An inside look at Mixpanel’s product journey | Vijay Iyengar (Head of Product) @ 00:26:51