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 ».

Documentation is a key when working remotely

The Product Coalition

The Coronavirus outbreak that led to massive remote work reminded me how documentation helps keep productivity Continue reading on ». productivity virus remote-working product-management documentation


Sign Up for our Newsletter

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

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.

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.

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.

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

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.

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.

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 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.

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

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 »

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.

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.

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 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.

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

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.

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.

‘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.

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 a simple Product spec can unify your company and make your product a success


Brainrants General Product Management Requirements product leadership product management Product Requirements Document Product spec stakeholder managementAs an Aussie-expat based in San Francisco, I briefly took a passing interest in baseball.

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. Even with the best documentation and the most robust processes in place, the reality is that outages are inherently unpredictable events where it is impossible to anticipate every situation you may find yourself in. Training and documentation. Documentation is one of the most critical aspects of a solid incident management process.

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.

5 Key Practices of a Successful MSP: #1 ? A Well-Defined and Documented Managed Services Strategy


Several months ago, I authored a five-part miniseries of Inside Technology Services blog articles, articulating the top mistakes made when starting a managed services (MS) business. The blogs were based on a TSIA Service Insight (research report) published for members in TSIA’s Managed Services discipline.

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. Products are becoming more focused on customer experience and who can get them to market the fastest, and companies who have the most effective requirements help get those products to market faster and with fewer defects.

To MRD or not to MRD …

The Product Bistro

In the modern era, it seems that product management and organizations have eschewed the venerable MRD or marketing requirements document. However, it still has a place in the toolkit, and it should be leveraged more often. product management

How Product Managers Can Lead Meetings Well

The Product Coalition

Here are some insights and lessons learned regarding how to organise meetings and your documentation well. Continue reading on Product Coalition ». product-management entrepreneurship meetings leadership productivity

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

Strategic Team Alignment: Elevating the Executive Gate Review [+Webinar]

280 Group

From the Directors and VP point-of-view, the Product One-Pager is an incredible document. When a boundary is documented, I expect the Product Managers to work incredibly hard to keep their products “in-bounds” and avoid a lot of uncomfortable meetings.