Team Thinking Visualized by Claude: The Atlassian Williams F1 Partnership

Pattern of Thought: Making the Invisible Visible

Formula 1 is often described as the fastest sport in the world, but the true speed of F1 is not measured in kilometers per hour. It is measured in milliseconds of judgment. The promotional film for Anthropic’s collaboration with the Atlassian Williams F1 Team condenses an entire race into a series of fragmented thoughts: Instinct. Load nine. Pressure. Calculating. Focus. 0.4 seconds. Analyzing. Teamwork. Adrenaline. Keep pushing past the limit. To the very last second. Hold on, team. Each of these words represents a real category of cognitive event happening inside a race team during competition.

“Pattern of Thought” is the name given to a Claude-powered visualization system designed to surface exactly this layer of work. When a driver crosses the finish line, cameras capture the car. What the cameras never show is the network of human cognition that placed the car in that position. The strategist who decided to pit one lap early. The tire engineer who spotted a degradation anomaly at lap 23 and radioed a warning. The data scientist whose compound model predicted a 0.4 second per lap advantage from switching to a softer tire. Pattern of Thought is the attempt to make all of that thinking legible — to visualize the cognitive substrate of performance.

To understand why this matters, consider what “Load nine” actually means. In F1 tire parlance, Pirelli (the sole tire supplier) designates compounds on a scale. “C1” through “C5” describes rubber hardness, where C1 is the hardest and most durable and C5 is the softest and fastest but quickest to degrade. “Load nine” is a shorthand reference used inside teams for tire load cycles — the stress applied to rubber across a stint. When an engineer says “load nine,” they are communicating a specific threshold in the degradation model: that the tire has absorbed nine units of load stress, and the predicted performance cliff is approaching. This is not casual conversation. It is a piece of structured information that triggers a cascade of decisions about pit stop timing, compound selection for the next stint, and driver instructions to manage pace. A single phrase unlocks an entire decision tree.

Similarly, “0.4 seconds” is rarely just a number. In race context it is almost always a gap: the undercut window. If a car is 0.4 seconds per lap slower than the car behind it after a pit stop, the car behind can realistically undercut — pit slightly later, emerge on fresher rubber, and overtake in the pit exit phase. 0.4 seconds is also the typical margin within which a pit crew targets its stop time. Below 2.4 seconds total is good; below 2.0 is excellent. The difference between 2.0 and 2.4 is that 0.4 — and in a tight race it decides track position. When Pattern of Thought captures “0.4 seconds” as a cognitive marker, it is capturing the moment a human mind registered a critical threshold and prepared to act.

The Invisible Work That Decides Every Race

Broadcast television shows you the car. It shows you the overtake, the pit stop, the spray of gravel when a driver pushes too hard. What it cannot show you is the work happening a hundred meters from the pit lane, inside the garage and on the pit wall, and five thousand miles away in the team’s factory where engineers are watching telemetry streams in real time.

A modern F1 race team operates as a distributed intelligence network. The race engineer sits in the pit lane with a headset, managing the driver directly. The performance engineers monitor dozens of sensor channels — tire temperature, brake temperature, fuel load, chassis balance — and flag anomalies before they become failures. The strategy team runs probabilistic models on every possible pit stop window, updating their recommendations every time a safety car appears, every time rain threatens, every time a competitor makes an unexpected move. The communications team manages media obligations during the race. The logistics team is already planning the freight load for the next race, which may be on a different continent within eight days.

All of this constitutes what organizational theorists call “distributed cognition” — intelligence that does not live in any single mind, but emerges from the interaction of many minds working with shared information. F1 teams are one of the most compressed and high-stakes examples of distributed cognition in professional life. Pattern of Thought is designed to surface that distribution — to make visible not just what decisions were made, but how the cognitive load was shared, when information flowed between nodes, and which mental models governed the choices that determined the result.

Claude enables this through a combination of natural language processing and pattern recognition. Race team radio communications are transcribed and parsed in near-real time, with Claude identifying decision-relevant phrases — tire calls, gap references, driver state communications — and classifying them into cognitive categories. Sensor data from the car provides a parallel stream of structured information. Claude correlates the two: when a driver reports “the front feels loose,” does the telemetry confirm a balance shift? When a strategist calls a pit stop, what gap data, tire model, and track position information preceded that call? The visualization layer then renders this as a dynamic map of team thinking — a pattern, hence the name.

Monaco: The Right Stage for a Thinking System

The choice to debut Pattern of Thought at Monaco was not incidental. Monaco is the most cognitively demanding circuit on the F1 calendar for reasons that go far beyond the famous barriers and the narrow streets. It is the circuit where outright car speed matters least and team strategy matters most.

Overtaking at Monaco is nearly impossible. The circuit is so narrow that a car that qualifies on pole position often wins, simply because there is nowhere for competitors to pass. This shifts the burden from mechanical performance to strategic intelligence. Pit stop timing, tire selection, reaction to safety car periods — these cognitive decisions become the primary competitive variable. A team with a slightly slower car can beat a faster car at Monaco through superior thinking. The track is, in effect, an amplifier of team intelligence.

This makes Monaco the ideal stage for a system designed to visualize team thinking. The correlation between cognitive work and race result is more direct here than anywhere else on the calendar. When Pattern of Thought maps the decision moments that led to a result at Monaco, it is mapping the actual causal chain of performance.

The broader implications extend well beyond motorsport. The concept of making team thinking visible — of capturing the patterns of cognition that drive outcomes — applies to any domain where distributed intelligence determines results. Surgical teams navigating complex procedures. Emergency response coordinators during a crisis. Trading desks managing portfolio risk in real time. In each case, there is a gap between the visible output and the invisible cognitive work that produced it. Pattern of Thought is a proof of concept that this gap can be closed with the right combination of AI, data infrastructure, and visualization.

🧠 Check your understanding

5 questions · your answers are saved in this browser only

1. 1. What does 'Load nine' refer to in an F1 race team's communications?

   The ninth driver on the team roster A tire stress threshold in a degradation model The ninth lap of a race stint A fuel load measurement in kilograms

   In F1 tire engineering, 'load' refers to the cumulative stress applied to a tire compound over a stint. 'Load nine' is shorthand for a specific threshold in a tire degradation model, signaling that performance degradation is approaching and a pit stop decision needs to be made.

2. 2. Why was Monaco chosen as the debut circuit for Pattern of Thought?

   Because Monaco has the most cameras and broadcast infrastructure Because it is the fastest circuit and shows AI speed best Because strategy and team thinking matter more than car speed at Monaco Because Anthropic has an office in Monaco

   Monaco is so narrow that overtaking is nearly impossible, which means team strategy and cognitive decisions (tire choices, pit timing, safety car reactions) become the primary competitive variable. This makes the correlation between team thinking and race result more direct at Monaco than anywhere else, an ideal setting for a thinking-visualization system.

3. 3. What does '0.4 seconds' typically represent in F1 race strategy?

   The time a driver saves by taking a different line through a corner The undercut window or margin within a pit stop timing target The gap needed between cars before a safety car is deployed The minimum interval between radio transmissions

   In race strategy, 0.4 seconds is a critical threshold in undercut analysis — if a chasing car is faster by this margin, it can pit and emerge ahead on fresher rubber. It is also the typical margin within which world-class pit crews target their stop times (sub-2.4 seconds is good; sub-2.0 is exceptional).

4. 4. What is 'distributed cognition' as it applies to an F1 team?

   The ability of a driver to think in multiple languages Intelligence that emerges from many minds working with shared information rather than residing in one person The AI system distributing race data to different team members The process of distributing sensor data across multiple servers

   Distributed cognition is an organizational theory concept: intelligence that does not live in any single mind but emerges from the interaction of many people using shared tools and information. An F1 team is one of the most time-compressed examples of this in professional sport.

5. 5. Which of the following is NOT listed as a role that Claude plays in the Pattern of Thought system?

   Parsing radio communications with natural language processing Correlating driver verbal reports with telemetry data Automatically making pit stop decisions for the strategy team Identifying decision-relevant phrases and classifying cognitive events

   Pattern of Thought is a visualization and analysis system that augments team thinking — it surfaces patterns and correlates information. It does not make decisions autonomously. Pit stop decisions remain with the human strategy team.

Reset quiz

🛠️ Build it yourself

Follow these exact steps to reproduce it yourself · estimated time: ~25 minutes

Prerequisites

• Access to Claude
• A set of Slack threads, emails, or meeting notes from a high-stakes team decision

Step 1 — Collect your decision artifacts

Gather the raw material from a real high-stakes decision your team made. This could be a product launch, a hiring decision, a budget call, or a crisis response. Pull together the Slack thread, the email chain, the meeting notes, or a written summary of what happened. Aim for at least 500 words of material — enough for Claude to identify distinct cognitive events.

Step 2 — Paste and prompt for decision moments

Paste your material into Claude with this prompt: “I’m going to share the communications from a key decision our team made. Please read through it and identify the distinct decision moments — specific points where the team chose one path over another. For each decision moment, note: what triggered it, what information was available, and what alternatives were considered.”

Step 3 — Map the information that drove each decision

Follow up with: “For each decision moment you identified, tell me: what piece of information was most critical to the choice made? Was there any information that was missing or uncertain at the time?” This reconstructs the information architecture of your team’s reasoning.

Step 4 — Identify the mental models in use

Ask Claude: “Based on these decision moments and the information used, what mental models or frameworks does our team seem to be using when we make decisions under pressure? Where do those models seem strong, and where might they create blind spots?”

Step 5 — Visualize the cognitive map

Ask Claude to summarize everything as a simple decision map: “Create a brief cognitive map of this decision: a timeline of decision moments, the information that drove each one, and the mental models that shaped the outcome. Format it as a structured list.” You now have a Pattern of Thought for your own team — a visible record of the invisible work that produced your result.