feat: update articles

Author: wx-chevalier

99~参考资料/2023~Produce Compass~系列文章存档/2024.0309~How to Write a Product Requirements Document? The Best PRD Template.md

@@ -0,0 +1,48 @@
+> [The article](https://www.productcompass.pm/p/prd-template) you've linked to, "How to Write a Product Requirements Document? The Best PRD Template," by Paweł Huryn, provides a comprehensive guide on creating a Product Requirements Document (PRD). Here are the key points and insights from the article:
+>
+> 1. **Why We Need a PRD**:
+>
+>    - The PRD is not about documenting "requirements" but rather about providing strategic context and focusing on outcomes.
+>    - It's essential for larger initiatives that span over several weeks and need to be communicated effectively to stakeholders.
+>
+> 2. **What’s Inside a PRD**:
+>
+>    - **Document Overview**: A brief summary for those who might not read the entire document.
+>    - **Stakeholders**: Key individuals involved, such as the Product Manager, Design Lead, and Lead Engineer.
+>    - **Communication Channels**: Links to Slack or Teams channels for interested parties.
+>    - **Context**: Explanation of the initiative, why it's being built now, and any recent changes or possibilities.
+>    - **Objective**: A clear, SMART (Specific, Measurable, Achievable, Relevant, Time-bound) objective that aligns with the product strategy.
+>    - **Success Criteria**: How success will be measured.
+>    - **Target Users**: Who the product is being built for and their needs.
+>    - **Constraints**: Any limitations such as geographic, language, or regulatory factors.
+>    - **Customer Jobs/Needs**: Focus areas for customer needs and how the product will address them.
+>    - **Competitive Advantage**: How the product will solve problems better than competitors.
+>    - **UX/Prototypes**: Overview of the user experience, including user flow diagrams and links to prototypes.
+>    - **Key Features**: List of key features with brief descriptions.
+>    - **Technology**: A high-level overview of the technology used, if relevant.
+>    - **Assumptions**: Assumptions about value, usability, viability, and feasibility, and how they've been validated.
+>    - **Risks**: Accepted risks and mitigation strategies.
+>    - **Timeline**: An estimate of the duration and what might be included in the first version.
+>
+> 3. **When to Write a PRD**:
+>
+>    - The PRD is an evolving workspace that aggregates key information and supports internal communication. It's particularly useful for documenting product discovery and facilitating alignment within the organization.
+>
+> 4. **Common Mistakes**:
+>
+>    - Avoid the waterfall approach where detailed specifications are documented in a heavy, rigid manner.
+>    - Keep the PRD concise and avoid overloading it with too much information.
+>    - Remember that the PRD should support empowered teams, not hinder them with excessive process.
+>
+> 5. **PRD Templates**:
+>
+>    - The article mentions that PRD templates are available in Notion and Google Docs, but the specific templates are locked for subscribers.
+>
+> 6. **Importance of Alignment**:
+>
+>    - The PRD should help in aligning the team and stakeholders around a common understanding of the initiative, its objectives, and its expected outcomes.
+>
+> 7. **Inspiration from Reed Hastings**:
+>    - The article references Reed Hastings' philosophy from his book "No Rules Rules," emphasizing the importance of giving employees freedom and avoiding overly rigid processes.
+>
+> The article emphasizes that the PRD should be a living document that evolves with the project, facilitating communication and alignment rather than serving as a static, detailed specification. It's a tool to support product discovery and implementation, not a constraint.

99~参考资料/2023~Produce Compass~系列文章存档/2024.0309~PRD Template (Product Requirements Document).pdf

@@ -0,0 +1,40 @@
+> [The article](https://www.productcompass.pm/p/product-model-first-principles-transformed-cagan) you've linked to is a detailed exploration of product model first principles as outlined in Marty Cagan's book "TRANSFORMED." The author, Paweł Huryn, shares insights and thoughts on the principles that can help product managers make better decisions, build better products, and enjoy their work. Here are some key points from the article:
+>
+> 1. **Product Team Principles**:
+>
+>    - Empowerment: Teams should be given problems to solve, not solutions to build, and be held accountable for the results.
+>    - Desired Outcomes: Teams should focus on customer problems and company problems with clear measures of success (desired outcomes).
+>    - Team Objectives: These consist of a significant problem and clear measures of success. They align with Objectives and Key Results (OKRs), where the objective is inspirational and the key results are the desired outcomes.
+>
+> 2. **Product Strategy Principles**:
+>
+>    - Product Vision: This is the future you are trying to create and how it will improve the lives of your customers. It keeps teams inspired and excited.
+>    - Product Strategy: This describes how you plan to accomplish the product vision while meeting the needs of the business. It involves deciding which problems are most important to solve.
+>    - Focus and Trade-offs: Strategy involves saying no to many good ideas to focus on the most important ones. This creates a clear direction and makes the strategy difficult to copy.
+>
+> 3. **Insights and Transparency**:
+>
+>    - Insights are crucial for driving strategy and can come from analyzing data, talking to customers, new technologies, and the broader industry.
+>    - Transparency is important for gaining buy-in from stakeholders and avoiding frustration. It involves being clear about data, reasoning behind choices, and strategic decisions.
+>
+> 4. **Collaboration and Product Discovery**:
+>
+>    - Collaboration does not mean consensus or democracy. Team members should feel free to challenge ideas and explore diverse perspectives.
+>    - Product discovery is a team effort, involving product managers, designers, and engineers working together to come up with ideas and test them.
+>
+> 5. **Value Proposition**:
+>
+>    - The value proposition is distinct from product strategy and applies to product vision, strategy, and discovery. It's a theory about why the product will be valuable to people and is tested at every level.
+>
+> 6. **Strategic Iteration**:
+>
+>    - Strategy is not a one-time event but an ongoing process that involves many iterations. Insights from product discovery can drive the next iteration of the product strategy.
+>
+> 7. **Leadership and Decision-Making**:
+>    - Leaders should be responsible for both coming up with solutions to problems and building and delivering those solutions. They should also be transparent about their strategic choices and why they made them.
+>
+> Paweł Huryn also includes a Q&A with Marty Cagan, where they discuss the relationship between product strategy and team objectives, the role of insights in driving strategy, and the importance of a holistic approach to product strategy.
+>
+> The article concludes by emphasizing the importance of these first principles in guiding product management decisions and practices. The next part of the series will discuss principles related to product discovery, delivery, and culture.
+
+# Product Model First Principles: Product Team and Product Strategy In Depth