Hey Reader, Welcome to the 24th edition of the 3-2-1 (check out previous issues here). Last edition I argued that judgment gets built through reps. This week I go one level deeper and try to answer what judgment actually is. A new HBR article gave me a starting taxonomy, AI helped me stress-test it, and now I need your judgment to finish the job. This edition ends with a chance to share your perspective, so read to the end! Let's get into it. 3 Things for Work (in L&D)How Do Workers Develop Good Judgment in the AI Era? (HBR)
The Tragedy of the Cognitive Commons (Human Resource Development Review)
Don't Be a Meat Proxy (Niklas Gruhn)
2 Things for LifeA thread of voice-to-text app recommendations (X)
What to Make of a Life by Jim Collins
1 Idea from MeAI helped me generate eight new forms of judgment. Now I need your judgment to choose four.I've been thinking about judgment for months now. First, I wrote about curiosity as a way to suspend judgment. Then I argued that AI shifts the cognitive load from production to judgment. Most recently, I described performance as judgment-in-context. But I never tried to define it. Then I found the work of David S. Duncan, a former McKinsey consultant and disciple of Clayton Christensen. In the HBR article linked above, he names five forms:
It was the most useful definition of judgment I had seen. Duncan's five cover the core of individual decision-making. But judgment in organizations also requires knowing what to ask, when to act, who to involve, and how much is enough. So I tried to fit it to Seek-Sense-Ship, the model we teach, to identify gaps. My first pass looked like this:
That looked lopsided. Three forms clustered around making sense of information. Only one helped you gather the right inputs. Only one helped you turn a recommendation into action. That may be because Sense is where most judgment happens. Or it may be because the model was missing something. So I set myself a mission: find the gaps and fill them in without turning the model into my garage at the end of the summer. Of course, I asked AI to help. But I didn't ask it to "give me more types of judgment." That would have produced a long list of clever-sounding synonyms. I asked it to find functions the original five did not perform, test each candidate for overlap, and create a more balanced model across Seek, Sense, and Ship. We ended up with eight candidates:
I don't think all eight survive. Scope may be a form of tradeoff judgment. Delegation may be the other side of ownership. I'm also not convinced these are all new. People needed inquiry, timing, and stakeholder judgment long before AI arrived. What AI changes is we now have to decide what to delegate to a machine, which outputs look right, and when to override a confident recommendation. AI can weaken judgment when it removes the struggle that develops it. But it can also strengthen judgment when we use it to open the problem instead of close it. Across Seek-Sense-Ship, that looks like:
That is how I used it here. AI expanded the possibilities, but it didn't make the final call. That part belongs to me and you. My goal is to add four forms to Duncan's five, creating a working model of nine. Which four would you keep? Reply with four numbers. That's it for this week - enjoy your Sunday! I'll be back in two weeks โ๏ธ Andrew P.S. If you want to see another demo of how I use AI to think better, check out the playback of my Maven session from last week. |
ICs can do more on their own with AI than ever before. This is both a challenge and an opportunity for L&D. This newsletter explores how to equip ICs with the influence skills that drive retention, accelerate OKRs, and position L&D as a strategic partner to the business. (Sent twice a month).
Hey Reader, Welcome to the 23rd edition of the 3-2-1 (check out previous issues here). This week I sat down with alumni of a thinking-skills program we've been running for almost two years. One of them, now leading a team, described working with AI as a pressure cooker. Everyone is expected to have an answer instantly, and AI makes instant answers easy. That conversation is the theme of 1 Idea From Me below, plus I've got two new papers that landed on opposite sides of the same argument up...
Hey Reader, Welcome to the 22nd edition of the 3-2-1 (check out previous issues here). This one started with a post from Jolene Skinner at MongoDB lamenting how the skills-based movement is distracting us from the real problem we need to solve. It charged my brain for the rest of the day. The problem, in five words: skills sit still, work doesn't. Let's get into it. 3 Things for Work (in L&D) Why the skills-based movement doesn't work for most companies (Jolene Skinner, LinkedIn) Jolene...
Hey Reader, Welcome to the 21st edition of the 3-2-1 (check out previous issues here). This one is about the most misunderstood idea in L&D, and why the way we use AI to write software is the wrong template for the rest of work. Let's get into it. 3 Things for Work (in L&D) A New Paradigm For Corporate Training: Learning In The Flow of Work (Josh Bersin) Where the phrase comes from. Bersin's 2018 original defines it as embedding learning content into the platforms where work happens, so you...