Ukd
Orko was a web application conceived as a cloud-native, online ERP system based on SaaS model. It sets out to essentially do what SalesForce did with CRM.
However, studies show that 75% of all ERP deployments end up as failure. When we conducted our user research, we found that this was primarily due to:
-
People's resistance to change
-
The overwhelmingly complicated interface of most ERPs intimidates employees.
-
Employees often do not see any value in many of the day-to-day activities they perform on ERP.
Orko has set out to change this scenario and bridge this delta of 75%.
Orko works primarily as a digital workspace for real-time resource management and aims to bring in transparency to the system. With Orko's base subscription, one can:
-
Track & Monitor Resources in real time: Teams, Smart Machines and other Assets
-
Secure Team Communication Channels: Text Chat, Video Calls & Meetings
-
Work Collaboration with Teams in real time Projects: Tasks & Tickets
Smart Forms with Analytical insights Process, Survey, Certification -
Smart Workflow Builder: Process flows with exception management
-
Efficiency Analytical Insights: Work Performance, Response Time, Initiatives
Case Study - Orko
The user study we conducted gave us good insight into what creates this delta and how Orko can look at positioning itself within this space. The main reasons for low adoption or ERP systems was attributed to:
-
People's resistance to change
-
The overwhelmingly complicated interface of most ERPs intimidates employees.
-
Employees often do not see any value in many of the day-to-day activities that they perform on the ERP system - and they feel it is a waste of their productive time.
-
SMEs often drop the idea of ERP implementation as there are substantial overhead costs - and if during the implementation journey they see resistance to the ERP system, they often drop the idea midway to cut their losses.
How do we bridge the delta of 75% between implementation of an ERP system and its usage?
Asking the right question:
The client knew the problem Orko is set out to solve; but wasn't sure where the digitization journey should start from - whether to position Orko in the ERP space, or workforce automation space or the IoT space or as something else. True Orko can fit in as a solution in multiple scenarios, but to position the product in a single space where it is solving a single problem was critical for the client to attract investors and users both.
The final output of the design thinking and market research process was the decision to position Orko as the primary data collection tool for digital transformation - which can be used across segments - such as workforce, sales, production etc. - and across sectors - such as BFSI, education, healthcare, etc.
Value proposition through user journey
Orko's brand
personality
The brand personality of Orko was of critical importance as that would contribute immensely in reducing the resistance towards accepting the tool by employees in the context of an ERP associated deployment. After various iterations, the personality emerged as:
-
Friendly
-
Helping
-
Cheerful
-
Corporate
Orko final
Prototype
