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
How product managers can move from ideas to action Watch on YouTube TLDR In this episode, I speak with Atif Rafiq about how senior product leaders approach strategy development and execution. He has developed a systematic approach to problem-solving that forms the basis of his book, Decision Sprint: The New Way to Innovate into the Unknown.
Yet most product managers still rely on long documents, jargon-filled briefs, and clunky slide decks that dont land with the people who matter. When done well, storyboarding helps PMs communicate clearly, align teams faster, and influence decisionswithout needing formal authority. How: Whats your unique approach?
Manage the Product, not the Team. Focus on your job as the product manager or product owner, and manage the product, not the team. Treat the Team as an Equal Partner. The team members are not your resources but the people who create your product. Assume that the team members want to do their best.
But then, one day, I found myself reading Ask Your Developer by Jeff Lawson and I realized I was the one making the mistake. Dont Ask Humans to Do Tasks That Should Be Automated If you arent familiar with Ask Your Developer, its a great read. API teams need to think about onboarding just like everyone else. This got me curious.
Last week, I shared that we often get asked, Do API teams need to do discovery ? Today, Ill be covering the most common usability issues that arise when developers start working with a new API. If we can make it as easy as possible for developers to adopt and get value from our API products, we can often acquire a customer for life.
” But do not allow people to dominate and tell you what to do, and don’t agree to a weak compromise. The SAFe product owner is tactical in nature and focuses on working on the product backlog and guiding the developmentteams. Myth #3: The product owner is responsible for the team performance.
It compounds quietly across every team, workflow, and decision. When data collection is messy, product managers lose visibility, teams waste hours chasing answers, and user experience suffers. This is where tools like Userpilot come in, providing product teams with comprehensive analytics that bridge these dangerous data gaps.
And also is a way of preventing errors and defect bugs in the software development process. Overview of the quality assurance Quality assurance service is a systematic process to ensure the frontend and backend development satisfies specific requirements and quality standards.
Ruthless prioritization translates to product teams spending time building the right thing at the right time. This discipline is the bread & butter for a winning product team, but building an effective product process takes a lot of trial and error. Our objective is to understand customer needs and adjusting. . It’s cyclical.
I realize that many product people have never worked in a product trio , don’t have access to customers, aren’t given time to test their ideas, and are working in what Marty Cagan calls “features teams” or “delivery teams.” If you missed the first one on product success and team satisfaction , be sure to start there.
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 challenge to the product managers is to translate these into a more functional plan for our engineering team. First Attempt.
Product trios are cross-functional product teams who are responsible for both deciding what to build and then building it. What about the other people on the team who aren’t part of the product trio? How can product trios adapt to remote work and distributed teams? Do product teams really work this way?
To understand if and to what extent your product is affected by technical debt, talk to the developmentteam, for example, in the next sprint retrospective. I find that developmentteam members usually have a good understanding where issues in the architecture and code are.
It’s also essential to creating a team where great people want to work. In a perfect product development world, communications are seamless, specifications are clear, and product and engineering teams work together without friction. These are team goals that get shared across the company. Share Leadership and Credit.
The developers sitting nearby just watched the show for the first time, but after a while they stood up to join the party one by one. Soon the whole team was standing behind the designer’s screen shouting new ideas and tips about the layout, the colors, the icons, the fonts and everything else. What to expect from a design team?
While we might think of all debt as bad, Janna says this isn’t the case. What’s not fine, Janna says, is when tech debt is accrued without intention; because this happens when there isn’t a shared understanding of how the product will be built, and tech debt usually arises outside the control of the tech team.
Product managers tell me – and the people managing product managers tell me – that one of their biggest challenges is communicating with the developmentteam. People complain about: Developers being poorly motivated, or having a bad attitude about what you want them to build. ” and “What?” and “What?”
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.
If the teamsdeveloping the different apps all created their own user-interface layers, there would be considerable code duplication, added development costs, and increased development time. After all, a platform exists to help teams build better products faster and cheaper.
The latter would work with one or more developmentteams to get the specification implemented. During the development phase, the product manager would be only loosely involved, typically attending a project steering meeting and possibly issuing change requests.
Product managers tell me – and the people managing product managers tell me – that one of their biggest challenges is communicating with the developmentteam. People complain about: Developers being poorly motivated, or having a bad attitude about what you want them to build. ” and “What?” and “What?”
Consider this article a requirements document: it’s structured into several user stories from the perspective of a hiring manager, for a product manager role. Ultimately, your resume should itself signal that you have the skills required to be a successful product manager on any team. If you’re. Storytelling.
It was about 12 months ago when I was challenged by our CEO to dismantle our squad and create a growth team. Not being too sure what a growth team was, we started anyway. We got access to work completed by Andrew Chen & Brian Balfour , took a few courses from the Reforge series and started developing our growth loops.
In a fastmoving digital economy, many organizations leverage outsourced software product development to accelerate innovation, control costs, and tap into global expertise. Rather than building and maintaining a large inhouse team, businesses partner with specialized vendors to handle design, development, testing, and deployment.
Many of my discussions with product leaders (CPOs, VPs and others who manage teams of product folks) are about the substance of product management: portfolios, competing stakeholders, pricing & packaging, tarot cards as a revenue forecasting model. Last A competitor announces ChatGPT-based retirement investment advice.
Prioritisation is a necessary evil of every product development lifecycle. Prioritisation is one of the most critical aspects of product development. Unfortunately this isn’t always the case – we’ve all come across poor decision-making in organisations. Poor Prioritisation. However, it doesn’t have to be this way.
I founded Prodify so my team and I can help companies by sharing knowledge from our previous experiences. It’s not because they’re bad at what they do. Often the senior leadership team thinks they talk about strategy a lot, but the employees under them don’t understand the strategy.
The first type of partial product manager is a holdover from waterfall days when product design entailed a sequential process of researching, then documenting, then passing along requirements for development. The company doesn’t create or test prototypes before building. Frequent, bespoke development for specific customers.
And she’s also always happy to coach the members of the Product Talk team in how to develop our own continuous discovery skills, too. While Welena’s role at Product Talk is not strictly as a product manager, that doesn’t stop her from developing and practicing her continuous discovery skills. You can submit your story here. .
At UX Studio , while we develop our products, uxfol.io and copyfol.io , we are mainly focused on agency work, meaning that we cooperate with several clients as external teams. This post was written from the perspective of designers, mainly intended for external teams and entrepreneurs. Five challenges and solutions.
At the beginning of any software development project, managers think of which methodology is between waterfall and agile. It’s essential to follow clearly defined processes or software development life cycle (SDLC) to ensure software development quality. Waterfall and agile: A smart method or bad solution?
Here’s our story how we’re developing a product using machine learning and neural networks to boost translation and localization Artificial intelligence and its applications are one of the most sensational topics in the IT field. If so, what is the value of the solution you’re developing? Often people confuse it with automation.
Here are five quick takeaways: Instead of relying on word of mouth to permeate the team, write things down. If Rohini’s team is making changes to the UI or the front end, they can test quickly and easily, but because their core product is payments-based, much more rigor is required compared to your typical software product.
The Best Product Managers use Product Management Software for: We’ve broken down this list into four stages of the feature life cycle that contributes to building the product value: opportunity identification and validation, design and prototyping, feature development, and launch and iteration.
Christina Wodtke’s path to her current standing as an established authority on the attributes of high-performing teams and the use of OKRs has been a roundabout one. She’s also due to deliver a workshop on how to design product teams with intention at MTP Engage Hamburg. So what about high-performing teams? And I loved it. ”.
While working on a knowledge management solution aimed at custom support and sales teams, we integrated with several customer support desks and CRM. These types of integrations can often require complex design, testing, and exception handling requirements. You need to design, code and test the integration itself. Documentation.
To unburden their teams, companies like Facebook, Google, and others have turned to product operations, whose job is to help product teams achieve better outcomes. At its core, product operations enables product teams to achieve better outcomes. Create frameworks for aligning company, org, team, and individual goals.
Empower Your Teams if you Want to be Truly Agile. Agile and Lean are not inherently poor or incorrect, rather they’re being used to solve problems they weren’t designed for. This normally takes some automation of testing and a suite of DevOps improvements, and this is where a lot of businesses stop. This takes time to learn.
Software development is rarely linear. If the team is unable to successfully manage those processes, it could cause chaos during development, and the customer will face sharp increase in development time and poor quality of work. The development work consists of iterations, called sprints, and proceeds in stages.
Instead of relying on someone else (like a coach or leader) to tell them what to do next, product teams can use an opportunity solution tree to keep track of their desired outcome , the opportunities they’ve identified to chip away at that outcome, and the solutions they’re considering to address those opportunities.
In fact, some methods are pretty poor. Some product managers make poor decisions because they don’t have the right skills. It’s from another team, so you can be completely honest with me. However, not all methods are equally effective when deciding what is valuable. Your Skills Resume: Can you Identify Profit? My name is Jacob.
Not enough people spend enough time on defining vision and purpose Most value propositions are weak Companies don’t adapt their team typology to make a product Very few products are indeed prioritized by value User Reasearch and UX are ofter used in the wrong way 1. Here is what I noticed. targeted and user centric. Like in a startup.
Learn who to listen to: “The Mum test” (Rob Fitzpatrick) This book will teach you that they’re some people you should never listen to, like your mum. Poor questions yield little value. ?? Plan your product: “story mapping” (Nielsen Norman Group) Often teams rely on lengthy requirements documents to move from a vision to a product.
Let’s establish this right upfront: nothing beats a well-managed full-time in-house team of local developers. Are there enough skilled developers at your location? And done right, I believe that outsourcing means you can come very close to your team next door in terms of productivity and innovation.
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