Recently done several projects with customers, but also because of the higher pressure barely fit that affect the truth of these two types of clients, time management throughout the RPA project, cost management, risk management, really big. I'm not going to write too much text to address these issues, to avoid the article becomes dull, obscure, or to draw a caricature of it to make a comparison.
First, let's define a
The first type of customers: aggressive, looking forward to the future development of enterprises, companies interested in intelligence, employees also want to throw out part of their work to make robot-sharing, so that they can do some other more meaningful work.
The second type of customer: companies can intelligently boss wants, but the staff did not want to appear due to a robot or take away their jobs because of the emergence of the robot and the robot to learn how to be bothered with it yourself and do nothing to make the whole robot She does, and then he does not need to manage the robot.
Let’s Go!!!
Start-up phase
The first type of customer
The boss asked, employees are also actively involved
The second type of customer
The boss asked, to silence, surface endorse the boss named
The planning stage - screening process, process design, environmental confirm
The first type of customer
And consulting with raised areas to explore each other, we decided a few processes and priorities, clarify the scope and risk, ready to actively cooperate with the environment. Whether the confirmation process designed to meet real business needs.
The second type of customer
Threw consulting, you can figure it gave no reply after consulting the proposal, the last leader was asked to reply. All make their own decisions consulting, IT and communication themselves. After the confirmation process is not designed, they do first
Implementation stage - development, testing, demand change
The first type of customer
Complete development, test developers and test himself together, to confirm whether there is a problem, find a small problem, small alterations to the amount. Alterations into the portion of the line does not affect.
The second type of customer
Complete development, test to see only part of the process results. Found a lot of problems, alterations large, high-impact changes to the original design. Must be changed in order to complete on-line, on-line time delay. After the change and found the problem, continue to change, decrease fatigue quality developers. What is more simple Excel will not see the results, such as Filter, taught him how to do, also he is engaged in business on the grounds refused to learn.
Closeout - on the line, actual
The first type of customer
Success on the line, the actual increase work efficiency.
Two types of customers
He has not been on the line.
So, the success of a project of RPA or not, is not a Party unilateral effort, and both parties work together to crystallization.
Attached regard to micro-channel public number
Micro-channel public number ID: RPA_Journey
Official website customer service ID: RPAPlus
Thank you for your attention and reading, I hope this article can help your business.
[RPA trade original pure dry content sharing]
[Quoted or reprinted, please be sure to indicate the source]
No reply RPA [the public may be invited into the group]
