Good teams have product, design, and engineering sit side by side, and they embrace the give and take between the functionality, the user experience, and the enabling technology.
Good teams get their inspiration and product ideas from their vision and objectives, from observing customers’ struggle, from analyzing the data customers generate from using their product, and from constantly seeking to apply new technology to solve real problems.
Good teams understand who each of their key stakeholders are, they understand the constraints that these stakeholders operate in, and they are committed to inventing solutions that work not just for users and customers, but also work within the constraints of the business.
Good teams are skilled in the many techniques to rapidly try out product ideas to determine which ones are truly worth building.
Good teams love to have brainstorming discussions with smart thought leaders from across the company.
Good teams are constantly trying out new ideas to innovate, but doing so in ways that protect the revenue and protect the brand.
Good teams insist they have the skill sets on their team, such as strong product design, necessary to create winning products.
Good teams ensure that their engineers have time to try out the prototypes in discovery every day so that they can contribute their thoughts on how to make the product better.
Good teams engage directly with end users and customers every week, to better understand their customers, and to see the customer’s response to their latest ideas.
Good teams know that many of their favorite ideas won’t end up working for customers, and even the ones that could will need several iterations to get to the point where they provide the desired outcome.
Good teams understand the need for speed and how rapid iteration is the key to innovation, and they understand this speed comes from the right techniques and not forced labor.
Good teams make high‐integrity commitments after they’ve evaluated the request and ensured they have a viable solution that will work for the customer and the business.
Good teams instrument their work so they can immediately understand how their product is being used and make adjustments based on the data.
Good teams integrate and release continuously, knowing that a constant stream of smaller releases provides a much more stable solution for their customers.
Good teams obsess over their reference customers.
Good teams celebrate when they achieve a significant impact to the business results.
— INSPIRED: How to Create Tech Products Customers Love by Marty Cagan