Goal Conflicts Cause Work Intake Problems, Finding Time To Concentrate, Conversations with Jeremy Willets and Jon M Quigley, SPaMCAST 816

Published: June 23, 2024, 9 p.m.

A funny thing happened on the way to SPaMCAST 816, I had so much fun during our first Summer Camp session I talked Jeremy into letting me share the audio of our discussion on the podcast. We discussed goal conflicts, the first of eight work intake problems, from our book, Mastering Work Intake. If the video is more your style check out the video on LinkedIn and then join us at 11:30 EDT on June 16th. This week we also have a visit from\xa0. Jon and I discussed the question \u201cIf all work is collaborative, when do you find time to concentrate?\u201d Learn To Tame Your Work Intake Beast! Jeremy Willets and I are celebrating summer in the northern hemisphere with a summer camp. We\u2019ll look at the primary causes of work intake problems\u2026 and how to solve them! Join us for an entertaining and informative LinkedIn Live event. The next weekly session begins at 11:30 EDT on June 16th. Each session will: Define one work intake problem per session,\xa0 Identify how to recognize the problem,\xa0 Offer a pragmatic approach to tackling the issue, and At least one scary story of work entry gone wrong (this is summer camp) We would like you to register at our Maven page so we can remind you when the session goes live. If you register we also have a Work Intake Problem Worksheet that we use in our workshops that we will email.\xa0 However, if you\u2019d rather not register on Maven you can set a reminder on LinkedIn at . In either case, we will announce when the sessions go live on LinkedIn. Feel free to share the invitation with others. Remind everyone to use sunscreen!\xa0\xa0 Re-read Saturday News Chapter 4 of Mihaly Csikszentmihalyi\u2019s is titled The Conditions of Flow. Flow states just don\u2019t occur randomly. They require several factors to align.\xa0 Some factors can be \u201carranged\u201d while others are context-driven or part of a large feedback loop. I find three concepts central to Chapter 4. Buy a copy and read along \u2013\xa0\xa0 Week 1: \u2013 \xa0 Week 2: \u2013 \xa0 Week 3: \u2013 \xa0 Week 4: \u2013 \xa0 Week 5: \xa0 Next SPaMCAST\xa0 On the next Software Process and Measurement Cast, we will talk with , Co-Founder and Chief Product Officer of - \xa0 One of the topics we discussed is whether building an AI solution is different than building any other solution.