How to get internal tools right
The advice here is unglamorous, which is probably why it gets skipped. The short answer to internal tools is that it is mostly a sequence of small decisions, not one big one.
The projects that go badly are rarely the ones with the hardest technical problems. The version that survives contact with a real deadline is the simple one.
What is actually at stake
The spreadsheet everyone fears is a specification. That sounds obvious written down. It is still the thing most often skipped. Budget a little time for it every quarter and it never becomes a project of its own.
The steps
- Establish what you have today before changing anything
- Internal tools rarely need to be beautiful, but they must be reliable
- Time saved compounds every single week
- Write down the decision so the next person does not re-litigate it
Time saved compounds every single week. Getting it slightly wrong is survivable. Ignoring it entirely is not. Doing this properly once is usually cheaper than doing it approximately three times.
What to do next
The short version
Strategy work is mostly deciding what not to do, and writing it down so it stays decided. Three things worth confirming about internal tools before you move on:
- Someone can say what the current setup is without going to look
- Internal tools rarely need to be beautiful, but they must be reliable — and you know whether that is true here
- There is a way to tell whether the last change to this helped
Worth checking on your own setup before it becomes someone else's problem to fix.