The reflex
A new need seems to call for another tool or another resource. You do not yet know whether what exists could answer it under decent conditions.
The builder’s reflex
Examine the resources you have and compare how well they fit against another solution, with the costs of use, of changing, and of upkeep.
Why
An existing tool, procedure or document may already cover part of the need. Examining them can avoid a purchase or duplicated work. That does not prove they are the cheaper option: an awkward adaptation, or a poor fit, can cost more than something different.
A community group wants to track equipment loans. A shared spreadsheet already exists for the inventory. Adding a loan log can work if people understand how to keep it and the access is right. If it mixes incompatible uses, another arrangement may be better, even with no software purchase.
Compare the future cost of the options rather than defending past spending. Training, maintenance, quality of service, access rights, dependencies and exit all count alongside the subscription. Search time counts too: cap the examination according to what is at stake, without assuming half an hour will settle every case.
An available resource is not automatically reusable. A contact file, a dataset, or a relationship with a partner may need an agreement and a use compatible with how it was collected or committed. Ask whoever is responsible what is possible. Backing a builder can mean easing that access, or helping compare the options, rather than imposing the tool you know.
Try this
On a precise need, write down the expected result and the constraints. Examine an existing resource with someone who knows it, then compare one realistic alternative, including a manual method.
Plan a small authorised trial and a limit on the effort. Judge whether the users can deliver the service expected, what would need rework, and who will maintain the solution.
Present the comparison to whoever can commit the means. If reuse is chosen, check after a suitable period of use that the hoped-for gain holds and that the extra dependency stays acceptable.
From where you sit
- Engineering: compare adaptation, upkeep and exit against adding a tool.
- Finance: separate money already spent from the future cost of each option.
- Operations: check the access, the uses, and the capacity to maintain it.
- Management: give time to the comparison before committing the means.
To discuss
Which existing resource deserves a trial, and what adaptation cost could justify something different?