Tom Alterman

AMA: Notable Head of Product, Tom Alterman on Product Development Process

October 16 @ 10:00AM PST
Register for AMA
We will email you Tom's answers to these questions after the event in case you can't make it.
How do you get inspiration for product design when it comes to designing a new product?
After gathering all the requirements and having great insights into users pinpoints, studied competitors, and market trends, How do you then get the inspiration for design layout before talking to your designer to translate all of this into an intuitive user experience
What activities do you include engineering in when working through problem statements?
When is it the appropriate time for QA? Who is responsible for quality when working in such a small team?
We have a small product and eng team, and are too early to have QA. Do you recommend we have eng test their own features? Is this the job of the product? Also should we have QA as part of our sprint, or the subsequent sprint?
How do you prevent rogue engineers from slipping in features that are good but not prioritized?
Who is involved in assessing the problems you choose to tackle?
What role do engineers have in planning which features you build in the sprint? How do I get buy-in without giving them control?
At what point do you talk about success metrics with your development team?
How do you ensure that the engineering team understands all the scopes of the project?
What is your end-to-end product development process?
What activities do you do to help set expectations between development and upper leadership?