It wasn’t, in any sense, a planning system, acting slowly on stale and summarized information. Instead, it acted fast on current, raw, and detailed information. The RAF’s force multiplier was an intelligence system.

What all of these things have in common is that they move information across an organization as fast as possible, and do so to empower immediate and responsive action. Their underlying assumption is that people are wise, and that if you can present them with accurate, real-time, reliable data about the real world in front of them, they’ll invariably make smart decisions. It’s not true that the best plan wins. It is true that the best intelligence wins.

What can you do as a team leader to create such an intelligence system for your team? First, liberate as much information as you possibly can. Think about all the sources of information you have, and make as many of them as possible available to your team, on demand. Planning systems constrain information to those who “need to know.” Intelligence systems don’t— they liberate as much information as possible, as fast as possible. So don’t worry too much at first about whether your team will understand the data or be able to make use of it. If you think the information will help your people gain a better understanding of their real world in real time, share it. ...

Second, watch carefully to see which data your people find useful. Don’t worry too much about making all this data simple or easy to consume, or about packaging it for people, or weaving it together to form a coherent story. The biggest challenge with data today isn’t making sense of it—most of us deal with complexity all the time, and are pretty good at figuring out what we need to know and where to find it. No, the biggest challenge with data today is making it accurate—sorting the signal from the noise. This is much harder, and much more valuable for our teams. So be extremely vigilant about accuracy; watch which information your people naturally gravitate toward; and then, over time, increase the volume, depth, and speed of precisely that sort of data.

Third, trust your people to make sense of the data. Planning systems take the interpretation of the data away from those on the front lines, and hand it off to a select few, who analyze it and decipher its patterns, and then construct and communicate the plan. Intelligence systems do precisely the opposite—because the “intelligence” in an intelligence system lies not in the select few, but instead in the emergent interpretive powers of all front-line team members. You are not the best sense maker. They are.

The more frequent sense-making rituals you establish on your team, the more information you will liberate, the more intelligence you will generate, and the more trust you will engender. Trust can never emerge from secrecy. Frequency creates safety.

As a leader, you are trying to unlock the judgment, the choices, the insight, and the creativity of your people. But, as we’ve seen in the last two chapters, the way we go about this doesn’t make much sense. We cloister information in our planning systems, and we cascade directives in our goal-setting systems. Instead, we should unlock information through intelligence systems, and cascade meaning through our expressed values, rituals, and stories. We should let our people know what’s going on in the world, and which hill we’re trying to take, and then we should trust them to figure out how to make a contribution. They will invariably make better and more authentic decisions than those derived from any planning system that cascades goals from on high.