Which of our own tools are worth keeping

Which of our own tools are worth keeping

Discretion comes first, so every case is illustrative. The method is real.

Where it started

A pharma device department had grown a collection of spreadsheets, scripts and macros over ten years: tolerance calculations, test data processing, requirement tracing. Engineers had built them to get the work done. Several were used in design verification. Nobody owned them, and some ran on one person’s laptop.

The strategic question

Which tools create enough value to be made professional, owned, validated where needed and strengthened with AI? Which should be merged, and which retired?

What we found

An inventory of 23 tools, each scored on hours saved per year, number of users, what happens if it is wrong, and the effort to make it professional. Six carried most of the value. Four were used in the design history file without any validation, which was the real risk. Nine duplicated each other or a system the company already paid for.

23 TOOLS, SCOREDHigh impact, low valueHigh impact, high valueLow impact, low valueLow impact, high valueHours saved per year →Impact of an error →4 riskyUsed in the design historyfile, never validated6 worth making professionalMost of the value13 othersIncl. 9 duplicates tomerge or retire

Three directions

01

MVP

Fix the four risky tools: an owner, documentation and validation where the DHF depends on them

Time
2–3 months
Cost
€60–100k
Risk
Low
02CHOSEN

Golden opportunity

MVP, plus the six high-value tools rebuilt as a shared toolbox, with AI assistants on the manual steps. Nine tools retired

Time
6–9 months
Cost
€250–400k
Risk
Medium. Tool validation
03

Full ambition

Everything rebuilt as one integrated engineering platform

Time
18–24 months
Cost
€1–1.5M
Risk
High. A large system before the need is proven

What was chosen

Golden opportunity. The four risky tools were fixed first, and the nine retirements were announced with a reason for each.

What it gave the client

About 3,000 engineering hours a year, one owner per tool, and a design history file that no longer depended on a laptop.