Software & IT consultancy · London EC2Write to us
Data ConsultancyConsidered software · clear advice

Overview › Notes

Notes for the decision makers.

Short, practical pieces you can use with or without us.

How to write a data dictionary people will use

Create one table with five columns: term, definition in plain English, source system or file, owner who settles disputes, and last reviewed. Start with the twenty terms that appear in board or management reports. Resist adding technical detail; that belongs elsewhere. Review it quarterly, and treat any argument about a number as a prompt to update it.

Twelve questions to ask of any software proposal

  1. Who will own the source code and the accounts?
  2. What exactly is excluded?
  3. Which assumptions, if wrong, would change the price?
  4. How are changes requested and priced?
  5. What does support cost after launch, and what hours does it cover?
  6. How is data exported if we leave?
  7. Who will actually do the work?
  8. How will we see progress?
  9. How is the software tested?
  10. What happens to our data during development?
  11. Which third-party services are involved, and who pays for them?
  12. What documentation is included at handover?

Migrating from a spreadsheet without losing trust

Freeze the structure, document the formulas, import historical data with a row-by-row reconciliation, then run old and new in parallel for at least one full reporting cycle. Switch only when differences are explained. Keep a read-only copy of the original for reference.

The day a new system goes live is not the day trust arrives. Trust arrives the first time its figure matches the one people expected.

Dashboards that lead to decisions

For each figure, write down who looks at it, how often, and what they do if it moves. If nobody would act, remove it. Show comparison points (last period, target) beside each figure, and put definitions one click away.

Access hygiene for shared files

List the shared folders and spreadsheets that hold personal or sensitive information. For each, record who has access and why. Remove leavers promptly, prefer group permissions over individual ones, and avoid sending copies by email. These are practical habits, not legal advice; your data protection lead should set policy.

A few terms

  • Authoritative source: the one system whose value wins when two disagree.
  • Reconciliation: a systematic comparison showing that two sets of figures agree, or why they differ.
  • Validation: checks applied when information is entered.
  • Integration: an automated exchange of information between systems.