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
Many CEOs of software-enabled businesses call us with a similar concern: Are we getting the right results from our software team? We hear them explain that their current software development is expensive, deliveries are rarely on time, and random bugs appear. The explanation from software leadership is often unsatisfying or unclear.
Whether you’re planning six months ahead or sitting in discussions right now, here’s the process I’ve developed through trial and error with clients over 15 years. Start demonstrating how you’ll solve their specific problems for the company/team. And how can I best show up for [name other team member(s)]?
I love that Marty Cagan and Jeff Patton have long been advocates of dual-track development. If you aren’t familiar with dual-track development, it’s the separation of product discovery from product delivery. Continuous integration reduces the risk of large code conflicts that used to take days or sometimes weeks of testing to resolve.
I try to help product and sales teams succeed under the mantra “Easy to Sell, Easy to Renew.” I’ve struggled to find many examples detailing how to bond product and sales teams ( Antonia Bozhkova offers a good perspective ). Your teams will realign and strengthen their partnership as they see the product through each other’s eyes.
Common misconceptions with UX and product development UX is a powerful and valuable tool, but misconceptions abound about what UX can do and how long it can take to reap the benefits. Engineering teams likely have a history of delivering features and delivering them very fast. False: “We don’t need to user test. Not so fast.
A Five-Step Methodology to Incorporate Generative AI into Business Strategy Developers, technologists, and innovators across enterprises are already using the new tools to boost their individual productivity at work and at home. You should invest in new technologies or upskill your team to implement generative AI successfully.
So, how do you ensure that UX gets its due in terms of investment? It encompasses the quality and consistency of research and design processes, resources, tools, and operations, as well as the organization’s propensity to support and strengthen UX now and in the future, through its leadership, workforce, and culture.
Where are product teams getting their feature ideas? Most concerningly, 19% of respondents reported that their top source of ideas comes from senior management, who are often disconnected from both customers and the product development process. Why do product teams become feature factories?
What does leadership entail in the context of design? How does an organization benefit from strong design leadership? Hired as external consultants, researchers, and product designers, sometimes we are asked to join an existing product team and help in transforming an organization from the inside. . Listen first.
But when I do product duediligence for SaaS-focused PE/VC firms, it's the very first thing I look at. Let’s IMHO, software product companies are fundamentally different from software services/outsourcing/custom development companies. Said What BigCorp demands, BigCorp gets. Hitting
By optimizing release management flows, teams can facilitate on-demand deployments that enhance business agility without compromising stability. Understanding precisely how to improve release management is key for more efficient software development. Effective release management is pivotal for agile software development.
Alongside a series of mergers, eight years ago Cambia founded a dedicated innovation team dubbed the Innovation Force — a common innovation investment nowadays, but ahead of its time back in 2011. “In In order to change the culture, we needed a dedicated team, but the team had to be both coaches and players,” says Max.
Alongside a series of mergers, eight years ago Cambia founded a dedicated innovation team dubbed the Innovation Force — a common innovation investment nowadays, but ahead of its time back in 2011. “In In order to change the culture, we needed a dedicated team, but the team had to be both coaches and players,” says Max.
Alongside a series of mergers, eight years ago Cambia founded a dedicated innovation team dubbed the Innovation Force — a common innovation investment nowadays, but ahead of its time back in 2011. “In In order to change the culture, we needed a dedicated team, but the team had to be both coaches and players,” says Max.
Hope also does some leadership coaching with her own company, Fearless Product. Teresa: For those of you that are Product Talk readers, Melissa writes our Product in Practice series where we’re sharing stories about teams doing great discovery work, so you may have seen her name there. Let’s go ahead and dive in.
This was the artifact the began the process of developing a new product, or a variant of a product. The leadershipteam asked for a formal Market Requirements Document to help their decision process. In the way back time, before Agile, before OKRs and other fads, product managers wrote MRDs, or Market Requirement Documents.
And while the medical profession pioneered the concept of professional ethics, other industries have also developed ethical codes. Engineering has developed a strict code of ethics that they are expected to adhere to in practice. This opened up questions for the team: What would the employee be comfortable with us sharing?
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