Search for:

Product Marketing

Tools

Interviews

Product Interview Prep

Product Management

Interview Questions

Product Development

DevOps

Product Analytics

Product Led Growth

Product Design

Programs

Product Career

Agile methodology guide. "> Agile

Glossary

Product Strategy

Become a Great Product Professional

Explore

Self-Paced Online Training Case Studies

Glossary

Find a guide to learn more about Glossary

What CRM means for product managers

I get asked “what does CRM mean?” more often than you’d expect from people who already ship product. The acronym is simple—customer relationship management—but for product managers the useful answer is not a vendor list. CRM is the system of record for how your company acquires, serves, and keeps customers. Your job is to treat it as a product signal surface, not a sales toy you ignore until QBR season....

Interview

Find a guide to learn more about Interview

Product Q&A with Justin Watt: What I would take from the conversation

Learn from the operating context I would read Justin Watt’s product Q&A as a conversation about how product work changes inside an agency. His background spans project and product management, internal products, client work, and teams that move across engagements. That context matters: an agency product team has to balance client goals, team autonomy, delivery quality, and the chance to learn from different problems. I would not treat one person’s...

The product lessons inside a cable bill: How I would protect customer value

Start with the customer job I see a cable bill as a reminder that a product is judged by the job customers hire it to do, not by the complexity of the provider’s internal system. A bundle can make sense when it gives people useful choice and convenience. It becomes a problem when customers feel they must pay for unwanted pieces to receive the one thing they value. I would...

Product Career

Find a guide to learn more about Product Career

Product Interview Prep

Find a guide to learn more about Product Interview Prep

Technical PM resume examples I’d actually use

A technical product manager resume should show you can translate between users and engineers, prioritize with technical constraints, and ship with operability in mind. When I scan these, I’m looking for systems judgment and collaboration evidence—not a fake CS degree or a dump of tech buzzwords. Here’s the structure, bullet frameworks, and generic examples I’d want you to adapt with your real experience. It complements our Technical Product Manager cluster...

AI product manager resume examples I’d actually use

An AI product manager resume should show you can define valuable problems, decide when AI is the right tool, partner with technical teams, and ship responsibly. When I review these, I’m scanning for product judgment plus AI literacy—not a laundry list of model names. Here’s the structure, bullet frameworks, and generic examples I’d want you to adapt with your real experience. It complements our AI Product Manager cluster (how-to, skills,...

Day in the life of an AI product manager (from what I’ve seen)

An AI product manager owns outcomes for products or features that rely on machine learning or generative AI. From what I’ve seen across startups and larger product orgs, a typical day still looks like product management—discovery, prioritization, shipping, communication—but with extra time on data quality, model evaluation, failure modes, and alignment with data science, ML eng, and risk/compliance partners. Exact calendars vary by company stage, whether you own a full...

Product Strategy

Find a guide to learn more about Product Strategy

Decision log for PMs

A decision log is the lightweight record I use to preserve important product choices and the context behind them. I write down what we decided, who decided it, when it was decided, what evidence informed it, and what assumptions or consequences still matter. The goal is not to document every preference. The goal is to stop the team from repeatedly reopening a choice without remembering why it was made. I...

One-pager for PMs

A one-pager is the short product brief I use when a team needs a shared starting point for a problem, opportunity, decision, or proposal. Its value is not that every subject can fit neatly on one page. Its value is that the constraint forces me to say what matters now, what I know, what I do not know, and what decision I am asking people to make. I use a...

Survey design for PMs

Survey design is the work of turning a product question into questions people can answer consistently. I use a survey when I need structured input across a defined group, a way to compare responses, or a follow-up to qualitative learning. A survey is not automatically representative, and a large response count cannot repair a confusing question or a poorly defined audience. I design for a decision, then state what the...

Programs

Find a guide to learn more about Programs

General Assembly product management: My worth-it checklist

General Assembly has helped a lot of people pivot careers. That history doesn’t automatically make every General Assembly product management course the right move in your market today. Here’s the checklist I’d run in 2026 before I paid tuition or rearranged my life around a cohort. What GA-style PM courses usually sell Employment-oriented curriculum Instructor-led cohorts (online and/or in-person, depending on offering) Portfolio-ish projects Career support of some kind (quality...

Berkeley product management: How I’d decide if it’s worth it

UC Berkeley’s brand carries weight. That still doesn’t answer whether a Berkeley product management program is the right spend of time and money for you. Here’s how I’d evaluate it—without treating the logo as an automatic yes. Wave3 Berkeley PM eval marker Sep23 What you’re usually choosing between Berkeley-style offerings typically split into something like: A certificate program — broader PM foundations, lectures + exercises, credential signal A more studio...

Stanford product management: Is it worth it? my honest review lens

Stanford on a syllabus looks impressive. Whether a Stanford product management program is worth it depends on your goal, budget, and what you'd do with the credential—not the logo alone. Here's the review lens I'd use. What these programs tend to optimize for University PM programs (Stanford included) usually emphasize frameworks, strategy, and academic rigor. They often attract: Engineers / technical folks adding product skills Graduate students exploring PM Employed...

Tools

Find a guide to learn more about Tools

Product management software: How I’d evaluate it

"Product management software" usually means tools for roadmapping, prioritization, delivery visibility, and stakeholder communication. Some teams use one platform; many stitch two or three. The win is shared truth—not logo collecting. What I want the software to do Express strategy and themes, not only tickets Support prioritization conversations with visible tradeoffs Connect (or at least not fight) engineering delivery systems Offer views for execs vs builders without duplicate data entry...

Product roadmap software: How I’d evaluate it

A roadmap tool won’t save a fuzzy strategy. It can save you from twelve conflicting slide decks. Here’s how I’d evaluate product roadmap software as a PM who still wants the roadmap to be true. Wave4 roadmap-software marker Sep23 What roadmap software is for Give the org a living view of themes, bets, and sequencing—connected enough to delivery that it isn’t fiction. Useful capabilities usually include: Timeline / now-next-later /...

Best product management tools: How I’d choose a stack

Tool lists age fast. Capabilities converge. So I won’t pretend a frozen “top N” ranking stays true. Here’s how I’d build a PM stack and which categories actually matter. Wave5 PM-tools marker Sep23 Categories I’d cover Category Job to be done What good looks like Collaboration / specs Async decisions that don’t die in chat Docs + comments with owners and dates Roadmap / discovery Intent, opportunities, prioritization Themes and...

What is Agile?

Find a guide to learn more about What is Agile?

RACI for PMs

RACI is a way I clarify roles around a task or decision: who is responsible for doing the work, who is accountable for the outcome, who should be consulted before it happens, and who should be informed afterward. I use it when ownership is unclear or when a cross-functional effort keeps producing duplicated work, missed approvals, or surprised stakeholders. RACI is not a replacement for judgment, trust, or communication. A...

Qualitative research for PMs

Qualitative research helps me understand how people describe a problem, work through a task, and make tradeoffs in context. I use it when I need depth: the language customers use, the workaround behind a request, or the reason an apparently simple workflow feels difficult. It does not tell me how common every observation is. It gives me material for forming and refining hypotheses, not permission to generalize beyond the evidence....

Customer shadowing for PMs

Customer shadowing is a research practice in which I observe a person doing real work in the context where the product is used. I pay attention to the task, environment, handoffs, tools, interruptions, and workarounds around the visible interface. A conversation can tell me what someone remembers or believes. Observation can show me what the workflow requires when the person is busy and the ideal path is not available. I...

What is DevOps?

Find a guide to learn more about What is DevOps?

Continuous integration and delivery: How I’d connect code to product learning

Define the two practices clearly I think of continuous integration as the discipline of integrating small code changes into a shared mainline frequently, with automated checks that reveal problems early. Continuous delivery extends that discipline so the product remains in a releasable state and a team can move a validated change toward users when the product decision calls for it. I would keep continuous deployment distinct as well. Deployment is...

Continuous integration: How I’d make integration a team habit

Treat integration as part of the work I would explain continuous integration as a team habit: integrate small changes into a shared codebase often enough that conflicts and defects are discovered while the context is still fresh. It is not simply a server that runs after someone pushes code, and it is not a substitute for thoughtful design or testing. I would agree with engineering on what the integration checks...

What is Product Analytics?

Find a guide to learn more about What is Product Analytics?

Experiment velocity for PMs

Experiment velocity is the pace at which a product team turns a meaningful question into evidence and a decision. I do not define it as the number of tests launched. A team can run many experiments and learn very little if the questions are weak, the instrumentation is unreliable, or decisions are left waiting in a queue. I care about shortening the path from uncertainty to responsible action. I use...

A/B test sample size for PMs

A/B test sample size is the amount of information I plan to collect before deciding whether a controlled comparison can answer my product question. I treat it as a planning decision, not a number I search for after the test has started. A sample-size estimate depends on the outcome, the baseline behavior, the change I need to detect, the uncertainty I will tolerate, and the traffic available to the experiment....

Statistical significance for PMs

Statistical significance is a way of describing how surprising observed data would be under a specified null model and analysis plan. I use it as one piece of evidence in a product decision, not as a synonym for importance, truth, or customer value. A statistically significant result can be too small to matter, while a useful effect can remain uncertain when the experiment is underpowered or noisy. This distinction matters...

What is Product Design?

Find a guide to learn more about What is Product Design?

Prototype for PMs

A prototype is a representation of a product idea that lets me learn before I commit to building the real thing. It can be a sketch, a clickable flow, a role-play, a coded slice, or something else that makes a question observable. I do not judge a prototype by how polished it looks. I judge it by whether it helps me learn something important with less cost and risk than...

Usability testing for PMs

Usability testing is a structured way for me to observe people attempting tasks with a product, prototype, or service. I use it to learn where the experience becomes confusing, what people expect to happen, and whether the design supports the intended goal. I am not testing a person’s intelligence, and I am not asking a participant to approve my design. I am testing whether the design communicates enough for someone...

Design sprint for PMs

A design sprint gives me a short, structured way to investigate a product question before I commit a team to a longer build. I use the idea when the decision is important, the problem is still fuzzy, and a small group can learn more by working together than by scheduling another sequence of disconnected meetings. The sprint is not a shortcut around research or engineering. It is a way to...

What is Product Development?

Find a guide to learn more about What is Product Development?

Product requirements document (PRD) for PMs

A product requirements document (PRD) is the shared brief I use to explain a product problem, the people affected, the outcome I want, and the boundaries around a proposed solution. I do not treat it as a contract that predicts every implementation detail. I treat it as a decision and communication tool: enough context for design and engineering to make good choices without asking me to dictate every choice in...

Dogfooding for PMs

Dogfooding means using the product I help build in a real work context. I value it because direct use can reveal confusing language, broken transitions, missing defaults, and operational friction that a plan or demo may hide. I do not treat dogfooding as proof that the product works for every customer. It is one source of evidence, and it becomes more useful when I define its limits. I use dogfooding...

Release notes for PMs

Release notes are part of the product experience, not a ceremonial list I publish after the real work is done. When I write them, I am helping customers understand what changed, why it matters to them, and what they should do next. A good note can reduce surprise, invite useful feedback, and make a product decision easier to discover later. A vague note can create confusion even when the underlying...

What is Product Led Growth?

Find a guide to learn more about What is Product Led Growth?

What is growth product management? my practical take

People ask me: "is growth product management right for me?" Fair question. Growth PM looks shiny until you realize your backlog is mostly experiments, funnels, and "why did activation drop 4% last week?" Here's my practical take on growth product management. What growth PM is Growth product management focuses on reducing barriers between users and value—so more people find, start, stick with, and expand in the product. You're optimizing the...

What is product-led growth? how I’d explain PLG to a product team

Product-led growth gets tossed around like a religion. I've seen teams slap a freemium toggle on a sales-led product and call it PLG. That's not the game. Here's how I explain product-led growth when a product team asks whether they should chase it. What PLG actually is Product-led growth is a go-to-market motion where the product is the primary driver of acquisition, activation, conversion, and expansion—not a human sales cycle...

What is Product Marketing?

Find a guide to learn more about What is Product Marketing?

Product engagement score: How I would measure meaningful use

Define engagement before measuring it I would not start by searching for one engagement number. I would first define what meaningful use looks like for this product and for the customer problem it is meant to solve. A user can click frequently without reaching value, while another user may need the product only occasionally and still depend on it. I would write down the behavior that represents progress, the audience...

Customer experience: How I would improve the whole product journey

See the journey, not one touchpoint I think of customer experience as the customer’s end-to-end relationship with a product or company: discovering it, deciding whether to try it, getting started, using it, getting help, renewing, expanding, or leaving. I would map that journey before choosing an isolated interface change or a single satisfaction number. For each stage, I would ask what the customer is trying to accomplish, what they need...