This is a fictional conversation between the president of a company and a professional engineer.
President: "Last time, we talked about how important it is to communicate the vision to employees."
Professional Engineer: "Yes."
President: "So, I talked to the employees about it."
Professional Engineer: "How was it for all the employees?"
President: "Well, nothing changed immediately, though."
Professional Engineer: "That sounds good. Now, there's something else I'd like to see."
President: "What?"
Professional Engineer: "This is the work that all of your employees are currently doing."
President: "Work?"
Professional Engineer: "Yes. Does that work align with the vision the company is aiming for?"
President: "...Now that you mention it, I've never thought about it."
Professional Engineer: "Okay, let's start by looking at it from there."
- Let's compare the vision with the current job.
- "Continuing as before" can sometimes get in the way of the vision.
- First, let's look at the workflow.
- Don't just look at the "jobs that are causing problems."
- Once you can see what kind of work needs to be changed
- Even so, we won't install the system immediately.
- Summary of this article
Let's compare the vision with the current job.
Last time, I talked about how a vision "serves as a benchmark when changing your work."
So, how should we actually use it?
For example, the company's vision is,
"We want to become a company that brings even more joy to our customers."
Let's assume that's the case.
There's no need to immediately look for a new system at this point.
First, let's look at my current job.
"Are our employees spending enough time talking with our customers?"
"Will we be able to answer customer inquiries immediately?"
"Are employees wasting time searching for necessary information?"
"If the person in charge is on leave, won't customer service come to a halt?"
That's how you should use your vision as a benchmark to look at your current job.
Then, the work you previously took for granted will start to look a little different.
"Continuing as before" can sometimes get in the way of the vision.
The company has some long-standing projects.
Paper documents.
Entering data into Excel.
Documents created every month.
A procedure that involves verification by multiple people.
A job only the person in charge understands.
Of course, there are reasons for each of them.
Perhaps it was a necessary job when we started.
However, if the company's direction has changed, then work needs to change as well.
for example,
"We want to improve our customer service."
Despite this, employees spend most of their day creating internal documents.
"I want to create a company where employees can fully utilize their abilities."
Even though I think that, there are many tasks that only the person in charge understands.
"I want to create a company where people can take on new challenges."
Even though I think that, I'm spending a lot of time preparing documents for approval.
That might happen.
The vision itself isn't bad.
The way we're currently working doesn't align with our vision.
First, let's look at the workflow.
President: "I see. But there's a lot of work, right? Are you going to oversee everything?"
Professional Engineer: "You don't need to look at everything from the beginning."
First, let's look at the jobs that seem particularly relevant to the vision.
Next, let's look at how that work is actually done.
for example,
Who will start it?
What will you receive?
What should I enter?
Who will verify this?
Where should I hand it over?
What kind of documents will you create?
Where is the delay occurring?
When you trace the workflow in this way, you can sometimes find that time and effort are being spent in unexpected places.
Then, consider whether that work is truly connected to the vision.
Don't just look at the "jobs that are causing problems."
There's something I'd like to point out here.
When reviewing your work,
"Let's find tasks that our employees are struggling with."
I sometimes think that.
Of course, that's important too.
But that's not all.
Even if employees aren't experiencing any immediate problems, there might be tasks that are hindering the realization of our vision.
For example, employees,
"We've always done it this way, so it's not a problem for us."
That's what I think.
However, that task takes me an hour every day.
If a company wants its employees to spend more time interacting with customers, is that extra hour truly necessary?
It's not just about "whether or not it's causing problems," but also "whether this work is connected to the direction the company is aiming for."
It's important to look at things from that perspective.
Once you can see what kind of work needs to be changed
President: "So, you decide on a vision, and then use that as a benchmark to look at your work. That way, you can see what needs to be changed."
Professional Engineer: "Yes."
However, even at this point, we don't immediately think, "Let's install the system."
The first thing to consider is,
"How can this job bring us closer to our vision?"
That's the point.
I'm quitting my job.
Reduce the workload.
Change the order.
Change the person in charge.
Share information.
Avoid entering the same information multiple times.
There are various methods.
One example of this is IT and AI.
Even so, we won't install the system immediately.
President: "So, IT and AI are the last things to consider?"
Professional Engineer: "Rather than thinking of it as the 'final step,' it's more like 'we'll think about it when it becomes necessary.'"
For example, simply replacing paper-based tasks with a system without changing the workflow itself will only result in mere digitalization.
What we should consider with DX is,
"How can we get closer to the company's vision?"
is.
The answer might be to change the way you work.
We might use IT.
We might use AI.
Alternatively, it might mean, "I'm going to quit this job."
That's why the order is so important.
Define your vision.
↓
Look at my current job.
↓
Identify the gap between the vision and reality.
↓
I'm thinking about how to change my work.
↓
If necessary, we will use IT and AI.
This is the approach to DX that we want to consider this time.
Summary of this article
When you say DX,
"What kind of system should we install?"
It's easy to think that way.
But there's something we need to consider before that.
"Where does the company want to go?"
and,
"Is your current job leading in that direction?"
is.
Defining a vision is equivalent to defining a goal.
And looking at your current job helps you understand where you stand right now.
Once you know your goal and your current location, you can see the "gap" between them.
What we need to consider with DX is how to bridge that gap.
President: "I see. So, just because you've decided on a vision doesn't mean you'll start DX right away."
Professional Engineer: "Yes. First, try to connect your vision with your current work."
President: "Okay, next let's ask the employees about their work."
Professional Engineer: "Yes, that's right. However, there's a little trick to it."
Next time, I'd like to start by asking employees, "How do you feel about your current job?"

