Trending Sources

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

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

High Octane Product Management

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

Three Superpowers of a Product Manager

Mind the Product

They show what has worked for us successfully day in day out, and demonstrate that the powers of a PM boil down to communication, documentation and data! But please note that release notes are not meant as a user guide – level up your documentation powers for this weapon of choice.

The Evolution of Modern Product Discovery

Product Talk

The days of gathering requirements from business stakeholders and documenting them in long product requirements documents are vanishing. We weren’t building what they wanted because product requirements documents are a terrible way to communicate.

Innovation begins with observation

Under10 Playbook

Just document it and they'll get the gag. In a recording session, Mick Jagger complained about Bill Wyman’s bass playing. After Jagger walked away, Wyman asked Keith Richards what to do, Richards whispered, “Just play what you were playing before.”

Product Roadmap Success: BWP Hosts Lively Roundtable Discussion

bpma ProductHub

According to Richard Banfield of Fresh Tilled Soil, a successful product roadmap is a strategic document that focuses on the product vision and conveys the path to achieve it.

The Ideal Product Marketing Candidate for B2B

High Octane Product Management

Understands the purpose of presentation slides – a series of visually appealing cue cards that tell a compelling value story, not product documentation in PowerPoint format! Wealth made simple: news and articles from IRC Wealth. This sample product marketing job description just might ruffle a few feathers. First, it’s not your typical “get the product off the shelf” job description. Second, there may be people in product marketing roles that don’t meet the requirements.

B2B 75

Be in a Band, not an Orchestra: how to Grow an Agile Product Team

Mind the Product

At this point each team had its own roadmap, but they were agreed together on a three-monthly cycle and shared with our partners in a nicely transparent document. The key thing to remember with a roadmap is that the document itself is uninteresting.

Agile 92

Ask Steve: How to deal with tiered pricing

Under10 Playbook

The team license however includes the ability to share documents; for example, one product manager can use another product manager’s persona definition. A2A: In a typical tiered pricing scenario, buying 101 seats in Tier 2 is cheaper than buying 100 seats in Tier 1.

Product Management for Dummies

Product Bookshelf

Writing, documenting and discussing the positioning statement, personas, and segments not only develops clarity for the team, but highlights challenges and opportunities with the current offering. Not just for dummies, this book is for everyone.

Books 33

The Dirty Dozen Roadmap Roadblocks

Product Powers

A good product roadmap is one of the most important and influential documents an organization can develop, publish and continuously update. It’s the one document that steers the entire organization in delivering on the company strategy. It's key to success, and yet many organizations struggle to produce effective roadmaps. In fact, many organizations don’t create one, even to publish internally. Or they do, but it is simply a collection of unrelated features and dates.

10 Product Insights You Should Have Read in 2016

Mind the Product

Product Requirement Documents Must Die. Product Requirement Documents are simply the worst possible way to bridge the gap between the customers’ needs and the team that are trying to build the solution.

The Rise of Modern Product Discovery

Product Talk

The product manager interviews key stakeholders to understand what they need, documenting what they find. I love that Marty Cagan and Jeff Patton have long been advocates of dual-track development.

The best roadmap isn't a big effort

Under10 Playbook

The roadmap has become one of the most commonly requested—yet frequently misunderstood—documents in the product manager’s arsenal.

Selling Vs. Learning

Mironov Consulting

I talk with product managers all the time, and always ask whether they are talking directly with end users and target customers. The most frequent response from enterprise product managers is “Of course! I’m on sales calls two or three times a week.” .

Why Write Requirements

Tyner Blain

Don’t just follow some prescription and go through the motions of documenting requirements. The simple act of documenting requirements based on your understanding of market needs will identify opportunities to improve your understanding of your market.

Let’s stop calling it software engineering

Under10 Playbook

As with authoring books, managers can try to control the creative process with documents and schedules and plans. Much of the language of software creation is based on the manufacturing metaphor. We “plan” software. We “engineer” software.

Features do not a Product Roadmap Make

Tyner Blain

All of the different containers for requirements document “what” the team will be building. Last month, Mike Smart of Egress Solutions and I gave a webinar for Pragmatic Marketing on product roadmapping when working in agile environments.

Launching Complex Products in International Markets

Mind the Product

Tax, legal documents, data privacy, pricing, billing, cancellation policies and recruitment will all vary from country to country.

Let’s Fire a Few of Our Customers

Mironov Consulting

Of course, we’ll need it to get FAA approval, find a couple of airline reference customers, port it to Airbus’ FlightOS, adjust for national/regional speech patterns, switch from batch to real-time processing, secure it to meet DOD 8500.01E and author new training/installation documents.

TEI 094: Creating product roadmaps for product managers – with Jim Semick - The Everyday Innovator – Resources for Product Managers and Innovators

Product Innovation Educators

A product roadmap is usually a visual document and communicates the why behind what you’re doing. With static tools, you create a static document. A product roadmap is usually a visual document and communicates the why behind what you’re doing.

Third-Party Software Integration: Best Practice, Perils and Pitfalls

Mind the Product

If your product supports multiple integrations, you’ll thank yourself for the good documentation down the line. Everything you build in house will need testing, documentation, support, maintenance, etc.

BOM: Product Portfolio

Pragmatic Marketing

That means crafting a business plan, positioning your portfolio, aligning to your customers’ buying process, and writing a market requirements document and marketing plan. January’s Box of the Month is the product portfolio.

Why Drawing Maps Sharpens Your Thinking

Product Talk

We get pulled in many directions, leaving little time to update documents. “Could it have been the drawing of maps that boosted our ancestors beyond the threshold which the other apes just failed to cross?”. – Richard Dawkins.

Outside-In User Story Example

Tyner Blain

This story has the “feel” of a programmer who is writing the code first, and then documenting the design second. Being “outside-in”, “outcome-based”, and “market-driven” is particularly important for creating successful products.

Requirements, Roadmaps & Rollouts: The B2B Product Manager Magazine, February 2017

High Octane Product Management

How Much “Market” Is In Your (MRD) Market Requirements Document? The February Issue of The B2B Product Manager is now available. In this issue we cover everything from requirements to roadmaps to rollouts. We also throw in a few tips for hiring the best Agile Product Owners, and a universal product management framework that’s been sitting right under our nose.

First Things First: How Does A Product Manager Start?

The Accidental Product Manager

Sorry, you’re not going to find this documented in your product manager job description. Product managers need to know how to get things started Image Credit: Andre Chinn. So you are in the process of starting your brand new product manager job. Congratulations. Now what?

Optimize to be Wrong, not Right

Mind the Product

Writing the funding documents, roadmaps and dates, schedules and scope slowly starts to close your mind to alternative exit ramps off the highway to hell. Let’s be honest. We have no idea what is going to happen a year, a week, or even five minutes from right now.

Crafting a Creative Culture by Jeff Veen

Mind the Product

Group chat delivers a sense of communication compression and momentum, it removes hierarchy, he says, whereas email has a sense of creating documents and space to be filled.

What We Learned About Building Products People Love in 2016

Mind the Product

My own clarion call, Product Requirement Documents Must Die , asked that we should once and for all stop wasting our time by writing product requirement documents and focus instead on a more efficient, collaborative and iterative process for product development.

Are You a Naughty Or Nice Product Manager?

Mind the Product

Product Requirement Documents made sense in the age of waterfall, and arguably still do make sense in certain, highly-specific niche cases.

Interview: Advice for the Innovator’s Dilemma with Paul Young

bpma ProductHub

Of course, you also have to document what you learned and share that with the rest of the team. Interviewed by Lance Morganelli.

Roadmap Alternative FAQ

svpg

This is a document that is managed by the delivery manager, but the only one that can typically add an item to this is the CTO/VP Engineering. In my prior article I discussed my favorite alternative to conventional product roadmaps. That article seemed to strike a chord in people, and I received quite a bit of very positive feedback. However, I also received more than a few questions. This didn’t really surprise me because as I said in the article, this is not a minor topic.

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.

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.

The Universal Product Management Framework: 3 Questions and an Org Chart

High Octane Product Management

If you’re in product management , the answers to these questions are the foundation of your requirements documents, product plans, user stories, etc. Wealth made simple: news and articles from IRC Wealth.

Inspiration: There cannot be a stressful crisis next week.

Under10 Playbook

With so much time focused on operational issues and emergencies, when are you going to work on the critical core documents that drive your product strategically? However, I've always kept a binder (or a folder) filled with the living documents of my product.

The Lean UX Process

Product Bookshelf

Lean UX focuses on shared understanding that is embodied in working software which can be tested with users rather than detailed design documentation. The first step of the process is to document and review your assumptions.