The Hidden Coordination Crisis at Scale
Bank Central Asia had built something formidable over six decades: a position as Indonesia's largest bank, a customer base spanning millions, and a reputation for reliability that transcended economic cycles. The bank's tagline—"Senantiasa di Sisi Anda" (Always by Your Side)—reflected genuine commitment to customer relationships. But maintaining that commitment at scale requires something most organizations struggle with: flawless internal coordination.
The marketing and communications division at BCA faced a specific version of a universal problem. As the bank grew and market competition intensified, the division's workload multiplied. Promotional campaigns needed coordination. Sales strategies required alignment across teams. Customer relationship initiatives demanded collaboration. Yet the division was managing this complexity through fragmented channels: email for some communications, spreadsheets for tracking, casual conversations for decisions. Projects existed in multiple formats—some in shared drives, some in people's heads, some in email threads. When a supervisor wanted to understand project status, they had to search multiple sources. When work needed to be redistributed based on capacity, there was no visibility into actual workload. When approvals were needed, they disappeared into email queues. The division was productive despite their systems, not because of them. BCA recognized that as competition intensified and customer expectations accelerated, they couldn't afford coordination friction anymore. They needed a platform that would make coordination automatic, transparent, and efficient.
Four Fractures in Marketing Department Coordination
The BCA marketing and communications division faced multiple interconnected challenges that were suppressing efficiency and creating unnecessary friction.
1. Project Status Is Invisible Until It Becomes a Crisis
When projects live across multiple systems—emails, spreadsheets, shared drives, individual files—there's no unified view of status. A supervisor might think a campaign is on track when it's actually stalled. An approval might be pending but nobody remembers it's waiting. A critical task might be assigned to someone already overloaded with work. The division was flying partially blind, discovering problems when they became urgent rather than managing them proactively.
2. Communication About Work Is Scattered and Inefficient
Project-related decisions and discussions happened across multiple channels. Email threads for strategic discussions. Instant messages for quick questions. In-person conversations for complex decisions. Documents were versioned across multiple locations. This scattered communication meant context was constantly lost. New team members couldn't easily understand project history. Decisions made in one conversation weren't necessarily visible to everyone affected. The division spent energy coordinating about coordination rather than actually executing campaigns.
3. Workload Distribution Is Guesswork
Supervisors had no systematic view of individual workload. They assigned work based on immediate need or assumption about capacity, not actual data. The result was predictable: some team members became overloaded while others had available capacity. Complex projects suffered because key people were overwhelmed. Simpler tasks were delayed because available capacity was unknown. The division couldn't optimize allocation because they lacked visibility into actual workload.
4. Approval Processes Create Unexplained Delays
Approvals were managed informally—conversations, email chains, verbal confirmation. There was no systematic tracking of what was waiting for approval or who had decision authority. Projects stalled because approvals were pending but nobody tracked them. Supervisors couldn't see what needed their approval. The approval process, meant to ensure quality, was instead creating bottlenecks.
The cumulative effect was organizational friction that was invisible until measured. The division was capable, the people were skilled, but the systems didn't enable them to coordinate effectively. They were constantly problem-solving about coordination rather than focusing on campaign execution and customer relationship management.
Building a Coordination Platform, Not Just a Task Manager
Suitmedia approached CommHub—the project management application for BCA—with a strategic insight: project management isn't about tracking tasks; it's about enabling coordination. The best project management systems make coordination feel natural, not forced.
Most project management tools are designed around task completion and metrics. CommHub was designed around how humans actually coordinate: they need to see what's happening, understand dependencies, communicate about decisions, and adjust plans when reality diverges from projections.
Move 1: Creating Brand Identity as Coordination Signal
The first strategic move was counterintuitive: before building functionality, Suitmedia invested in brand strategy. This wasn't about aesthetics; it was about creating a shared mental model.
The team developed a brand concept: "One Communication Environment: modern, simple, bold, hi-tech, and comfortable." This wasn't marketing language—it was an operational vision. The application would serve as a single location where coordination happened, removing the need to switch between email, spreadsheets, and messaging apps.
The name "CommHub" reinforced this positioning: a hub for communication about marketing activities. But the brand strategy went deeper. The team created a brand promise: "help every employee in connecting and communicating with each other in one environment." This promise oriented every design decision. Features that supported connection and communication were prioritized. Features that created silos or required leaving the application were reconsidered.
The brand personality was carefully designed. CommHub wasn't meant to feel like an austere corporate tool. It was meant to feel modern, supportive, and human-centered. This personality would shape design choices, language, and interaction patterns. A tool that feels like it's trying to help you is adopted differently than a tool that feels like surveillance or bureaucratic overhead.
The logo design reflected this personality: bold, modern, representing connection and activity. It wasn't decorative—it was a visual signal that this was a different kind of tool, one designed around how humans actually work rather than how process flows are traditionally mapped.
Move 2: Information Architecture Built for Visibility and Action
The interface design reflected ruthless clarity. Suitmedia chose blue and white (echoing BCA's brand identity) and sans-serif typography to maximize readability. The goal wasn't beauty for its own sake—it was clarity. Tasks shouldn't be misread. Data shouldn't be ambiguous. Information should be instantly graspable.
The core innovation was task categorization and transparency. Rather than a simple list of tasks, CommHub presented categories that reflected actual decision needs: Late (overdue tasks requiring attention), Running (active tasks), Upcoming (future tasks), and Pending Approval (tasks waiting for authorization).
This categorization served multiple purposes: it made visible what needed immediate attention (late tasks), what was active and on track (running), what was planned (upcoming), and what was blocked by approval processes (pending). A supervisor opening CommHub instantly knew where action was needed rather than having to hunt through hundreds of tasks to find problems.
Workload visibility became systematic. The application displayed task counts for each category—not just as numbers but as signals. A supervisor could see that one person had 8 late tasks while another had 2. They could see pending approvals accumulating. They could see upcoming workload to plan for future capacity needs. This visibility transformed workload management from guesswork to data-informed decisions.
The interface also displayed aggregate metrics: total tasks needing attention, tasks requiring approval, team capacity status. These weren't abstract numbers—they were operational signals. An increasing number of pending approvals signaled that the approval process was creating bottlenecks. High numbers of late tasks signaled capacity problems. These signals enabled supervisors to identify and address problems early rather than discovering them when deadlines were missed.
Move 3: Approval Workflows as Communication, Not Gatekeeping
One of CommHub's most important innovations was reimagining approvals as communication rather than bureaucratic checkpoints. Approvals in traditional systems are often sources of friction—they create delays and mystery. CommHub made approval processes transparent and efficient.
When a task needed approval, it appeared in the "Pending Approval" category—visible to both the person awaiting approval and the approver. The context was immediately available: what's being approved, why, what information supports the decision. Rather than approval being a hidden bottleneck, it became a transparent process.
Approvers could see their approval queue—what was waiting for them, priority order, deadline information. This transparency meant approvals didn't languish forgotten in email queues. They were managed systematically.
The approval process included communication features. Rather than just a binary approve/reject decision, the system allowed comments, questions, and suggestions. An approver could suggest revisions. A requester could provide additional information. Approval became dialogue rather than gatekeeping. This transformed approvals from potential bottlenecks into opportunities for quality improvement and knowledge sharing.
Move 4: Communication Integration for Context Preservation
Projects aren't just tasks and deadlines. They involve decisions, trade-offs, learning, and communication. CommHub integrated communication directly into project context rather than requiring teams to switch to separate messaging or email.
Comments on tasks created permanent context. If a decision was made about campaign positioning, that decision lived with the task rather than disappearing into email archives. New team members joining a project could understand the context by reviewing task comments rather than asking people to re-explain decisions.
Notifications were designed to surface relevant information to relevant people. A team member didn't get notified about every action; they got notified about actions affecting them or requiring their attention. This prevented notification fatigue while ensuring critical information reached the right people.
The communication integration had a subtle but important effect: it made context persistent and retrievable. In email or messaging systems, context typically decays. Over time, decisions and discussions become harder to locate. In CommHub, context stayed with the project, making organizational learning possible and institutional knowledge retrievable.
Operational Impact: From Fragmented Execution to Coordinated Delivery
The impact of CommHub was visible in how the marketing and communications division worked—not just in metrics but in daily experience.
1. Coordination Friction Decreased Dramatically
The most immediate impact was that teams spent less time figuring out what to do and more time actually doing it. Rather than supervisors hunting through emails and spreadsheets to understand project status, they opened CommHub and had clarity. Rather than team members asking "what's my priority today?", they could see it. Rather than approvals disappearing, they were tracked systematically.
This friction reduction had compounding effects. Meetings became more productive because people already knew project status. Decisions happened faster because approvers weren't playing catch-up. Handoffs between team members happened more smoothly because context was preserved.
2. Workload Management Became Data-Informed
For the first time, supervisors had visibility into actual workload. They could see which team members were overloaded and which had capacity. They could see which types of projects consistently took longer than expected. They could forecast upcoming workload and plan accordingly. This transformed workload management from crisis response (constantly discovering overload) to proactive planning.
The result was more balanced allocation. Work was distributed based on actual capacity rather than assumption. High-performer bias—where the best people get overloaded because they're reliable—became visible and manageable. Team members experienced more reasonable workload, reducing burnout and improving retention.
3. Project Delays Became Predictable and Preventable
With visibility into late tasks and pending approvals, supervisors could intervene before deadlines became crises. If a project was trending late, they could reallocate resources. If approvals were stalling, they could investigate and unblock. The division moved from reactive crisis management to proactive problem prevention.
4. Knowledge Transfer and Onboarding Improved
Context embedded in project comments meant new team members could understand decisions and context without extensive coaching. Institutional knowledge didn't disappear when people changed roles or left the organization. Projects had documented context that was accessible and learnable.
5. Team Morale and Engagement Increased
Perhaps most importantly, working became more satisfying. Team members experienced clarity about what was expected. They saw their contributions tracked and recognized. Approvals happened within expected timeframes rather than mysteriously stalling. Workload felt manageable rather than overwhelming. The application supported them rather than creating additional burden.
The tagline "working has become more fun" wasn't marketing hyperbole—it reflected genuine experience. When coordination becomes seamless, when you know what you're supposed to be doing, when your effort is tracked and recognized, work feels different. It feels like you're part of a coordinated team rather than struggling through chaos.
6. Supervisor Effectiveness Multiplied
Supervisors could manage more projects and people with better visibility and less meetings. They could make faster decisions based on data. They could detect and address problems earlier. Their leverage—the ratio of their time to outcomes they influenced—increased substantially.
Three Principles That Generalize Beyond BCA
1. Project Management Is About Coordination, Not Task Tracking
Most project management tools treat projects as collections of tasks to complete and track. The best tools treat projects as coordination challenges. People need to know what's happening. They need to understand dependencies. They need to communicate about changes. They need visibility into capacity and bottlenecks. CommHub succeeded because it was designed around coordination needs first, task tracking second. The companies that win with project management tools are those that treat them as coordination platforms, not compliance systems.
2. Visibility Enables Better Decisions Than Policies
Organizations often try to solve coordination problems with policies: "Don't assign work when someone is overloaded." "Get approvals within 24 hours." "Communicate status weekly." These policies help but they're not solutions. CommHub made visibility systematic: supervisors could see actual workload and approve work accordingly. Approvals became transparent so delays were obvious. The visibility enabled better decisions than any policy could enforce.
3. Tools That Respect How Humans Actually Work Are Adopted Differently
CommHub succeeded because it reduced friction rather than adding process. It consolidated fragmented channels into one place. It made visibility automatic rather than requiring manual reporting. It supported natural communication patterns rather than enforcing rigid workflows. Tools designed around how people actually work are adopted enthusiastically. Tools designed around ideal processes are often resisted or circumvented.
Strategic Insights for the C-Suite
1. Coordination Infrastructure Becomes Critical at Scale
As organizations grow, coordination complexity increases exponentially. The mechanisms that worked for small teams (everyone knowing what everyone is doing) break down. Systems and tools become necessary. But most organizations invest in coordination systems only after problems become severe. BCA invested proactively. The result was that growth didn't create coordination chaos. For any organization scaling rapidly, investing in coordination infrastructure early pays dividends in preventing the coordination breakdown that typically accompanies growth.
2. Project Management Tools Are Fundamentally About Visibility
Many organizations think of project management tools as systems for tracking completion and enforcing accountability. The strategic insight is that they're systems for creating transparency. When supervisors can see actual workload, they make better allocation decisions. When approvals are visible, they don't fall through the cracks. When project context is preserved, learning happens. The most sophisticated use of project management tools focuses on leveraging the visibility they create rather than just tracking outputs.
3. Employee Experience Matters More Than Features
CommHub could have included dozens of features—advanced reporting, complex workflows, integration with external systems. Instead, Suitmedia focused on simplicity and clarity. The result was an application that people wanted to use rather than had to use. For any internal tool, employee experience determines adoption and effectiveness. Tools that feel like they support you are used fully and enthusiastically. Tools that feel burdensome are minimally used or circumvented.
4. Brand Strategy for Internal Tools Is Often Overlooked But Powerful
Most organizations design internal tools around functionality. CommHub was designed around brand strategy first—"One Communication Environment: modern, simple, bold, hi-tech, and comfortable." This strategic framing oriented every design decision and created shared mental models about the tool's purpose. For any internal tool, investing in clear strategic positioning and brand concept improves outcomes substantially.
5. Approval Processes Are Communication Opportunities, Not Just Gatekeeping Mechanisms
Traditional approval systems treat approvals as checkpoints: someone decides yes or no. CommHub treats approvals as communication. Approvers provide feedback and suggestions. Requesters provide additional context. Approval becomes dialogue. For any organization with approval processes, reimagining them as communication and quality improvement mechanisms rather than purely gatekeeping can transform their impact on organizational effectiveness.
