Although every innovation in technology is unique but there are commonalities within the innovation process. Based on the lessons we’ve learned carrying out the work of technology innovation over the past few years, we’ve created the steps needed to go from idea to a meaningful product.
1. Find an Unmet Need
If you’re closer to a problem the closer you’ll be towards finding the solution. The world is filled with needless and unfulfilled that leave people suffering, and not realizing that there is a better solution. Solutions aren’t always easy to come up with and often, symptoms obscure the underlying issue.
After processing thousand inspection reports PCS realized there was a gap in the need to improve the efficiency of reporting on inspections, as regulations were placing pressure on existing processes and increasing the stakes. Through direct conversations with a variety of inspectors, and experiencing the limitations of current processes and observing the limitations of existing processes, we recognized the necessity. Then, we were able to analyze the most common issues in the existing methods and tools.
2. Study the Effects of a Solution
When you resolve one problem, you end up creating multiple. Did you just solve the problem? Was there a larger need that made the solution ineffective? The needs aren’t isolated. They are heavily connected to other problems being solved by a massive sum of cash. When change starts to happen and the existing systems are removed It is essential to validate every idea that is possible and to understand the consequences on the proposed solution. Innovative innovators like Sakichi Toyoda offer a valuable approach to root cause analysis to ask “why” five times. The answer to the five fifth “why” typically will pinpoint the source.
The first four answers provide insights into the cause and symptoms that are related to the issue. The process of reporting inspections had many areas to improve however, we needed to know what steps within the process were in place and what changes they could make.
For the Mobile Inspection Forms TM we needed verify whether we had actually reduced the amount of time inspectors filling out reports and if these reports were more accurate due to the elimination of common mistakes like incorrectly formatted station number and incorrectly naming reports or saving a previous report or other report, etc.
These factors would tell us whether the benefits of technology were positive. The streamlined process resulted in enormous time savings, which inspectors adored, but also made it easier to automate a lot of the things office managers normally did. We learned about assumptions and the effects we didn’t think about by trial and error before we were able to nail it.
3. Gathering Requirements from stakeholders
A clearly defined problem in context determines the initial requirements for technical solutions. The next step is to uncover the expectations users have regarding technology. What are their expectations when using the technology? What can it do to help them? Harder? What do they think is the biggest concern with technology.
We spoke to experts in the field and discovered what they did and did not appreciate about the present Excel solutions. The basic interaction with prototypes of UI/UX can help users clarify what they are expecting and build confidence so that they know the future. This can save time later.
4. Design & Plan with all stakeholders
A lot of technologies begin with a vague notion of a problem. They also have an over-inflated view of an answer: an easy recipe with low-impact. Determine what is needed to solve the problem by consulting experts in technology and business experts, as well as those who are closest to the issue present in the room.
We had to go through several cycles before we could add budgets, schedules, and a well-trained inspector and business advocate to ensure that we’re on the correct track throughout the process. The creation of a high-performing team is vital. Honesty and sanity are crucial when it comes to this. If the issue isn’t genuine or you don’t have the resources necessary to address it, spare everyone time and to find a different problem you have the ability to address.
5. Build and Deliver Often Using Clear Requirements
Here, engineers perform their thing. Clare requirements and expectations, coupled with a problem to be solved an actual problem creates an environment that allows for true innovation to come to fruition. Technology is developed by assembling functional pieces at a time, with the potential for chance of failure and risk at each stage, therefore setting precise parameters can facilitate clear communication and a clear understanding of the inherent risks associated with innovation.
When we developed Mobile Inspection Forms TM initially, the delivery and review of the development was too dissimilar, which led to the development team to their own with no communication. More clear roles and better communication helped solve this issue for us.
Break down development into smaller functional units, with specific requirements and be sure to communicate frequently. If a feature is going to take an enormous amount of time to build and isn’t important, it’s better to create it in smaller chunks and then get feedback rather than devote a lot of time constructing it, and then building it again.
6. Feedback, Feedback, Feedback
Steve Jobs taught us that people don’t know what they want until you demonstrate it to them. The same is true for things they don’t like. It is important to create space for people to talk about things they dislike about the information you provide them, and then observe how they are confused or annoyed.
While the main components in Mobile Inspection Formulas that were designed We had totally impartial experts who had experience in the field to test the system and provide feedback from the field. Whatever time you spend trying to figure out the issue from the beginning and gather all the necessary information for the ideal solution to technology, the truth is that you’ll receive more thorough and extensive details after someone tests the solution you created.
A shorter time frame for feedback allows faster access to this wealth of data. This is definitely the case for pipeline inspectors and we ensured that all feedback received is taken into consideration and is incorporated into needs to be considered for the next stage of development.
7. Iterate
Innovation is a fundamental process. Sorry if this title made you believe that there are only 10 steps to creating an innovative technology, but that’s not the case. Each step builds on the one before it, and should you proceed too soon to the next step it will be a relapse back to any step that missed the due diligence requirement. Sometimes, it’s all the way through to Step 1 and you only learned the wrong thing to do.
If you’ve completed the first 4 steps properly but, it’s beneficial to repeat steps five and six as often as you are able to afford and as quickly as you can. If in doubt, iterate! Resolve the mistakes, and bring more clarity around the contextual requirements that you didn’t realize existed prior to beginning. Check every aspect. We used an Agile method of product development called Scrum to manage the iterations. The structure and communication provided an excellent overview of the team’s resources, and allowed everyone to help with projects that took longer than anticipated.
It is crucial to concentrate on the most important aspects to the users first, so that the most crucial components are in place in case you encounter budget or time limitations. It is possible to continue to improve your technology for a long time however, the feedback of those who are using your technology will show the time when it’s ready.
8. Tell Them Why They’ll Love It
You’ve made something extraordinary and everyone needs to be aware of the reasons why it’s exceptional and why it’s there to meet a need you are able to comprehend. Innovative technology opens a new realm of possibilities Tell people about it! Let them see what’s been developed and let them test the technology. If they always get excited and are able to present the value of the solution without prompting, congrats.
If not, you’re back at step 1, 2 or 3. Do not be discouraged, however this occurs all the time. We ran full-scale tests of our system three times before we received the approval of the project managers and inspectors. We now have a solution that actually works, we’re telling all the people in the globe about our mobile Inspection Forms TM and how they are revolutionizing the way pipeliners gather information about the progress and quality in midstream development.
9. Launch in partnership with Key Stakeholders
The stakeholders who are utilizing and dependent to your tech will provide you the most important data that can be incorporated into new versions of your technology. Technology launches should actively involve these important stakeholders throughout the deployment process. We discovered that it is best to bring certain key stakeholders directly on the team that will be deploying.
Consider a technology launch as a true partnership between the technology consultant and other key stakeholders is essential to its general success. When using mobile inspection forms TM We develop an individual strategy for each project, ranging from online instruction to field technicians that are capable of acting as pipeline inspectors and offering on-site Tier 1 assistance every day.
We are attentive to the needs of the inspectors and managers, and then adapt every deployment to allow them to achieve success. Sometimes, this means tailoring the procedures around their requirements or speeding up application updates in order to release features that they require.
10. Empathy and Support Technology
It’s impossible to be perfect. There are flaws in any technology, and people are extremely adept in showing them. After all the work to develop a fantastic product, it is easy to get dissatisfied when something you believe may be a minor issue appears huge emotionally to someone who can’t do their job simply because it is there. Support is based on empathy. You need to be able to relate to the person, and then try to understand the issues, and take responsibility for any lapses within the solution, and establish an approach that ensures that every issue is identified and addressed as fast as is possible.
We have learned over time that when working with pipeline inspectors, it is best to work with people who can empathize with the situation on the ground, so we entrusted our own inspectors into the field to work with them. PCS’s Support team is made up of experienced professionals who know what a jeep means and the meaning behind it, what MTR is and the distinction between a tie-in and a mainline welding, and the reasons why it is important.
We try to be empathetic with inspectors, comprehend their issues and views and then think about the best way to resolve their issues quickly due to the highly-sensitive nature of field work. If you are attentive to them, they may suggest a different issue that can lead to your next innovation in technology.