How to document like a pro being a product manager?

The Product Coalition

Tools & tips that will help you with a good system and methods for documentation. When you find some time sitting by your desk you spend it documenting all the actions, decisions, design etc. You don’t want to stress over finding a document.

Minimum Requirements Documentation: A Matter of Context

Johanna Rothman

A colleague asked me about the kinds of documentation the team might need for their stories. How little could they do for requirements documentation? I start with the pattern of Card, Conversation, Confirmation when I think about requirements and how much documentation. That's one way to create minimum documentation—break the story into usable pieces. If the PO writes stories or epics as problems to solve, the PO manages some of the documentation effort.

What is a Market Requirements Document (MRD)?

Actuation Consulting

Of all the documents you create while developing a new product or product extension the Market Requirements Document (MRD) is most important of all. It can be a simple document, a wiki, a spreadsheet, a unique software tool, or something else you devise to fulfill this important step in your process. T he Core of the Market Requirements Document. Documentation requirements – What are the types, formats, and delivery methods for documentation?

How to Write Product Requirements Document

NextBigWhat

The post How to Write Product Requirements Document appeared first on NextBigWhat. [link] There are four core sections of a PRD — defining purpose, describing features, setting release criteria, sketching rough timing. According to Marty Cagan, the PRD’s goal is to explain the “What”, not the “How”. In each section, remember to be clear on the problem being solved versus the solution otherwise you may lead the team to make incorrect assumptions.

Why “Build or Buy?” Is the Wrong Question for Analytics

implemented solution isn’t thoroughly documented. Backed by Documentation and Support: Partnering with a trusted third-party platform guarantees. documentation that allows for a seamless knowledge. WHY “BUILD OR BUY?” IS THE WRONG QUESTION FOR ANALYTICS Introduction.1

Who Should Own Product Documentation?

ProductCraft Debates

In a LinkedIn post, he suggested that if only we debated the question of who should own documentation, all would be well. Despite the dusty library feel of it, documentation is an important. The post Who Should Own Product Documentation? This week’s debate question came from a reader of ProductCraft who was responding to our debate on where design should sit.

Agile Misconception #2: We Don’t Need Documentation

Atomic Spin PM

Documentation means a lot of different things to different people. If you’ve used a waterfall software development process, you’re all too familiar with documentation. From requirements to systems architecture to design, you’re creating documentation at every step of the process.

Re-designing the Product Briefing Document from the Ground Up ???

The Product Coalition

Due to this increased communication overhead, we needed to re-think how we could improve communication, product workflows and handover documentation across our ever expanding teams. After listening to the podcast, I thought I would have a shot at creating my own document.

MRDs – How Much “Market” Is In Your Market Requirements Documents?

Proficientz – Product Management University

A Market Requirements Document That’s All “Market” Think of your MRD as the headliner to the product requirements. Save the “how” components for your product requirements document. The post MRDs – How Much “Market” Is In Your Market Requirements Documents? Wealth made simple: news and articles from IRC Wealth. Most B2B organizations use a M arket R equirements D ocument (MRD) for driving new solutions to market.

Using Process Mapping to Document your Roadmapping Process

ProductPlan

When a company hires a fancy management consulting firm to help them “optimize” operations, one of the first things they’ll do is document how things are currently being done. They will interview stakeholders and individual contributors, review documentation, and hold whiteboard-heavy meetings to unpack the current methods being utilized in the company. It will be a visual document that is light on text and heavy on process and flow.

A Lean Alternative to a Business Plan: Documenting Your Product/Market Fit Hypotheses

Sachin Rekhi

Here is what I typically capture when initially documenting a startup's product/market fit hypotheses: 1. But it's important to document why specifically you think you'll be able to create a solution that is ideally 10x better than the existing solutions on the market.

Hope for the best or prepare for the worst? How we manage critical incidents at Intercom

Inside Intercom

Over the past few months, we’ve been working on solidifying our incident response process and documentation. Training and documentation. Documentation is one of the most critical aspects of a solid incident management process.

Building an API that Developers Love

Mind the Product

Without documentation developers will have no clue where to start. For this purpose, they have developed Double Doc- a library that allows users to write the documentation in the code. ProductTank San Francisco Uncategorized Video API API-first Business model Documentation SDK

Tools to Help Product Managers Think Strategically and Commercially

Mind the Product

This first post covers Positioning Documents, which I bought to Onfido from Pragmatic Marketing training, and Line of Business Meetings, which Kevin brought with him. The Positioning Document and Line of Business meeting act as communication devices. Positioning Document.

Developing a PRD

Actuation Consulting

Essentials of a Product Requirements Document (PRD). In this week’s post, I’m going to discuss the nuts and bolts of the PRD (Product Requirements Document). What is a Product Requirements Document? A PRD is a document that serves the development team. Supports include such items as documentation, accessories, shipping, packaging, installation, replacement parts, and maintenance.

Marketing doesn’t stop when you’ve acquired a customer

Inside Intercom

Minimum viable documentation. No matter what product you’re taking to market, chances are you’ll need some amount of documentation to support it. When you’re working at an early stage startup with dozens of competing priorities, there’s a temptation to publish the quickest, easiest types of documentation (usually a series of hastily put together FAQs) just to try keep your head above water.

How should product managers write requirements?

Product Manager in Heels

Data documentation documents Requirements use cases wireframes workflowsA requirement is a short statement of the problem. Everyone has different ways to write requirements.

What PRD template provides a useful roadmap?

bpma ProductHub

Product Requirement Documents (PRDs) are documents product managers use to achieve several important objectives. By Daniel Wu’ – An ideal PRD discusses users, shows features in a visual prototype, and includes key hypotheses. They (1) create purpose and context for the teams they work with, allowing key stakeholders to feel heard; and (2) clearly communicate the vision.… … Product Strategy

Optimal Product Process™ 3.0 Phase Two: Plan

280 Group

Document planned changes for product strategy, directions and features in a product roadmap. Product Management completes the business plan and market needs documents. Product Marketing completes the market strategy document.

Writing Market Requirements Effectively

280 Group

Whether you are writing requirements for Agile and delivering user stories for the product backlog or writing a more traditional market requirements document, there is one technique that I have found can be very effective.

Optimal Product Process™ 3.0 Phase Seven: Retire

280 Group

If you are diligent, review and document what went well and what didn’t go so well. It also covers the roles, responsibilities, tasks and documents associated with each phase. This post describes the seventh phase in the Optimal Product Process: Retire.

Slite uses productboard to rally the team around what customers want

ProductBoard

Slite is a simple collaborative documentation tool that helps businesses stay organized and work more thoughtfully. Founded in 2016, the company’s simple tool acts a single source of truth for all internal documentation and processes.

Why I do the thing I hate

BrainMates

Given we all hate reading documents so much, why do I spend my life writing them? And don’t get me started on 60+ page documents. I write really, really long documents, despite my hatred of reading them! In this context, a document must add value. Documents 101.

Create an Opportunity Definition

Under10 Playbook

Spending more than a day completing a business document for an idea that won’t go forward is waste. That’s why many teams use a one-page definition document to profile the opportunity.

Waterfall or Agile? It Turns Out It Really Doesn’t Matter.

Sequent Learning

We were the epitome of a linear-driven organization with our phased scoping documents, business cases, product requirements documents (PRDs) and development plans. ? Waterfall or Agile?

Waterfall or Agile? It Turns Out It Really Doesn’t Matter.

Sequent Learning

We were the epitome of a linear-driven organization with our phased scoping documents, business cases, product requirements documents (PRDs) and development plans. ? Waterfall or Agile?

Inspiration: a simpler system that worked perfectly

Under10 Playbook

How many of these documents do you have? And now, no one can say what sections belong in which documents. And some parts go in multiple documents. Before you know it, you're not building a product; you're building a bunch of documents. Under 10 documents.

What are your ten templates?

Under10 Playbook

And planning doesn’t mean people locked in their offices, thinking deep thoughts, and creating myriad documents that no one ever reads. I believe in minimal process, brief artifacts, and living documents. These living documents are the ones that I reference often.

Optimal Product Process™ 3.0 Phase Four: Qualify

280 Group

It also covers the roles, responsibilities, tasks and documents associated with each phase. This post describes the fourth phase in the Optimal Product Process: Qualify. Download the entire Optimal Product Process Ebook 3.0: CLICK HERE.

The most powerful method for training the sales force

Under10 Playbook

I recommended that he answer the questions in print, share the document on the sales portal for all sales people, and refer them to that document if they called. Sadly, the use of “Confidential” on a document almost guarantees that customers and competitors will obtain it.

TEI 236: The best tools for managing virtual product teams – with Jonathan Soares

Product Innovation Educators

We’ll usually receive designs, technical documents, or a high-level scope of work ahead of time. Every organization and its documentation is different. Thinking through your requirements and documenting them is a great first step.

Engineering led? What to watch for

The Product Bistro

Documentation: This is one of the conundrums of the world. Engineers love detailed documentation. They will read chip documentation, compiler and CPU errata tables, and in general get very intimate with the hardware they are designing. However, they loathe the requirement to create usable end user documentation. There are three principal types of companies: Sales led, marketing led, and engineering led.

Report templates for less status meetings

Folding Burritos

In others, it might be Slack, or a shared document/wiki page with a simple format that people know how to get to (and that you regularly remind me them to have a look).

Prianka Rayamajhi on aligning the Copper design team around a shared vision

Miro

We talked to Prianka Rayamajhi, an experienced Product Design leader, and asked her about the best practices for visually documenting and collaborating on cross-functional projects […]. Leading tech companies are often the first to test out innovative methods of work, so it’s no surprise that they’re also looking for ways to collaborate efficiently on complex projects.

Should Product Roadmaps Have Dates?

Roman Pichler

A product roadmap is a living document; it has to be regularly updated to account for the development progress, user data and feedback, and changes in the overall product strategy. What Product Roadmaps Are (in a Nutshell). To start with, let’s briefly recap what a product roadmap is.

Who Should Own Product Positioning?

Pragmatic Marketing

Positioning documents will define your product category, the problems it solves and the personas it serves. A positioning document contains the who and what. Marketing then leverages this foundational document to create solutions: campaigns, sales tools, web pages and so on. Product positioning is a key element of product management. Whenever I work with a new team, I always begin with roles and responsibilities. Who owns what?

Developing A Product Vision and Strategy

Actuation Consulting

Today we will look at two of the most important: the Product Vision and Product Strategy documents. Defining a Product Vision Document. The Product Vision document looks into the future. The Role of the Product Strategy Document. Your Product Strategy document explains what high-level actions will need to take place in order for your product to live up to the anticipated deliverables in the Product Vision document.

The Phenomenal Product Manager: Influencing Engineers – Part 3

280 Group

For a prima donna, when you are delivering a market requirements or product requirements document, or specifying some features, you may want to be less specific about how they should be implemented.

How Little Can You Do (& Still be Effective)

Johanna Rothman

In a regulated industry, the managers can advocate for more agile approaches with auditors and help clear the way from non-value-add documentation. Teams might need to supply some documentation, but not as much as people might think.). Back in Manage It!, I suggested that for requirements, the questions should be, “How little can we do?” ” and still have a great product. My argument was this: the longer the project (regardless of approach), the more risk there is.

Developing a Test Strategy for the Agile World

Centercode

Adam : I think people get too caught up in the fact that a test strategy does not belong in Agile because we want to “limit documentation.” For Waterfall, we will discuss breaking the habit of having excessive documentation just because we have the time to create it.