This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Here are her 10 tips for developing useful handover documents that not only capture where the product is today, but also serve as an evergreen go-to reference for anybody wanting a contextual overview. Read more » The post 10 tips for writing good product handover documentation appeared first on Mind the Product.
The team conducted 72 tests in seven days, meticulously documenting each attempt. However, by returning to their documentation the next day and deeply studying why each attempt had worked or failed, they discovered that they had misinterpreted the results of test number 13.
In this Sunday Rewind post, we go all the way back to the pre-pandemic days of March 2016 when Martin Eriksson shared his thoughts on why Product Requirement Documents (PRDs) don’t always work. [.] Read more » The post SUNDAY REWIND: Product requirement documents must die appeared first on Mind the Product.
Product Roadmapping Once product positioning is established, product managers move into the more action-oriented activity of roadmapping. This planning phase requires careful consideration of multiple contextual factors that significantly impact how roadmaps should be developed and managed.
Save time and increase efficiency with print-shop ready documents. In this eBook, you will learn how to deliver print shop-ready documents, save time, and ensure your work looks equally good in print as it does on screen. Learn step-by-step ways to set up PDF documents for pre-press and print.
A step-by-step guide to generating accurate marketing materials with your existing product documentation and AI. Read more » The post How to use existing product documentation to generate marketing materials using AI appeared first on Mind the Product.
The AI tool supports this process by: Providing prompting questions to spark discussion Suggesting potential angles teams might have missed Organizing ideas into structured formats Documenting key insights for later reference During the workshop, my team worked on the question, How do I use the space I have in my yard to create a garden?
Era of interactive, conversational documents is just around the corner, ready to transform the way we search, learn, and work. The corporate landscape is teeming with PDF documents. In the realm of clinical trials, for instance, the lion’s share of documentation is stored in this format. Can Adobe make a bold move?
An ultimate approach to Design Documentation Managing projects efficiently is crucial to keep your work process moving smoothly. This is where a Design Documentation Notion Template comes into play. Why Use a Design Documentation Template? Project Overview Start by filling out the Project Overview section.
Because these documents are such an essential component of your job as product manager, you also need to strategize your roadmap presentation. Brett will cover how to prepare, present, and follow up on product roadmaps, with actionable takeaways and insightful tips around documentation and communication. The common ways to realize ROI.
Product Requirement Documents (PRDs) are important, but there are certain tips and tricks to ensure they reach maximum value! Continue reading on Product Coalition »
Here’s my approach when working with companies in this situation: Document what you’ve learned from conversations and observed from previous prioritization decisions in a strategy memo format. The metrics people care about reveal true priorities. Sometimes, despite asking all the right questions, strategy remains fuzzy. What gets killed?
At Proscai, I had the task to build a new Point of Sale (POS) solution for our clients and these three phases along with its corresponding documents helped me plan the development process and make sure all the team and stakeholders understood why, how and what we were building. Define Product Vision and Strategy.
– and, although we wish it were true, one message or document doesn’t work for all groups. Product Managers must be able to communicate to a variety of people across different departments – stakeholders, developers, designers, marketing, leadership, etc.
Risks can't be eliminated, but they can be mitigated through structured assessments, clear documentation, and expert guidance. Effective risk management in product development balances safety, compliance, and opportunity. Engaging specialists ensures efficiency, regulatory adherence, and product security while reducing costly oversights.
It is customary for strategy documents to be living documents, and frequently modified as the product manager receives input and feedback from three main areas: the market as a whole, customers specifically, and voices from inside the company. What systems/metrics/processes do we need to measure and track winning?
The software requirement document template or the SRS document template are the outline of the plan that needs to be followed while developing your software application. What is a software requirement specifications document? SRS documentation is crucial in the healthcare software development niche.
When I need to take a break from writing, I save the document. But the ability to save the document is a feature, a part of the overall product. A feature owner is an individual who owns a capability end users can interact with, for example, the ability to persist a Word document or to edit it. Word is the product.
AI and Strategic Planning Your strategic plan is little more than the collective information from the markets and your value-based opportunity analysis assembled into a document with your investment decisions, plus the execution tactics from other disciplines required to make it happen. You don’t even have to create the document.
The game-changing potential of artificial intelligence (AI) and machine learning is well-documented. Any organization that is considering adopting AI at their organization must first be willing to trust in AI technology.
When proposing redesign to stakeholders, you should prepare a document that will create a proper context for them and provide answers to the most common questions they likelyhave. Note that you dont have to provide an in-depth explanation of the reasoning right in the introduction; you will do it later in the document.
Help your team adapt and keep clients aligned with these documents, meetings, and conversations. Roadmaps are altered by user feedback, new strategies and changing client needs. In a recent live stream from one of our mentors of The Product Mentor , Andrew Hsu, lead a conversation on this topic.
“It’s always a good idea to share a document detailing the rollout and rollback plans with the team”. Document and share your plan and actions. We use GitHub Issues (we call them tracking issues here at Intercom) to share context and document every step we take during the rollout in comments.
This document can be used to communicate quarterly objectives that you hope to achieve. If done correctly, this document can be a powerful tool that motivates your design & engineering team by setting ambitious yet achievable & well-planned goals. For more details about Theme, Epic, and User Story, refer to this article.
Speaker: Michael Veatch, Senior Director, Implementations & Ella Aguirre, Director of Solution Consulting
You'll walk away from this session with: An understanding of the critical elements of a payments implementation framework that drives sustainable business growth 📈 An inside look at a digital-first implementation and why it works best for software platforms compared to a DIY documentation approach 🛠 Knowledge of best practices for creating (..)
AI can help in many parts of making a product, from research to writing product plans and documents. He shares that product managers are reporting efficiency gains of around 50% when using AI to assist in drafting these important documents.
With her help, I wrote the first strategy document for Headspace, which eventually led to the complete reimagination of Headspace , maximizing growth for our guided mindfulness product and adjacent spaces. Instead, they’re meant to help the reader understand the strategy document better. Here is a template for that document.
I haven’t had much luck in showing my raw documents and notes to stakeholders–they can’t consume this. I try to get this into my product reference document and have it passed around to marketing, comms and product before heading to engineering. It forces me to articulate why the roadmap items exist on the roadmap. .
One of the barriers to high performance is creating documentation. The emotions associated with teams creating documentation, which is a conduit to sharing knowledge, were very negative. It takes a long time to create documentation. You go through your process and we create the documentation for you.
Speaker: Lisa Mo Wagner, Product Management Coach, Writer, Speaker and WomenTech Ambassador
A product roadmap is a living document, a snapshot in time that is subject to frequent change. This strategy is ineffective for developing a valuable product because it does not consider the volume of customer feedback. As a result, teams will fail to implement customer feedback in a timely manner, resulting in incorrect feature development.
We write a document that evolves over four to six weeks during which all of the leads from different teams contribute. We tap into all of that to write the vision document. [8:27] The document includes at most two pages about the vision. The strategy document provides North Star metrics. At Amazon, they call this PRFAQ.
The primary tool that we use is the PRFAQ document, short for press release and frequently asked questions. When someone has an idea for a product or service, the first thing they do is write a PRFAQ document. 8:55] Do you involve the customer in writing the PRFAQ document? 15:50] Why have a meeting about the PRFAQ document?
Document issues or friction points. The biggest trap is to fix everything before you even know whats broken or whos on your side. Instead: Fill Your Calendar with introsfrom sales directors to back-end dev leads. Meet Each PM individually to see where theyre swamped or excelling. What if your team only respects hierarchies?
And then the product manager turns around, writes typically long requirements documents , and then hands that off to the rest of the team. The product manager gathers requirements, documents them, a designer creates a design based on those requirements, and the engineers build software based on those requirements.
Document your Key Assumptions. If it’s a senior PM, it may be showing an exciting opportunity to VPs or CPO. If it’s executives, it may be what they need to present to the board. To achieve success, you need to understand how success is defined.
Product managers would spend their time searching for documentation on performing basic functions like our routine cadence for team meetings, getting executive approval on a project initiative, and other general product development process tasks. Cross-team dependencies got more complex and took longer to resolve with more people on our team.
This screenshot shows how Edwin can take a quote from a document he’s uploaded to the “Interviews” section of Vistaly and then highlight things to send directly to specific parts of the opportunity solution tree. Click the image to see a larger version.
Product design process cheatsheet by Prophecy Product Design Cheatsheet is a helpful document created by Prophecy that provides a step-by-step workflow for product development, focusing on 6 key stages of the design process. Document the changes or features that need adjustment based on user feedback.
There's work to be done. -- 2016: "I want a product manager who can be great at writing specification documents. It sounds like something we should be doing." 2019: "If someone says 'that's not agile' one more time I'm going to quit" We took some things a little too far, without really understanding them. Where do I find them?"
Its also good at analyzing complex documents (like multi-page PDF reports) and extracting specific data fromthem. Claude AI Claude has a few advantages over ChatGPT, such as ability to provide thoughtful technical assistance with tasks like coding and math.
In my company, we review a living document with our management chain on a quarterly basis to align business direction for the short-term (immediate one to two quarters) to the long-term (two to five years). To summarize the process, I advise you to start the document by focusing on defining the problem.
Less than 1% have documented competencies with scorecards for rating performance. Many competencies we care about weren’t documented. Problem: Many competencies we care about aren’t documented. And many organizations, unfortunately, don’t make it any easier. We held people accountable for outcomes they don’t control.
Replace lengthy PRD templates with evolving, checklist-based documents to simplify the product management process and improve team collaboration. Read more » The post Ditch the PRD template and embrace the PRD checklist appeared first on Mind the Product.
We organize all of the trending information in your field so you don't have to. Join 96,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content