About
Resources
© All rights reserved
Implementing procurement automation software is necessary for operational purchasing departments to stay competitive and resilient. Manual tasks are time-consuming and hinder procurement teams to reach their full potential. It is common for teams to resist change; introducing a new software solution can lead to push back from employees, who often need to be persuaded of the benefits.
Purchasing departments can be reluctant to determine a key user for the software project. However, having a key user is of great value since they act as an interface between the purchasing department and the software provider. The work of a key user is important for the success of both the implementation and the solution itself.
A key user is an employee who specialises in a product or software and is considered the primary contact person for all questions, problems or trainings that relate to it.
In purchasing, they play a key role in the introduction of new processes and software solutions. In procurement automation projects, operational buyers often assume the role of the key user. When implementing an automation software in operational procurement, key users support the process by representing the professional interests of their division or department. Their tasks include supporting the definition of the new system’s scope of services, accompanying the introduction process, encouraging the adoption of the software among colleagues, and support colleagues after the go-live.
Key users accompany the entire automation project in operational purchasing and have a wide variety of tasks during the different phases:
Analysis phase
Key users help to define the scope for improvement in the purchasing department by formulating the goals and requirements of the automation software.
Netfira offers a checklist for defining software requirements that support enterprises in specifying users’ goals, IT requirements, business requirements and more.
The software selection checklist supports companies in defining goals that meet the SMART criteria and selecting the right procurement automation software.
Key users are also involved in the market analysis; they obtain product information through direct contact with potential software providers and review case study materials.
Negotiations
Since key users are often part of the analysis phase, know the existing systems and what functionalities the automation solution should have, it is not uncommon for them to join the negotiations.
Development of the rollout strategy
After choosing a software solution, key users are also part of the process of accessing the initial needs and developing the rollout strategy.
Implementation phase
In the implementation phase, key users are indispensable. They ensure that requirements are implemented correctly from a technical point of view. Furthermore, they carry out functional tests and give feedback to the project and management teams on a regular basis.
Training phase
Key users are responsible for designing training concepts and training their team members who will work with the procurement automation software.
Go-live
Key users actively accompany the go-live.
After the go-live
When using the procurement automation solution, key users stay the first point of contact for questions and problems. They collect ideas for improvements and thus contribute to the further development of the automation project.
Usually, key users fulfil several functions and roles in a company.
Key users are specialists in their field. They are experts in using the systems and know all processes. They can provide input and offer insight to the challenges in operational procurement like manual document processing on a daily basis.
As ambassadors, they have two functions: On the one hand, they communicate the underlying idea of the automation software as well as the motives and goals of the department management or executive board to the service provider. On the other hand, they are ambassadors for the purchasing department and the users when communicating with management for they know and understand the problems and challenges.
Key users take on a central role as testers. They test both beta versions and new versions of the software before they are rolled out in the purchasing department. That way, key users ensure that the automation tool meets the needs of the organisation. Therefore, they are always in direct contact with the software provider to give feedback.
As trainers, they design training concepts and can explain the functionality and operation of the procurement automation software to the team.
Key users act as supporters who can answer questions about the operation and use of the automation solution for purchasing.
As multipliers or corporate influencers, they increase the knowledge about the implemented procurement automation solution and its benefits. They play a vital role in promoting the new solution within the department and thus contribute to greater use and corresponding amortisation.
Appointing a key user has several benefits:
Whether a key user is determined in a procurement automation project or not, can heavily impact the outcome of the project. The benefits of key users when implementing new software should not be underestimated. They are experts in their field, influencers and a feedback channel to the management level. Key users enable smooth communication between all parties and support the adoption of digital automation tools on both a personal and technical level.
© All rights reserved
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category. |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | The website's WordPress theme uses this cookie. It allows the website owner to implement or change the website's content in real-time. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
_GRECAPTCHA | 5 months 27 days | Google Recaptcha service sets this cookie to identify bots to protect the website against malicious spam attacks. |
__hssc | 30 minutes | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
__hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
Cookie | Duration | Description |
---|---|---|
_hjAbsoluteSessionInProgress | 30 minutes | Hotjar sets this cookie to detect a user's first pageview session, which is a True/False flag set by the cookie. |
__cf_bm | 30 minutes | Cloudflare set the cookie to support Cloudflare Bot Management. |
Cookie | Duration | Description |
---|---|---|
hubspotutk | 5 months 27 days | HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
_ga | 1 year 1 month 4 days | Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
_gat_gtag_UA_* | 1 minute | Google Analytics sets this cookie to store a unique user ID. |
_gid | 1 day | Google Analytics sets this cookie to store information on how visitors use a website while also creating an analytics report of the website's performance. Some of the collected data includes the number of visitors, their source, and the pages they visit anonymously. |
_hjFirstSeen | 30 minutes | Hotjar sets this cookie to identify a new user’s first session. It stores the true/false value, indicating whether it was the first time Hotjar saw this user. |
_hjRecordingEnabled | never | Hotjar sets this cookie when a Recording starts and is read when the recording module is initialized, to see if the user is already in a recording in a particular session. |
_hjRecordingLastActivity | never | Hotjar sets this cookie when a user recording starts and when data is sent through the WebSocket. |
__hstc | 5 months 27 days | Hubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
Cookie | Duration | Description |
---|---|---|
_hjIncludedInSessionSample_3458699 | 2 minutes | Description is currently not available. |
_hjSessionUser_3458699 | 1 year | Description is currently not available. |
_hjSession_3458699 | 30 minutes | Description is currently not available. |