Product Manager and MRD

The difference between MRD and BRD

BRD: What is the benefit of doing so and what is the benefit?

The MRD definition: After BRD clear that this is worth doing, describe what should be done and explain why. If BRD is a proposition, then the MRD wants us to use arguments to support BRD, and to demonstrate how we are going to get BRD business goals. It is through a series of analyses that we come up with a set of methods that we think are best suited to do this and guide the implementation of the document.

Second, MRD reading object

MRD reporting target: Colleagues at all levels of future participation in the product, including the product manager themselves.

①MRD is the perfect product birth Analysis description document.

② after a period of time, the product of various derivative documents, product basis, team judgment, should refer to MRD.

③ Product participants understand the various backgrounds, data, and methods of the product.

Iii. The main contents of MRD

1. Document Description

Document Description: Document basic information, document modification record, document purpose, document summary.

Document BASIC information: Company name, product name, document creation date, creator, creator contact, department, position.

Document modification Record: date, version, modified person, modification record, approver.

Document purpose: To describe the product market, user, product planning, core objectives, product roadmap, project planning and so on.

Document Summary: Document description, Market description, User description, product description.

2. Market explanation

Market Description: summary (optional);

Current market problems and opportunities: write as needed-two to three points: product aspects-complex shape, poor user experience, technical aspects-(speech compression technology is immature, foreign search engine for Chinese understanding is not deep); operational aspects-(industrial chain downstream, heavy entities, light line, resulting in the partition of travel agency profits, The user side (the emergence of new requirements, obvious demand);

Target Market Analysis: Market Size, market characteristics, development trends (development evaluation for the next 2-5 years), Time boundary (the duration of the market forecast).

Market Analysis Conclusion: Generally speaking, there will be a comparison of the market business value of the conclusion.

3, User description

User description: Target user group (accurate: age, income, region, education);

Target group characteristics: The main analysis of commonness;

Establish virtual user roles: visualization, common user characteristics, user names, user skills, and product-related user characteristics.

Make user Role cards: Classify users, extract typical roles, and represent target users.

User Scenario Analysis: A demonstration of the scene, the user in time, place, complete the story of something.

User Motivation Summary, User goal Summary (clear substance), analysis of the main factors affecting user use.

Note: Analyze the market from the technical level, insight into the user psychological case analysis. Motivation and goals are inconsistent.

4. Product Description

Product Positioning: What products we use to meet the user or user market, for what users, what to do.

The core goal of the product: To solve the target market, the core needs of the users, and the highest work level.

Product structure: Overall structure, not functional structure. Is the core goal of the product, market positioning, the direct embodiment of product positioning.

The roadmap of the product;

Product Functional Requirements: User registration, message, and so on.

Non-functional requirements: effectiveness, performance, scalability, security, robustness, compatibility, availability, operational requirements, user experience.

Iv. characteristics of excellent MBR

Strong logic (argument, argument, argument);

Visualize something abstract;

Reliable data, rational analysis, subjective and uncertain objectivity;

The wording of the words, concise and clear;

reasonable product schedule analysis;

Attaching importance to non-functional requirements;

Explain the professional terms.