Good documentation makes sure your organisation keeps understanding and managing its own data solution, even when the developer leaves. But documentation can also slow development down if it is used the wrong way.
From practice
In 1996, during a graduation project at Philips, I was asked to stop documenting according to the SDM method and simply start building. Even then it was clear that involving the customer as early as possible matters, for example with a prototype. Today we call that Agile.
Agile and proof of concept
- Agile: developing in short sprints, built on simplicity, communication, customer feedback and collaboration.
- Proof of concept (POC): an early version to test whether the wishes and requirements are feasible, from sketch or wireframe to working prototype.
What we document
- System architecture: the design and how the parts fit together.
- Data model and data dictionary: which data exists and what it means.
- Data flows: from source to report.
- Operations manual: how the solution is loaded, monitored and changed.
Just enough to manage it yourself, without slowing development down. No documentation at all? Then it starts with reverse engineering.

Specialisms
Read how we work, topic by topic.
Impact analysis for model changes New
Know what breaks in your historical data before you migrate.
Reverse engineering
Finding out how an existing system works, even when nobody remembers.
Migration
To a new platform or the cloud, without losing your history.
Rebuild and new build
A new data warehouse, or an existing one rebuilt, better.
Performance and efficiency
Faster loads and reports, lower costs.
Data modelling
The foundation: a model that grows with your organisation.
Visualisation
Dashboards that answer the question you are really asking.
Documentation
So your organisation can keep understanding and managing it on its own.
Get more out of your data?
Get in touch for a no-obligation introduction.







