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.

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?

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.

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.

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

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 »

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.

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.

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

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

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?

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.

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.

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.

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

RealtimeBoard

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.

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.

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.

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.

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?

Product Manager Writing Skills to Grow Your Influence

Proficientz – Product Management University

If someone can scan through your document and come to the conclusion you intended, you’ve nailed it. How important are good writing skills for product managers? The short answer is, really, really important.

Optimal Product Process™ 3.0 Phase Three: Develop

280 Group

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

10 Time-Tested Tactics for Mobile Beta Test Planning

Centercode

The information you can glean from MRDs and PRDs (Marketing Requirements and Product Requirements Documents, respectively) can give you a headstart on test planning. Other Documents That Help with Mobile Beta Test Planning: Product plans. Product documentation.

8 Keys to Getting Started

Product Management Lessons from the Trenches

Review your advertisements, walk through the purchase experience, install and use the product, reach out for help via the support experience, read the documentation, etc. Review company documents and presentations.

B2C 195

How to Improve Business Case Accuracy (With Tools That Work)

Sequent Learning

It goes without saying that a product business case is one of the most important documents produced and managed by product managers. As you know, the product business case is a standard method used to justify investments in new products, enhancements, technologies, etc.

Technical Debt and Product Success

Roman Pichler

Why Technical Debt Matters for Product People. As the person in charge of the product, you may not be terribly concerned about how clean and well-structured the code is.

Vision 287

7 Free Citrix Optimization and Monitoring Tools That You Cannot Do Without

eG Innovations

The performance benefits of using Citrix Optimizer are documented in this blog by Login VSI: [link]. 7 Citrix Site Documentation Scripts. You may be asked to document the configurations set up in your Citrix site for delivery to a customer.

Tips for Rewriting a Digital Product

Roman Pichler

Capture your decisions and document the new strategy for your product, for instance by creating a new, forward-looking Product Vision Board. See the Rewriting Effort as an Opportunity to Innovate.

Vision 225

Announcing Agile 2.0.0 – The Newest and Bestest Agile Ever

Modus Create

No Documentation. The best part is that you never have to document anything. itself isn’t documented. Modus is pleased to announce Agile 2.0.0 We have taken agile to the power of two by applying Agile to Agile, and eliminating all the waste in software development.

Agile 67

The Role of the Product Management Champion (12 Tasks They Should Own)

Sequent Learning

Standards organizations produce guidelines, documents, and other items that […]. What is A Product Management Champion? An executive champion serves as an advocate for a specific activity, function, or center of excellence in an organization.

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.

The Anatomy of The Product Brief

Product Manager in Heels

A Product Brief is a stable, widely shared, "one-page" document describing the goals and benefits of a feature as well as the scope of a project. Key Links: Links to requirements documentation, wireframes/mock-ups, research, etc.

Would-Be Product Manager’s Instruction Manual

Product Management Unpacked

Document product requirements, user stories and artifacts to ?support People often describe a product manager as “CEO of the Product.”

Sustainable Pace in Product Management

Roman Pichler

Many years ago, I was discussing a lengthy requirements document with the product manager in charge of a healthcare product. What is Sustainable Pace? Sustainable pace is an important agile principle.

3 sins of implementing Agile

The Product Coalition

Documentation and testing are not Agile I have heard so many developers not wanting to do testing or documentation because those are not Agile. Relevant Agile Manifesto quote: Working software over comprehensive documentation.

Agile 78