"Digital transformation" has become a phrase without precise content. Process consultants use it when talking about workflow redesign. Software suppliers use it when talking about cloud migration. Regional planning offices use it when talking about grants. General-purpose articles use it when talking about anything to do with computers and companies.
Behind each of these uses is a different idea. An SME owner facing the phrase does not know which of the ideas is being proposed, and often the person proposing it does not know either. Money is spent on projects called "digital transformation" without anyone having asked beforehand what should actually change, in practice, in the company's typical day after the project.
The way to bring the phrase back to a useful level is to lower it to the concrete. Not "digitally transform the company", but: what changes on Monday morning for the owner, what changes for the front desk, what changes for the senior collaborator. If nothing measurable changes in their day, the transformation has not happened, regardless of the money spent and the richness of the reports delivered.
What changes for the owner, if the transformation is real
The owner of a medium-sized Italian SME, before a real transformation, has a day similar to this. He opens his laptop at half past eight. Thirty emails arrive in three inboxes (personal, operational, accounting). He opens WhatsApp, where he has twenty messages from clients, suppliers, collaborators. He has a meeting at nine with the administrative manager to review the previous month's accounts. Then a difficult client at ten on the phone. Then an urgent request from the production manager at eleven. Lunch skipped. In the afternoon, he tries to catch up on the list of things he wanted to do this morning and did not do. At seven in the evening he goes home with the feeling of having put out fires, not of having governed the company.
After a real transformation, the day changes in concrete ways.
The thirty incoming emails are sorted before they even reach the owner. Half are handled by a system that knows the company and replies to recurring questions. Another quarter is assigned to the right collaborators with the context already prepared. Only the remainder reaches the owner, with clear priority and a summary of useful context.
The twenty WhatsApp messages have passed through a similar filter. Clients writing for information receive answers in reasonable times even when the owner is in a meeting. Exchanges requiring the owner arrive with a reminder explaining the context, so that the owner does not have to rebuild it.
The administrative meeting at nine is not a re-reading of data the owner could read on his own. It is a conversation on decisions, because the data has already been prepared, summarised and contextualised by the system. The owner enters the meeting knowing what he has to decide, not what he has to learn.
The urgent request at eleven is still urgent, because some urgencies are real. But half of the "urgent requests" that arrived before were only repetitions of questions already asked, or symptoms of collaborators who did not have access to the context. The system has absorbed many of these, and what remains genuinely requires the owner.
At seven in the evening, the owner has worked on three to five significant decisions instead of fifty micro-interruptions. The feeling is different, and measurable. He can quantify what he has done, what has remained open, what he has decided. The sensation of putting out fires decreases.
What changes for the front desk
The front desk, in an Italian SME, is typically the role most overloaded with routine. She answers the phone, filters visitors, handles the owner's diary, prepares documents, archives, takes care of things that are not in her job description but that "someone had to do".
Before the transformation, her day is fragmented into hundreds of micro-activities, with zero residual time. If she falls ill, the practice slows down visibly. If she resigns, the replacement takes months to rebuild the knowledge she had.
After a real transformation, the front desk becomes a decision centre, not an executor of tasks. Routine calls are filtered. Repeatable questions are handled by the system on WhatsApp. The filtering of the owner's diary is automated based on rules defined together. The time dedicated to activities requiring judgement (such as handling a difficult client, deciding how to move an appointment with multiple constraints) grows.
The front desk, afterwards, does not have less work. She has work of different quality. The time taken from micro-activities is invested in things that previously were not done for lack of time: following clients in negotiation to make sure they are not lost, verifying that outgoing communications are consistent with the company style, proactively contacting inactive clients.
The practice or the company, overall, works with the same front desk but covers many more fronts. And if the front desk falls ill or resigns, the system keeps working on the parts that have been automated, while the human part can be temporarily covered by colleagues or by a less traumatic replacement.
What changes for the senior collaborator
The senior collaborator, in an SME, is typically the person who "knows how things are done". He is the operational glue of the practice. His competences are diffuse, not documented. Younger colleagues often consult him. Clients prefer him when they can. The owner considers him indispensable.
Before a real transformation, the senior is overloaded because everyone interrupts him for information nobody else has. He consumes his time on questions that, if answering did not require his judgement, should not pass through him.
After, the part of knowledge that does not require judgement has been made explicit and structured. Younger colleagues can consult the system for standard questions ("how do we handle commerce clients in this situation?"). The system replies with the information the senior would have given before. The senior intervenes only where his real judgement is needed, which is much less often than before.
His day lightens in volume and enriches in quality. He can dedicate himself to the work where his judgement really counts: exceptional cases, strategic clients, qualitative training of juniors. This training, in the absence of transformation, does not happen because the senior does not have time.
There is an important side effect. The transformation structures the senior's knowledge. This means that when the senior retires or changes company, the company does not lose everything he knew. It loses his presence, his judgement, his relationship with clients. But the structured part of his knowledge stays available to those who come after.
The practical test
If after a project called "digital transformation" the owner continues to put out fires as before, the front desk is still overloaded, and the senior is still constantly interrupted for routine questions, the transformation has not happened. What may have happened is a technological migration, a software installation, a change of supplier. It is not transformation.
This is the practical test worth applying before investing and afterwards. Monday morning, three months after the project closes, ask the owner, the front desk and the senior what has changed in their day. If the answer is "not much, we use the new software but the day is similar", the project has not produced transformation. If the answer is "until recently we used to lose a lot of time on X, and now X is handled by the system", something has really changed.
The work that produces real transformation has a specific characteristic: it does not start from tools, it starts from information flows. It maps how information circulates today in the company, identifies where it accumulates uselessly on the owner, the front desk and the senior, designs a setup in which most of the circulation is automatic and human intervention is reserved for decisions requiring judgement.
Only after this design do you choose tools. Tools are not the project; they are the consequence of the project. A good project produces targeted choices, not generic configurations.
This way of proceeding is slow at the start. An operational map takes weeks, not hours. But the return is visible in the months that follow, when the tools introduced do what they should do because they have a structure in front of them that supports them.
The starting point
An owner who wants to understand whether in his company digital transformation makes sense as a project, and how to do it, can start from a simple exercise. Choose a typical week and, at the end, count how many hours you spent on activities that really required your judgement and how many on things that someone else (a person, a system) could have done in your place given the right context.
If the second figure is higher than the first, there is a lot of margin. If it is lower, there is less urgency, but often other bottlenecks elsewhere (front desk, senior) deserve the same examination.
From this observation a concrete idea emerges of what should change. From there, digital transformation stops being a slogan and becomes a specific plan for your company. In forty-five minutes of structured conversation, this picture takes clear form and stays with you, regardless of what you decide to do afterwards.