{"id":27611,"date":"2024-04-24T14:44:39","date_gmt":"2024-04-24T12:44:39","guid":{"rendered":"https:\/\/www.xalt.de\/?page_id=27611"},"modified":"2025-09-03T11:49:09","modified_gmt":"2025-09-03T09:49:09","slug":"case-study-changement-management","status":"publish","type":"page","link":"https:\/\/www.xalt.de\/en\/case-study-changement-management\/","title":{"rendered":"Case Study - Change Management"},"content":{"rendered":"
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\t
<\/div>\n\t\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Case study: Change management for developer self-service and knowledge database with Confluence and Jira Service Management<\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

The story<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Our client, an industry leader, wanted to streamline its development processes by introducing platform engineering for its development teams. The company recognized the potential of automation to increase efficiency and productivity and introduced a developer self-service portal.<\/p>

This initiative aimed to automate various developer processes, such as the creation of AWS organization accounts and Microsoft Co-Pilot accounts (ChatGPT\/OpenAI for internal use), reducing the time required from several days to just one hour.<\/p>

However, the introduction of new technologies is often associated with challenges, especially in terms of user acceptance and effective use by the teams.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

The challenge<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The biggest challenge for the company was to ensure that employees could seamlessly transition to using Developer Self-Service. Despite the clear benefits of the new system, there was considerable resistance and discomfort towards change among the workforce.<\/p>

Our clients' employees were used to traditional processes and were reluctant to adopt new technologies because they did not understand them and feared a steep learning curve. This resistance threatened to undermine the potential efficiency gains from the automated system.<\/p>

The company also recognized the need for a central knowledge base where developers could easily access information and resources related to the new services. The lack of such a platform led to confusion, inefficiency and a fragmented approach to problem solving and information sharing within the development team.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

The procedure<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

To overcome these challenges, our client needed a change management strategy supported by Confluence and Jira Service Management as key tools. The strategy needed to enable faster user adoption and foster collaboration between the company's teams.<\/p>

\"\"<\/a><\/p>

Confluence<\/b> was used to create a central knowledge base. This platform contained all the necessary documentation, guides and resources related to Developer Self-Service. It included step-by-step instructions for creating AWS Organization and Microsoft Co-Pilot accounts, FAQs and troubleshooting tips. Confluence enabled the development team to easily access up-to-date information, share knowledge and collaborate more effectively.
How was this implemented with Confluence?<\/p>