Cover Image for Same Roadmap, Different Reality: Resolving Product and Engineering Misalignment
Cover Image for Same Roadmap, Different Reality: Resolving Product and Engineering Misalignment
Avatar for Predictable Progress
Practical sessions on leadership, product and engineering alignment & visibility. Hosted by Gary Joyce, Predictable Progress.
Hosted By

Same Roadmap, Different Reality: Resolving Product and Engineering Misalignment

Virtual
Registration
Welcome! To join the event, please register below.
About Event

​Building software is getting cheaper. Agreeing what to build, and making sure everyone is working towards the same outcome, hasn't necessarily got any easier.

​Product and Engineering teams can both be busy, capable and committed — yet still end up working towards different interpretations of the roadmap.

​The usual answer is to communicate better. That's not wrong. It's also not the whole problem.

​In this free, live 60-minute session, we'll look at three underlying causes of misalignment between Product and Engineering, why they happen, and some practical ways to address them.

​This session draws on more than 20 years of working inside software delivery, including leading complex, multi-team initiatives. I'll use practical examples from that experience to show where things go wrong, what the consequences look like, and what can be done differently.

​What we'll cover

​1. Strategy doesn't survive contact with planning

​How strategic priorities get lost as work moves into planning, leaving teams unclear about why they're doing what they're doing.

​The fix: Make the connection between strategy, initiatives and day-to-day work visible.

​2. The roadmap is a promise to leadership and a guess to the team

​How leadership and delivery teams can walk away from the same planning conversation with very different understandings of what's actually going to happen.

​The fix: Establish a regular roadmap conversation that makes changes, assumptions and delivery confidence explicit.

​3. Features reach the team before both sides have shaped them

​How features get committed to before Product and Engineering have properly explored the problem, scope and technical implications together.

​The fix: Bring Product, Engineering, QA and UX into high-level feature shaping before commitments are made.

​You'll leave with

  • ​A way to identify which of these three root causes is affecting your team.

  • ​Practical approaches to addressing each one.

  • ​A one-page Alignment Audit to help you assess your own environment.

  • ​A specific first action you can take away and put into practice.

​Before the session

​You can download the one-page Alignment Audit in advance. It's a working document we'll use during the session, so feel free to print it or have it open alongside Teams.

​Download the Alignment Audit (PDF)

​There's no need to complete it beforehand. You won't be asked to share your individual answers — it's there to help you reflect on your own team's circumstances.

​Who should attend?

​This session is aimed at people working in and around software product delivery, including:

  • ​Product Managers and Product Leaders

  • ​Engineering Managers and Technical Leads

  • ​Delivery Managers and Programme Leads

  • ​CTOs, CPOs and other technology or product leaders

​Whether you're experiencing these challenges directly or trying to understand why delivery isn't matching expectations, the session should give you something practical to take away.

​Format

  • ​60 minutes, live and online via Microsoft Teams.

  • ​A mix of presentation, anonymous polls and practical reflection.

  • ​Opportunities to ask questions and join the discussion.

  • ​No requirement to turn your camera on.

  • ​The session will not be recorded.

​You'll receive the Teams joining details after registering.

​If you register but can no longer attend, please cancel your place so someone else can take it.

​About the host

​I'm Gary Joyce, Founder and Principal Consultant at Predictable Progress.

​I work with product and engineering teams to make software delivery visible, align priorities and ensure that what gets built reflects what the business actually needs.

​I've spent more than 20 years working in software delivery, including leading complex, multi-team initiatives where dependencies, competing priorities and delivery expectations need to be brought together.

​Predictable Progress helps organisations get a clearer view of what's happening, what's getting in the way, and what needs to change.

​Website: https://www.predictableprogress.co.uk

​Code of Conduct

​This is intended to be a constructive, inclusive and respectful discussion.

​Everyone attending is expected to:

  • ​Treat other participants with respect, regardless of their role, experience, background or point of view.

  • ​Challenge ideas and approaches constructively, without making personal remarks or attacks.

  • ​Give others space to contribute and avoid dominating the discussion.

  • ​Avoid discriminatory, harassing, abusive or intimidating behaviour.

  • ​Respect the confidentiality of examples and experiences shared by other attendees. Please don't attribute comments to individuals or share identifiable details outside the session without their permission.

  • ​Keep contributions relevant to the session and avoid unsolicited promotion or selling.

​The host reserves the right to remove anyone whose behaviour is disruptive, disrespectful or otherwise inconsistent with this Code of Conduct.

​By registering for and attending the session, you agree to follow these guidelines.

Avatar for Predictable Progress
Practical sessions on leadership, product and engineering alignment & visibility. Hosted by Gary Joyce, Predictable Progress.
Hosted By