tokoroten: I think Iā€™m starting to understand why Iā€™m so stuck on the word DX. I feel that the essence of DX, ā€œgaining agility through software that is easy to changeā€, is not understood by people other than software engineers because the word ā€œdigitalā€ does not include ā€œagilityā€.

nishio: ā€œwork hard at operationā€ is more agile than ā€œsoftware updateā€ in a low-tech company that canā€™t outsource software. Thereā€™s no way to get the message across.

t_wada: ā€¦ ā€¦!

nishio: personally, I thought it was ā€œobviousā€ and Iā€™m surprised the response was unexpected w

nishio: There are ā€œcompanies that cannot outsource softwareā€, ā€œoutsourcing to an in-house companyā€, and ā€œcompanies that can outsource software to their information systems departmentā€. There are ā€œcompanies that cannot outsource softwareā€, ā€œoutsourcing to an in-house companyā€, and ā€œcompanies that allow each department (even non-engineers) to tinker with the softwareā€.

tokoroten: Thatā€™s because Japanese labor laws are designed on the premise of gaining agility in personnel changes. The terrible reality is that you will lose just by following the common sense of the society, because you will inevitably be a loser in the use of software just by adopting the Japanese labor system.

  • imageimage
  • tokoroten: The work rules published by the Ministry of Health, Labor and Welfare are based on the premise of gaining agility through personnel changes

  • Just adopting the ā€œJapanese corporate work styleā€ as envisioned by the Ministry of Health, Labor and Welfare will make you a loser in the use of software.

    • image

nishio: Ah, I see. I wonder if Cybozuā€™s system of ā€œno personnel transfers against the will of the employeeā€ (i.e., supervisors do not have the authority to make transfers) is possible because of the agility provided by the software.

tokoroten: ā€œIT availability comes and goesā€ and ā€œthere is no place for software talent to move toā€ was a way of thinking until the 90ā€™s. Today, thanks to cloud computing, IT can be deployed anytime and anywhere. Today, thanks to the cloud, it is possible to deploy at any time, IT availability is constant, and software talent can be deployed anywhere.


nishio: itā€™s obvious that companies that outsource software modifications are slow, but I painted a picture of what happens when departments outsource internally to their internal systems departments

  • image
  • nishio: If only 1/N of all employees are capable of updating internal systems, then in a situation where updating needs occur in all departments, the load will naturally be N times as heavy on the information If there are only 1/N people who can update the internal system, then in a situation where the need for updating occurs in all departments, N times the load will naturally be concentrated on the information system. If each department can do this within their own department, the communication costs associated with in-house outsourcing will be reduced.

  • tokoroten: A true horror story ā€œWhy doesnā€™t this system fix so many errors?ā€ Iā€™ve already made a request to the head office, but the IT department at the head office wonā€™t be available until six months from now, so I canā€™t fix it until six months from now.

  • tokoroten: i would like to talk about domestic violence on a regular basis

  • nishio: too much lol

    • I seeā€¦ if the group companies are large and there is a rule that you can only use what is within the group, there will be no free competition in the market, so in-house outsourcing will be slower than regular outsourcing.

tokoroten: When I hear about Cybozuā€™s HR department building their own system, it reminds me of the story about Facebook hiring programmers for marketing and HR. I donā€™t know how true it is, but it reminds me of the story that Facebook hires programmers for marketing and human resources, otherwise they canā€™t improve their systems.


Regarding ā€œJapanese labor laws are built on the premise of gaining agility through personnel transfers, so simply adopting a Japanese-style personnel and labor system will inevitably make you a loser in the use of software.

chachay: In this arrangement, I think the job system is for people who are particular about the format of documents (but the format is well designed and finely updated with high expertise), and the membership system is for people who have a flexible workflow from a broad perspective (which is covered by the operation). I think itā€™s more like a membership system that allows flexible workflow from a broad perspective (covered by operations)ā€¦

tokoroten: in a world with extremely strong labor unions, no software, no outsourcing or subsidiaries, I think so! The reality is that if you want to get promoted or move into another position, you are expected to go beyond the JD, and if your JD is to create software, you are expected to do all the work involved in that.

nishio: There are two factions: one is the ā€œmembership-based employment plus the right to transfer personnelā€ approach to multi-skilling, and the other is the ā€œjob-based employment plus the right to fireā€ approach to procuring the necessary skills on the market. Cybozu has introduced a membership-based work style with no personnel transfers where there were two factions, and perhaps IT and information sharing are the way to achieve multi-skilling.

tokoroten: Iā€™ve included the fact that Cybozuā€™s HR department is developing their own system by tapping into kintone in my next presentation material for a companyā€™s new employee training.

relevance - slow-moving business


This page is auto-translated from /nishio/DXćØć‚¢ć‚øćƒŖćƒ†ć‚£ using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. Iā€™m very happy to spread my thought to non-Japanese readers.