Every morning, your day starts with the RPA daily. Together with the RPA consultant and analyst, your fellow RPA developers, and the project lead, you briefly review the ongoing projects and planning. This way, everyone stays informed about what is happening, what is being worked on, and communication lines remain short. After the daily, you align a few remaining details in a process with the analyst so you can continue working on your RPA script.

At 11:00, you receive a helpdesk ticket that needs to be resolved: a client’s process has stopped because the robot can no longer find a field within an application. Most likely, an update has taken place in the application. After making a small adjustment in the script, you can deploy a new robot version live and inform your colleague that the issue has been resolved.

Between 12:00 and 13:00, it’s time for lunch, and at the same time, you join a card game in the cafeteria.

After lunch, you’ve been able to focus on your script again. The robot is now able to import a file and prepare the rows from that file for further processing within the CRM application.

At 14:30, you have a meeting with the product owner of Spider: you would like to request a new feature in Spider that would make your work easier. The product owner asks you many detailed questions to clearly understand your needs and determine the value for Nidaros and its clients.

Around 15:00, you take a short break—playing a game of pool or getting some fresh air—so you can return sharp for the slow-start session with a client. After the internal reviews, you now show the client via Teams how the robot handles the process step by step in the production environment. If everything goes well, the robot can remain active.

You end the day by preparing for the monthly work session you have on-site tomorrow at a large labor union.