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

Published: Sept. 4, 2017, midnight

b'This is the Engineering Culture Podcast, from the people behind InfoQ.com and the\\xa0QCon conferences.\\n\\nIn 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 \\u2013 Turn the Ship Around.\\n\\nWhy listen to this podcast:\\n\\n - Create organizations for the future that have the right balance of thinking (blue-work) and doing (red-work)\\n - The person doing the work has much more contextual information about the situation than any manager or commander\\n - Empowerment on its own is not enough \\u2013 strong technical/domain knowledge is a necessary precondition\\n - Match the language you use to the type of activity being done \\u2013 thinking vs doing, blue-work or red-work\\n\\nMore on this: Quick scan our curated show notes on InfoQ http://bit.ly/2grZxbR\\n\\nYou can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq\\n\\nSubscribe: www.youtube.com/infoq\\nLike InfoQ on Facebook: bit.ly/2jmlyG8\\nFollow on Twitter: twitter.com/InfoQ\\nFollow on LinkedIn: www.linkedin.com/company/infoq\\nWant to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2grZxbR'