--- title: "General Stanley McChrystal’s Shared Consciousness: What I Learned About Organizational Visibility From Hundreds of Teams" url: "https://www.collective-genius.com/insights/general-stanley-mcchrystal-s-shared-consciousness-what-i-learned-about-organizat" author: "Jeff James Martin" organization: "Collective Genius" date_published: "2026-08-16T07:00:28.823Z" date_modified: "2026-08-16T07:00:28.823Z" reading_time_minutes: 14 cluster: "Organizational Execution" tags: ["Organizational Intelligence", "Organizational Visibility", "Team-of-Teams", "Organizational Execution", "Decision Making", "Cross-Functional Alignment", "Peak OS"] description: "General Stanley McChrystal’s Shared Consciousness explains why scaling teams need shared context. Learn what hundreds of teams taught me about organizational visibility, intelligence, and Peak OS." --- # General Stanley McChrystal’s Shared Consciousness: What I Learned About Organizational Visibility From Hundreds of Teams General Stanley McChrystal’s concept of Shared Consciousness explains why growing organizations need more than information: teams need enough shared context to understand the larger operating environment and make better decisions. After working with hundreds of teams, I have seen that organizational visibility becomes the bridge between disconnected information and organizational intelligence. One of General Stanley McChrystal’s most important ideas in the Team of Teams framework is **Shared Consciousness**. After working with hundreds of CEOs, founders, leadership teams, and growth companies over more than two decades, I have come to believe it addresses one of the most common and least understood problems in organizational execution: **Most organizations do not suffer from a lack of information. They suffer from a lack of shared context.** Sales has information. Product has information. Engineering has information. Customer Success has information. Finance has information. Leadership has information. The problem is that those groups often do not see enough of the same reality at the same time. That creates a strange condition inside growing organizations. Everyone can be intelligent. Every team can be working hard. The company can possess enormous amounts of data. And yet the organization itself can still behave unintelligently because the information required to understand the whole is fragmented across teams. McChrystal’s idea of Shared Consciousness provides useful language for what high-performing organizations need instead. The McChrystal Group describes Shared Consciousness as the collective intelligence and understanding that comes from a shared view of the operating environment and strong internal connectivity. It emphasizes consistent, transparent information sharing and reliable forums through which people build common understanding. In my work, I have increasingly described the organizational version of this as **shared visibility** and, ultimately, **organizational intelligence**. The goal is not for everyone to know everything. The goal is for the organization to create a **common operating picture** that allows people to understand enough of the whole to make better decisions within their part of it. That distinction becomes critical as companies scale. ## Information Is Not the Same as Organizational Intelligence Organizations have never had more information. There are dashboards. CRMs. Project-management platforms. Financial reports. Slack channels. Business intelligence systems. OKR platforms. Customer analytics. AI-generated summaries. Meeting transcripts. Documents everywhere. Yet adding more information does not necessarily make an organization more intelligent. The McChrystal Group makes a similar distinction in its work on Shared Consciousness: the challenge is not merely distributing more data but creating the context necessary for people to develop situational awareness and act effectively. That distinction matters. Data tells you something happened. Information helps explain what happened. Shared context helps people understand why it matters. Organizational intelligence helps the organization decide what to do next. That last step requires connection. Imagine Sales sees a sudden increase in demand from a particular customer segment. That is useful information. But perhaps Product is prioritizing features for another segment. Engineering is allocating resources around that roadmap. Marketing is running campaigns based on last quarter’s ideal customer profile. Finance is planning headcount based on assumptions made six months earlier. Customer Success is simultaneously seeing unexpectedly high retention from the same segment Sales just discovered. Each function possesses valuable information. But the opportunity does not become organizational intelligence until those signals connect. When they do, something changes. The company can collectively recognize the pattern, understand its implications, decide whether priorities should change, and coordinate action. That is much closer to what Shared Consciousness actually enables. ## The CEO Often Becomes the Organization’s Human Integration Layer This is one of the most consistent patterns I have seen as companies grow. At first, the founder knows almost everything important happening inside the company. They are in customer calls. They participate in product discussions. They talk with Engineering. They know the investors. They review the financials. They interview candidates. They hear complaints. They understand the history behind decisions. Because the company is small, the founder naturally creates shared context. Then the organization expands. Functions become deeper. More conversations happen without the CEO. More people develop specialized knowledge. More decisions occur simultaneously. Soon, no individual can realistically know everything happening inside the organization. But many companies continue operating as though the CEO should. The result is that the CEO becomes the integration layer. Sales tells the CEO something. The CEO tells Product. Product raises another issue. The CEO connects Engineering. Finance needs context. The CEO explains it. Customer Success discovers a risk. The CEO brings everyone together. Information goes up. Decisions come down. More information goes up. Eventually the CEO becomes the only person with anything close to a complete picture. In *Peak Teams*, I describe how exhausting this becomes. CEOs need visibility into what teams are doing without personally executing or checking every detail. The organization needs a system that allows teams to own the work while keeping everyone on the same page. That is an organizational visibility problem. And it cannot be solved by asking the CEO to communicate more. ## Shared Consciousness Moves Context From the CEO Into the Organization A scalable organization has to move important context out of individual heads and into the operating environment. This does not mean documenting everything. It means intentionally making the information that affects execution visible to the people whose decisions depend on it. People should understand the company's direction. They should see the outcomes the organization is trying to achieve. Teams should understand how their own outcomes connect. Relevant metrics should be visible. Dependencies should surface before they become failures. Risks should travel across team boundaries. Important decisions should not disappear inside a leadership meeting if they change the work of other teams. The organization should be able to answer: Where are we going? What matters most right now? Are we making progress? Where are we off course? What has changed? What teams depend on one another? Where are decisions required? What do we know now that we did not know before? When enough of those answers are visible, people can make much better decisions without needing to continuously ask leadership what is happening. Shared context begins replacing centralized coordination. ## Visibility Does Not Mean Everyone Sees Everything This is an important distinction. When leaders hear the words transparency or shared visibility, they sometimes imagine an organization drowning in information. That would be counterproductive. An engineer does not need every sales conversation. Sales does not need every technical discussion. Everyone does not need to attend the executive meeting. Every Slack channel does not need to become public. Shared Consciousness is not universal information access without judgment. It is making **relevant context accessible across boundaries**. A Product leader may not need every Sales metric, but should understand meaningful changes in the market that affect the product roadmap. Finance does not need the details of every engineering sprint, but should understand important capability investments that affect the financial plan. Engineering does not need to listen to every customer call, but should understand patterns in customer behavior that change priorities. Leadership does not need to inspect every task, but should be able to see whether important outcomes are on or off course. The operating principle is simple: **People need enough visibility into the whole to make better decisions about their part.** That is very different from everyone knowing everything. ## The Common Operating Picture One of the most useful phrases in McChrystal Group’s work is **common operating picture**. In a Team of Teams transformation with a Fortune 100 energy company, the organization established a cross-functional Operations Forum connecting leadership, technical specialists, field experts, and other critical participants. The forum created a recurring place to bring current information and context together, helping develop a shared view of reality across the organization. McChrystal Group describes it as building shared consciousness on a weekly basis and connecting ground-level information with leaders responsible for broader strategic objectives. This idea translates remarkably well into growth companies. A common operating picture should allow teams to see the organization’s most important outcomes, performance signals, risks, priorities, and dependencies without reconstructing the company from a dozen disconnected systems. This is one of the reasons I have become increasingly focused on visibility in Peak OS. A company needs more than a strategy. It needs a shared picture of whether that strategy is actually being executed. A company needs more than goals. People need to see how company outcomes and team outcomes connect. A company needs more than metrics. Teams need to understand what those metrics are telling them and how changes affect the rest of the organization. A company needs more than meetings. It needs a rhythm through which information becomes shared understanding, decisions, and action. That is the difference between a dashboard and a common operating picture. ## Cross-Functional Dependencies Are Where Visibility Often Breaks Some of the most consequential organizational problems occur not inside teams, but **between them**. Marketing generates demand that Sales cannot convert. Sales sells a capability Product has not prioritized. Product creates commitments Engineering cannot deliver on the expected schedule. Customer Success identifies a customer pattern that never reaches Product. Finance changes assumptions without the operating teams understanding the impact. People builds a hiring plan disconnected from the actual capabilities required by the strategy. These problems can initially look like execution failures. Often they are visibility failures first. One team did not know something another team knew. Or both teams possessed the information but interpreted it differently. Or the dependency did not become visible until it was already causing a problem. The strongest teams I have worked with do not eliminate dependencies. They expose them. They make it normal to ask: Who else does this affect? What do we need from another team? What does another team need from us? What assumption are we making? What happens elsewhere if we change this? That behavior turns cross-functional work from a series of handoffs into a connected system. ## I Have Seen How Small Differences in Reality Create Large Execution Problems Sometimes the lack of shared context appears in remarkably simple ways. In *Peak Teams*, Flowspace Chief Revenue Officer Anne Hallock described how the company discovered that Sales and Customer Success were measuring a shared metric differently. Both teams were working from what they believed was valid information, but their definitions of success were not actually the same. Creating greater transparency around priorities and goals helped the organization establish a more unified operating picture across teams. I have seen versions of this hundreds of times. Two departments use the same word but mean something different. Two executives quote different annual targets. One team believes an initiative is the highest priority while another believes it has been deprioritized. Everyone says they understand the strategy until their decisions reveal different interpretations of it. These are dangerous problems because they can remain invisible for a long time. There may be no obvious conflict. People may like one another. Teams may be hitting local objectives. But they are operating from different versions of reality. Shared visibility exposes those differences while there is still time to resolve them. ## Peak OS Creates Visibility Through Connected Outcomes One of the ways Peak OS approaches this problem is by connecting outcomes across levels of the organization. The mission establishes why the organization exists. The Three-Year Vision creates a shared longer-term destination. The One-Year Plan defines what success should look like in the nearer term. Company OKRs identify the capabilities and outcomes that matter now. Team outcomes connect functional work back to those company priorities. KPIs provide visible signals about how the business is performing. The important word is **connect**. A collection of goals is not a system. Every department can have excellent goals and still create organizational drift if those goals were created independently. In *Peak Teams*, I describe how OKRs become particularly valuable when the entire team understands how functional objectives intersect. An objective in one area rarely exists in a vacuum; its success often depends upon the work of other teams. Visibility makes those relationships explicit. Instead of: Here are the Sales goals. Here are the Product goals. Here are the Engineering goals. The organization begins asking: How do these outcomes collectively move the company forward? That shift is subtle but fundamental. ## The Weekly Operating Rhythm Should Build Shared Consciousness Shared Consciousness cannot be created in an annual planning session and then assumed to exist for the rest of the year. Reality changes too quickly. Customers change. Markets change. Metrics change. People change. Plans change. New information appears constantly. That is why McChrystal Group emphasizes consistent information sharing and forums that repeatedly reconnect people around the operating environment. It is also why operating rhythm is fundamental to Peak OS. The Weekly Camp is not intended to be a traditional status meeting. Its purpose is to reconnect execution. Teams review objectives. They review KPIs. They surface things that are off course. Relevant updates create context. Triage identifies the most important problems and decisions requiring collective attention. Actions receive owners. Communication travels back through the organization. The rhythm continually answers a central question: **What does the team need to understand now in order to execute well next?** When Weekly Camp becomes a sequence of lengthy status reports, it loses much of this value. When it creates a common operating picture, it becomes an organizational intelligence loop. ## Visibility Should Lead to Decisions This is where many organizations stop too early. They create dashboards. They hold meetings. They distribute reports. Everyone becomes more informed. But nothing changes. Visibility has value only when it improves execution. A KPI moves off course. What does that tell us? A customer pattern changes. What decision follows? A dependency appears. Who needs to act? An objective is slipping. Is the issue resources, ownership, strategy, timing, or something else? A new opportunity emerges. Does it matter enough to change the plan? Information has to move through a progression: **Signal → Shared Understanding → Decision → Action → Learning** Without shared understanding, people make isolated decisions. Without decisions, meetings become reporting exercises. Without action, visibility becomes observation. Without learning, the organization keeps rediscovering the same problems. Organizational intelligence requires the whole loop. ## Shared Consciousness Makes Empowerment Possible This is one of the reasons Shared Consciousness is so important within the broader Team of Teams model. Leaders often want decisions pushed closer to the work. That is a good instinct. But decision authority without organizational context is dangerous. If Sales makes decisions based only on Sales information, Product decisions based only on Product information, and Engineering decisions based only on Engineering information, distributed decision-making can accelerate fragmentation. People need context before they can responsibly exercise autonomy. McChrystal Group's Team of Teams model connects Shared Consciousness with Empowered Execution for exactly this reason: teams need information and understanding if they are going to make sound decisions without waiting for everything to move through traditional hierarchy. That relationship maps directly to something I have observed repeatedly: **Shared context enables distributed ownership.** The better the organization's shared operating picture becomes, the less often people need to ask the CEO what to do. ## Organizational Visibility Reduces CEO Dependency This may be one of the clearest signs that a system is working. Without organizational visibility, the CEO becomes essential to coordination. With organizational visibility, the CEO remains important to leadership but becomes less necessary as the information router. Instead of answering: “What is Product doing?” “Did Sales know about this?” “Who owns that?” “Are we still committed to this priority?” “What happened to that metric?” “Has Engineering seen this customer issue?” The organization increasingly answers those questions itself. That does not weaken the CEO. It frees the CEO to do the work only the CEO can do. Maintain direction. Build the organization. Allocate attention and resources. Develop leaders. Work with the board. Make the decisions that truly belong at the CEO level. The goal is not a company without leadership. It is an organization that does not require leadership to manually reconnect it every day. ## AI Will Make Shared Consciousness More Important, Not Less Organizations are entering an era in which information will become even easier to create. AI can summarize meetings. Analyze metrics. Generate reports. Surface patterns. Monitor projects. Answer questions across large knowledge bases. That may solve some information-access problems. But it does not automatically create Shared Consciousness. In fact, organizations may face the opposite problem: an explosion of available information without enough shared understanding about what matters. The competitive advantage will not simply be possessing more intelligence. It will be the organization's ability to **turn intelligence into collective understanding and coordinated action**. The same organizational questions remain. Which signals matter? Who needs to know? What changed? What does it mean? Who decides? What do we do next? What did we learn? AI can strengthen the information layer. The organization still needs an operating system that turns that information into execution. ## What Hundreds of Teams Taught Me About Visibility The longer I work with teams, the more convinced I become that visibility is one of the hidden foundations of high performance. Alignment gets easier when direction is visible. Accountability gets stronger when commitments are visible. Trust grows when teams can understand one another's work. Cross-functional coordination improves when dependencies are visible. Decision-making improves when people have broader context. Learning improves when results can be compared against expectations. And CEOs gain freedom when they can see the organization without personally becoming the mechanism through which everyone else sees it. This is why organizational visibility is more than transparency. It is an execution capability. ## The Organization Needs a Shared View of Reality General Stanley McChrystal’s concept of Shared Consciousness provides a powerful way to understand a challenge I have encountered repeatedly across hundreds of teams. As organizations grow, knowledge becomes distributed. That is inevitable. The problem begins when understanding becomes distributed too. Different teams begin operating from different assumptions, different priorities, different signals, and sometimes entirely different versions of reality. The answer is not centralizing all information with leadership. It is not putting everyone in every meeting. And it is not creating another dashboard. The answer is creating enough connection that the organization develops a **shared view of what matters**. A common direction. Connected outcomes. Visible performance. Known dependencies. Relevant risks. Clear decisions. A dependable operating rhythm. And continuous learning. That is how information becomes organizational intelligence. That is how shared consciousness enables a Team of Teams. And it is one of the most important lessons I have learned about scaling organizational execution: **The organization does not need everyone to know everything. It needs the right people to see enough of the whole that they can make better decisions about their part.** ## Related Insights [What Is Peak OS?](https://www.collective-genius.com/insights/what-is-peak-os-mq7jqhdx) [What Is Organizational Execution?](https://www.collective-genius.com/insights/what-is-organizational-execution-mq4rcx9p) [What Is Organizational Intelligence?](https://www.collective-genius.com/insights/what-is-organizational-intelligence-mq7jys1i) [What Is a Business Operating System?](https://www.collective-genius.com/insights/what-is-a-business-operating-system-mq4qmt39) [What Is Operating Rhythm?](https://www.collective-genius.com/insights/what-is-operating-rhythm-mq4qywur) ## Key Takeaways - Organizations rarely suffer from a lack of information; they often suffer from fragmented context. - McChrystal’s Shared Consciousness creates collective understanding through relevant information flow and strong organizational connectivity. - Organizational visibility gives teams enough of a common operating picture to make better decisions without requiring everyone to know everything. - CEOs often become organizational bottlenecks when they are the primary people connecting information across teams. - Connected outcomes, KPIs, risks, dependencies, decisions, and operating rhythm help move context from the CEO into the organization. - Visibility becomes valuable when it produces shared understanding, decisions, action, and organizational learning. - Shared context enables distributed ownership and creates the foundation for empowered execution. ## Frequently Asked Questions ### What does Shared Consciousness mean in General Stanley McChrystal’s Team of Teams framework? Shared Consciousness describes the collective understanding created when people have access to relevant information, maintain strong internal connectivity, and develop a shared view of their operating environment. It allows teams to make decisions with broader organizational context. ### What is organizational visibility? Organizational visibility is the ability for leaders and teams to see the relevant priorities, outcomes, metrics, risks, dependencies, and decisions required to understand how the organization is executing. ### Is organizational visibility the same as transparency? No. Transparency often refers broadly to making information available. Organizational visibility is more purposeful: it makes the information and context that affect execution visible to the people whose work and decisions depend upon it. ### What is a common operating picture? A common operating picture is a shared understanding of the organization's current situation, including priorities, performance, risks, changes, dependencies, and decisions. McChrystal Group has used recurring cross-functional operating forums to create this shared context in Team of Teams transformations. ### Why does a CEO become a bottleneck when organizational visibility is weak? When information is fragmented across teams, the CEO often becomes the person who collects, interprets, and redistributes context. Decisions and dependencies then continually escalate upward because other people cannot see enough of the organization to act confidently. ### How does Peak OS create organizational visibility? Peak OS connects mission, long-term direction, annual planning, company and team outcomes, OKRs, KPIs, roles, risks, dependencies, problem-solving, and operating rhythm so teams can understand both their own work and the organizational context surrounding it. ### How does Shared Consciousness improve decision-making? Shared Consciousness gives people relevant context before they act. Instead of making decisions from the perspective of one function, teams can understand broader priorities, dependencies, and consequences and make decisions that better serve the organization as a whole. ### Why will organizational visibility matter more as AI becomes more capable? AI can dramatically increase the amount of information organizations can generate and analyze. That makes the ability to identify meaningful signals, create shared understanding, coordinate decisions, and turn information into action even more important. Source: https://www.collective-genius.com/insights/general-stanley-mcchrystal-s-shared-consciousness-what-i-learned-about-organizat