Product Development Consulting Flashcards

Question 1

What is product development consulting, and what does a consultant typically do?

Accepted Answer

Product development consulting is the advisory work of helping an organization decide what products to build, how to build them, and how to bring them to market. A consultant typically brings outside perspective, structured methods, and experience from other teams. The aim is better decisions, not simply more output.

Question 2

What is the difference between an output and an outcome in product work?

Accepted Answer

An output is a deliverable the team produces, such as a feature, a report, or a release. An outcome is the change in customer or business behavior that the output was meant to create, such as higher retention or faster task completion. Consultants push teams to measure outcomes.

Question 3

What is a product discovery phase, and why do teams run one before building?

Accepted Answer

A product discovery phase is a period of focused learning that tests whether a problem is worth solving before a team commits to building a solution. Teams use interviews, prototypes, and data review to reduce uncertainty. Discovery is cheaper than building the wrong thing, so it protects time and budget.

Question 4

What does it mean for a consultant to act as a facilitator rather than an expert?

Accepted Answer

Acting as a facilitator means guiding a team through a process so the team reaches its own conclusions, rather than handing down answers. The consultant designs workshops, asks clarifying questions, and keeps discussion on track. This approach builds ownership, so the team can continue the work after the engagement ends.

Question 5

What is a minimum viable product, and what is its main purpose?

Accepted Answer

A minimum viable product is the smallest version of a product that still delivers enough value to test a key assumption with real users. Its main purpose is learning, not polish, so the team can decide whether to expand, change direction, or stop.

Question 6

Why do consultants often define the problem before proposing a solution?

Accepted Answer

Consultants define the problem first because a solution aimed at the wrong problem wastes effort even when it is well built. A clear problem statement names who is affected, what they struggle with, and why it matters. This gives the team a shared standard for judging ideas and keeps debates focused on evidence.

Question 7

What is the purpose of a stakeholder map in a product engagement?

Accepted Answer

A stakeholder map identifies everyone who has influence over or interest in the product, and it records how much power each person holds and how involved they should be. Consultants build one early so they know whose approval matters and whose concerns must be addressed. Missing a key stakeholder often causes late rework.

Question 8

How does a consultant typically begin an engagement with a new client team?

Accepted Answer

A consultant typically begins by learning the business context, including goals, constraints, existing products, and past attempts. They then review available data, interview key people, and agree on the questions the engagement must answer. Clear scope and shared success criteria at the start prevent confusion later.

Question 9

What is the difference between qualitative and quantitative customer research?

Accepted Answer

Qualitative research gathers rich, descriptive information about why people behave as they do, usually through interviews, observation, or open-ended feedback. Quantitative research measures how many people do something or think something, using surveys, analytics, or experiments. Strong discovery usually combines both, so the team understands the reasons and the scale.

Question 10

What makes a customer interview question open-ended and useful?

Accepted Answer

An open-ended question invites the customer to describe their own experience, rather than answering yes or no or choosing from options you supplied. Good questions ask about past behavior, such as when someone last tried to solve a problem, rather than hypothetical wishes like whether they would use a feature.

Question 11

Why do researchers distinguish between what customers say and what they actually do?

Accepted Answer

Customers often describe their habits or preferences inaccurately, either from memory or from a wish to appear reasonable. Observed behavior, such as how someone actually completes a task or what they buy, usually gives more reliable evidence. Teams therefore compare interview statements with observation and usage data before drawing conclusions.

Question 12

What is a customer journey map and how is it used in discovery?

Accepted Answer

A customer journey map is a visual record of the steps a person takes to reach a goal, along with their actions, thoughts, and emotions at each step. In discovery, it shows where people struggle, abandon tasks, or rely on workarounds. Those points often reveal the most promising opportunities for improvement.

Question 13

What is the jobs-to-be-done perspective on customer needs, and why do teams use it?

Accepted Answer

The jobs-to-be-done perspective holds that customers hire products to make progress in a specific situation, so the useful question is what job they are trying to get done. Teams use it to focus on the underlying goal rather than on demographics or existing features. This can reveal competitors that are not obvious.

Question 14

What is the purpose of a problem interview in product discovery?

Accepted Answer

A problem interview explores how a person experiences a problem, without pitching a solution. Its purpose is to learn how often the problem occurs, what it costs the person, and how they cope with it today. If the problem is real and painful, the team has a stronger basis for designing something new.

Question 15

What is sample bias, and why does it matter in customer research?

Accepted Answer

Sample bias occurs when the people you study differ in important ways from the wider group you want to understand, so their views do not represent that group. A team that interviews only its most loyal users may overestimate satisfaction and miss the reasons others leave. Recruiting participants from several segments reduces this risk.

Question 16

How can a team tell when it has learned enough during discovery to move forward?

Accepted Answer

A team has learned enough when its key assumptions have been tested and the evidence consistently points toward a decision, such as pursue, change, or drop the idea. Many teams set explicit exit criteria in advance. Continuing to research without a decision is a common way discovery drifts.

Question 17

What is a product strategy, and how does it differ from a product roadmap?

Accepted Answer

A product strategy is a statement of where the product is going, who it serves, and how it will win, expressed as choices about priorities and trade-offs. A roadmap is a plan that sequences work over time to carry out that strategy. Strategy explains why, while the roadmap shows what and when.

Question 18

What is a product vision and why should it stay stable over time?

Accepted Answer

A product vision describes the lasting change a product hopes to create for its users, written in broad terms that do not depend on a specific feature set. It should stay stable so decisions share a consistent direction. Strategies and plans can change as evidence arrives, but the vision gives them a common purpose.

Question 19

What is a North Star metric, and what makes a good one?

Accepted Answer

A North Star metric is the single measure that best captures the value a product delivers to customers, and tracking it helps every team align around that value. A good one reflects customer value, predicts long-term business health, and can be influenced by the work teams actually do.

Question 20

What does it mean to prioritize using a scoring model such as impact versus effort?

Accepted Answer

Scoring models rate each candidate initiative on factors such as expected impact and the effort required, then rank the options to guide choices. An impact versus effort grid plots ideas on two axes to reveal quick wins. Scores are aids to judgment, so teams should discuss the assumptions behind each rating.

Question 21

What is opportunity cost, and why does it matter when choosing product work?

Accepted Answer

Opportunity cost is the value of the best alternative you give up when you commit resources to one option. In product work, every feature a team builds means another initiative waits, so the real cost of a choice includes the work it displaces. Naming that trade-off openly helps leaders say no to attractive requests.

Question 22

What is a value proposition, and what should it communicate?

Accepted Answer

A value proposition states the specific benefit a product offers a particular customer group, and why it beats the alternatives that group uses now. A strong one names the customer, the problem or goal, and the outcome delivered. Vague claims about being innovative or high quality usually fail to differentiate the product.

Question 23

What is a market segment, and why do consultants ask teams to choose one first?

Accepted Answer

A market segment is a group of customers who share needs or behaviors that matter for product design. Choosing one segment first lets a team focus its research, design, and messaging on people whose problem it can solve well. Broad targeting often produces a product that satisfies no one clearly.

Question 24

How should a team decide when a strategic bet is no longer worth pursuing?

Accepted Answer

A team should decide in advance which signals would show that a bet is failing, like missed adoption targets. When those signals appear, the team reviews the evidence openly and chooses to pivot, persevere, or stop. Agreeing on these thresholds early keeps the decision based on data rather than on sunk cost or attachment.

Question 25

What is a prototype, and what is it used to learn?

Accepted Answer

A prototype is a simplified, partial, or temporary version of a product idea that lets people react to it before the team invests in full development. Prototypes help learn whether users understand the concept, can complete key tasks, and see the value. Their fidelity can be low, since the goal is insight.

Question 26

What is the difference between low-fidelity and high-fidelity prototypes?

Accepted Answer

Low-fidelity prototypes are rough, such as paper sketches or simple wireframes, and are quick to change, which encourages honest feedback. High-fidelity prototypes look and behave much like the finished product, with detailed visuals and realistic interactions. Teams usually start low and move higher once the direction is clearer.

Question 27

Why do design teams run usability tests with real users?

Accepted Answer

Design teams run usability tests because people's observed behavior reveals friction that designers, who know the product too well, often miss. Participants are asked to complete realistic tasks while the team watches and notes where they hesitate, err, or give up. The findings guide specific fixes.

Question 28

What is a design sprint, and what does it aim to produce?

Accepted Answer

A design sprint is a short, structured process in which a team moves from a problem to a tested prototype using defined steps. It usually includes mapping the problem, sketching options, deciding on one direction, building a prototype, and testing it with users. Its aim is a validated answer to a key question.

Question 29

Why is accessibility an important consideration in product design?

Accepted Answer

Accessibility matters because a product that people with disabilities cannot use excludes a meaningful part of its potential audience and can create legal and reputational risk. Designing for accessibility, such as using clear labels and keyboard navigation, often improves usability for everyone. Consultants build accessibility checks into every review.

Question 30

What is a design system, and how does it help product teams?

Accepted Answer

A design system is a shared collection of reusable components, patterns, and rules that define how a product should look and behave. It helps teams build consistent interfaces faster, because designers and engineers draw from the same parts rather than reinventing them. It also makes quality easier to maintain as products grow over time.

Question 31

What is the difference between a heuristic review and a usability test?

Accepted Answer

A heuristic review is an expert evaluation in which a reviewer checks an interface against established usability principles, without involving users. A usability test observes real people attempting tasks, which reveals problems that experts may not predict. The two methods complement each other, since reviews are quick while tests provide direct evidence of behavior.

Question 32

How should a team handle conflicting feedback from different user groups during design?

Accepted Answer

A team should first check whether the conflicting feedback comes from different needs, contexts, or segments, since each group may be right about its own situation. It should then weigh each perspective against the primary segment and the problem the product is meant to solve. Documenting the trade-off keeps the decision transparent.

Question 33

What is a go-to-market plan, and what does it cover?

Accepted Answer

A go-to-market plan describes how a product will reach its intended customers, including the target segment, positioning, pricing, channels, and launch timing. It connects product decisions with marketing, sales, and support so that all teams prepare for the same launch. Gaps in this plan often show up as missed launch goals.

Question 34

What is a launch checklist and why do teams use one?

Accepted Answer

A launch checklist is a shared list of tasks, owners, and deadlines that must be completed before, during, and after a release. Teams use it to catch dependencies that are easy to forget, such as legal review, support documentation, monitoring alerts, and rollback plans. Reviewing it together before launch day reduces surprises.

Question 35

What is a key performance indicator, and how does it differ from a vanity metric?

Accepted Answer

A key performance indicator is a measure tied directly to a goal the team cares about, such as activation rate or repeat purchases. A vanity metric looks impressive, such as total downloads, but does not reflect value delivered. Good indicators change behavior when they move, while vanity metrics often rise without improving the business.

Question 36

What is a feedback loop in product development, and why does it matter?

Accepted Answer

A feedback loop is the cycle in which a team releases work, gathers evidence about how people use it, and uses that evidence to decide the next change. Short loops let teams correct course quickly. Consultants help teams shorten loops by defining what to measure and how often to review it.

Question 37

What does it mean to iterate on a product after launch?

Accepted Answer

Iterating after launch means making small, deliberate changes based on evidence from real use, then measuring whether those changes produced the intended outcome. Each cycle should have a clear hypothesis, a planned change, and agreed success criteria. Iteration is not random tinkering, because unplanned changes make it hard to tell which adjustments actually helped.

Question 38

What is an A/B test, and what conditions make its results trustworthy?

Accepted Answer

An A/B test randomly splits users between two versions of an experience and compares a chosen measure between the groups. Results are more trustworthy when assignment is random, the sample is large enough to detect a meaningful difference, and the team defined the success measure before the test began.

Question 39

How do consultants help a team decide whether a launched product is succeeding?

Accepted Answer

Consultants help a team agree on success criteria before launch, then review results against those criteria at set intervals. They compare leading indicators with lagging indicators to see both early signals and durable results. When evidence is mixed, they guide the team toward a clear decision: invest further, adjust, or retire the product.

Question 40

What is a retrospective, and how should teams use it after a release?

Accepted Answer

A retrospective is a structured review in which a team examines what went well, what did not, and what it will change in its next cycle. Effective retrospectives focus on process and decisions rather than blame, and they end with a small number of concrete actions with named owners.

Product Development Consulting Flashcards

1Foundations of product consulting

2Discovery and customer research

3Strategy and prioritization

4Design and prototyping practice

5Launch, measurement and iteration

Learning Resources