Short technical notes for people planning internal systems.
Illustrative image, AI-generated
SL-01
When a spreadsheet should become a system
When more than two people edit it, when it has hidden columns nobody dares delete, when errors are found by customers, or when it is emailed as an attachment. Below that line, a well-designed spreadsheet is often the right tool.
SL-02
Design for the exceptions first
The happy path is easy. Ask staff what happened last week that did not fit. Part deliveries, cancelled orders, approvals while someone is on leave. A system that cannot handle these will be bypassed within a month.
SL-03
Sync, webhook or nightly export?
Webhooks give near-instant updates but need monitoring. Scheduled synchronisation is simpler and tolerant of outages. Nightly exports are crude but robust. Choose by how stale the data can safely be.
SL-04
Getting staff to actually use the new tool
Involve them in the survey, release early to the people with the most pain, remove the old route once the new one works, and make the first week easy with someone on hand to help.
SL-05
Clean your data before you migrate it
Duplicate customers, free-text dates and blank mandatory fields will not fix themselves in a new system. Budget for a cleaning pass and decide who signs off the result.
SL-06
Every system needs an owner
Not IT. A person in the business who decides what the system should do and approves changes. Without one, systems drift into disuse.
Cookies and storage
This site uses no analytics or advertising cookies. One essential browser entry remembers this choice. Optional storage is not used before you accept, and is cleared if you reject.