I lead corporate systems by asking whether a date, a table or a withdrawn document still means what its business owner intended after the technology has handled it.
I began as a developer who took satisfaction in making an application behave consistently. A successful import, a reproducible conversion or a completed background job offered a clear result. Business-systems leadership gradually made that definition of success less comfortable. The software could do exactly what its transformation specified while changing the meaning of a date, detaching a number from its label or continuing to offer a document its owner had withdrawn. I had to learn to ask what the user was entitled to infer after the system had finished.
A technically successful transformation is incomplete if it changes the business meaning that people are entitled to rely on.