Includes Internal builds, SharePoint, and new platform tools for other ecosystems (e.g. Google, Salesforce, etc.)
||Modern Intranet (like Simpplr)
||Why it matters
|IT built (or configured)
Configurable platform, platform approach built by IT
||Purpose Built (Out-of-the-box)
Purpose-built workflows to drive engagement and prevent failure
||This forces a Build vs Buy type decision
It’s not evident on the onset and many vendors will tell you otherwise. But fundamentally customization forces this tradeoff.
Text-heavy, complex, and folder schemas frustrate employees and slow business agility.
Easy to use, and easy to administer. Built-in collaborative approach to employee communications.
||This is a top reason for intranet failure
Products need to be intuitive upon initial use - users have a low tolerance for complexity. Once a system is to be bad, we don’t go back!
|Deployed in years
According to Nielsen Norman, the average intranet takes an average 1.2 years to deploy!
Not only does this consume resources, the risk of failure increases with every passing day.
Immediate deployment, content creation in minutes.
||High risk for failure
Maintaining momentum is difficult. Leaders change, priorities change, and momentum can be lost. 1.2 years is not acceptable. More time = More risk of failure.
Lacks mobile-friendly delivery approaches that target employee work habits.
Flexible delivery approaches to drive consumption (e.g. mobile, notifications, Slack, Teams, push notifications, native newsletters, etc.)
||You have to meet employees where they are
Traditional portals are no good if you don’t have hooks to drive engagement.
Employees are forced to navigate all content. Targeting relies on traditional metadata, manual hardcoding, and filters.
Personalization goes beyond filters & metadata.. Personalization framework creates 1,000 targeted experiences for 1,000 employees.
||Employees hate noise and clutter
Irrelevant information hurts the experience, sucks employee time, and hurts future adoption.
|Content Dumping Grounds
Classic CMS approaches lack controls to prevent your intranet from becoming a junk drawer.
Simpplr created the industry’s first Auto-Governance Engine which uses technology to automatically keep intranet content fresh and eliminates duplication.
||Once users find outdated info - trust is gone
Lack of stringent content governance and processes lead to content dumping grounds, a top reason for intranet failure.
Every customization needs to be redone. This requires training/heavy resources when upgrading, patching, and maintaining.
||True SaaS Approach
Limiting customization ensures you can incorporate latest innovations, UI, and security enhancements.
||Inhibits continuous innovation
Highly customized approaches suck up resources and make it difficult to keep current with newest features. Eventually it becomes obsolete.
The combination of platform tool scope-creep, customizations, and lack of internal designers typically create a complex, hard to use configuration.
The system is as easy to use as a blog. No training is required and it's built for business users to administer.
||This makes communications hard
Oftentimes, technical complexity creates a dependency on technical resources. This ultimately creates tradeoffs and backlogs so businesses can’t update news/knowledge at the speed of business.
|Implicit Maintenance Costs
This model implies operating expense aligned with the platform. Additional resources are needed for the initial deployment and for ongoing maintenance.
||Transparent Subscription Pricing
Transparent pricing without hidden SOWs or operating costs.
||Total Cost of Ownership is usually hidden
Typically headcount and services engagements add up to cost more than software subscriptions.