David Marquet on the Difference Between Red-Work and Blue-Work

Engineering Culture by InfoQ

• Episode: David Marquet on the Difference Between Red-Work and Blue-Work
• Website: Engineering Culture by InfoQ
• Feed URL: http://feeds.soundcloud.com/users/soundcloud:users:258266127/sounds.rss
• Duration: 00:16:52
• Published: 2017-09-04 02:00

This is the Engineering Culture Podcast, from the people behind InfoQ.com and the QCon conferences. In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to David Marquet about his keynote talk at the recent Agile 2017 conference and his book – Turn the Ship Around. Why listen to this podcast: - Create organizations for the future that have the right balance of thinking (blue-work) and doing (red-work) - The person doing the work has much more contextual information about the situation than any manager or commander - Empowerment on its own is not enough – strong technical/domain knowledge is a necessary precondition - Match the language you use to the type of activity being done – thinking vs doing, blue-work or red-work More on this: Quick scan our curated show notes on InfoQ http://bit.ly/2grZxbR You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Want to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2grZxbR