Document. Refine. Repeat! Mastering the Product Process.

280 Group

Market Needs and Product Description documents are created, along with a theoretical product roadmap. Product development teams, executives, operations teams, and sales all contribute to these documents. . Document, Refine, Repeat! . The post Document. “What if?”

Documentation is Not the Enemy

The Product Coalition

documentation product-management business-analysis‘Let me just spend 1 hour playing around with the app so I can figure out what happens when the user is logged in…and they have this… Continue reading on Product Coalition ».


Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

What Should Be in your Product Requirements Document

The Product Coalition

product-manager product-management product-development documentation startupA guide for you and the team before you build the product Continue reading on Product Coalition ».

Product Ops: Lessening the Need for Product Requirements Documents


Implementing product ops at your company will reduce your team’s need to produce clunky, one-way communication vehicles like the product requirements document (PRD). the product requirements document, and why would you ever want one? Product ops professionals document the good stuff.

How to Sell Your Roadmap to Your Leadership Team

Speaker: Brett Truka, CEO, Devetry

A product roadmap needs to both capture your product’s strategy and outline your execution plan. Because these documents are such an essential component of your job as product manager, you also need to strategize your roadmap presentation. In other words, you need to speak your executive suite’s language. In this webinar, Brett Truka, CEO of Devetry, shares his experiences and advice on how to successfully sell your roadmap to your leadership team.

What Is Good Documentation, Anyway?


This is a serious question and one you should be asking yourself regarding documentation. As product people, we act as the keepers of documentation throughout every stage of the product development process. Read more » The post What Is Good Documentation, Anyway?

Writing An Effective Six-Pager Product Document

The Product Coalition

Effective Documentation Strategy for Product Managers Photo by Daian Gan from Pexels It takes me five days to come up with a fifty- pager Product Documentation and ten for a six-pager! Writing a one-pager, or a six-pager product documentation is as difficult.

Don’t let your first Product Requirements Document be your last

Mind the Product

This post shares some fresh research on how product managers are feeling when writing a Product Requirements Document followed by a practical tool to hopefully solve this problem.

The Exceptional Product Requirements Document

Actuation Consulting

Last week we covered the basics of the Product Requirements Document (PRD). This week I’ll lay out the eight things that set a PRD apart as a highly useful document. Deliver these eight, and you’ll have a document that smoothes out development and leads to a positive outcome. Deliver These Eight for an Exceptional Product Requirements Document. The document does not require the reader to fill in gaps.

Product Requirements Document (PRD): A Guide for Product Managers

The Product Coalition

Every product manager, at some point in her career, has written and read a product requirements document (PRD) in some form. Continue reading on Product Coalition ». product-manager product-requirements product-management

It's Alive! Bringing Your Product Roadmap Back From the Dead

Speaker: Lisa Mo Wagner, Product Management Coach, Writer, Speaker and WomenTech Ambassador

In this webinar, Lisa Wagner, Product Management Coach, will teach you how to create an effective outcome and data-driven roadmap that allows you to implement customer feedback in a timely manner.

3 Reasons You Don’t Need a Sales Discovery Document for Every Product


Do you recommend a sales discovery document for each product? 3 Reasons You Don’t Need a Sales Discovery Document for Every Product. You don’t need a product-specific sales discovery document for that.

Why Your Software Project Needs a Product Requirements Document

The Product Coalition

Those who have worked in the software industry for a while have likely witnessed a project that went off the rails. Lack of vision… Continue reading on Product Coalition ». project-management software-development product-requirements prd product-management

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 a Product Requirements Document (PRD)

PMLesson's Ace the PM Interview

As Product Managers, we write a product requirements document (PRD) to answer a few key questions: Why are we working on an initiative? Supporting documents: you'll work with your design and engineering counterparts to define the interaction design and technical implementation of the solution.

Data Science Fails: Building AI You Can Trust

The new DataRobot whitepaper, Data Science Fails: Building AI You Can Trust, outlines eight important lessons that organizations must understand to follow best data science practices and ensure that AI is being implemented successfully.

The Indispensable Document for the Modern Manager

First Round Review

To build the strongest teams from the get-go, PatientPing Co-founder and CEO Jay Desai has written the definitive user guide — on himself. Read on to see how his tactical framework creates the bedrock for productive employee/manager relationships. Continue reading at First Round Review »

How we built this: User Interviews’ Document Signing


Since 2015, User Interviews has helped researchers talk to their users, gather feedback, and make better product decisions.

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.

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.

How to Create Effective Requirements Documents

The Product Coalition

Hint — focus on the problem and not on the solution Continue reading on ». business product-design product-management startup requirements

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. We as product people know that it’s in everyone’s best interest to document everything but we don’t want to spend too much time & effort in it. You don’t want to stress over finding a document. All the edits are in one place, no need of saving a document in your computer.

How to Write Product Requirements Document


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.

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


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.

How To Write A Business Requirements Document (BRD) – Detailed Steps

The Basics of Product Management

A Business Requirements Document is the foundation of any successful product launch. In every organization, the product team is the primary team that is responsible for preparing the business requirements document. What Is A Business Requirements Document (BRD)?

Introducing Document Signing—Automate getting NDA’s signed, no back and forth needed


Introducing Document Signing—our newest feature that makes it super easy to get your NDA or release form signed by participants so you can focus on the research itself. No more chasing down document signatures, or cancelling sessions with participants who didn’t sign your document

Maslow’s Hierarchy of Needs for Developer Documentation

The Product Coalition

How to write a dev doc that fulfills your reader’s deepest needs. Continue reading on ». writing-tips writing technical-writing technology product-management

The Indispensable Document for the Modern Manager

First Round Review

To build the strongest teams from the get-go, PatientPing Co-founder and CEO Jay Desai has written the definitive user guide — on himself. Read on to see how his tactical framework creates the bedrock for productive employee/manager relationships

Using Process Mapping to Document your Roadmapping Process


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.

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. There is a common misconception that documentation should be done away with entirely in Agile development. There should still be some documentation. Agile Documentation Basics.

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. Hiten Shah Whilst researching how other early-stage startups communicate their product vision and proposed features, I found a great podcast episode from Drift discussing their “one-pager” document. After listening to the podcast, I thought I would have a shot at creating my own document.

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

Sachin Rekhi

The process I've used involves documenting your initial product/market fit hypotheses, systematically validating each of the most uncertain hypotheses, and continually iterating on and updating those hypotheses as your team learns through customer validation, MVP launches, and future product iterations. Here is what I typically capture when initially documenting a startup's product/market fit hypotheses: 1.

Even in agile you should use a Project Initiation Document

The Product Coalition

When you think of Project Initiation Documents, or PIDs, you think of Prince2 project management, and the need to document a variety of… Continue reading on ».

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. The positioning document is a very simple one-pager which serves as a communication tool between product manager and product marketing manager.

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. This means that every time developers update the code, they’re prompted to document it immediately. ProductTank San Francisco Uncategorized Video API API-first Business model Documentation SDK

‘How To’… Create User & Buyer Scenarios


They are used during the product planning stage to reduce higher level market problem descriptions into smaller problem chunks where the more detailed requirements can be identified and documented. Once all the user and buyer personas, scenarios, goals, tasks and problems have been collated and mapped out then the information can be easily packaged up into a Market Requirements Document (MRD). Updated June, 2020.