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
Doug joined us in episode 518 and is back to share battle-tested strategies that will help you fix problems faster and smarter. While corporate environments often expect perfect planning and immediate success, true innovation requires multiple cycles of creation, testing, and refinement. hours every day dealing with problems.
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.
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?
I ran into documentation that was incorrect. Do they pair program with their customers to understand where there are gaps in their documentation or their endpoint coverage? Do they usability test their API? So I started by searching for a Teachable API and found some documentation. Error codes were incomprehensible.
Guest post by Mark Mayo, Senior Quality Engineer at Terem Technologies This is the process of writing code and using tools to automate the user interface (UI) testing of front-end components of websites, desktop applications or mobile applications. But, getting it right goes beyond the coding of the tests and the tools you use.
Customer advisory boards arent just for updates – they should be used to test ideas, validate direction, and catch misalignment early. Asynchronous work requires structure – not just fewer meetings, but better workflows, clarity, and shared documentation. Want the Frameworks to Apply These Lessons?
It emphasizes the importance of understanding users and building, testing, and iterating quickly. These are some of the questions on the quiz that Eva and her CEO created to test employees’ understanding of Continuous Discovery Habits. Introducing Continuous Discovery Habits to Passion.io Click the image to see a larger version.
Depending on the country where the consumer is located, Chis company may need to request different documents from them in order to fulfill know your customer/know your business (KYC/KYB) requirements, an identity verification process thats used to prevent financial crime. This meant that not all orders were affected by this complexity.
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.
Inaccurate, Incomplete, or Insufficient Documentation By far the most common challenge engineers face when working with a new API is inaccurate, incomplete, or insufficient documentation. If that language is not well documented, then engineers wont know how to construct requests or interpret responses. Why does this happen?
Yet most product managers still rely on long documents, jargon-filled briefs, and clunky slide decks that dont land with the people who matter. Test if the story makes sense. 90% of executives say they prefer visual storytelling over dense reports. As Tom put it: Clarity beats polish every time. Show it to your team.
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.
Document your Key Assumptions. The information you gather doesn’t just have to be A/B tests. It can include many sources of information, user testing, anecdotal data from other teams, like sales or support, what your competitors are doing, and the instincts of your executives. Add new assumptions as you gather them.
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.
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. Prototyping Prototyping involves creating representations of your ideas to test with real users.
Each solution has a status attached to it as well, so its easy for the team to track whether theyve done any assumption testing or taken any other action related to any given solution. Potential solutions Below the opportunity layer, Vistaly allows them to create potential solutions that are linked to specific opportunities.
Test with diverse participants: Pilot your survey with users from various cultural backgrounds to identify and address cultural blindspots. How to avoidit: Document assumptions: Clearly outline your assumptions and hypotheses in your researchbrief. Have you done a pilot test of your questions?
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). The idea is to treat the strategy as a prototype that will undergo many iterations and testing. Testing the Proto-Strategy.
We believe there’s only so much you can do with automated tests and pre-production environments. We encourage engineers to observe and test the changes they ship in production using little tricks like Slack notifications upon deployment completion. Document and share your plan and actions. Why do we ship fast?
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.
Plugging in: how to generate insights Analysis: how to prioritize and understand feedback Communication: how to synthesize information Test/Build/etc & then repeat. I haven’t had much luck in showing my raw documents and notes to stakeholders–they can’t consume this. The feedback loop process is. It’s cyclical. Get Insights.
In a waterfall process, the product manager gathers requirements (typically from internal stakeholders ), writes up a requirements document, and hands it off to the designer. The designer then attempts to do the design work required in the requirements document. The designer gets a new requirements document.
AI can help in many parts of making a product, from research to writing product plans and documents. The future of product management will involve using more AI tools, like advanced language models and creating fake data for testing. AI can help in many parts of making a product, from research to writing product plans and documents. *
Release notes are documents that accompany a new product or update release. Here are the most common types of release notes: Software release notes : These documents summarize changes made in a new software release. Product release notes : These documents provide an overview of changes made to the broader product.
Document issues or friction points. Use contractors for short, specialized taskslike user testing or a big platform migrationbut keep strategic continuity in-house. The biggest trap is to fix everything before you even know whats broken or whos on your side. Meet Each PM individually to see where theyre swamped or excelling.
Lets say youre testing a longer onboarding flow after a feature release and tracking results through your analytics platform. This proves that even if the test results look promising, your data is skewed, and the rollout hurts your key segment. Build internal documentation hubs. Create shared definitions and stick to them.
My advice in this article may not stand the test of time. I recommend teams conduct story-based customer interviews to discover opportunities and run assumption testing to discover the right solutions. We test desirability, usability, feasibility, usability, and ethical assumptions. But this is where I stand today.
A/B testing is a powerful tool that can help you uncover hidden opportunities and optimize your marketing efforts. Whether you’re looking to attract new leads or improve engagement with existing customers, this article will guide you through the A/B testing process from start to finish. We’ll cover: What A/B testing means.
Opportunity solution trees , experience maps, interview snapshots, interview notes and recordings, story maps , assumption maps, assumption test plans , and results. Share the highlights of what you are learning from your assumption tests and give them a clear picture of how and when you might make a decision.
Figma, on the other hand, gives you a transparent and almost flat document system. Document organization. Unless it’s your team’s master document, it will hardly ever be opened by someone else. But Figma documents are specifically built to be shared, which demands more careful organization. No more “final-final-ver.99…”
Forming such a team connects the person in charge of the product—the product owner—with the people who design, architect, program, test, and document the solution—the developers. This team consists of a product owner , a Scrum Master , and several developers, which are also known as development team.
There are standard procedures which require users to sign acceptance documents. Delivery drivers have standard procedures which require users to sign acceptance documents (Image: Shutterstock). We tested the code very, very quickly – and if I’m honest I would have liked to have spent longer on testing.
One of the most valuable skills in any customer support or product engineering team is navigating internal codebases and documentation – this is how you learn that, more often than not, the answer is there if you take the time to look for it. Taking 15 minutes teaches you the skill of not only knowing what to look for, but how to look for it.
Many product managers, including myself, often reflect and think hard around the areas which they need to invest in to progress in their career; is it A/B testing, data analysis, go to market skills? Guest Post by: Alexander Berry (Mentee, Session 11, The Product Mentor) [Paired with Mentor, Brad Popiolek].
Additionally, consider asking the team to collect data that shows how much technical debt there is, where it is located, and how bad it is, for example, by using code complexity, dependencies, duplication, and test coverage as indicators. But these practices do not only help create an adaptable architecture and clean code base.
You can ask me to change the color somewhere or put a button on a screen, and I will probably do that, but I really like to get challenging problems where I can do my research build prototypes, do user tests, and come up with a solution that will raise our product to the next level. Designers has to work well with developers.
API Growth to 2109 | Wendell Santos Michael Endler outlines the core pillars of an API product offering in his article, How APIs Become API Products , and one of the paramount compliments to a stellar, well-documented, API is the API Developer Portal. So, what UX elements make a great API Developer Portal? www.Astral.sh ). from Routable.
He asked the community how to determine when a trio should run through the entire pattern of identifying and testing assumptions vs. building something quickly to learn. Trevor turned to the CDH community to get their take on identifying and testing assumptions vs. building to learn.
They iteratively test their ideas with customers week over week. You can use digital whiteboards like Miro and Mural to collaborate on shared visual documents like the opportunity solution tree. If you’ve never used these tools, take advantage of the example documents these companies provide to help you get started.
And software developers and testers want to know that their time spent writing and testing code is purposeful. Since we log many actions in our product’s database, I used my background in SQL and R to create a shared document with product KPI’s all in one spot. I now update this document weekly and share it with team leads.
Here, we’ll dive into the ways we can apply the film industry’s tried and tested model to future projects. Document this step with in-depth notes, seeking feedback from contributors. Link all relevant documents and resources to provide a holistic overview of the topic. Translating film industry phases to tech.
Janna recommends usability tests to cull your design debt. By testing, you can identify areas of issue, and you can track your improvements by having users retake the test over time. By testing, you can identify areas of issue, and you can track your improvements by having users retake the test over time.
These are planning, analysis, design, development, testing, implementation, and maintenance. you’ll identify both functional and non-functional requirements to create a comprehensive Product Requirement Document. DocumentationDocument all gathered requirements use case scenarios, and any decisions made during the analysis process.
For this reason, we chose to run exclusively on AWS and wherever possible, we make use of battle-tested AWS services, be it RDS Aurora for our relational databases, the Simple Queue Service (SQS) for our async workers or ElastiCache for our caching layer.
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