Before you commission software, follow one order.
A practical way to find the real scope of an internal tool—before you pay someone to build it.
Read the fieldnoteNotes for the
work ahead.
Practical thinking on software, systems and the decisions around them. Written to help you ask better questions.
The backup you have never restored is still a question mark.
A completed backup job tells you less than you think. Here is how to turn a recovery assumption into a useful test.
Read the fieldnote“Managed hosting” needs a second page.
The questions that belong beside the monthly price: responsibility, recovery, maintenance and the exit route.
Read the fieldnoteBuy for the working day. Not the spec sheet.
A small-fleet purchasing checklist that goes beyond the processor badge and the lowest quotation.
Read the fieldnoteWhat happens when a payment callback arrives twice?
A worked example of the duplicate-message problem—and the questions to ask before connecting business systems.
Read the fieldnoteThe handover is part of the product.
The website is live. Now find out whether your business can actually operate it without the original developer.
Read the fieldnoteNo fieldnotes match that search.
Try a broader term, or browse all six.
Useful beats loud.
These fieldnotes use worked examples, checklists and primary references where needed. Examples are illustrative; we don’t dress them up as client case studies. Have a question or correction? Write to us.
A good place to start
Let’s make your next move a useful one.
Tell us what’s getting in the way.
We’ll work out the next step together.