Stop Brainstorming: Do THIS Instead

Productivity doesn’t die from social media, multitasking, meeting overload, or email volume. A Microsoft study points to a more fundamental culprit: unclear objectives. But the deeper mechanism is even more practical—people lose momentum by “running around in circles,” confusing speed with velocity. Speed is how fast someone moves; velocity is progress from point A to point B. If work accelerates without changing direction, it produces motion without outcomes.

The fix offered is a deceptively simple tool called the circle map, one of the eight thinking maps used to turn information into knowledge through “cognitive scaffolding.” The method is straightforward: write the topic in the center, list everything known about it in the outer circle (the context), and then use a surrounding rectangle to capture the frame of reference—how the person decides what matters, what influences the definition, and what assumptions sit underneath.

That frame is where disagreements and stalled progress often originate. The transcript illustrates this with a carpet example. A graphic designer’s frame emphasizes minimalism—clean lines and harmonious colors—so the carpet reads as chaotic and ugly. A casino owner’s frame emphasizes utility and profit—hiding dirt, managing wear, keeping players engaged—so the same carpet becomes a functional, even “perfect” solution. The circle map’s value is forcing the frame into the open, turning hidden lenses into explicit statements that can be examined.

Personal life planning shows how the tool separates controllable factors from “gravity problems.” In Arthur’s life example, items inside the circle—such as fitness, a 60-hour work week, and certifications—are within his control. Items outside the circle but inside the frame—like age, the economy, the number of hours in a day, and political realities—can’t be changed, only worked around. The exercise then shifts from trying to fight unchangeable conditions toward reframing: What is the frame of success? The transcript ties this to identity pressure—who someone believes they should be versus who they are intrinsically—arguing that burnout or depression can come from friction between the true center and the imposed frame.

The same logic scales to teams and projects. For an IT project, participants start by filling the circle with features, tasks, stakeholders, and other defining elements. Then each person writes a single sentence describing their frame of reference—engineers may prioritize stability and reducing technical debt, product owners may prioritize shipping the next feature, and project managers may prioritize staying within budget. Once those frames are shared, the group surfaces assumptions: what each role believes the customer values (stability, features, or cost). Externalizing frames moves them from private mental lenses to objects the team can debate, validate with market data, and revise.

The closing “homework” is practical: build a circle map of life to spot friction between authentic self and imposed frames; map a day instead of doing long-form journaling; and experiment with different fill orders, including an empathy-mapping approach where different stakeholders become different frames. The central claim remains blunt: most arguments and issues live in the frame of reference, not in the context itself.