Hi, this is Higashi.
I sometimes hear engineers working in technology development say, “We’ve developed a good technology, but the production development team isn’t using it.”
They have improved its performance and confirmed that it works. Yet it still hasn’t found its way into an actual development project. After putting so much time into it, that must be frustrating. I often see people around me struggling with this.
I work for an automotive manufacturer, where I am involved in both technology development and production development: developing vehicles for series production. Around me, these responsibilities are often handled by separate teams. Working in both roles has made me think about how difficult it can be to get a new technology used.
Today, I’d like to share a few things I have learned from that experience.
- Adopting a new technology takes work for the people using it
- Knowing the developer can make it easier to give a technology a try
- Working on real projects changes the problems you choose to solve
- Once people use it, the next problems become clearer
- The effort at the beginning can reduce wasted development later
- Explore together what is stopping people from using it
Adopting a new technology takes work for the people using it
When you develop a technology that improves performance or accuracy, you naturally want people to use it.
The production development team, meanwhile, has ongoing work and deadlines to meet. To adopt something new, they need to check whether it will help their project, learn how to use it, and verify that the results are sound.
It may also change parts of their workflow. Even if they can see the potential benefits, they may not be ready to try it straight away.
In my own production development work, I feel there is a gap between understanding the merits of a proposed technology and using it in the work in front of me.
Closing that gap takes a clear explanation of the technology, along with a working relationship that helps people feel comfortable trying it.
Knowing the developer can make it easier to give a technology a try
One thing I have noticed while working in both roles is that everyday working relationships can create an opening for people to try something new.
When you work together on production development problems, you get more opportunities to understand the other person’s situation and concerns.
When I then propose a technology, I sometimes get the impression that people are thinking, “If you’re recommending it, I’ll give it a try.” I haven’t asked them directly whether that is how they feel; it is simply my own impression.
From the user’s perspective, knowing who developed the technology and having someone to turn to when they run into trouble may make the first step easier.
After hearing an explanation, they might wonder, “Will this work under our conditions?” or “Can I ask for help if something goes wrong?” Their experience of working with the developer may help them decide.
I feel that getting a technology adopted starts well before the finished technology is introduced.
Working on real projects changes the problems you choose to solve
Another major benefit is being able to treat the difficulties in production development as problems I face myself.
In technology development, we often learn about those difficulties by hearing about them from other people.
But even when I think I understand a problem after hearing about it, actually doing the work can change my view. What takes time? Where is it difficult to make a decision? What would make the job easier if it were solved? Experiencing these things within the workflow makes the problem more concrete.
Then, alongside asking how to improve a particular performance measure, I can start thinking, “Could we make that task easier?” or “Could we support that decision?”
It also becomes easier to explain where and how the technology would help when I propose it.
For me, the benefits of working in both roles are connected: it becomes easier to get a technology tried, and easier to develop something that fits the situation in which it will be used.
Once people use it, the next problems become clearer
Even a technology developed to meet a real need can reveal unexpected problems when people start using it.
You listen to their feedback, make improvements, and have them try it again. As this exchange continues, it becomes easier to see what to develop next.
I feel that the following steps have started to connect in my own work:
Understand a production development problem → Develop a technology → Have people try it → Improve it → Identify the next problem
Once someone uses a technology, you have an opportunity to hear their feedback. Improving it in response can make them more comfortable coming to you again. Keeping that relationship going also helps you decide where to take the technology next.
Getting to that first use can be difficult. That is why I think it is important to keep following how the technology is being used in the person’s work after they have tried it.
The effort at the beginning can reduce wasted development later
Working in both areas means more to learn and think about at first. Understanding the production development team’s situation and trying things together also takes time.
Still, once the cycle of understanding a problem, developing a technology, and getting it used starts working, I feel that the initial effort begins to pay off.
Having a concrete use in mind makes it easier to decide what to prioritize. Getting feedback early can also reduce the need to change direction after a great deal has already been built.
If development continues without knowing whether anyone will use the result, a mismatch with the team’s needs may only become apparent after the work is finished. Discovering that mismatch earlier can help reduce effort spent developing things that do not get used.
The time spent staying close to the work can lead to better results later. That is the positive cycle I have felt through working in both roles.
Explore together what is stopping people from using it
When a technology you developed goes unused, it can feel as though your effort has been rejected.
At a time like that, it may help to ask where the people who would use it are getting stuck.
Does the technology address a problem they are currently facing? What do they need to prepare before trying it? What is missing that would let them check the results?
Talking through these questions in the context of their actual work can sometimes make the next step clearer.
Being involved in production development has given me more opportunities to consider the situation of the people receiving a new technology. I want to keep working with them to understand their problems, have them try what I develop, and use the results to improve it.
If you are struggling to get your technology used, I hope something here is helpful.
See you next time!


コメント