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
Drawing from his 20+ years of technology experience and extensive research, Nishant shared insights about how these activities vary across different organizational contexts – from startups to enterprises, B2B to B2C, and Agile to Waterfall environments.
The discussion explores practical applications of AI tools like ChatGPT and Claude in product development, including MVP refinement, customer testing, and marketing content creation. However, Mike emphasizes the importance of balancing AI capabilities with human oversight, warning against over-reliance on AI.
Prioritization is where product leadership gets tested. Balancing technical constraints, stakeholder agendas, and long-term goals is hard. Even experienced PMs get stuck in opinion-driven debates or lose clarity under pressure.
Most innovators don’t have a technical background, so it’s hard to evaluate the truth of the situation. The explanation from software leadership is often unsatisfying or unclear. And unless they have a tech background, they can’t look under the hood themselves. It also provides concrete recommendations for improvements.
It’s not about finding the right tech stack; it’s about finding the tech stack that works for your team. When it comes to the tools that support your continuous discovery, it’s not about finding the right tech stack. It’s about finding the tech stack that works for your team. Tweet This.
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. Simple task, right? First Attempt.
Case Study: Improving Data-Driven Decision Making for CSR Leadership Civian is a data-driven platform designed to help businesses measure, optimize, and showcase the social and economic impact of their investments in communities. During our tests, we identified some broader user behaviortrends: 1.
This can be done for example by involving the developers and product owners in the user research, the wireframes assessment and the usability testing sessions. A new leadership role is also a good opportunity to assess and evaluate whether you have the right skill sets and resource capacity in your team. Resource management.
Step 1: Preparation (3-5 weeks) The preparation step is a foundational effort where a lot of the groundwork and duediligence is done to inform the strategy selection process. Leadership interviews: This is a critical input to the process and is often forgotten or skipped for various reasons.
He is convinced that product is the single most important success driver for tech companies, which is why he founded Prodify to share what he learned from being an advisor to over 50 tech companies to realize their full potential. Ben has led successful technology products for the last 25 years. He
Lily has spent 13 years in the tech industry working mainly with startups in the SaaS and mobile space. She has worked on a diverse range of products – leading the product teams through discovery, prototyping, testing and delivery. Email sponsor@mindtheproduct.com for more information.
Feasibility risk impacts the capacity of the team to build the product given time, skills and technology constraints. The sales team and leadership promised the clients to deliver the product without having any discussion with the engineering team. The Aviation Authority and leadership were appalled by our product.
We provided consulting, insurance brokerage, information technology and business process outsourcing services. This was due to incorrect contribution amounts, the system not finding an account, or invalid employer data. At Hewitt, I was a Business Analyst on the TWA (Trans World Airlines) and Nalco Team.
Challenging situations are great opportunities to grow as a human being and by doing so, you increase your leadership power. Additionally, keep an eye on market developments, new trends and technologies, and the competition. As Superman puts it, “You are much stronger than you think you are. Trust me.”. Strengthen Your Expertise.
This is the first of two posts that deep dive on A/B testing, expanding on a talk I gave at Google Playtime 2016 in London. In this post I share some of the learnings we’ve had after running 60+ A/B tests at Peak , looking at each step of the A/B testing cycle in turn. Brainstorm your A/B tests. Prioritise your A/B tests.
This individual leads the product team, not by being the boss but by exercising emergent leadership. It’s important that they have the right skills to spot and evaluate design and technology opportunities and to develop a rough understanding of the likely effort required to implement product decisions.
While product managers have a variety of techniques to cope with this ambiguity, from the Mind the Product slack channel to thunderdome-like meetings, one powerful solution is product review. This is a formal review of the product’s progress by senior product managers in order to assess the status and suggest avenues to explore.
In the past few years, we’ve seen the “ great flattening ” of tech: rising expectations of fewer ICs to own larger swaths of the product and manage multiple teams while staying hands-on. Instead of spending valuable time after the meeting reviewing notes and drafting a summary, do the work in the meeting itself.
Under Musk’s leadership, Tesla adopted a first-principles approach to rethinking fundamental aspects of the electric car. Guided by fundamentals and first principles — Tesla transformed the trajectory of automotive technology. Building a plan to test for DMF as you go into your roadmap is critical. Does it make sense?
The most effective teams foster a culture of structured disagreement not consensus where ideas are tested through rigorous debate, but personal attacks and politicking are off-limits. Every meeting becomes a performance review rather than a space for creative problem-solving. OKRs should serve the strategy, not dictate it.
For example, a relatively common type of incident might be a brief outage of Intercom due to a database failover. Communication : When needed, communication with customers, support, sales and leadership can occur. Resolution : The incident is resolved, and follow-up actions like an incident review occur. Defining principles.
In this episode, sponsored by Pendo , listen to learn about: * Product Management in transport tech. * The different stages of tech companies. * Is technology consumption sustainable? Technology potentially can keep up, but humans can’t. Sustainable Technology piece at ByteAnt. Quote of the Episode.
The value of this approach is that rather than having all of the decision-making power come from the leadership team, it gets diffused to the teams closest to your customers. It’s important that outcomes be set by a two-way negotiation between leadership and the product team. This leads to better decisions. – Tweet This.
That’s another level of difficulty and in her new book, The Team That Managed Itself: A Story Of Leadership, Christina Wodtke does just that. That’s another level of difficulty and in her new book, The Team That Managed Itself: A Story Of Leadership, Christina Wodtke does just that. Drawing [.]. Timothy Gallwey. *
Now an executive and leadership coach, she’s devoted a lot of time over the last few years to working with teams on [.]. Lily has spent 13 years in the tech industry working mainly with startups in the SaaS and mobile space. The Thick of It and W1A shows.
Lily has spent 13 years in the tech industry working mainly with startups in the SaaS and mobile space. She has worked on a diverse range of products – leading the product teams through discovery, prototyping, testing and delivery. Showcase your brand to our audience of avid listeners as a sponsor of The Product Experience.
Instead, I review the lessons learned from myself and my team that created and launched the summit. Product leadership. 14:24] Other decisions we were happy with: Pre-recorded sessions—technology worked. We need to test it better across many platforms. [22:27] Product leadership. * Customer research. Communication.
Lily has spent 13 years in the tech industry working mainly with startups in the SaaS and mobile space. She has worked on a diverse range of products – leading the product teams through discovery, prototyping, testing and delivery. Showcase your brand to our audience of avid listeners as a sponsor of The Product Experience.
An in-depth review revealed that misaligned goals between IT and customer service teams, coupled with outdated processes, were the primary issues. By collaborating with residents and testing new formats or themes, we could design events that truly resonate and foster a sense of belonging. Or consider a fitness goal.
Achieving and Scaling Product-Market Fit: A Guide for Product Managers in Mid-to-Large Tech Companies Introduction As product managers in mid-to-large technology companies, you’re no stranger to the challenges of maintaining and scaling product-market fit (PMF).
” and “Whose opinion does the leadership team value most?” I’m curious—what experiences have most shaped your philosophy toward product leadership?” The leadership team bought into the future she helped them envision. Information-source diversity: Review your research sources.
I enjoyed in-person meetings, especially in-person product review meetings. Early in the pandemic, this led me to resent virtual meetings, especially virtual product review meetings. This particular product review meeting was a breaking point. I struggled to figure out how to run the product review meeting effectively.
Industries such as high tech, banking, pharmaceuticals and medical products, education and telecommunications, healthcare, and insurance stand to gain immensely. Remember that we are still in the nascent stages of generative AI technology. The risk of falling behind is real.
Continuous integration reduces the risk of large code conflicts that used to take days or sometimes weeks of testing to resolve. A group of people (sometimes senior leadership, sometimes a budget oversight committee, sometimes a product team) prioritizes and funds those ideas, initiatives, or projects. The business was the customer.
I saw that in an organization that had management signoff for changes the technical people made. Over those 10 years, the technical teams created more robust testing and deployment scripts. The effects of that batching: Every change requires several days of delay because the managers need to review the changes.
Lily has spent 13 years in the tech industry working mainly with startups in the SaaS and mobile space. She has worked on a diverse range of products – leading the product teams through discovery, prototyping, testing and delivery. Suggest a guest to us here. Talk to us. Tweet at us!
Due to rapidly-changing technology, customers have high expectations for the products they use. Challenge #3: We don’t test with users enough. In mobile product management, testing is essential. To start, here are ten steps for beta testing your mobile app. Challenge #1: I have too many responsibilities.
Lily has spent 13 years in the tech industry working mainly with startups in the SaaS and mobile space. She has worked on a diverse range of products – leading the product teams through discovery, prototyping, testing and delivery. Showcase your brand to our audience of avid listeners as a sponsor of The Product Experience.
Here’s what we learned about product leadership. You can manage the team in exactly the same way you have managed product up until this point – with artefacts like canvases, processes like testing assumptions, and tools like metrics to demonstrate progress. Book suggestion: Product Leadership. Developing Your own Team.
As a product leader, you are the product manager for a leadership team, and the tricks you learned in product teams remain valuable, they just need a little tweak. Using the rigour of a value proposition canvas to describe your organisation can help you to be honest with yourself: As a Tech Startup. Value Proposition.
Respect their UX/UI and technology decisions and their right to determine how much work can be done. Developing a successful digital product requires more than technical knowledge. This will not only lead to better technical decisions and a better product. Be aware that collaboration requires leadership.
Following a talk at ProductTank Bristol, he joined us to chat about the advice he gives both to aspiring product managers and to those angling for leadership positions. Links mentioned in this episode: Six leadership styles, from the Harvard Business Review. Quote of the episode. Or can you continue to be a practitioner?
Therefore, the first question any aspiring agile startup should answer for itself is simple: is it a sales-driven, product-driven, or tech-driven enterprise? However, if the competition is fierce, technology is advancing rapidly, and big players are investing large amounts, there is no way to avoid becoming a learning organization.
Without going into actual project-related detail, any sync I have in the AM would fall in the “catch-up,” “quick sync” or “review bad livesites” category. Sometimes I’ll still be in meetings, as there are occasional team or leadership calls scheduled for lunch. If I went into the office: 8:30 AM is when I wake up.
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