HomeinsightsWorking alongside the Change Manager: A Project Manager’s experience
digital solutionsgovernance & service management
Working alongside the Change Manager: A Project Manager’s experience
Christelle Martin, Senior Project manager & Alain Geerts, Head of Governance & Service Management Service Line · October 09, 2000
In a previous article, we highlighted the need for companies to seek support during their transformation. We spoke to Nadège Martinet, a senior Change Management consultant, about her role in leading change within a strategic project at a major watchmaking company.
How is the Change Manager perceived by the project manager, and how do the two roles coexist? Christelle Martin, a senior project manager working on the same project as Nadège, answers questions from Alain Geerts, Head of our Governance & Service Management Service Line.
AG: Christelle, in what context did you work together?
CM: My collaboration with Nadège, in her role as Change Manager, took place as part of a project to migrate a CRM solution to Salesforce. The client, a major player in the luxury watch industry, was preparing for a global ‘big-bang’ launch for over 1,200 users spread across several continents. In such an ambitious context, change management was a key factor for success, just as much as the quality of the solution or adherence to the schedule.
AG: What were your respective responsibilities?
CM: As Project Manager, I was responsible for delivering the project within the defined timeframe, scope and budget. This involved, in particular, coordinating the various stream leaders to define deliverables, draw up the schedule, monitor the progress of the work and adjust priorities where necessary to achieve our objectives.
For her part, Nadège was responsible for ensuring the solution was successfully adopted by users. Her role involved anticipating the impacts of the change, engaging stakeholders and consistently maintaining a user-centred approach.
AG: How would you describe working with the Change Manager on this project?
CM: For us, the success of a project depends above all on a genuine spirit of collaboration. On this project in particular, we wanted to embody the ‘One Team’ value in our day-to-day work. We worked as true partners: each of us had our own area of responsibility, whilst bringing complementary skills and perspectives to the table. This close collaboration enabled us to make consistent decisions, speak with one voice and maintain a shared objective: the success of the project and user buy-in.
AG: Did the division of responsibilities seem clear to you from the outset?
CM: This collaboration can sometimes seem a bit vague from the outside, but in our case, the roles were very clear from the start. Communication and user training naturally fell under Change Management, as did engaging sponsors, key managers and all stakeholders.
One aspect that was less obvious at the outset concerned leading the project team. Traditionally, this responsibility falls to the Project Manager.
However, we quickly realised that it made a lot of sense for Nadège to take on this role. As the project team is the primary ambassador for change, it was essential that they were committed, calm and confident. Thanks to her more neutral perspective and her expertise in people management, she was able to foster an extremely positive atmosphere. For my part, this allowed me to focus fully on the challenges of building and delivering the solution, whilst knowing that the team’s cohesion was in good hands.
AG: In what ways did the Change Manager’s involvement make the project run more smoothly?
CM: Being able to rely on a Change Manager allowed me to devote more energy to the development and deployment of the solution. I was able to focus on delivery commitments, risk management and resolving critical issues, safe in the knowledge that the other aspects of the project were under control.
Her presence also fostered better alignment between the BUILD activities and those related to adoption. Training requirements, communication needs and user preparation were incorporated into our planning at a very early stage. This enabled us to anticipate issues rather than react to them. Having this constant representation of the user’s voice within the team made discussions run more smoothly and ensured decisions were more relevant. I genuinely felt that the final solution would not only be technically sound, but also fully tailored to the needs on the ground.
AG: What advice would you give to a project manager who is being asked to work with a Change Manager for the first time?
CM: My first piece of advice would be to view the Change Manager as a genuine partner in the project, rather than simply someone who steps in at the end to prepare a few communications or training sessions.
Next, involve them right from the project’s initiation phase. Even if their role is still limited at this stage, their contribution is already invaluable. They help to identify stakeholders, understand organisational impacts and take user needs into account. Then involve them to an increasingly greater extent during the planning and execution phases. Incorporating the user’s perspective from the outset helps to embed this aspect throughout the project and prevents it from being addressed only as the go-live date approaches.
Finally, you must be prepared to listen to alternative viewpoints, such as the possibility that the organisation is not ready to adopt the solution at the pace set out in the schedule.
AG: To conclude, what lessons have you learnt from this collaboration?
CM: Having a Change Manager on the project team made a real difference. Firstly, at the launch stage: users were prepared, confident and eager to discover the new solution. Adoption took place much more naturally than on other comparable projects.
Furthermore, the Change Manager’s skills in communication and supporting teams helped to maintain a consistent and transparent message throughout the programme. We avoided both over and unrealistic promises, which strengthened the project team’s trust and credibility.
Finally, I would emphasise that change management does not end at go-live. Feedback, communication initiatives and celebrations following the go-live helped to recognise everyone’s contribution. One year on from this particularly successful launch, the teams have fond memories of this journey; they remain very close-knit and are ready to tackle new challenges together.
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept All”, you consent to the use of ALL the cookies. However, you may visit "Cookie Settings" to provide a controlled consent.
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
__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.
_GRECAPTCHA
5 months 27 days
This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks.
cookielawinfo-checkbox-advertisement
1 year
Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
cookielawinfo-checkbox-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-checkbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
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-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-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.
JSESSIONID
session
New Relic uses this cookie to store a session identifier so that New Relic can monitor session counts for an application.
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.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Cookie
Duration
Description
__cf_bm
30 minutes
This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
__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.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie
Duration
Description
__hstc
1 year 24 days
This is the main cookie set by Hubspot, 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).
_ga
2 years
The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_ga_*
1 year 1 month 4 days
Google Analytics sets this cookie to store and count page views.
_ga_JYCPSB48B8
2 years
This cookie is installed by Google Analytics.
_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.
CONSENT
16 years 2 months 25 days 10 hours
YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.
hubspotutk
1 year 24 days
This cookie is used by HubSpot to keep track of the visitors to the website. This cookie is passed to Hubspot on form submission and used when deduplicating contacts.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie
Duration
Description
IDE
1 year 24 days
Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile.
test_cookie
15 minutes
The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.
VISITOR_INFO1_LIVE
5 months 27 days
A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.
YSC
Session
YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.
yt-remote-connected-devices
never
YouTube sets this cookie to store the user's video preferences using embedded YouTube videos.
yt-remote-device-id
never
YouTube sets this cookie to store the user's video preferences using embedded YouTube videos.