In an office in Bandung, an operations director had just signed a contract for an ERP system worth Rp 400 million. Six months later, the system was running — technically. The servers were on, the application opened, the initial data was loaded. But only 30 percent of the modules were actually used, and only by two people in the finance department. Warehouse staff still recorded stock in notebooks. The sales team still used personal spreadsheets. Every month, the company paid licenses for a system most employees considered "management's property," not theirs.
That director made a very common mistake: he measured digital readiness from the technology side, when digital readiness is actually determined by a far more human side — processes, skills, culture, and data.
This story could have been prevented. All the signs were visible before the contract was signed: operational processes that had never been standardized, employees who had never been trained on any system, and a work culture that relied on memory and individual initiative. What was missing was one thing: an honest assessment of how ready the company actually was for digitalization. That is what a digital readiness assessment is.
What Is a Digital Readiness Assessment
A digital readiness assessment is the process of evaluating how prepared an organization is for digital transformation: how solid its process foundations are, how capable its people are, how well-organized its data is, and how supportive its culture is.
The key point: this assessment is not about technology. Technology is actually the easiest part of digital transformation — it can be bought. What is difficult, and what most often fails, is the human part. A company can buy the best system in the world and still fail at digitalization if its processes are chaotic, its team's skills are lacking, or its culture resists change.
A digital readiness assessment answers one fundamental question before you spend your first rupiah: is this company more likely to succeed or fail if we start digitalizing now, and what needs to be fixed first to raise the odds of success?
It is like building a two-story house: you do not immediately order materials and call the builders. You first check the soil, the condition of the existing foundation, and whether the budget is ready. Building on unexamined ground is not just risky; it almost guarantees a cracked house.
Why This Assessment Matters for Indonesian Businesses
Digital transformation numbers in Indonesia sound encouraging on the surface, but hold a more complicated story underneath. Internet adoption keeps rising — DataReportal records more than 220 million internet users in Indonesia, and social media penetration is among the highest in the region. The government is also pushing SME digitalization through various programs. But individual technology adoption does not automatically mean organizational readiness.
The reality we often see: companies buy good systems, and then the systems sit idle. Global research released by McKinsey shows that around 70 percent of digital transformation programs fail to reach their targets — and the main cause is almost never technology, but human and organizational factors: processes that do not change, skills that are missing, and cultural resistance.
In Indonesia, the failure pattern is similar, with one local twist: digitalization decisions are often made at the owner or director level without involving the people who will use the system daily, so systems are bought "for the company" but never become "owned" by the people who use them.
That is why an assessment at the start is so valuable. It is cheap compared to the cost of failed systems, fast compared to the time wasted, and honest compared to the optimistic assumptions that usually decorate meeting rooms.
The Assessment Framework: Five Dimensions of Digital Readiness
To evaluate digital readiness comprehensively, look at these five dimensions. They are interconnected; weakness in one dimension drags the others down.
1. Processes and Operations
How standardized are your business processes? Are workflows documented, or do they live in each person's head? Does every process have a clear owner?
This is the most underestimated dimension. Many companies want to digitalize while their processes are still "drivers know their own routes." Digitalization is essentially converting manual processes into processes run by a system, and a system cannot run a process that is not clear. Digitalizing a chaotic process only produces faster chaos.
2. Data and Information
How well-organized is your data? Are sales, stock, and financial figures stored in one trustworthy place, or scattered across spreadsheets, notebooks, and people's heads?
Data is the fuel of all digital systems. New systems cannot work well if the data loaded into them is dirty, duplicated, and inconsistent. A data assessment looks at: what data you have, where it lives, how accurate it is, and who is responsible for keeping it that way.
3. People and Skills
How capable is your team at using technology? Is there someone who can act as a "bridge" between business needs and technical language?
This dimension is not only about technical skills but also learning capacity. Teams that have worked a certain way for years need time and support to change. Employees who fear technology are a real barrier, and a one-day training session is not enough to overcome it.
4. Culture and Leadership
How ready is the organization to accept change? Does leadership support transformation consistently, or merely buy a system and hope everything works out?
Culture is the subtlest and most decisive dimension. Successful digital transformations almost always have a driver at the leadership level who is directly involved, not just signing budgets. On the other hand, a culture that punishes mistakes will make people reluctant to try new things — and digital transformation is full of experimentation.
5. Existing Technology
Last, and only now, technology: what systems already exist, how old are they, how extendable are they, and how well do they fit future needs?
This dimension is deliberately placed last, because the most common mistake is starting here. Existing technology matters, but it only has meaning in the context of the other four dimensions.
Readiness Levels: Understanding Maturity
After assessing the five dimensions, organizations usually sit at one of four levels. There is nothing shameful about any level; what matters is honestly acknowledging your position, because the right strategy differs at each level.
Level 1: Novice
Processes run informally, data is scattered across paper and heads, and the technology in use is whatever is at hand. At this level, digitalization starts with the fundamentals: standardizing simple processes, tidying records, and building recording habits. We explore this starting point in more detail in our SME digital transformation guide.
Level 2: Assisted
Processes are partly documented, data is starting to accumulate in spreadsheets or simple applications, and technology is used for individual tasks. At this level, the focus is integration: connecting data that is still separated and reducing the work of retyping between systems.
Level 3: Integrated
Processes are documented, data flows between systems, and technology is a normal part of daily work. At this level, organizations can start considering larger systems such as ERP and automating repetitive processes.
Level 4: Adaptive
The organization not only uses technology but continuously evaluates and improves it. Data drives decision-making, and technology change is welcomed as routine. At this level, the question is no longer "are we ready" but "what innovation comes next."
An important pattern to understand: you cannot skip levels by buying systems. Moving from Level 1 to Level 2 is mainly about habits and processes, not technology. Level 2 to Level 3 is about integration. Level 3 to Level 4 is about culture. Buying an ERP at Level 1 is like installing a jet engine on a becak — technically possible, but it will never fly.
How to Run an Assessment: Practical, Not Theoretical
A digital readiness assessment does not have to be a major project with expensive consultants. For most businesses, a structured and honest process is enough. Here are the steps:
1. Gather Perspectives, Not Just from Management
The most common mistake: assessments that only involve management, when the people who know the ground truth are the operational staff. Interview or survey the people who actually run the processes: cashiers, warehouse admins, salespeople, finance staff. Their answers about "how the work is actually done" are often very different from management's picture.
2. Score the Five Dimensions on a Simple Scale
For each dimension, score 1 to 4 according to the maturity levels above. Do not chase false precision; what matters is direction and consistency. If you are torn between two levels, take the lower one — a pessimistic score is safer than an optimistic one.
3. Find the Gaps
Compare your scores with your target. If you want to reach Level 3 in two years, where is the biggest gap? Often the answer is surprising: not technology, but process and culture.
4. Prioritize by Impact and Sequence
Do not fix everything at once. Pick one or two dimensions that block the most, and start there. A sequence that usually makes sense: get processes and data in order first, then talk about big systems.
5. Repeat Periodically
Readiness is not a static condition. After six months or a year, run the assessment again to measure progress. This periodic rhythm also creates accountability: what gets measured tends to get improved.
Reading the Results: What They Mean for Your Strategy
Assessment results should change your decisions — if they do not, they are just another document wasting time. Here is how to read the results:
If scores are low in process and data but high in technology: You are in danger of buying an unused system, like the story that opened this article. Hold off on buying big systems. Focus the next six to twelve months on fixing processes and data.
If scores are low in skills and culture: Do not start with a big project. Start with a small successful project, build early wins, and let confidence grow. One POS system that the retail team proudly uses is worth more than an ERP used by two people.
If scores are high everywhere except technology: This is the rarest and most pleasant case. The organization is ready; only the systems need to catch up. This is where large technology investment makes sense, and the organization can pursue bigger systems — we discuss when it is time to move to ERP in our ERP article.
If all scores are low: Do not panic, and do not give up. Almost every organization starts here. What is needed is realistic expectations: not transformation in three months, but steady, gradual improvement over one to two years.
Decisions That Should Wait Until the Assessment Is Done
Several major decisions should not be made before the assessment is complete, because the results often change their direction:
- Buying an ERP or large system. This decision is most often made too quickly. Assessments frequently reveal that the problem is not a lack of systems but processes that are not ready to be run by one.
- Rewriting old applications. Before deciding to rebuild, make sure the processes the new system will run are healthy. Rewriting a system for a chaotic process only moves the problem.
- Large-scale technology hiring. An honest assessment often shows the real need is not more people but clearer processes and better-suited systems.
- Build vs. buy decisions. The "custom or package" question — which we cover in our custom vs. off-the-shelf software guide — can only be answered well once you know the organization's readiness level. A Level 1 organization is not ready for custom systems; a Level 3 organization might be.
The principle is simple: an assessment is not for delaying decisions, but for ensuring decisions are made on reality rather than assumptions.
Who Should Run the Assessment
An assessment can be run in-house, but there is great value in an outside perspective. Internal teams are often too close to the organization: they have grown used to the existing chaos, or on the contrary, they are defensive about old ways of working. External consultants or partners bring tested frameworks and the courage to say unpleasant things.
We have covered when businesses need professional help in our IT consultant guide. In short: a digital readiness assessment is one of the moments where external help is most valuable, because its results determine the direction of investments that can reach hundreds of millions of rupiah.
Sample Questions You Can Use
To help you get started, here are example questions for each dimension. Answer them honestly, and do not hesitate to have field staff answer the same version of the questions — differences between levels are often more informative than the answers themselves.
- Process: Does every core workflow have written documentation? If the key person is unavailable tomorrow, could someone else run their work without guessing?
- Data: Can you state today's exact stock count without asking someone else? Can last month's sales figures be verified from a single source?
- People: Can every team member use the digital tools their job requires without help from others? Is there someone who can translate business needs into system needs?
- Culture: Are honest mistakes discussed openly, or hidden? Does management set an example by using the systems, or do they often "exempt themselves"?
- Technology: Are the existing systems recorded and documented? Is any part dependent on one person or one device?
Five questions per dimension — 25 questions in total — is enough for a useful first map. The key is not completeness but honesty.
Common Mistakes When Running an Assessment
A carelessly run assessment can be worse than no assessment at all, because it provides a false sense of security. Here are the most common mistake patterns we see:
Assessing perception instead of evidence. Assessments based only on management feelings — "our team is surely ready" — almost always miss the mark. A healthy assessment requires simple evidence: see directly how processes run, ask for real data samples, and observe how decisions are recorded. One day watching operations provides more information than a week of discussion in the meeting room.
Listening to only one side. Leaders tend to rate readiness higher than field staff — not because they lie, but because they see the organization from a different angle. Directors see reports; cashiers see queues. An assessment involving only management produces a map that is accurate upstairs and wrong downstairs.
Focusing too much on technology. The most common tendency: the assessment turns into a hardware and software inventory — how many servers, which apps, what versions. Yet technology is only one of five dimensions, and often not the most decisive one. An assessment that only talks about technology will misdirect your priorities.
Using an inconsistent scale. If one person rates the process as "already tidy" and another rates it "still chaotic," the results cannot be compared. Make sure every dimension is scored against the same level definitions by all assessors — or better, have the same person score all dimensions to maintain consistency.
Jumping to solutions before finishing the assessment. People who have already imagined the answer — "we need an ERP" — will twist the assessment results to fit their conclusion. Discipline yourself: let the assessment finish first, read the results with an open mind, then talk solutions. If the results contradict your initial belief, that is a sign the assessment is working.
Not following up. An assessment whose results are never executed is an expensive document. Assign an owner to every finding, set deadlines, and review progress. An assessment is not the end of the process; it is the starting point of improvement.
Digital Readiness Is Not Assessed Once; It Is Managed
One misconception needs correcting: a digital readiness assessment is not a one-time exam that you pass and move on. It is a management tool used periodically, like a health check — not only when you are sick, but also when you are well.
Organizations that manage their digital readiness well have a rhythm: an initial assessment to establish the starting point, improvements in the weakest dimensions, digital projects run at an appropriate capacity, then a reassessment to measure progress. Each cycle makes the organization more ready for the next.
This pattern is also why we at Kartech. start every engagement by understanding the business problem first — a process we call Frame — before discussing technical solutions. Because we believe the right technology can only be found after organizational readiness is understood honestly. If you would like to assess your business's digital readiness, our team in Bandar Lampung can help map it. Start from the contact page or see our range of services on the services page.
First Step: Honesty
Back to the operations director in Bandung: had he run an assessment before buying the ERP, he might have discovered that his organization was at Level 1 or 2, that warehouse processes were not standardized, and that the team was not ready. He might still have bought a system — but a smaller version, with a slower implementation phase, more serious training, and realistic expectations. The same Rp 400 million could have produced a system people actually used.
A digital readiness assessment is, in the end, an exercise in organizational honesty. It asks questions that are often uncomfortable: are our processes really as good as we think? Can our data truly be trusted? Is our team ready to change?
Those questions are not pleasant, but answering them is cheaper than paying for the answers later — when the systems are bought, the teams are disappointed, and the expected transformation has turned into idle budget. Start with an honest assessment, and let the rest follow.
