When I first joined this project, the organisation’s knowledge management was almost non-existent.
Teams used JIRA for task tracking and Confluence as a scattered notepad. There was a structured workflow, but no shared standards, and no single source of truth. Documentation was inconsistent, fragmented, and mostly tribal knowledge stored in people’s heads.
Onboarding a new supplier took nearly three months, because they had to rediscover processes, dependencies, and historical context through trial and error. Documentation was nobody’s responsibility — yet everyone suffered from its absence.
Identifying the Root Cause
It quickly became clear that the biggest problem wasn’t inefficiency — it was knowledge isolation.
The organisation lacked the ability to capture, share, and reuse knowledge systematically.
Before requesting formal approval or funding, I decided to prove that change was possible. I started building a “Ways of Working” intranet using SharePoint, capturing processes, rules, and best practices gathered directly from stakeholders.
Where no rules existed, I facilitated workshops and interviews to co-design them together. This collaborative approach was essential: people rarely resist what they helped to create.
Through these sessions, we aligned stakeholders with different agendas and built the foundations of what became our Master Documentary Process.
Building the Master Documentary Process
By the sixth month, we had a fully defined Master Documentary Process — a structured framework that governed how every project and product component was documented and updated.
We used OneNote to standardize the template for these master documents, ensuring every change or note was traceable, owned, and version-controlled.
To make this sustainable, I also pushed for audit and monitoring authority, ensuring the process didn’t die as a one-time initiative. That decision proved critical for embedding the change into the organisation’s operating rhythm.
From Manual Chaos to Automated Intelligence
Once the documentation model stabilized, we began full automation using the Microsoft Power Platform:
- Power Automate was configured to gather data directly from JIRA, process it, and push updates or new tickets automatically.
- Power Apps provided visual dashboard for the adminstration, forms, data input interface.
- SharePoint served as the knowledge backbone and intranet, hosting directories, processes, and standard operating procedures.
- OneNote became the universal master document template, linking seamlessly with project repositories.
- Power BI aggregated all project, financial, and estimation data into real-time performance and budget dashboards.
These tools were all new to the organisation, so we had to build capability from the ground up — through training sessions, coaching, and constant support.
When we started, I only had theoretical knowledge of Power Platform’s potential. To make this transformation credible, I made a deliberate decision to learn the platform hands-on, until I could tell solid engineering from vendor nonsense.
That technical literacy became a cornerstone of the project’s success.
KPIs and Measurement Framework
We established key metrics to track both delivery and process maturity:
| Category | KPI | Purpose / Measurement |
|---|---|---|
| Delivery | Sprint Velocity | Tasks delivered vs. committed |
| Lead / Cycle Time | Average ticket turnaround time | |
| Process | Documentation Coverage | 50% of projects following Master Doc template |
| Automation Rate | 15% of data flows automated via Power Automate | |
| People | Onboarding Duration | Time from hire to full contribution |
| Knowledge Retention | Ratio of resolved vs. repeated process inquiries | |
| Finance | Estimation Accuracy | Planned vs. actual delivery variance |
| Cost Efficiency | Cost per deliverable improvement trend | |
| Governance | Audit Compliance Rate | Projects passing documentation audit |
| Stakeholder Satisfaction | Alignment score post-workshop |
These metrics transformed our knowledge base from a passive archive into an active management tool — one that drives operational decisions and strategic insights.
Cultural Shift and Change Management
The most difficult part wasn’t automation — it was human alignment.
Each stakeholder came with their own habits, priorities, and level of influence. Negotiating a shared standard required persistence, diplomacy, and transparency.
But once people saw that the new process actually saved time and made their work easier, adoption accelerated.
Within months, documentation went from being a burden to being a shared source of pride — a visible sign of professionalism and maturity.
Outcomes and Lessons Learned
This transformation turned what was once a chaotic collection of tools into a cohesive, automated knowledge ecosystem.
We went from “barely documented” to 70% automated, from reactive reporting to real-time performance visibility.
This gave us the insight to manage fluctuation and the flexibility to scale operations and project effort up or down as needed.
The biggest lesson: automation succeeds only when human behavior and process design are solved first. Technology amplifies clarity — not confusion.
How is it going what should be the next phase:
From defining the project goals to creating the organisational process assets took about six months. Fine-tuning them, embedding them into the culture, and maintaining the ceremonies and quality-of-life improvements took another six. By the end of the first year, new opportunities began to open up.
The next phase will focus on:
- Expanding automation into resource forecasting and predictive analytics
- Integrating AI-assisted documentation and semantic search capabilities
- Establishing continuous improvement loops across all project and delivery processes