Make the work visible first
Who does what, in which order, with what input and with what definition of done? Those questions belong before the software decision.
Use tools to support behaviour
A system is valuable when it reduces friction and makes responsibility easier to see. It cannot create ownership by itself.
Measure what changed
A successful implementation should make the work more repeatable, less dependent on individuals or easier to improve.
Process first. Software second. Otherwise you may automate the confusion.