こしばゆういちのブログ

理系院卒→ハードウェアエンジニア→HR人材開発マネージャー

How to regret from doing DX

Ah!!! It shouldn't be like this!

Hello, I'm Yuichi Koshiba, Learning & Development Manager of DHL Supply Chain Japan. For the past 2 times, I have posted a blog related to DX.

yuichi-koshiba.hatenablog.com

yuichi-koshiba.hatenablog.com

Have you been motivated to go with DX? Ok, now I'll share some ways to regret from doing DX based on my passed experience or what I've seen.

The 2 best way to quickly regret

The 2nd best way is to start from the task you really want to quit. I know that you are busy everyday with many tasks. Some of them might be what you cannot find the reason to do. You should try to DX them.

And, the best way is to implement famous system without thinking anything. The more expensive, the better features, and more you likely to regret. These days the advertisement of HRIS (Human Resource Information System) can be found anywhere. You should think nothing, but implement it.

Frameworks to resolve problems

Why the above 2 ways are the best way to regret? As I posted before, DX has 2 aspects, "to create new values" and "to reduce costs." These activities are both commonly doing problem solving. Let's take a look at some frameworks of them.

Problem solving framework to create new values

To create values is an activity to find unfamiliar or non-past cases problems, and solve it with new method. Finding that kind of problem itself sounds so difficult and no one can do unless they are super flexible professional group, however there some framework we can refer to. One of them is design thinking. The framework is introduced by IDEO, one of the consultant famous with their numerous outcomes in the area of creating new values.

designthinking.ideo.com

Please refer to the link above for the details, but I want to stress out here that they are starting with "empathize." To define a problem they are going to tackle in, they deeply empathize to users. The way is to interview users many many times, or they sometimes be a user by themselves and have a deep empathizing. After defining the problem, they ideate the way to solve, prototype it, and test it.

Problem solving framework to reduce costs

It is quite obvious that this activity happens because we know that there is a problem which is a cost that should be reduced. The framework to be adapted will be the most popular problem solving method, you can find everywhere in some books or trainings.

  1. Define problem to be solved.
  2. Investigate true cause.
  3. Find solution.
  4. Set Action plan, and review.

What we can find from these framework

Now, when can DX be adapted in these framework? Is it from the very first time you decide to solve some problem? Well, DX is just one of the solutions. In the frameworks we have seen here, you can find that the timing to think of solutions is quite in later stage. You have plenty things to consider before starting DX. Is the task that you really want to quit worth to be solved by DX? If you have a plenty of budget to implement expensive DX system, that's a very happy situation. However, what do you want to resolve by that? The best way to regret is to consider nothing of these.

Are you doing something worth doing?

In one of my favorite comedy show broadcasted in TV, 2 ladies are acting as a factory worker standing in some production line. One of the ladies says, "Now, you put the screw here first. Right after that, I'll unscrew it."

Everyone shouts "It doesn't mean anything!" But, if you are doing something which doesn't mean anything, it means that you are doing the same comedy. If you are making some PPT that no one checks after your hard work, I recommend you to throw the work away before you think how you can DX it. However if you are willing to keep doing your comedy show, you should challenge to DX it.

Ah, for your reference, some of the book is saying that 80% of your task can be quit.

www.amazon.co.jp

So, you want to regret from doing DX? Then you should try what I've recommended!