Design concepts are the first step in creating a great product. They enable product teams to discover and fix problems long before the development phase.

Testing assumptions is one of your most important responsibilities as a PM. It’s also one of the most ambiguous. Using an assumption map can help make validating your assumptions more tangible.

Walk through the seven stages of the new product development process and discover how to take new products from idea to market.

In this guide, we’ll highlight the difference between strategy and tactics and explore how each impacts the other.

The purpose of a design concept is to help designers and developers visualize what the product should look like and, in doing so, drive additional value for customers.

The software testing lifecycle consists of multiple phases, including alpha, beta, and general availability, designed to enhance the user experience.

In this guide, we’ll highlight the difference between OKRs and KPIs and demonstrate how you can use them both to drive value and better outcomes.

The vision statement drives the end goal of the product, aligning stakeholders and roadmaps. The mission statement drives the “how” of the product.

There are important separations between types of decision-making processes: should this be made by a group or individual? Do you need consensus?

Review what iterative and incremental development means, weigh the pros and cons, and see how an iterative and incremental development process works in practice by looking at examples.

A contingency plan — also known as a “plan B” or “backup plan” — is used by organizations to effectively respond once a risk occurs.

Despite calling ourselves scrum teams, we often aren’t equipped to learn fast enough. Here are three steps to improve your release management process and set your next deployment up for success.