Building and conveying vision
summary
Panel lays out concrete practices: a three-piece: people product profit framework to tie vision to business outcomes, treating vision as a living document with edits and checkpoints (roughly twice a year plus quarterly and six‑week reviews), explicit technical projects that merit standalone visions like a data infrastructure overhaul, collaborative product‑engineering decision rules, and remote realities (around 70% remote work) that change cadence and communication. Sponsors listed: Honeycomb.io and CircleCI.com.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:09Maria Gutierrez
- 6:51What Does Vision Look like in Your Role
- 8:38Relationship from Vision to Strategy
- 22:27Align Your Team
- 23:23Getting Aligned
- 24:21How Do You Align those Teams unto Your Vision
- 27:25Why Do Technical Vision Statements Seem To End Up in Practice as a Bunch of Architectural Best Practices and Principles
- 37:20Vision versus Values
- 42:18Final Thoughts
related talks
24mScaling a Product Vision Through World-Class Team and Culture
30mJames Stanier, Winter Wi, Janet Balneaves a panel discussion at LeadDev London 2023
31mHarmonizing Across Product & Engineering (Cross Team Collab)
48mBuilding a Product and Engineering Relationship that Works
33mHow to Set a Customer Centric Vision and Strategy to Realize It
33mPrioritizing Effectively and Forming a Product Vision
40mPerspectives on effective product development culture
01h 00mPanel