Information Scaling - Part 2
*Note: This is a three part series discussing Information Scaling, how to understand it and how to prepare your business for it. Read Part 1 here: Information Scaling - Part 1
Information Scaling Rules
As I was researching Information Scaling, I was struck by how often Information Scaling events seemed to catch businesses off guard. Why did it seem that history repeated itself again and again where some businesses fared better than others? It’s as if there were bigger controls at play. Why were we making the same mistakes? As it turns out I wasn’t the only one who was thinking about these questions and there are several theories that explain the why and how these “Information Scaling Rules” are applied.
Believe it or not we only have ourselves to blame. What we’re colliding with here are human constraints. While some are biological, most we’ve acquired from how and where we were raised and the experiences we’ve had. We created them. Here are the theories that explain why we as humans react the way we do during Information Scaling events.
Dunbar’s Number (1992)
Rule: Humans biologically can only manage a limited number of relationships.
How it contributes to Information Scaling
As organizations grow during Information Scaling events, the bigger it gets, the more relationships between employees fracture. This is because of the increased communication which in turn dilutes the message. We see this happen when employees complain of the lack of culture or the distrust in leadership.
The Trap
The founder controls all the information that goes out to the company.
The founder relies on his personality and in-person contact to maintain relationships.
The founder feels culture will evolve naturally.
The Fix
Create deliberate channels to disseminate information, e.g. town halls, department meetings, weekly team meetings.
Providing more depth in communication, e.g. Why the need for this project, problems it will solve, etc.
Build project teams from across the company e.g. By sourcing a team inter-departmental you create more camaraderie and communication company wide.
Use centralized systems for knowledge gathering and storage e.g. Prevents hoarding of information and creating an “us vs them” between employees and departments.
Organizational Information Theory (1969)
Rule: An organization's biggest challenge in growth is to interpret information efficiently by creating structures and processes.
How it contributes to information scaling
As information increases during scaling events, ambiguity increases with it. Different people begin interpreting the same data in different ways, which leads to misalignment and slow decision-making. Without structured interpretation, the organization becomes overwhelmed by its own information.
The Trap
As the volume of information increases, the processes required to absorb that information multiplies. This inevitably slows decisions down due to a backlog of information that has to be processed.
Businesses often get stuck in a loop of doing business one way. Information Scaling events look like trends at first and the new opportunities can easily be dismissed.
Companies fall in love with their efficient processes even when their data becomes less reliable. They spend too much time protecting their process that they miss the decision making windows leading to stagnant growth.
The Fix
Most businesses can get very strict with their processes. Practice introducing new ideas and methods. Creating a culture of constantly evolving and improving. This will allow the team to react quicker when environments change and they don’t have to wait for official orders from the top.
Usually the team sees changes coming before the executive team does. Having regular meetings and empowering the team to make decisions allows your team to stay ahead of the curve.
Create thresholds for action. Indicators don’t have to reach a negative percentage for action to take place. By creating indicators that initiate change early at specific increments, you can mitigate issues from getting out of hand quickly and severely.
Media Richness Theory (1986)
Rule: Use specific media channels for the type and importance of the information you are trying to convey e.g. Complex or emotional topics, Video or In-person. Simple data or routine updates, Chat or Email.
How it contributes to information scaling
When a business scales, the sheer volume of information can crush a company if they try to handle every decision in a meeting. MRT allows a company to scale by "offloading" routine or “low-detail” tasks to lean media, reserving expensive, high-bandwidth "human time" for high-stakes strategic pivots. It essentially creates a hierarchy of communication that prevents leadership from becoming a bottleneck.
The Trap
Businesses often default to text media, Chat and Email, for everything because it’s fast. This leads to massive miscommunication on complex projects because the medium can't carry the necessary nuance.
Some companies over-compensate by making every small update a face-to-face meeting, which kills productivity and creates meeting fatigue.
As companies grow, important insights from the front lines get diluted as they move up the chain. By the time information reaches a CEO via a memo, the emotional context of a customer problem is lost.
The Fix
Explicitly define which channels are for what. (e.g., "Policy changes are emails; brainstorming is a whiteboard session; status updates are automated dashboards.")
Train teams to recognize when a text thread is starting to drift. If a chat conversation goes over 5 minutes without a resolution, the rule must be to get on a call to get clarity.
Encourage executives to occasionally engage with additional team members or talk directly to customers. This injects raw, rich data back into a system that has become too reliant on minimal, clean reports.
Transactive Memory Systems 1987
Rule: TMS means your team's productivity isn't based on superstar employees, but on the individual roles and processes of the company. If everyone knows who to talk to and where to go to find out information, then the organization moves faster.
How it contributes to information scaling
TMS allows a business to handle massive amounts of data without burning out individual employees. Instead of every employee needing to be a generalist, TMS creates a distributed knowledge system. As the company grows, you don't need everyone to learn every piece of new information, you just need to update the knowledgebase so the group knows who’s responsible.
The Trap
The Single Point of Failure: Knowledge becomes siloed in one person's head; if they quit or get sick, that entire area of the company is deleted.
The Update Lag: As the company grows, people continue to go to "Bob" for tech advice even though Bob moved to sales three years ago, leading to massive bottlenecks.
Cognitive Roadblock: Managers often try to be the "central hub" for all info, becoming a roadblock for communication rather than a facilitator.
The Fix
Standardize Expertise: Use internal tools such as knowledgebases, Task Management Systems, SharePoint Sites or even Wiki/Forums where employees list “Roles”, "Responsibilities" and "Processes" so the who knows what is searchable and transparent.
Cross-Training for Redundancy: Ensure at least two people "encode" the same specialized information so the TMS doesn't crash if one node is removed.
Regular Knowledge Audits: Conduct "who do you go to for X?" surveys. If everyone points to the same overworked person, it’s time to redistribute that knowledge load.
Cognitive Load Theory (Sweller, 1988)
Rule: In business, efficiency isn't about how much information you can give an employee; it's about limiting the friction an employee experiences so that they can understand it. If a workflow requires someone to keep ten browser tabs open just to complete one task, you have maxed out their cognitive load before they’ve even started the actual work.
How it contributes to information scaling
CLT allows businesses to scale by chunking information. Experts aren’t smarter; they use mental shortcuts that allow them to treat complex sets of information as a single "chunk". Scaling information effectively means designing training and systems that turn complex, multi-step processes into these singular, automated chunks for employees.
The Trap
The Firehose Effect: Dumping three months of "must-know" data into a single week of orientation, which ensures almost none of it moves to long-term memory.
The Split-Attention Tax: Forcing workers to constantly toggle between different software tools or unorganized manuals to find what they need for a single task.
The "Expert Blindness" Problem: Senior leaders design training for beginners that assumes the beginner already has the expert’s mental "shortcuts," making the instructions impossible to follow.
The Fix
Use "Worked Examples": Don't just tell an employee to "figure it out." Provide completed templates and step-by-step examples first, so they can learn the pattern without the stress of worrying if they got it right or wrong.
Audit for Extraneous Load: Regularly cut down on meeting duration, chat notifications, and complex formatting in documents to free up mental space for high-value thinking.
Scaffold the Learning: Break complex training into "micro-missions." Let an employee master one small "chunk" of the job until it becomes automatic before adding the next layer of complexity.
Media Synchronicity Theory (1999)
Rule: In business, you should never use a meeting to dump data, and you should never use an email thread to resolve a heated disagreement. Use slow channels to distribute facts and fast channels to align perspectives.
How it contributes to information scaling
MST allows a business to scale without "meeting fatigue." By moving all updates, reports and data dumps to the correct channels, the organization can push massive amounts of information to thousands of people simultaneously. This preserves expensive live meeting time only for the critical moments where a team needs to get on the same page.
The Trap
The "Status Update" Meeting: Dragging ten people into a room to read data that could have been an email, wasting hours of collective productivity.
The Slack/Email War: Trying to resolve a complex conflict or nuance via text, leading to 50+ messages of confusion because the medium lacks the "speed" to align everyone's understanding.
The Consensus Freeze: Attempting to reach a group decision through chat and email, which results in endless waiting and "reply-all" loops that stall progress.
The Fix
Default to Asynchronous: Make it a policy that all initial information sharing happens via "low-sync" tools (wikis, docs, knowledgebase) so people can process it at their own pace.
The "Three-Reply" Rule: If a text-based conversation (Email/Chat) hasn't reached a resolution after three exchanges, mandate an immediate jump to a "high-sync" channel (Call or Video Call).
Pre-Meeting Homework: Only allow meetings to start once the understanding of information is finished. Use the live time strictly for debating, deciding, and converging on the path forward.
Adaptive Communication Alignment
Rule: Effectiveness in business is measured by the receiver’s comprehension, not the sender’s effort. Adaptive alignment means a CFO gets a data-heavy spreadsheet while a creative team gets a visionary narrative, even if the underlying goal is the same.
How it contributes to information scaling
ACA contributes to scaling by reducing rework and clarification loops. When communication is aligned from the start, information moves through the organization without getting stuck in "What did they mean by this?" cycles. It allows leadership to transmit a core strategy across diverse departments (engineering, sales, HR) by "translating" it into the specific professional language of each group, ensuring total organizational buy-in.
The Trap
The Echo Chamber Effect: Leaders only communicate in their own preferred style (e.g., overly technical), which alienates or confuses departments that think differently, creating "cultural silos."
The Velocity Gap: High-speed communicators (who want quick bullets) clash with high-detail communicators (who want deep context), causing frustration and perceived incompetence on both sides.
The Persona Friction: Companies use a "corporate voice" that is too rigid, failing to adapt to the nuances of different client segments or internal remote teams, leading to a lack of trust and engagement.
The Fix
Implement "User Manuals": Have team members create a "How to Work With Me" document that explicitly states their preferred communication style, level of detail, and response times.
The Context-First Header: Train staff to begin every communication with the intended outcome (e.g., "For Information Only" vs. "Action Required"), which helps the receiver align their mental state before processing the details.
Style-Switching Training: Invest in coaching that teaches managers how to identify the "Social Styles" of their direct reports, allowing them to flip between "driver," "analytical," or "amiable" tones based on who they are talking to.
Personality Theory (Big Five, MBTI-type frameworks)
Rule: Personality is the "operating system" and skills are the "apps." It’s much easier to teach a detail oriented person how to use a CRM than it is to teach a disorganized person how to care about details.
How it contributes to information scaling
Personality frameworks allow a business to scale by optimizing cognitive diversity. By understanding team members' traits, leaders can assign roles that match natural inclinations. For example, high-Openness individuals handle the "scaling" of new, ambiguous ideas, while high-Conscientiousness individuals "scale" the systems and repeatable processes that keep the company stable as it grows.
The Trap
Stereotyping & Bias: Using results to "box people in" (e.g., "She's an Introvert, so she can't lead the pitch"), which kills potential and creates resentment.
The "Hiring Clone" Problem: Leaders subconsciously hire people with personalities just like their own, creating a "homogenous brain" that lacks the friction necessary to catch mistakes.
Pseudoscientific Over-reliance: Treating a 15-minute quiz as an absolute truth rather than a conversation starter, leading to rigid management decisions based on flawed data.
The Fix
Use for Development, Not Selection: Use these tools primarily for post-hire team building and communication workshops, rather than as a "pass/fail" gate for hiring.
Seek "Complementary Friction": Purposefully pair opposites, like a high-Openness visionary with a high-Conscientiousness project manager, to ensure ideas are both creative and executable.
The "Trait, Not Type" Approach: Focus on specific behaviors (e.g., "needs more time to process info") rather than labels (e.g., "The Architect"), allowing for growth and situational flexibility.
Leadership Communication Theory
Rule: A leader’s job is to act as a noise filter. Every vague instruction from the top creates hours of wasted "interpretation time" at the bottom. Effective leadership communication removes the friction of doubt so the team can move at full speed.
How it contributes to information scaling
Leadership Communication Theory scales information through Narrative Leverage. As a company grows, a leader cannot talk to everyone individually. By creating a powerful, simple "Core Narrative" (the mission/values), they provide a mental framework that employees use to make autonomous decisions. This "scales" the leader’s intent without requiring their physical presence in every meeting.
The Trap
The Illusion of Transparency: Leaders assume because they know the strategy, everyone else does too, leading to "trickle-down confusion" where the front line is flying blind.
The Signal-to-Noise Failure: Sending out massive, "corporate-speak" memos that contain so much fluff that employees stop reading them entirely, missing critical updates.
The Authenticity Gap: Using scripted, robotic messaging during crises or changes, which destroys trust and causes employees to seek "the real truth" through the grapevine/rumor mill.
The Fix
The "Rule of Seven": Accept that people need to hear a core message seven times in seven different ways (email, town hall, 1-on-1, etc.) before it is truly internalized.
Commander’s Intent: Borrow from military strategy, don't just give tasks; communicate the "end state." If the plan changes, the team still knows the goal and can adapt without waiting for new orders.
Feedback Loops (Two-Way Streets): Actively solicit "bottom-up" communication to verify that the message received is actually the message that was sent, preventing the "telephone game" effect.
Scaling the Human, Not Just the Business
Information scaling isn't just a technical challenge or a byproduct of growing, it’s a human endurance test. As we’ve seen, the "rules" governing how we communicate, remember, and process data are rooted in our biology and social evolution. The tech we use might scale at the speed of light, but the human brain hasn't had a significant "firmware update" in about 50,000 years.
When businesses stumble during growth, it’s rarely because they lacked the right software. It’s usually because they tried to run a 500-person company on the informal, "vibes-based" communication of a five-person startup.
The Path Forward
To navigate the chaos of scaling without losing your culture, or your mind, keep these three principles in your back pocket:
Design for the Bottleneck: Recognize that the bottleneck is almost always attention, not information. Use Cognitive Load Theory and Media Synchronicity to stop drowning your team in "data dumps" and start giving them clarity.
Build the System, Not the Superstar: Relying on one "genius" to hold all the info is a recipe for disaster. Use Transactive Memory Systems to make knowledge searchable, transparent, and redundant.
Narrative is Your Force Multiplier: As a leader, you can't be in every room. Leadership Communication Theory tells us that a clear, repeated mission acts as a compass, allowing your team to make the right decisions autonomously when you aren't there to give the orders.
Scaling is inevitable if you’re successful, but chaos is optional. By applying these Information “Scaling Rules”, you stop reacting to growth and start architecting it. The goal isn't just to get bigger, it's to get smarter, faster, and more aligned as you go.