Products
System of Record
A system of record instead of spreadsheets
system-of-record.txtas is → to be
Today the same fact lives in two spreadsheets and an email thread, and somebody is asked which version is current. Afterwards there is one record, every change is written down, and the history is there to read.Illustrative hours, not a measurement.
When the same information lives in three places, one of them is wrong and nobody knows which. System of Record is the one place that holds what is currently true — with who may change it, and a history of who did. The tools you already use are connected to it before anything is replaced.
One place holds what is true, with a history of who changed what, instead of a spreadsheet whose current version is a question.
How it runs
- one place that holds what is currently true
- who may see and change what, written down and enforced
- a history of what changed, when, and who changed it
- what you already use connected before anything is replaced
Where it does not fit
- genuinely one-off analysis, which belongs in a spreadsheet
- processes about to change for other reasons
Size: a large piece of work — an estimate from the pattern, not from your business.
What we would want to know before committing
- which processes currently live in spreadsheets or inboxes
- who needs which access
- what has to be traceable, and for how long
- which existing tools must stay
- map the current process with the people who run it
- confirm which existing subscriptions can be retired, if any
- establish the migration path for existing data