To reflect, map the system, then map the context outside the system; that’s where surprises come from. Or sketch the pace layers from fast to slow, then add drivers and levers; those that are deep are powerful but hard to move. After a project in a debrief ask the team to sort surprises into three categories: what we didn’t know, what we couldn’t know, what we didn’t want to know; and then ask why. Before a project, consider emotion in defining task order. Use a few quick wins to build momentum, then tackle the scary tasks early, so anxiety can’t drag you down. Finally, go for a walk or take a
...more
