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
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.
Creating a strong, cohesive team takes intention and planning. Researchers have been studying team dynamics for decades. There’s a significant body of knowledge about which organizational structures provide the best results given the circumstances, goals, and personalities involved in a team. 5-second summary.
Scrum came about even earlier than the agile manifesto almost a whole decade to be exact (although you can traces origins earlier back to 1986 with the article The New New Product Development Game ). McElroy wrote a short memo where he described “Brand Men” who had overall responsibility for the brand and managing of a product.
3) Most companies use weak heuristics, opinions and archaic decision processes to place bets on a handful of unproven ideas. The alternative is of course evidence-driven product development. In product management circles the term “Product Discovery” has become most synonymous with evidence-driven product development.
Taking agile, a process otherwise optimized for small, cross-functional, collaborative teams and making it work at scale is fascinating. Think of a couple dozen teams (a couple hundred people) working to deliver across a couple hundred systems, for a multi-billion dollar organization. Getting Faster at Building the Wrong Thing.
Originally software engineer, long time ago no one on my team believes that anymore that I ever coded and then have started five companies and Drift is the fifth. So you have field, inside, BDRs (business development representatives), ADRs (account development reps), CSMs (customer service Managers), etc all these acronyms that we all know.
Thing is I’ve learned a lot about how to develop products. All right, here’s the thing: this is this is where I learned actually waterfall but if this is the product development right. And so what you realize is that in the system developed they were doing 10 times the prototypes we were. I’m an engineer.
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