[A Prescription for Promoting DX, Part 1] "What is DX?" - Starting with the Difference from IT Implementation: The First Step

[A Prescription for Promoting DX, Part 1] "What is DX?" - Starting with the Difference from IT Implementation: The First Step

This is a fictional conversation between the president of a company and a professional engineer.

One day, the company president came to me with this request.

President: "How's our DX (Digital Transformation) going?"

Professional Engineer: "What aspects are you referring to when you say 'what's going on'?"

The president looked a little puzzled.

President: "Well, we have an IT department, don't we? They're able to advise us on improvements like wanting to speed up this task or wanting to automate this Excel spreadsheet, right?"

Professional Engineer: "Yes, that's fine."

President: "I see. In that case, doesn't that mean our DX is progressing well?"

Professional engineer: "Mr. President, I think that's a little different from what we discussed..."

Their conversation doesn't seem to be quite connecting.

So, what's wrong with it?

What was the CEO's idea of "DX"?

The president probably had an image like this in his mind.

"We will use IT to make things easier for our employees who are facing difficulties."

This is by no means a wrong way of thinking.

In fact, automating Excel tasks, digitizing paper documents, and streamlining tedious tasks with systems are all important for a company.

For example, consider this question:

  • "I want to do this calculation quickly, so could you teach me how to use a macro?"
  • "I want to export this form to another Excel file. Is there a good function I can use to do this?"
  • "I want to send out an email to everyone at once. Do you have any suggestions for a good way to do that?"

Making these kinds of jobs easier with IT is certainly worthwhile.

However,"DX itself"If you think of it that way, it changes a little.

What exactly is DX (Digital Transformation)?

The term DX is being used in many different contexts.

Simply put, it's about using digital technology to transform the way we work, how we organize, and even the business itself.

This isn't simply a matter of "installing a new system."

What's important is,

"How can we use digital technology to transform our company?"

That's the point.

If we leave this point vague and simply systematize each task in front of us one by one, before we know it, "IT implementation" will become the goal itself.

Three stages commonly used when considering DX

When considering DX, it is often explained in the following three stages.

Digitization – Start by making it electronic.

This is the stage where we're digitizing information that's currently on paper.

for example,

  • Convert paper documents to PDFs.
  • Recording time on a PC or smartphone instead of using a paper time card.
  • Digitizing ledgers that were previously managed on paper.

That's about it.

Digitalization – Using digital technology to transform workflows

We are now in the stage of using digitized information to streamline the entire workflow.

For example, information received through online orders can be directly linked to inventory management, production, accounting, and other processes.

The key is not just to make each individual task easier, but to look at the overall workflow.

DX – Transforming the company itself

Further along the line, there's a stage where we consider new business models, services, and organizational structures based on the digital landscape.

For example, the shift from "owning" a car to a service that allows you to rent one anytime using your smartphone.

From "renting" DVDs to a service that allows you to enjoy videos via the internet.

In this way, digital technology can change the very nature of business itself.

So, what was the president looking at earlier?

The part the president was thinking about earlier was probably the one closest to the viewer.

"Our employees are having trouble."

"I want to make this process more convenient."

"I want to automate Excel."

Of course, these improvements are also necessary.

However, if you only focus on that aspect, you lose sight of "where the company as a whole wants to go."

When considering digital transformation (DX), it's necessary to look not only at the work at hand, but also at the purpose and meaning that work holds within the company.

"Let's just digitize it for now" - wait a moment.

Let me share one of my own experiences.

When I used to work, I had a lot of paper files around my desk.

"If we scan and digitize all of this, we can search through it, and we won't need cabinets anymore. We might even be able to reduce the office space."

That's what I was thinking.

However, when I actually tried it, it wasn't that easy.

The paper sizes are different.

It's stapled together.

Some are single-sided, while others are double-sided.

There are also large blueprints.

And most importantly, I have to do the digitization work while also doing my regular job.

In the end, the work took about a month.

In the end, the amount of paper was reduced to the point where it could fit in a coin locker.

Upon closer inspection, I realized that some items were no longer necessary and ended up discarding them.

I noticed something here.

Before digitizing, it's important to visualize what the digitized version will look like.

It certainly took time, but there were also advantages to digitizing the process.

However, on the other hand, a new job arose: the need to properly store that electronic data on servers.

It's not a matter of "digitizing something because it's paper," but rather, in the first place,

  • What do you plan to use the digitized version for?
  • Does this document need to be digitized?
  • Who is using it, when, and for what purpose?
  • First of all, can't we eliminate the very work that generates this document?

We need to start thinking from there.

It's not always the case that "systematizing the work that's causing problems is the solution."

There's one more thing to keep in mind when considering DX.

it is,Simply automating a problematic task isn't always the best solution.That's the point.

For example, let's say there's someone who has been in charge of a certain job for many years.

That person knows the workflow very well.

"In this case, do this."

"This is how you should interpret this data."

"This case is different from the usual."

I build my work by accumulating such experiences and judgments.

So, let's say the decision is made to "systematize this work."

At first glance, this seems like a good improvement.

But what if we simply embedded that person's unique way of working directly into the system?

What if that person gets transferred?

What if you quit your job?

If we need to modify the system, who will have the authority to make that decision?

In other words,

Systematizing tasks that are highly dependent on specific individuals or tasks that are currently being handled can potentially become detrimental to the overall structure of the company.

It's important to consider whether what you're trying to do aligns with the overall structure of the company.

Before systematizing, take a bird's-eye view of your work.

So, what should we do?

I believe it's important to first look at the work itself from a broader perspective before implementing a system.

For example, we will check the following:

  • Where will that work ultimately lead?
  • Is that job necessary for the organization?
  • Who is doing that job?
  • Can you explain why the procedure is structured that way?
  • How do you handle exceptions when they occur?

And in order,

  1. Understand the job content
  2. Organize the work procedures.
  3. Eliminate unnecessary work
  4. Make it so that anyone can do it the same way.
  5. Furthermore, we will systematize the necessary parts.

This is one way of thinking about it.

Of course, this doesn't mean that all tasks must be done in this order.

just,

"We'll systemize it because it can be systematized."

Instead,

"We consider the best way of working for the company, and if necessary, we systematize it."

I think that perspective is important.

Digitizing and improving work are not the same thing.

Let's summarize what we've discussed so far.

Convert paper documents to PDFs. Automate Excel tasks. Implement systems. Use AI.

All of these are means to improve the company, but they are not ends in themselves.

What matters is what happens afterward.

"I wonder if this job could be any better."

"Is there a way to create a work structure that allows employees to perform at their best?"

"As a company, isn't there a way we can do a better job?"

As a result of this consideration, we decide to use IT and AI. That is one starting point when thinking about digital transformation (DX).

So, where should we actually begin?

After reading this far, you might be wondering, "So, what exactly should my company do?"

AI, cloud computing, system modernization... The term DX (Digital Transformation) can sound daunting, but you don't need to jump straight into thinking about digital technologies and systems.

First, take a look around the company.

"Are there any problems within the company?"

"Is it okay to continue doing things this way?"

I think it's perfectly fine to start with such a small question.

What does the company want to become in the future?

Let's examine the gap between the company's current state and its desired future state. From there, we can consider the necessary IT and AI solutions.

Next time, we'll discuss, "So, where should our company begin?"

When researching DX, the conversation inevitably revolves around "What is DX?" and "What technologies are involved?"

However, from the company's perspective, what they really want to know might be something more immediate and personal.

"So, where should our company start?"

Next time, I'd like to consider those questions in more detail.

Copied title and URL