Questions before solutions
Three questions that keep consulting work anchored to the real problem.
Before proposing a fix, I want three answers. What keeps happening that should not? Who pays the cost when it happens? What would become easier if the problem went away?
These questions are basic on purpose. They keep the work tied to observable pain instead of preferences, fashion, or the loudest request in the room.
Good software decisions usually follow from that clarity. The right answer might be a small app, a better report, a deleted step, or no code at all.