This is a personal blog, Hiro's room!


How to define product requirements from many perspectives

Cover Image for How to define product requirements from many perspectives

The main role of product managers is to define product requirements and put them into words as a PRD (About PRD, it is explained in more detail in What is PRD in product management?). In this phase, product managers have to take many perspectives into account, otherwise the product requirements need to be changed over and over again during development or even after finishing it, but how? Here, I devided into five groups the requirements you should consider when it comes to product management. Moreover, not only considering various requirements but also putting these into words eventually is essential because the main communication with the stakeholders is basically performed through PRDs.

Business Requirements

  • Goal - What you want to achieve by the product
  • Summary of Proposal - How you simply describe the product
  • Scope of Work - What should be scoped and not scoped
  • Risk - What can affect to user experience, development or costs
  • Dependency - What has internal and external relationships

Project Requirements

  • Schedule - When you want to release the product
  • Phase - Which phase you are going through considering the future plans
  • Test Plan - What kind of bugs can be accepted
  • Project Member - How many people will join the product team

Technology Requirements

  • Use Cases - What personas can do with the product
  • Features - What features are necessary to achieve the use cases

Performance Requirements

  • Response Speed - How fast a response should be by a click or tap
  • Access Load - How much accesses can be responded

Design Requirements

  • Wireframes - How the screens simply look like in skeletal black and white diagrams
  • User Flow - How the path users follow on the product to do the task look like
  • Localization - Which languages the product has
  • Accessibility - How the product can be disability-friendly
# product management
Copy Link to Share

Related Posts

How does Google set goals and achieve them with OKRs?

An Obejective and Key Results (OKRs) framework is an effective goal-setting tool for communicating what you want to accomplish and how you will accomplish it. It is well known as an big contributor to Google's success. OKRs have recently gained popularity among tech companies from Silicon Valley.

# teamwork# leadership

The power of data without compromising privacy by Data Clean Room

In today's digital world, companies have access to more customer data than ever before. While this data can be incredibly valuable for understanding customer behavior, improving products and services, and driving business growth, it also raises significant privacy concerns.

# data# privacy# marketing

What is Agile Software Development?

Agile Software Development - also referred simply as Agile - is an iterative approach to focus on continuous releases and incorporating customer feedback with every iteration. In short, Agile is important for software development to delight customers and be more competitive.

# engineering# teamwork

Create your product strategy before jumping into roadmap and backlog

Before diving into the nitty-gritty of building your product roadmap or developing new features, your product strategy should be defined to make the right decisions in the ever-changing world. A product strategy is a high-level description of what the business wants to achieve with its product and how to achieve it.

# product management# teamwork