Infrastructure Financing Moves at the Speed of Decisions
PT Sarana Multi Infrastruktur operates in one of the world's most complex markets: infrastructure financing in Indonesia. The company sits at the intersection of public need and private capital, structuring deals that move billions of rupiah into projects that build the country's future. Speed matters enormously. A financing decision delayed by weeks can mean a project stalls, a contractor loses momentum, or an opportunity moves to a competitor. Yet PTI SMI had inherited a problem that plague most large organizations: approval processes that were built for control but had become shackles on velocity.
Approvals at PT SMI required navigating multiple systems. A manager needed to log into one application to review a loan decision, another to approve travel authorization, another to clear procurement requests. Each system had its own interface, its own login, its own notification mechanism. Information wasn't synchronized. Approvals that completed in one system didn't automatically notify downstream stakeholders in another. The result was predictable: approvals moved slowly, managers struggled to track what was pending, and critical business decisions waited in queues while executives hunted for the right applications on their phones. The company's strategic objective—accelerating infrastructure financing—was being undermined by infrastructure that fragmented rather than unified decision-making.
The Hidden Tax of Fragmented Approval Architecture
Most organizations underestimate the cost of scattered systems. It appears as friction, not as an explicit business problem. PT SMI faced three interconnected fractures that together created a significant competitive drag.
1. Decision-Makers Trapped in System Navigation
Executives and managers spent disproportionate time locating decisions rather than making them. A CFO might need to approve five different types of requests in a given day—a loan decision, a travel authorization, a procurement order, an HR action, a vendor payment. Each lived in a different system. Each required a separate login. Each had a different interface and navigation logic. The cognitive load wasn't in the decision itself; it was in finding where the decision was waiting. Studies consistently show that context-switching and system navigation consume 15-20% of knowledge workers' productive time. For a company processing hundreds of approvals daily, this represented significant organizational drag.
2. Approvals Disappear Into Notification Chaos
Notification systems across PT SMI's applications weren't synchronized. A manager might receive an email about a pending approval, but not see it in the application itself. Notifications might arrive hours after the request was submitted. Critical approvals could be forgotten because they disappeared among dozens of notifications in different channels. There was no unified view of what required attention. Executives couldn't prioritize effectively because they lacked visibility into their full approval queue. Some decisions got fast-tracked because they were front-of-mind; others languished because the notification never surfaced.
3. Institutional Knowledge About Approval Status Is Invisible
When approvals were scattered across systems, the organization had no unified visibility into bottlenecks. Which types of decisions moved fastest? Where did approvals stall? Which managers approved quickly versus slowly? This data didn't exist because there was no single system capturing it. PT SMI couldn't optimize their approval processes because they couldn't see their approval patterns. They were flying blind on one of their core operational processes.
The cumulative effect was straightforward: approvals moved slowly. Business decisions took longer than they should. The company's strategic mission—accelerating infrastructure financing—was undermined by operational friction that was both invisible and pervasive.
Building Approval Infrastructure as Competitive Advantage
Suitmedia approached the Mobile Approval application with a precise strategic framing: approval processes don't exist to slow decisions; they exist to ensure good decisions. If they're doing anything else, they're broken.
The team recognized that the problem wasn't the approval concept. PT SMI needed oversight and control—infrastructure financing involves significant capital and regulatory compliance. The problem was that approval mechanisms had become obstacles rather than enablers. They required so much navigation that they actually discouraged timely decision-making.
Move 1: Unifying Fragmented Systems Into Single Decision Interface
The first strategic move was architectural: consolidate all approval pathways from across PT SMI's ecosystem into a single mobile application. But this wasn't about merging databases or creating a new system that replaced existing applications. It was about creating a unified decision interface that could surface approvals from multiple source systems.
The Mobile Approval application became a dashboard for decisions. Regardless of which backend system generated an approval request—whether it originated in the Loan Origination System, the HR system, the procurement platform, or the travel management system—it appeared in the same interface with the same logic.
Suitmedia engineered integrations with five critical PT SMI applications: Perjalanan Dinas (travel management), Nota Disposisi (internal memo system), HRIS (human resources), LOS (Loan Origination System), and E-Procurement. Each integration pulled pending approvals into the unified mobile application in real time.
The architectural decision had profound implications. A manager no longer needed to remember which system housed which decision. They opened one application. They saw all pending approvals. They acted. This simplification removed the primary source of friction—the cognitive and logistical burden of system navigation.
But simplification alone wouldn't drive adoption. Suitmedia added a behavioral layer: the application presented approvals with context. Rather than a bare notification ("Approval required for TRX-2847"), the system displayed the full decision scenario ("Travel authorization for Jakarta-Surabaya trip, approved budget: 5.2M, requested by: Budi Santoso, Department: Infrastructure Advisory"). Managers could make informed decisions without leaving the interface.
Move 2: Reimagining Notification as Decision Support
Traditional notification systems are reactive: they tell you something happened and hope you remember to act on it. Suitmedia reimagined notifications as proactive decision support.
The Mobile Approval system intelligently surfaced pending decisions based on priority, deadline, and impact. A critical loan approval with a deadline approaching received more prominent display than a routine expense report due next month. Managers' attention was directed toward decisions that actually needed it, rather than drowning in undifferentiated notifications.
The notification architecture also handled time sensitivity intelligently. Urgent approvals triggered push notifications; routine items appeared in the queue but didn't interrupt. The system learned from user behavior: if a manager typically approves travel requests in the morning and loan decisions in the afternoon, the notification timing could adapt to those patterns. This wasn't surveillance; it was respecting how people actually work.
For decisions that couldn't be approved immediately, the system included a "bookmark" feature that allowed managers to flag approvals for later action. A manager reviewing decisions on a commute could bookmark complex approvals to revisit at the desk with full documentation available. Routine decisions could be handled immediately. The system accommodated both patterns.
The notification redesign had a critical psychological effect. Instead of feeling overwhelmed by notification chaos, managers felt supported. The system was doing cognitive work—prioritizing decisions, tracking deadlines, surfacing what mattered. This feeling of support rather than overwhelm is critical for adoption of any system that asks people to change behavior.
Move 3: Creating Audit Trail and Organizational Learning
The Mobile Approval system created something PT SMI had never had before: unified visibility into approval patterns across the entire organization.
When an approval was granted, the system automatically archived it with metadata—who approved it, when, from which source system, what decision was made. For the first time, PT SMI could analyze approval velocity: Which types of decisions moved fastest? Where did bottlenecks occur? Which managers approved quickly versus slowly? Were there decisions that typically stalled? Were certain departments or request types experiencing systematic delays?
This data transformed approval processes from compliance overhead into strategic intelligence. If the data revealed that loan approvals were taking 40% longer than acceptable, leadership could investigate: Were there insufficient approvers? Did approvers lack information to decide quickly? Was there uncertainty about decision criteria? Once the bottleneck was visible, it could be addressed.
The archive also served a training function. New managers could see how their predecessors had handled similar decisions. If there was ambiguity about decision criteria, the archive provided empirical examples. Over time, the organization became more consistent in how it made decisions because patterns were visible and learnable.
The System Architecture Reflected Operational Reality. Different approval types required different workflows. A travel authorization was fundamentally different from a loan decision. But both needed to be managed, tracked, and archived. The Mobile Approval system was intentionally flexible—it could accommodate different approval workflows while maintaining a consistent interface for the decision-maker. A manager reviewing the application never needed to think about the underlying workflow complexity; they just saw: here's what needs a decision, here's the information I need, here's how to approve.
Operational Impact: From Bottleneck to Accelerator
Measuring the impact of an approval system is challenging because the benefits appear as velocity—decisions moving faster—rather than as easily quantifiable outputs.
1. Approval Cycle Time Compressed
Before the Mobile Approval application, a typical approval might take 2-3 days to complete. A request would be submitted, a notification would go out (maybe reaching the approver immediately, maybe delayed), the approver would need to navigate to the right system, review the decision, and approve. With Mobile Approval, the same decision could be made within hours. The request appeared in a unified interface. The decision context was immediately visible. Approval was a single action. The velocity improvement was substantial—what took days now took hours.
2. Decision Accuracy Improved
When managers were rushing between systems, trying to locate approvals and struggling with fragmented information, decision quality suffered. Approvers might miss critical context or make decisions without full information. The Mobile Approval system presented complete decision context—relevant documents, budget information, historical decisions, supporting details. Managers could make faster and better decisions simultaneously. More informed approvals meant fewer incorrect decisions that needed reversal.
3. Approval Backlog Visibility Became Possible
For the first time, PT SMI's leadership could see where approvals were stalling. They discovered that certain types of requests consistently had longer cycle times. They identified approvers who were bottlenecks (either because they were overloaded or because they were indecisive). They found requests that were falling through the cracks. This visibility enabled targeted intervention—reassigning workload, clarifying decision criteria, escalating complex decisions.
4. Manager Productivity Increased
The time managers had previously spent hunting for approvals across multiple systems became available for actual decision-making and strategic work. A manager who previously spent 45 minutes a day navigating between applications now spent 15 minutes in Mobile Approval and reclaimed 30 minutes for higher-value activities. Across dozens of managers making hundreds of decisions monthly, this represented substantial productivity gain.
5. Compliance and Audit Trail Became Automatic
Infrastructure financing is regulated. Decisions need to be documented, traceable, and auditable. The old system required manual record-keeping. The Mobile Approval application automatically created an audit trail—who approved what, when, and from which device. Compliance reporting shifted from manual assembly to automated extraction. Risk management became easier because the organization had systematic visibility into decisions and approvers.
6. Employee Experience Improved Measurably
Perhaps most importantly, managers felt more in control. Rather than being surprised by notifications or struggling to remember which approvals were pending, they had a dashboard view of their decision workload. This sense of control and organization reduced cognitive stress. Employees reported feeling more efficient and less frustrated by system navigation.
Three Principles That Generalize Beyond PT SMI
1. Bottlenecks Are Often Architectural, Not Behavioral
Most organizations approach slow approval processes as a people problem: "Managers are taking too long to decide." In reality, the bottleneck is often architectural: the system requires too much navigation, information isn't accessible, approvers don't have clarity on decision criteria. Suitmedia's solution addressed the architectural problem, not a behavioral one. The result was faster decisions without needing to change who approves or how they approve.
This principle extends broadly. When organizational processes are slow or inefficient, the instinct is often to add oversight or change people. The first diagnostic question should be: Is this a system problem? Can we eliminate friction through better architecture? Usually, we can—and the result is faster, more efficient processes without requiring behavioral change.
2. Unified Interface Reduces Cognitive Load More Than Optimization
PT SMI could have optimized each individual approval system. Made each one faster. But the real problem wasn't individual system performance; it was context-switching. A manager dealing with five systems, five interfaces, five login processes faces cognitive load that no optimization within individual systems can address. Unification—consolidating into a single interface—addresses the root problem: cognitive overhead.
This explains why unified platforms often outperform highly optimized specialized tools. The specialized tools might be technically superior, but the unified interface wins because it reduces friction at a higher level—the level of decision-making and workflow, not just feature performance.
3. Systems Should Support How People Work, Not How Processes Are Designed
PT SMI's approval processes were designed for control and documentation. That's legitimate. But the implementation—scattered across multiple systems, requiring multiple logins—didn't support how managers actually work. Managers need to see all their pending decisions quickly. They need context immediately available. They need to act efficiently. The Mobile Approval system respected both requirements: maintain the governance and documentation processes that the organization needs, but deliver them in a way that supports manager workflow.
Strategic Insights for the C-Suite
1. Approval Velocity Is Often Underestimated as a Competitive Factor
In knowledge-intensive businesses—particularly those involved in financing, consulting, and project management—decision speed directly correlates with competitive performance. The company that can approve loans faster wins market share. The organization that can authorize projects faster executes them faster. Yet most companies accept slow approval processes as inevitable. PT SMI's investment in unified approval infrastructure wasn't a nice-to-have; it was a competitive lever. The companies that win in industries where speed matters are often those that have eliminated friction from critical decision processes.
2. Unified Interfaces Solve Problems That Optimization Cannot
Organizations often invest in making individual systems better—faster, more intuitive, more feature-rich. This helps, but it doesn't address the core problem of fragmentation. A manager dealing with five great systems still faces five context-switches. A single good interface beats five great fragmented interfaces because it reduces cognitive load at a higher level. When considering enterprise system architecture, evaluate the total user experience, not just individual system performance.
3. Approval Patterns Contain Strategic Intelligence
When approval processes are opaque, the organization lacks visibility into how decisions are actually made. When they're transparent and data-captured, patterns emerge. Bottlenecks become visible. Opportunities to accelerate emerge. Decision criteria become clear. PT SMI gained the ability to continuously improve their approval processes because they could suddenly see them. Most organizations don't have this visibility because their approval processes are scattered and undocumented.
4. Operational Friction Is Invisible Until Removed
Before Mobile Approval, managers accepted slow approvals as normal. They didn't consciously think "this is frustrating"—friction had become invisible. Once the friction was removed, they realized how much productivity and attention had been consumed by system navigation. The companies that gain competitive advantage often do so by removing friction that competitors have accepted as inevitable. This requires someone to question what's normal and imagine what's possible.
5. Governance and Agility Are Not Opposites
Many leaders believe faster approval requires less oversight. PT SMI proved the opposite. The Mobile Approval system maintained all governance requirements—approvals still required authorization, decisions were still tracked and audited, compliance requirements were still met. But it delivered governance in a way that enabled speed rather than enforcing slowness. The best organizations find ways to maintain control while enabling velocity. That's a design problem, not a policy problem.
