The Hidden Cost of Growth Without Connection
PT Zurich Insurance Indonesia had built something remarkable: a thriving insurance operation that had expanded steadily since 1991, establishing itself as a credible player in one of Asia's most competitive markets. But growth creates a paradox. The same energy that drives expansion—hiring rapidly, opening new divisions, pursuing new market segments—can fragment an organization from the inside.
Zurich Indonesia faced a problem that doesn't show up in quarterly reports but corrodes everything: communication was breaking down. As the company scaled, information flowed unevenly. Management announcements didn't reach frontline staff consistently. Employees had questions but no clear channel to ask them. HR policies existed but weren't widely known. Teams in different offices felt disconnected from each other and from company direction. The organization had grown faster than its communication infrastructure could support. Leaders knew this created risk—misaligned teams, duplicated effort, employees who felt isolated despite working for a large corporation. They needed a system that could scale with the company and make every employee feel connected to the mission.
Three Communication Fractures in a Scaling Organization
Most companies experience communication breakdown as they grow. Few address it systematically. Zurich Indonesia faced three interconnected fractures that were becoming increasingly expensive.
1. Information Scattered Across Disconnected Channels
Company updates lived in email inboxes, some in shared drives, some on printed notices in break rooms. An employee trying to understand current company policy or recent announcements would need to search multiple sources—many of which might be outdated. HR policies, operational updates, strategic announcements, and procedural changes existed somewhere, but not in one place. New employees struggled to find baseline information. Existing employees couldn't distinguish between official policy and rumor. Critical updates sometimes never reached certain departments. When information isn't centralized, organizations leak knowledge constantly.
2. The Management-Staff Information Gap
Zurich Indonesia's leadership wanted transparency. But the mechanisms for two-way dialogue didn't exist. Employees had questions—about strategy, about policy changes, about their role in the company's direction—but no structured way to ask them. Management held town halls and sent memos, but these were one-way broadcasts. Employees couldn't respond, clarify, or push back. Over time, this created an invisible barrier: employees stopped asking questions because they didn't see a pathway for their voice to be heard. Management assumed they were communicating effectively because they were sending messages, not realizing the messages weren't landing as dialogue.
3. Knowledge Trapped in Silos
In a growing insurance company, institutional knowledge is competitive advantage. How does the claims team handle complex cases? What's the best practice for customer retention? How did another department solve a similar problem? But this knowledge lived in individual computers, team conversations, and tribal memory. When people left, it left with them. When teams expanded, new hires couldn't access what their colleagues had learned. The company was repeatedly solving the same problems because it had no infrastructure to share solutions.
The cumulative cost was substantial: duplicated work, slower decision-making, lower employee engagement, institutional knowledge leaking out the door with departing staff, and a pervasive sense among employees that they were working in isolation despite being part of a large organization.
Building an Intranet That Functions as Organizational Nervous System
Suitmedia approached ZINC (Zurich Innovation Center) not as a website but as infrastructure—the connective tissue that would allow information to flow freely and employees to feel like they were part of something larger than their immediate team.
The team began with a fundamental insight: an intranet fails when it's designed for IT. It succeeds when it's designed for how people actually work.
Move 1: Centralizing Information Without Creating Bureaucracy
The first strategic move was architectural: consolidate all employee-facing information into a single, discoverable location. But centralization can become a dead end if the system requires employees to navigate dense hierarchies or outdated navigation structures.
Suitmedia created a news feed as the primary interface. This wasn't a traditional document repository. It was a live stream of company information, designed to meet employees where their attention actually is—in real-time updates they see when they log in. Strategic announcements, policy changes, operational updates, team achievements, and company news all appeared in a prioritized feed.
The news feed served a psychological function beyond information delivery. It created presence. Employees checking ZINC daily saw evidence that the company was moving forward, making decisions, celebrating wins. They felt less like distant observers and more like participants in something active. The feed also solved a critical compliance problem: management could ensure that critical information reached everyone simultaneously. There was no debate about whether people "knew" about a policy change—it was published on ZINC on a specific date.
But centralization required intelligent organization. Users didn't need to navigate complex folders to find what mattered. Suitmedia implemented category filters—employees could view updates relevant to their department, their role, or their interests. A frontline claims adjuster could see company-wide announcements, HR updates, and claims-specific procedures without wading through technical infrastructure information. The same system worked for executives, administrative staff, and field agents.
The design principle was ruthless clarity. Minimalist layout. Generous white space. Obvious navigation. Every visual element served a function—nothing decorative, nothing confusing. This wasn't about being austere; it was about respecting employees' time. People access intranets between urgent tasks. They need to find what they're looking for and move on.
Move 2: Opening Two-Way Channels Between Leadership and Staff
This was the strategic pivot that transformed ZINC from information repository to communication platform. Suitmedia created "Ask Soekrisno" (the CEO) and "Ask HR" as direct dialogue mechanisms.
The insight was deceptively simple: employees have questions. Leadership wants to be transparent. But without a structured channel, both sides pretend to communicate while actual dialogue doesn't happen. The "Ask" features created explicit permission for dialogue.
An employee could submit a question about company strategy, policy interpretation, or organizational direction. The question went to the relevant leader. Unlike email—where questions disappear into inboxes—these questions were managed systematically. Leadership committed to responding within a defined timeframe. Responses were published (or at least summaries were) so other employees could see the dialogue.
This created multiple second-order effects:
First, it surfaced what employees actually wanted to know. Management often assumes they're communicating what matters. In reality, employees care about different things. The "Ask" features revealed these gaps. A CEO might think employees want to hear about market strategy; the questions revealed employees actually cared about career development opportunities and remote work policies. Leadership could now see reality through the questions being asked.
Second, it built trust through transparency. When employees see their CEO or HR director answering questions honestly—even when the answer is "we don't know yet" or "here's why we made that decision"—it changes the relationship. Trust isn't built through perfection; it's built through honest dialogue. The "Ask" features created evidence that management was listening and responding.
Third, it reduced rumor and speculation. When employees can't ask questions, they fill the information void with guesses. Rumors spread. Anxiety increases. When they can ask directly and get direct answers, the organization becomes more stable. Certainty, even when the news is difficult, is preferable to uncertainty.
The CEO and HR responses also became training artifacts. New employees could see the questions their peers had asked and how leadership had responded. Policy clarifications published through "Ask HR" became de facto policy documentation—more useful than formal manuals because they addressed real scenarios employees encountered.
Move 3: Creating Infrastructure for Institutional Knowledge Sharing
Beyond news and dialogue, ZINC needed to function as a knowledge repository—a place where employees could find best practices, case studies, procedural guidance, and institutional memory.
Suitmedia built a document management system integrated directly into the intranet. But unlike traditional document repositories that become digital filing cabinets where files go to be forgotten, this system was built for discovery and retrieval. Employees could search for documents, filter by department or topic, and see the most relevant, recently updated materials first.
The system had built-in version control and update dates—employees could trust they were accessing current information, not outdated guidance. For a regulated industry like insurance, this was critical. Compliance depends on everyone following current procedures. When procedures are scattered across old emails and outdated Word documents, compliance becomes guesswork.
But more importantly, the document system created incentives for knowledge sharing. Managers could publish team methodologies, case studies, and problem-solving approaches. When an employee solved a complex claims situation, they could document it for others to learn from. Over time, this transformed ZINC from a distribution channel for top-down information into a repository of organizational intelligence.
The System Architecture Reflected Organizational Reality. Different departments needed different information. A claims manager needed different content than a sales representative. But both needed access to company-wide announcements, HR policies, and strategic direction. ZINC's architecture allowed departmental customization while maintaining company-wide coherence. Managers could populate department-specific feeds; the platform ensured critical company information appeared everywhere.
Operational Impact: From Broadcast Channel to Organizational Backbone
Measuring the impact of internal communication infrastructure is challenging because the benefits are often invisible—they appear as things that don't go wrong rather than as dramatic successes.
1. Information Search Time Collapsed
Before ZINC, finding a policy or procedure could take hours. Employees would email HR, check shared drives, ask colleagues, search email archives. After ZINC, the same information was discoverable in minutes through centralized search. For a company with hundreds of employees making similar queries repeatedly, this efficiency gain was substantial. Multiply "30 minutes saved per employee per week on information search" across the entire organization—the time savings alone justified the investment.
2. Management-Staff Relationship Shifted From Broadcast to Dialogue
The "Ask" features changed how employees experienced leadership. Rather than management as remote decision-makers, leadership became accessible. Questions revealed what employees actually cared about. Leadership responses revealed that management was listening. This wasn't about being friends; it was about transforming the psychological relationship from hierarchical distance to mutual respect. Employees who feel heard are more engaged, more loyal, and more likely to go beyond minimum job requirements.
3, Onboarding Velocity Increased
New employees could access all baseline information immediately: company history, organizational structure, policies, procedures, benefits, culture documentation. Instead of spending their first weeks in orientation sessions or asking colleagues repeatedly, they could self-serve. This meant they became productive faster and freed HR to focus on relationship-building rather than information delivery.
4. Consistency of Information Improved
Before ZINC, different employees might receive different information depending on who they asked or which email thread they found. After ZINC, there was a single source of truth. Policy interpretations were consistent. Strategic direction was clear. Compliance became easier because everyone was working from the same baseline.
5. Organizational Memory Became Retrievable
When employees left, knowledge used to leave with them. With ZINC's document system, team methodologies, case studies, and problem-solving approaches were captured and accessible to new team members. This meant the organization learned from experience rather than repeating the same lessons repeatedly.
6. Engagement Metrics Improved
Perhaps most importantly, employee sentiment shifted. In a survey conducted months after launch, employees reported feeling more connected to the company, more aware of company direction, and more confident that they could access information when they needed it. For a growing organization, this sense of connection is critical—it makes employees feel like they're part of something larger than their immediate team.
Three Principles That Generalize Beyond Zurich
1. Centralization Enables Scale
Growing organizations face a choice: let communication fragment (which creates autonomy but loses coherence) or centralize information (which requires discipline but creates alignment). The companies that scale successfully do both—they centralize critical information while allowing departmental autonomy in other areas. ZINC demonstrated that this balance is possible. Company-wide announcements were centralized; departmental procedures could be localized. The result was organizational coherence without bureaucratic rigidity.
This principle extends beyond internal communication. Any system that needs to function across a growing organization faces the same tension: local autonomy versus global coherence. The companies that navigate this successfully treat it as an architectural problem, not a political one.
2. Access to Leadership Requires Infrastructure, Not Just Willingness
Most leaders believe they're accessible. But accessibility without infrastructure becomes a bottleneck. A CEO who says "my door is always open" might receive 10 questions a week through informal channels—and those questions probably come from senior staff comfortable approaching the executive suite. "Ask Soekrisno" on an intranet reaches hundreds of employees who would never approach the CEO informally. Infrastructure democratizes access. It removes the social friction that prevents many employees from asking questions.
3. Systems That Require Discipline Fail; Systems That Reward Participation Thrive
If ZINC had required managers to post updates, employees to search for information, and staff to use it instead of email, it would have become a compliance burden. Instead, Suitmedia designed it so that using ZINC was easier than the alternatives. News feed was more convenient than email chains. Searching ZINC was faster than asking colleagues. Asking leadership questions directly was more satisfying than speculating. The system succeeded because it aligned with how people wanted to work, not because it imposed a better way.
Strategic Insights for the C-Suite
1. Communication Infrastructure Is as Critical as IT Infrastructure
Most companies invest heavily in servers, networks, and security systems. Few invest proportionally in communication platforms. Yet poor internal communication costs more than server downtime—it manifests as duplicated work, misaligned teams, lost institutional knowledge, and disengaged employees. Zurich's investment in ZINC wasn't a nice-to-have; it was essential infrastructure for a scaling organization. The companies that grow most successfully treat internal communication with the same rigor they treat financial systems.
2. Transparency Paradoxically Increases Trust and Stability
Leaders often fear transparency—worry that opening dialogue will surface complaints, expose disagreements, or create instability. The opposite is true. Employees who can't communicate develop anxiety and rumors. Employees who can communicate directly, who see leadership responding honestly, develop confidence. The "Ask" features worked because they promised dialogue, not perfection. A CEO answering "we don't know yet, here's what we're considering" is more trustworthy than a CEO who never acknowledges difficult questions.
3. Scaling Requires Systems, Not Just Hiring
Growing companies often think scale is about hiring more people. In reality, growth without system infrastructure creates chaos. Communication breaks down. Knowledge gets lost. Decisions slow. Zurich Indonesia could have hired more HR staff to answer repeated questions, but the real solution was a system that made answers accessible. The companies that scale most efficiently are those that replace people with systems—not to reduce headcount, but to free people from repetitive work to focus on judgment and relationship.
4. Employee Engagement Flows From Connection, Not Just Compensation
Zurich's employees didn't become more engaged because compensation changed. They became more engaged because they felt connected—to company direction, to each other, to leadership. This connection came from infrastructure that made information accessible and dialogue possible. For most companies, employee engagement initiatives focus on perks and benefits. The highest-leverage intervention is often simpler: give people access to information and make sure their voice can be heard.
5. The Best Intranet Is Invisible
The most common mistake in building intranets is designing them to showcase technology or enforce processes. Suitmedia's approach was the opposite: design the system so employees forget they're using a system. They think they're searching for information (not navigating a taxonomy). They think they're asking their CEO a question (not submitting a form). They think they're sharing a best practice (not uploading a document). When the interface disappears and employees just experience the functionality, that's when the system succeeds. This principle applies broadly—the best organizational systems are those that feel natural to use, not those that require training and compliance.
