High Level Background
MTS is going through a period of significant change. In 2024 we embarked on a company-wide Digital Transformation (“DX”) Programme, which will result in a complete change to our technology stack (removing our legacy ERP with D365 and various ISVs). The MTS IT and Portfolio Delivery teams will be at the centre of this DX programme and so now is a unique and exciting time to join our business and play a key role in the successful delivery of our programme objectives.
Specific background
Two years into the programme, we are about to embark on End-To-End Testing, before proceeding with User Acceptance Testing. There will be two separate Go Live points in the programme, the first scheduled for July, the second for October.
Our systems integrators have been producing delivery artefacts such as Functional Design Documents, Integration Design Documents, Report Design Documents and these are captured on Azure DevOps, which is being used as our collaboration tool both internally and externally. These documents form part of Knowledge Transfer to our own technical teams, together with the Teams recordings, albeit the latter mainly being used to enable functional testing.
Problem Statement
There is insufficient capacity with both systems integrators and internal teams to capture, structure, and produce clear, accurate, and maintainable technical documentation that explains how the new ERP solution works end‑to‑end — in a way that enables our internal IT teams to support, operate, and enhance the system after go‑live.
Role Overview
To address the capacity gap, we are looking for a Technical Author to turn fragmented solution knowledge into a coherent, navigable, long‑term knowledge base. Activities we expect to be done are:
- Translate complex technical information into structured documentation
- Consolidate knowledge from multiple SMEs, architects, and integrators
- Standardise documentation formats and terminology
- Fill gaps where SIs haven’t produced operationally useful artefacts
- Create a single source of truth for IT operations, support, and future change
Deliverables which need to be considered - although we are looking for guidance on Must Haves and prioritiation:
- End‑to‑end technical architecture overviews (platforms, components, environments, integrations, security layers)
- Solution component documentation (how each module, extension, or customisation works technically)