Last Wednesday we travelled to Bergen, Norway to host a breakfast seminar with our first reference customer case, Fjordkraft. The goal of the seminar was to advise new customers on getting started and share their experience over the last year.
- Norway’s second largest power provider
- 13 billion KwH yearly
- 800,000 Customers
- 5 billion NOK in revenue
Tor Håvard Wiig, was kind enough to summarize his experience and give insight into the best practices they have developed. When he started the pilot project a year ago, his objective was clear; Fjordkraft should improve their documentation by making it simpler, easier to share, more understandable and finally contribute value.
These objectives became defining requirements for evaluating Ardoq. As you see below in his slides from the seminar (in Norwegian), the tool had to follow Fjordkraft’s values.
- Make it easier
- Create value
- Be friendly
Understanding the scope and goal of any project is necessary for success. Tor Håvard looked to Fjordkraft’s core values to help guide the early expectations and set up the project requirements.
He explained that as with any project, you have to expect some level of investment in internal resources to achieve success. He continued to highlight the value of personally using the tool and getting his team involved in order to develop ownership early.
His ambitions were high. He had hoped to include not only the IT side of the organization, but the business as well. If documentation was to be valuable, it needed to capture the whole lifecycle of a project, from requirements to implementation and maintenance.
To roll out this ambitious plan he started small. This is something that we can recommend others to do as well. Compared to other examples of all-encompassing routine changes, their “per project” approach showed high rates of participation, acceptance and little pushback.
Tor Håvard explained that by identifying a business case or defining a proof of concept, he was able to include the right people, secure the time and budget necessary and get immediate value while still testing the solution. You can find a list of examples of business cases in the highlights of his presentation below.
After identifying a project or business case to start from, you should take into consideration a couple of other things in order to increase the chance of success.
First of all, book the time needed to really take on the project. Regardless of how easy a tool is, there is always a bit of time in getting familiar with the functionality and identifying the most likely places of getting quick value.
Secondly, involve the right people to help champion the project. By involving more people you are able to reduce the time needed to complete and evaluate the project, as well as increase the quality of the documentation created.
Finally, don’t be afraid to use the Ardoq team. Fjordkraft set out with an optimistic outlook when they first started with an early version of the solution. Tor Håvard saw the potential in automating the visualizations, democratizing the process of documentation, and the value of sharing documentation across business functions. That being said, he was quick to set up feature requests, report issues, and involve Ardoq in the training of new team members and consultants. His willingness to build a relationship with our team has helped us build a better solution, which in turn delivered on his early expectations.
In the end, they choose to continue to roll out Ardoq across the organization. What started as a project grew from 5 to 45 users and now include teams from both sides of the organization. Early feedback led to a two way integration with Jira as well as multiple features to help non-technical users to contribute to documentation.
Fjordkraft now actively uses Ardoq to:
- Capture requirements and users stories
- Document critical business processes
- Document their datawharehouse
- Document their system architecture
- Document their infrastructure
- Document all relationships and dependencies between everything listed above
But Tor Håvard isn’t satisfied, yet.
He is continuing the push internally to include Ardoq in documenting the entire organization from strategic vision down to the infrastructure. His drive has helped guide our development, and we are continuing to work closely with him and his team to improve Ardoq in both functionality and usability.
Part of the reason they choose to use Ardoq was not just cost and time saves, but that Ardoq also fit in with their core values.
Highlights from the slides
Expectations Fjordkraft had for Ardoq:
- Make it easier
- Document easier
- Understand documentation easier
- Share knowledge easier
Expecations Fjordkraft had for Ardoq
- Create Value
- Documentation integral in daily operations
- Proactive change management
- Reduce mistakes
- Show relationships and dependencies
- Make us better purchasers
- Cost savings
Getting started with Ardoq
- Make a simple business case or PoC
- BC: Internal Auding- do we have quality documentation
- BC: Onboarding consultants, reduce the time to contribute value
- BC: Proactive change management
- PoC: Ardoq is willing to help 🙂
Getting Started with Ardoq
- Necessary investments in internal resources is crucial
- Secure backing to allocate time to work with Ardoq in the start
- Make time in your calendar to use Ardoq
- Get others onboard early
- Ally yourself with postive colleagues
- Benefit from starting with a project
- Be persistant and keep focused until Ardoq becomes a part of the organization
- The system matched our values:
- Makes documentation easier
- Documentation is much more value adding
- Bonus: Supplier matches “Be Friendly”
Are you interested in championing your own case? Feel free to contact Ian to get more information on getting started. Or sign-up now for a free trial.
Subscribe to our newsletter
If you want to know more about Ardoq, subscribe to our newsletter: