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.
I wanted to share with you the framework I use when doing this. I then do various interviews with executives all the way to Product Management team members and surrounding functions. Below is a brief overview of the framework that I use and a few signs of where you should start if you want to run this exercise yourself.
What do you do when your team is working their socks off and yet they are getting little credit for the work being done, mainly because the team isn’t able to set concrete expectations with the stakeholder? This obviously reflected as a failure to deliver on part of the engineering team. THE CHALLENGE. THE CAUSE.
So I’ve been on the hunt for a framework that actually helps you measure and increase your velocity. From the creators of DORA, SPACE, and DevEx, and in collaboration with Laura Tacho and the team at DX , I’m excited to introduce you to Core 4. Her background is in developer tools and distributed systems.
Hence it is critical that one is aware of the best practises of the role and develops his own philosophy which results into maximum positive leverage for the organization. As I strive towards becoming a product leader, I wanted to understand the best practises in product management and in the process develop my own product philosophy. .
I’ve been on a journey when it comes to PM developmentframeworks. I have a lot to learn and there are definitely faults with this, but if somebody else can find use in it, I’ll be delighted. It’s designed to highlight at-a-glance how effective a Product Manager is and where growth opportunities are.
Through conversation, talent reviews, and direct experience leading large organizations, I’ve developed a few key principles to help new skip leads better understand and perform their role. How do I help line managers deal with IC performance issues on their team instead of dealing with them myself?
Similar stories have inspired new product and business developmentframeworks , thousands of articles, and numerous books. Companies simply ship too many poor products and features. Agile is sometimes seen as a panacea to all product development problems. Enter Lean Customer Development. So where is the problem?
The Scrum Guide released in November 2020 states that “the product goal describes a future state of the product … [It] is the long-term objective for the Scrum team.” The product owner is accountable for “developing and explicitly communicating the product goal.” The entire Scrum team is “focused on one … product goal” at a time.
It can be hard to reach the required level of buy-in without using design-by-committee , brokering a weak compromise, and agreeing on the smallest common denominator—which is hardly the foundation of a successful product. This approach makes it easier to reach unanimity and consent without making weak compromises.
As a support leader, you already know how important it is to take care of your customers – but it’s just as important to take care of your support team. Here’s why human support is so crucial for any customer-centric organization, and how it can have a significant impact on your team, your business, and your customers. Here’s why.
I was asked to give a ten-minute overview of my continuous discovery framework and then participated in a fireside chat where the host, Cecilie Smedstad , asked me to go deeper in a few areas. Discovery is a team sport. I did classic web development before there were frameworks back in the ’90s. Week over week.
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.
. – Tweet This The product team at Botify knows this all too well. While Chief Product Officer Christophe Frenet initially guided this transition, many members of the team stepped in to facilitate this process. However, Claire adds it wasn’t all bad. Along the way, they’ve given a lot of thought to this process.
” The secret to shipping successful product, then, is clearly defining for your team the problem that you’re setting out to solve. A great problem statement supercharges product development. It inspires and guides your design team, it makes evaluation simple, and it creates direction for scoping and iteration.
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.
I think one of the ways to minimize the chance of this happening is to have an always on routine of talking to customers e.g. standing time to talk to customers that almost gets backed into the operating rhythm of the team. There is definitely truth in that. the short story is that not all tech debt is bad. Of course?—?the
I’ve asked friends who do the job at social events and got the same answer, and frequently asked members of my own teams, who struggled to find the time to do it. To compensate, I’ve seen UX researchers & designers pick up the mantle a lot more, and the design teams have really leaned into this space. What can be cut first?
It’s an approach that’s served him well along the road to building the HubSpot sales team, where he was CRO for nine years. This has created large amounts of data for running teams. . A data-driven framework for scaling. Mark’s latest ebook, The Science of Scaling , outlines a precise framework for success.
This led me to reach out to 14 leading Product Managers and talk with them about how they use customer feedback in their own companies and teams. Frameworks like Jobs-to-be-Done are extremely helpful in determining exactly what the product is supposed to be doing for its customers — that is, the needs it serves.
The definition of product management has been changing and evolving over the past 10 years and I’m not sure it’s for the better. In other words, the agile development process is redefining what we call product management. If you have product owner responsibilities, you have to be 100% all in with your UX and developmentteam.
From this article, you will find out how to develop a strong growth marketing strategy and learn growth marketing tactics for different customer journey stages. Market development targets new markets with existing products, while product development – existing markets with new products. If so, we’ve got you covered.
At Intercom, we always “ start with the problem ” when beginning any project – it’s part of how we apply the Jobs-to-be-Done framework. To capture our thoughts and give clear definition to our team, we write a document called a problem statement. “It takes thought, writing, re-writing, and research.
Welcome to JEDI Training for Continuous Discovery Teams. I’ve had the luxury of working with teams all over the world, and I teach them a structured and sustainable approach to continuous discovery. The reason why I like to share that is in today’s talk, we’re going to get into my continuous discovery framework.
His book, Why Are We Yelling: The Art of Productive Disagreement , takes some of these learnings and distills them into an actionable guidebook for “how to turn arguments into a productive and enjoyable dialog rather than a bad-natured confrontation.”. I like to think of them as neither good nor bad. Short on time?
We’ll hear from several members of the product team at Ramsey Solutions about their not-so-smooth transition to working in product trios, especially when it came to getting engineers to participate. Meet the Continuous Discovery Champions at Ramsey Solutions The product team at Ramsey Solutions is 40+ squads strong.
In a recent talk at UX London , I discussed some lessons learned while growing the design team at Intercom, reflecting on the technology industry’s obsession with tools, and pointed out how our sense of tools as objects or apps blinds us to the reality that the processes we adopt and develop are also, in effect, tools.
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.
We experience these effects everyday when we use products like Uber, where the more drivers who join, the shorter your wait times; Slack, where the more team members that join, the quicker it is to communicate with more of your colleagues; and Airbnb, where the more travelers that join, the better the listing reviews. Cold Start Theory.
If you’ve read Teresa’s Torres book, Continuous Discovery Habits , you’re probably familiar with her continuous discovery framework for building better products that are actually guided by user feedback. If you haven’t read the book…well, you are definitely missing out. What is continuous discovery?
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. Thinking about how to get people to invest is definitely a skill to keep practising. Your Skills Resume: Can you Identify Profit?
STATIK (Systems Thinking Approach To Implementing Kanban 1 2 ) can be a great technique to help teams get up and running quickly, even teams that are using Scrum. . Applying this approach designed for Kanban can dramatically accelerate the forming and improvements of a Scrum team. How does work flow through the team/system? .
One of my all-time favorite quotes in our industry comes by way of the legendary VC, John Doerr , where he argues that "we need teams of missionaries, not teams of mercenaries.” Teams of missionaries are engaged, motivated, have a deep understanding of the business context, and tangible empathy for the customer.
While it’s true that a math problem will have a definitive answer, the ways of getting to that answer are multiple. Now all the philosophical aspects about accepting failure aside, what we, as a society, have developed is undervaluing the power that comes from overcoming and correcting a mistake. Let’s talk about this for a second.
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.
Product marketing focuses on getting products into the hands of the right users, whereas product management focuses on developing the product. It is a merger between product development and sales to ensure a product satisfies specific customer needs and business goals. Product management focuses on product development.
It’s not necessarily bad when product management adapts to each company’s specific needs. Below is the discussion Melissa Perri had with John Cutler and Jim Semick on why teams that are scaling need product ops. Processes & Practices: The more product teams grow and multiply, the less homogenous they get.
I'm a firm believer that Objectives & Key Results (OKRs), the goal-setting framework invented at Intel and popularized by Google and John Doerr , can be a highly effective leadership tool for a team of any size. I've seen teams define new OKRs every month, every quarter, or every year. Writing Effective OKRs. Quarterly OKRs.
A few weeks later, she offered me a job on her team. I kept meeting with every team in the company to learn more about what my business was good at, even if it didn’t involve direct contact with the products that I was building. When I was at HERE Maps, working with various teams to implement things, they didn’t just “do it.”
In today’s data-driven SaaS scene, these can affect hundreds of millions of users and cause damage in the billions of dollars, and as compliance frameworks become requirements to do business, businesses are turning to third-party services that can help expedite and facilitate the process. And just continuing to push it higher with the team.
Mental models are frameworks we use to make decisions, explain things, or think about the world. Out of thousands of different mental models, some apply uniquely well to helping teams building great products. Mental models you need for product development: 1. Causal loops. Pioneers, settlers, and town planners.
Much has been written about the process of creating product roadmaps, not least the six great articles written by my own team. I believe the actions of a product leader all too often are the root cause of a “bad” roadmap. I would define a good roadmap as one that the team understands and feels ownership over.
Will Larson has managed infrastructure teams for some of the biggest names in software. Partnering with the Infrastructure, Data and Developer Productivity teams, his group builds the tools that support every Stripe engineer and keep Stripe reliable and performant. Today he’s leading Foundation Engineering at Stripe.
With a Master’s degree in human-computer interaction and over two decades of experience in user research and user experience in companies like Oracle, he now leads the design team across all product offerings at IBM. The design team at IBM likes to employ a “make to learn” method. Arin: It’s definitely iterative.
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