How can engineering teams maintain momentum while navigating ambiguity in product direction and experimentation? In this roundtable, we'll explore the challenge of unlocking engineering velocity without falling into the traps of over-planning or reactive building. Drawing from experience managing shifting focuses with differing priorities we'll unpack questions like: When should engineers enter the product design process? How do we balance iteration speed with stakeholder confidence? What role does autonomy play in high-functioning teams without risking misalignment or throwaway code? Join us for a candid discussion on strategies to synchronize engineering, product, and design for smarter delivery, deeper collaboration, and sustainable velocity.
Alan is an engineering manager at change.org where he's passionate about growing the careers of his team members and coaching them to keep their technical skills sharp. Currently, he manages two teams which are focused on petition growth and juggles how to keep both teams efficient while collaborating with them on how to improve the software development lifecycle. He's previously worked at Adobe in addition to small startup companies focused on cybersecurity + resource management.