15 Product Management Terms and Concepts Everyone In Tech Should Know

Aakash Mehta | Product Leader
14 Mar 202312:11

Summary

TLDRIn this informative video, Akash, a seasoned product manager and Harvard MBA, introduces 15 key terms essential for product management. He covers concepts from defining product requirements with a PRD to utilizing A/B testing and understanding disruptive innovation. Akash also explains the significance of MVPs, product-market fit, and the importance of adapting through pivots. The goal is to equip viewers with the language and foundational knowledge to excel in product management, encouraging further learning through a dedicated playlist.

Takeaways

  • πŸ“ The importance of a Product Requirements Document (PRD) as a collaborative tool to communicate product specifications and the 'why' behind the product.
  • πŸ“‹ Acceptance Criteria as a subset of the PRD, defining the minimum requirements for product launch, crucial for developers and QA testers.
  • πŸ”„ A/B Testing as a method to determine which product version performs better by subjecting users to variations in features or design.
  • 🧾 The Backlog as a comprehensive list of planned products and features, serving as a central repository for ideas and ensuring nothing is overlooked.
  • πŸ’₯ Disruptive Innovation as a framework by Professor Clayton Christensen, describing how new market entrants can disrupt existing markets with simpler, cheaper, and easier-to-use products.
  • 🏷 Feature Flags as a technique to hide or reveal parts of the code to specific users, allowing for testing and feature control without deploying new code.
  • πŸ›  Jobs to be Done (JTBD) as a framework to understand customer needs, emphasizing that people hire products to solve specific problems in their lives.
  • 🏁 MVP or Minimum Viable Product as the basic version of a product with just enough features to address a customer's pain point and gather feedback for further development.
  • πŸ”— Product-Market Fit (PMF) as the stage where a product fully meets the needs of its target audience, indicating readiness for scaled growth and a key factor for investment.
  • πŸ—Ί Roadmap as a prioritized plan outlining the product team's direction, including key initiatives for each quarter and year, aligning all stakeholders.
  • πŸ’” Technical Debt as the cost of maintaining a product hastily developed, which if neglected can lead to significant issues and bugs in the future.
  • πŸ‘₯ User Stories as a customer-centric way to articulate product features within the PRD, helping to understand the purpose and goal of each feature.
  • 🎨 UX or User Experience as the overall experience a user has with a product, focusing on ease of use, visual appeal, and intuitiveness, typically designed in collaboration with product managers.
  • πŸ“ Wireframe as a simplified representation of the UX design, a low-fidelity sketch used for initial stakeholder feedback and storytelling.
  • πŸ”„ Pivot as a strategic change in product direction based on new information or market trends, allowing for adaptation and alignment with customer demands.

Q & A

  • What is the purpose of a Product Requirements Document (PRD)?

    -A PRD is a document that defines the requirements and specifications for how a product should be built. It's written by the product manager in collaboration with engineers, designers, and other team members, serving as a key tool for communication with the development team, stakeholders, and others involved in the product development process.

  • Can you explain the role of acceptance criteria in product management?

    -Acceptance criteria are usually written in the PRD and define the minimum requirements that need to be met by the product for it to be launched. They are crucial for developers and QA testers as they specify what must be built into the product to ensure it meets the necessary standards for launch.

  • What is A/B testing and how is it used in product management?

    -A/B testing is a method of launching two versions of a product to determine which performs better. It involves showing small variations of a product to different subsets of users to see if a change improves the user experience. Successful variations are then rolled out to all customers and incorporated into the final product.

  • How does a product backlog differ from a PRD?

    -A product backlog is a comprehensive list of features and products that a team plans to work on. It serves as a repository for all ideas coming from various stakeholders and ensures that nothing is overlooked. Unlike a PRD, which is more detailed and specific, a backlog is a high-level overview of potential work items.

  • What is disruptive innovation and how does it relate to product management?

    -Disruptive innovation is a framework that describes how new products or services can disrupt existing markets. It involves introducing a product that meets the needs of a customer segment that is underserved by existing offerings. These products often start with lower performance but improve rapidly, eventually outperforming established products in the market.

  • What are feature flags and how do they benefit product development?

    -Feature flags are a mechanism that allows product managers and development teams to hide parts of the code while in public. They enable the control of which features are visible to which customers, facilitating the testing of new features and the mapping of features to different product versions or customer segments.

  • Can you describe the Jobs To Be Done (JTBD) framework and its significance?

    -Jobs To Be Done is a framework that focuses on understanding the needs of customers when they purchase a product. According to this framework, people hire products to solve specific needs or problems in their lives. This perspective is a profound mindset shift that influences product design and development to better meet customer needs.

  • What is the significance of a Minimum Viable Product (MVP) in product management?

    -An MVP is a version of the product with the minimum features required to address a customer's pain point. Its purpose is to quickly gather customer feedback and determine what to continue building. MVPs are essential for startups and companies to avoid investing in full-fledged products that may not meet actual customer needs.

  • What does Product-Market Fit (PMF) mean and why is it important?

    -Product-Market Fit (PMF) is the point at which a product has been built to fully address the needs and requirements of its target audience. Achieving PMF is crucial for a product's success and is an ongoing process of iteration and testing. It is often a prerequisite for venture capital investment in startups.

  • What is a roadmap in the context of product management?

    -A roadmap is a prioritized backlog that outlines what a product team and product manager plan to work on. It provides a high-level plan of what is coming in the pipeline, covering key products and initiatives for each quarter and year. A roadmap helps align the entire team and ensures everyone is working towards the same goals.

  • What is technical debt and how can it impact a product?

    -Technical debt is the cost of maintaining and supporting a product over time, often due to shortcuts taken during development to quickly release a product. If left unaddressed, technical debt can lead to significant problems, as the underlying infrastructure may become unstable, causing many things to stop working and bugs to emerge.

  • What are user stories and how do they contribute to product development?

    -User stories are a way of viewing product features from the customer's perspective. They are written from the customer's point of view, such as 'As a user, I want to see X because why.' This approach helps the team understand the purpose of each feature and ensures that the product is designed to meet the actual needs of the users.

  • What is the role of user experience (UX) in product management?

    -User experience (UX) refers to the overall experience a user has when interacting with a product, including ease of use, visual appeal, and intuitiveness of the flow. It is typically designed by product designers in collaboration with product managers to ensure the product effectively addresses the key customer problems or jobs to be done.

  • What is a wireframe and how does it aid in product development?

    -A wireframe is a simplified representation of the UX and visual design of a product. It is a low-fidelity design that provides a quick sketch of what the product will look like. Wireframes are used for storytelling, allowing product managers and designers to pitch the product and gain insights from stakeholders.

  • What does a pivot in product management entail and why is it important?

    -A pivot in product management is a change in direction for a product based on new information or market trends. It can involve shifting focus from certain products or features to others in response to customer feedback or competitive activity. Pivots are crucial for startups and product managers to adapt to changing market demands and ensure they are addressing real customer needs.

Outlines

00:00

πŸ“š Introduction to Product Management Key Terms

Akash, a Harvard MBA graduate with a decade of product experience, introduces a video aimed at teaching 15 essential terms and concepts for product managers. He outlines the structure of the video, which will cover terms related to problem selection, defining success, and team collaboration for product execution. The video is designed to enhance viewers' understanding of product management language and skills.

05:02

πŸ“ Understanding Product Requirements and Acceptance Criteria

The first key term discussed is the Product Requirements Document (PRD), a crucial document outlining product specifications and requirements, created in collaboration with various team members. The PRD includes the 'why' behind the product, user and market research. Acceptance criteria, defined within the PRD, sets the minimum requirements for product launch, guiding developers and QA testers in ensuring the product meets its must-have features before release.

10:04

πŸ”¬ A/B Testing and the Importance of Experimentation

A/B testing is introduced as a method to compare two product versions to determine which performs better, a common practice on platforms like Netflix, Amazon, and Google. It involves variations in user interfaces or algorithms to measure their impact on user experience. Successful changes are then implemented for all users, highlighting the iterative nature of product improvement.

πŸ—“ The Role of the Product Backlog in Feature Planning

The product backlog is described as a comprehensive list of features and products planned by the team. It serves as a repository for ideas from various stakeholders, ensuring nothing is overlooked. The backlog is the first reference for product managers when deciding which feature to tackle next, maintaining a clear vision of the product's development trajectory.

πŸ’₯ Disruptive Innovation and its Impact on Markets

Disruptive innovation, a concept by Professor Clayton Christensen, is explored as a framework explaining how new market entrants can disrupt established markets. It involves introducing simpler, cheaper, and easier-to-use products that, despite initial lower performance, improve rapidly to challenge existing products. Akash shares his experience learning from Christensen and provides a video on how Airbnb disrupted the hotel industry.

🏁 Feature Flags for Controlled Feature Release

Feature flags are discussed as a tool for selectively enabling or disabling features for different customers without deploying new code. This method allows for testing new features and managing SKU-based feature mapping, providing flexibility in product development and customer experience management.

πŸ›  Jobs-to-be-Done Framework for Customer Needs

The Jobs-to-be-Done framework by Professor Christensen is introduced, emphasizing that customers 'hire' products to solve specific needs or problems in their lives. This framework encourages a shift in mindset from selling products to addressing customer jobs, with an example given about the purchase of headphones to listen to music.

πŸš€ MVP and the Path to Product Market Fit

The Minimum Viable Product (MVP) is defined as a product version with the minimum features necessary to address a customer's pain point. Its purpose is to quickly gather customer feedback and inform further development. The concept of Product Market Fit (BMF) is also discussed, highlighting the importance of building a product that fully meets the target audience's needs for scalable growth.

πŸ—Ί The Strategic Importance of the Product Roadmap

A product roadmap is described as a prioritized plan outlining the product team's initiatives for each quarter and year. It aligns all stakeholders on the product's direction, aids in planning, and supports sales efforts by providing a clear vision of the product's future.

πŸ’” The Risks of Technical Debt in Product Development

Technical debt is discussed as the cost of maintaining and supporting a product over time, often due to shortcuts taken during development. If left unaddressed, it can lead to significant problems, including system failures and bugs, as the underlying infrastructure may be unstable.

πŸ“œ User Stories and their Role in Feature Development

User stories are explained as a method of viewing product features from the customer's perspective, helping to understand why each feature is being built and its purpose. They are part of the PRD and are written in a format that reflects the customer's needs and goals.

🎨 The Role of UX Design in Product Development

User experience (UX) design is highlighted as the overall experience a user has with a product, including ease of use, visual appeal, and intuitiveness. It is typically developed by product designers in collaboration with product managers to ensure it addresses the key customer problems or jobs to be done.

πŸ“ Wireframing for Product Design Visualization

Wireframing is introduced as a simplified representation of the UX and visual design of a product, serving as a low-fidelity design tool. It can be created by product managers to provide stakeholders with a preliminary sense of the product's look and feel, facilitating storytelling and gaining insights.

πŸ”„ Pivoting for Adaptability in Product Management

Pivoting is described as a strategic change in product direction based on new information or market trends. It allows product managers to adapt to customer needs and changing market behaviors, ensuring continued focus on solving real customer problems. Successful companies like Spotify, Airbnb, Uber, and Amazon are cited as examples of businesses that pivoted early to address customer needs.

πŸ›‘ Building the Skills for Successful Product Management

The video concludes by emphasizing that knowing product management terms is not enough; it's crucial to build the necessary skills and mindset. Akash provides a playlist covering essential product management skills to further equip viewers for success in the field.

Mindmap

Keywords

πŸ’‘Product Management

Product Management is the process of guiding a product from its conception to its launch and beyond, ensuring that it meets the needs of the market and the company. In the video, it is the overarching theme, as it discusses the language and skills necessary for someone to excel in this field.

πŸ’‘PRD (Product Requirements Document)

A PRD is a critical document in product management that outlines the features and specifications of a product. It serves as a blueprint for the development team and communicates the 'why' behind the product, as mentioned in the script, and includes user and market research.

πŸ’‘Acceptance Criteria

Acceptance Criteria are the minimum requirements that a product must meet before it can be launched. They are usually part of the PRD and are essential for developers and QA testers to know what they need to achieve, as illustrated in the script.

πŸ’‘A/B Testing

A/B testing is a method used to compare two versions of a product to determine which performs better. It is a common practice in digital platforms like Netflix and Amazon, as referenced in the script, and helps in making data-driven decisions to improve user experience.

πŸ’‘Backlog

A backlog in product management is a comprehensive list of features and products that a team plans to work on. It is a tool for tracking ideas and ensuring that all necessary tasks are accounted for, as explained in the video.

πŸ’‘Disruptive Innovation

Disruptive Innovation refers to a new product or service that disrupts an existing market by offering a simpler, cheaper, and more accessible alternative. The script cites the book 'The Innovator's Dilemma' by Clayton Christensen and gives the example of Airbnb disrupting the hotel industry.

πŸ’‘Feature Flags

Feature flags are used to hide or reveal parts of the codebase to different users without deploying new code. They allow for testing new features and managing different product versions, as described in the script.

πŸ’‘Jobs-to-be-Done (JTBD)

Jobs-to-be-Done is a framework that suggests customers 'hire' products to get a job done. It emphasizes understanding customer needs deeply, as mentioned in the script, and is a shift from traditional product feature focus to customer problem-solving.

πŸ’‘MVP (Minimum Viable Product)

An MVP is a version of the product with just enough features to satisfy early customers and provide feedback for future development. The script explains that building MVPs is essential for startups to test their product ideas in the market efficiently.

πŸ’‘Product-Market Fit (PMF)

Product-Market Fit is the stage where a product fully addresses the needs of its target audience and is ready for scaled growth. The script highlights its importance for any product and mentions that it is an ongoing process of iteration and testing.

πŸ’‘Roadmap

A roadmap is a high-level plan that outlines the direction of a product, including what initiatives will be addressed in the upcoming quarters and years. It helps align the entire team, as explained in the script, and provides a clear vision for the product's future.

πŸ’‘Tech Debt

Tech debt refers to the cost of maintaining and supporting a product that has been hastily developed. It's like borrowing from the future to meet present deadlines, as mentioned in the script, and if ignored, can lead to significant problems down the line.

πŸ’‘User Stories

User stories are a way of describing product features from the customer's perspective. They are part of the PRD and help the team understand why a feature is being built and its purpose, as explained in the script.

πŸ’‘User Experience (UX)

User Experience encompasses all aspects of how a user interacts with a product, including its usability, aesthetics, and intuitiveness. The script discusses how UX is designed in collaboration with product managers to ensure it addresses the customer's needs.

πŸ’‘Wireframe

A wireframe is a basic visual representation of a product's design. It's a simplified sketch that helps stakeholders understand the product's look and feel before it's fully developed, as described in the script.

πŸ’‘Pivot

A pivot in product management is a strategic change in direction based on new information or market trends. The script mentions that pivots are crucial for startups to adapt to customer demands and behaviors, with examples of successful companies like Spotify and Airbnb.

Highlights

Introduction to 15 key terms and concepts for product management.

Explanation of the Product Requirements Document (PRD) as a collaborative tool for defining product specifications.

Importance of acceptance criteria in the PRD for defining minimum requirements for product launch.

A/B testing as a method to determine which product version performs better, with examples from Netflix, Amazon, and Google.

The concept of a backlog as a comprehensive list of planned product features and ideas.

Disruptive innovation framework by Professor Clayton Christensen, including its application in business and product management.

Feature flags as a technique to hide and test new features in a live product environment.

Jobs-to-be-Done (JTBD) framework by Professor Christensen explaining customer needs when purchasing a product.

Definition and purpose of a Minimum Viable Product (MVP) in product development.

Product-Market Fit (PMF) as a critical milestone for product readiness and scaling.

The role of a roadmap in aligning product team efforts and planning for future product development.

The concept of technical debt and its impact on product maintenance and support over time.

User stories as a customer-centric approach to feature development within a PRD.

User Experience (UX) as the overall experience a user has while using a product, including design and usability.

Figma as a popular tool for UX design, including its features for flowcharts and UI elements.

Wireframe as a simplified representation of UX design for initial stakeholder feedback and storytelling.

Pivot as a strategic change in product direction based on new information or market trends.

The necessity of understanding product management jargon for effective communication and skill building.

Transcripts

play00:00

do you want to become a pro at

play00:01

navigating the complex world of product

play00:03

management well in this video I'm going

play00:05

to cover 15 key terms and Concepts used

play00:08

by product managers by the end of this

play00:10

video you will be a pro at the language

play00:13

of product management so grab your

play00:15

notepads and let's get started hey my

play00:17

name is Akash I have a decade of product

play00:19

experience I'm a Harvard MBA grad and

play00:22

Angel invest in startups on this channel

play00:24

we talk about ways to level up your

play00:26

product management skills and career

play00:28

let's go so I've broken down the terms

play00:30

into the three parts of a product

play00:32

manager's role which are choosing the

play00:34

right problems to solve defining what

play00:37

success looks like and working and

play00:39

executing with the team for the product

play00:41

success

play00:43

okay first we have PRD or product

play00:45

requirements document this is a document

play00:48

that defines the requirements and

play00:49

specifications for how a product should

play00:52

be built it's written by the product

play00:53

manager in collaboration with the

play00:55

engineers designers and other folks on

play00:59

their cross-functional team it's an

play01:00

important tool for communicating with

play01:02

the development team stakeholders and

play01:04

other folks who will be working on the

play01:07

product a great PRD addresses the why

play01:09

behind the product as well as user and

play01:11

market research

play01:13

so next we have acceptance criteria the

play01:15

acceptance criteria is usually written

play01:17

in the PRD itself and is a way for the

play01:20

product manager to Define what are the

play01:22

minimum requirements that need to be met

play01:24

by the product in order for it to be

play01:26

launched this is very important for

play01:28

their developers and QA testers who will

play01:31

be working on the product because it

play01:33

tells them what criteria they need to be

play01:35

looking at to make sure are built into

play01:38

the product and those are our must-haves

play01:40

and minimum requirements that are needed

play01:43

for the launch of the product

play01:45

okay next let's look at a B testing so a

play01:48

b testing is a way of launching two

play01:50

versions of the product in order to see

play01:53

which performs better all of you and all

play01:55

of us unknowingly every day are subjects

play01:58

of a b testing on sites like Netflix

play02:01

Amazon Google and others what this means

play02:05

is that a small subset of users is

play02:08

always seeing small variations in the

play02:11

checkout button placement or an ad

play02:14

placement or the watch next screen or

play02:17

the algorithm that's used in the Netflix

play02:19

ranking and ratings algorithm then the

play02:23

website sees if that small change made a

play02:27

positive impact on your user experience

play02:29

or not only the tests and experiments

play02:31

that had a outsized positive impact on

play02:34

your user experience are actually rolled

play02:36

out to all customers and all users and

play02:39

built into the final product

play02:42

okay so backlog backlog is really the

play02:45

laundry list or complete list of

play02:47

products and features that a product

play02:49

team plans to work on it's a great way

play02:52

to keep track of all of the ideas that

play02:54

are coming through from the sales team

play02:55

the customer experience team customers

play02:58

designers anyone who is involved and a

play03:02

stakeholder of the product itself it's

play03:04

great to make sure that everything that

play03:05

needs to be done is kept in one place

play03:08

and nothing falls through the cracks

play03:10

anytime a product manager is thinking of

play03:12

what feature to work on next the backlog

play03:14

is usually the place that they will go

play03:16

to first to see what is the ideas and

play03:20

Concepts that are on the backlog that

play03:22

need to be worked on

play03:24

okay disruptive innovation so this is

play03:27

actually the most popular framework that

play03:30

is used in the world of business and

play03:32

around product management this was first

play03:35

written by Professor clay Christensen in

play03:37

the book innovators dilemma I actually

play03:40

had the Good Fortune of taking Professor

play03:42

christensen's class at Harvard during

play03:44

his last year of teaching this course so

play03:46

this term actually describes how new

play03:48

products and entrance to the market are

play03:51

able to disrupt existing markets and

play03:53

existing players who are dominant in the

play03:56

market it all starts by introducing a

play03:58

new product or service that addresses a

play04:00

customer segment whose needs are being

play04:02

over met or not met at all by the

play04:05

existing products and services these new

play04:07

products are typically things that are

play04:09

simpler cheaper and just easier to use

play04:12

they have lower performance when they

play04:14

are actually introduced but quickly

play04:17

improve their performance to disrupt the

play04:20

existing products in the space and

play04:22

slowly all the customers are move to

play04:25

this new product I have a video that

play04:27

I'll link to here about how Airbnb has

play04:30

disrupted the hotel industry so give

play04:32

that a watch okay

play04:34

so feature Flags uh feature flags are a

play04:37

great way for product managers and

play04:39

development teams to keep parts of the

play04:42

code actually hidden and secret while in

play04:45

public so products that are already

play04:47

shipped and out there in production

play04:49

environments have multiple feature flags

play04:52

and each feature flag determines which

play04:55

product should be seen by which customer

play04:57

so for example a customer when they buy

play05:02

a new product or a buy a new plan for a

play05:06

existing product that they already have

play05:08

what happens is in the back end they

play05:10

don't ship new code to the product for

play05:13

that customer they just turn on the

play05:14

feature flag for that customer it's a

play05:17

great way to test new features or have

play05:19

SKU based mapping of features and parts

play05:23

of a product

play05:24

for a complete code base

play05:27

okay jtbt or jobs to be done this is

play05:30

again a framework by Professor

play05:32

Christensen that talks about what the

play05:35

needs of a customer are when they buy a

play05:38

product so according to this framework

play05:40

people don't actually buy products they

play05:43

hire them to solve real needs and

play05:46

problems in their lives for example

play05:48

people don't really buy headphones they

play05:51

hire headphones in order to listen to

play05:54

music that they love it might sound

play05:56

simple but it's a profound mindset shift

play05:59

that has deep implications okay let's go

play06:01

here MVP or minimum viable product this

play06:05

is a version of the product that has the

play06:07

minimum features required to address the

play06:10

customer's pain point it then gives the

play06:12

product managers and product team a

play06:15

signal in terms of what to continue

play06:17

building and invest more development

play06:19

time and effort on the goal of an MVP is

play06:22

to get a product idea out to customers

play06:24

as quickly as possible and then gather

play06:27

that feedback building MVPs is essential

play06:29

for any startup or any company because

play06:33

without MVPs you'll be building

play06:34

full-fledged products and then realizing

play06:37

that it doesn't even solve a actual

play06:39

product or customer need

play06:41

okay BMF or product Market fit this is

play06:44

the point at which a product has been

play06:46

built to address its target audience is

play06:49

needs and requirements at a complete

play06:52

level this is when the product is ready

play06:54

for scaled growth finding product Market

play06:56

fit is really essential for any product

play06:58

and it's an ongoing process of iteration

play07:01

and testing many VCS won't even invest a

play07:05

series a round of funding in a startup

play07:08

until they have achieved product Market

play07:09

fit

play07:11

okay roadmap so a road map is the

play07:14

prioritized backlog that a product team

play07:18

and product manager plans to work on

play07:20

it's basically a high level plan of what

play07:22

is coming in the pipeline and what

play07:25

everyone should be targeting for each

play07:28

quarter and each year it covers all the

play07:31

key products and initiatives that are

play07:33

going to be addressed each quarter and

play07:35

each year that the product manager

play07:38

engineering team designers and everyone

play07:40

should be aligned on this helps everyone

play07:42

to know what direction the product is

play07:44

going in and helps the sales team to

play07:47

sell the product better helps the

play07:49

engineering team to plan better and just

play07:51

helps everyone know what direction they

play07:53

should be aiming towards

play07:55

okay let's go here so take that so this

play07:58

is the cost of maintaining and

play08:00

supporting a product over time it arises

play08:02

as a result of taking shortcuts during

play08:04

the development of a product to get it

play08:06

out the door and ship to customers as

play08:08

quickly as possible so like any debt

play08:11

techdead is a way of borrowing

play08:13

development effort from the future to

play08:15

the present but what that means is if

play08:17

this Tech Deck is gone unaddressed for

play08:19

long periods of time it can spell

play08:22

disaster and big problems for the

play08:24

product because many things will stop

play08:26

working and a lot of bugs will come up

play08:29

because a lot of the underlying

play08:31

infrastructure is shaky

play08:34

so another common term you might see is

play08:36

user stories and this is actually

play08:38

something that forms a part of the PRD

play08:40

itself user stories are a way of seeing

play08:43

the products features from the eyes of

play08:46

the customer so the user stories are

play08:48

written from the perspective of the

play08:50

customer such as as a user I would like

play08:53

to see X because why this helps everyone

play08:57

to understand why they are building

play08:58

every part and every feature in a

play09:01

product and what the actual goal of that

play09:04

feature or user story is

play09:08

the ux or user experience this is

play09:11

actually just the overall experience

play09:13

that a user feels when they are using a

play09:15

product this includes how easy it is to

play09:17

use how visually appealing it is and how

play09:20

intuitive the entire flow is when it's

play09:23

all mapped together this is typically

play09:25

built by product designers in

play09:27

collaboration with the product managers

play09:28

to make sure that is actually addressing

play09:31

the key customer problem or job to be

play09:34

done figma is nowadays the most popular

play09:36

tool for user ux design and it includes

play09:39

flowcharts screens and other UI elements

play09:44

so wireframe is actually just a

play09:47

simplified representation of what the

play09:50

actual ux and visual design of the

play09:53

product will look like it's a low

play09:55

Fidelity design which means it's a very

play09:57

quick sketch uh might even have been

play10:00

done on pen and paper in the past or

play10:03

might be done using a two lug balsamic

play10:06

nowadays this can even be done by the

play10:08

product manager themselves just to give

play10:10

stakeholders a sense of what the product

play10:13

will look and feel like when it's

play10:15

actually built this becomes a key tool

play10:18

for storytelling that can be used by the

play10:20

product managers and designers to pitch

play10:23

the product and gain the experience and

play10:27

gain the insights from stakeholders

play10:30

okay and finally pivot so a pivot is

play10:33

essentially a change in direction for a

play10:36

product based on new information or new

play10:39

customer Trends in the marketplace in

play10:41

product management a pivot can involve

play10:43

shifting Focus from a particular set of

play10:46

products and features to new ones

play10:49

because there is new information from

play10:51

customers or there is new activity from

play10:54

competitors pivots are an important tool

play10:56

for product managers and startups

play10:58

because it enables them to keep changing

play11:01

direction based on what is the most

play11:04

up-to-date and precise current

play11:07

requirements that they see in the market

play11:09

if it's allow them to adapt and respond

play11:11

to changing behaviors in the market and

play11:13

these help them to make sure that they

play11:15

are continuing to focus on the real

play11:18

customer demand and customer problem or

play11:21

job that needs to be solved many

play11:23

companies like Spotify Airbnb Uber

play11:26

Amazon and more

play11:28

started and succeeded because they

play11:31

pivoted early and to the to address the

play11:34

actual customer problems okay so that's

play11:37

all 15 terms but the problem now is that

play11:40

knowing all of these terms isn't just

play11:42

enough knowing the jargon definitely

play11:43

makes communication easier but it

play11:46

doesn't help you actually building all

play11:47

of these skills and building the mindset

play11:50

and skill sets that are needed to be a

play11:52

successful product manager so for that

play11:54

I've made this playlist that covers all

play11:56

the essential skills that a product

play11:58

manager needs to know you should

play11:59

definitely watch that next this will get

play12:01

you up to speed on all the skills as

play12:04

quickly as possible

Rate This
β˜…
β˜…
β˜…
β˜…
β˜…

5.0 / 5 (0 votes)

Related Tags
Product ManagementKey TermsStrategiesHarvard MBAAkashPRDAB TestingBacklogDisruptive InnovationMVPProduct Market Fit