In the energy market our client acts simultaneously as developer and project manager for numerous large‑scale projects that range from integrated planning to high technical complexity. The existing structure is shaped by a matrix organization, where communication across multiple departments and external service providers requires considerable effort. Processes are still in the build‑and‑standardisation phase: guidelines are only now being drafted and uniform procedures are missing. A recent SharePoint migration delivered the technical platform but not the accompanying process definitions, so the new document repositories are hardly used. The DMS to be implemented is sourced externally, must be operated by an external vendor, and the contractual framework lacks service‑level agreements (SLAs), making planned further development difficult. Against this backdrop the central question arose: How can a DMS be introduced in a way that creates real value for the company?
An Initial Gap Analysis
The core problem lies in the mismatch between technology and process. A powerful DMS is available but remains unused because users do not know clear procedures and the permission structure is not sufficiently aligned with collaboration involving external service providers. Without standardized communication paths and defined user stories for vendor tasks, misunderstandings, delays, and uncontrolled document versions emerge. The absence of SLAs in the vendor contract raises the risk that necessary adjustments are hard to schedule and change requests remain unaddressed for long periods. Historically grown SharePoint and exchange platforms exacerbate the issue because they no longer meet today’s demands for transparency, user‑friendliness and security.
From “What” to “How”
The approach combines a technical rollout of the DMS with targeted process optimisation. First, lessons learned from already completed large projects are systematically analysed and transferred into a new process framework. This includes the analysis and documentation of all existing and newly established processes, tools and standards. Special emphasis is placed on the rigorous formulation of user stories that clearly define the expectations for external service providers and the information needed to fulfil them.
In the next step the requirements for the external DMS are precisely defined and the necessary interfaces to existing systems (especially SharePoint) are designed. SharePoint is integrated not as a pure storage system but as an information hub: for each project a landing page is created that aggregates central metadata, current status reports and links to the DMS. The permission strategy is redesigned so that external providers receive targeted access to project‑specific folders while internal users retain comprehensive visibility.
To secure user acceptance, the DMS user experience is aligned with the defined processes. Intuitive navigation, context‑aware help and automated workflows make the system understandable even for less tech‑savvy users. At the same time a training programme is built that blends face‑to‑face sessions with on‑demand videos, ensuring that every role, from project manager to document controller, acquires the necessary competencies.
Finally, a governance model is established to take responsibility for the ongoing evolution and steering of the platform. The model defines clear roles for vendor management, specifies how DMS changes are tracked and prioritised, and incorporates monitoring that measures usage, performance and adherence to the defined processes. This creates a continuous improvement loop that involves both internal teams and external partners.
Conclusion
Through a structured DMS rollout the company becomes capable of leveraging the knowledge accumulated from completed projects effectively. The defined and documented processes and guidelines are made transparently available to all employees via SharePoint, breaking down information silos and strengthening the organization’s self‑efficacy. Clear role and task allocations, supported by standardized communication formats and user stories, reduce misunderstandings with external service providers and enable purpose‑driven collaboration.
The refined permission strategy ensures that data remain secure while still being quickly accessible. This decisive factor in an industry where time pressure and regulatory requirements are ever‑present. An improved user experience lowers training effort and raises acceptance, embedding the DMS not only technically but also culturally.
At the end of the project, process flows operate markedly more efficiently: documents are found faster, approvals are automated and changes are tracked transparently. All decisions, minutes and technical data are consistently documented, which greatly simplifies audits, internal reviews and future project planning. Consequently, the client benefits from a stable, scalable platform that meets current project needs and serves as a foundation for further digital‑transformation steps.
Overall, the approach demonstrates that a DMS delivers genuine value only when technical implementation and process design work hand‑in‑hand. Through focused change management, clear governance and the incorporation of experiences from previous large projects, the DMS becomes a strategic enabler: it creates transparency, boosts efficiency and lays the groundwork for sustainable growth in the energy sector.
In our whitepaper on IT architecture we outline how central, strategic applications such as a DMS can be embedded into the overall architecture to generate lasting positive impact.
Image source: Nana Smirnova / Unsplash
We are IT partners
Our motto: Establish IT in everyday business as a solution, not as a source of problems.
