Start with the person and the purpose.
I want to understand who needs help, what they are trying to do and what is getting in the way. The answer might be a clearer conversation, a simpler process or a system. I do not assume it needs software.
How I work
Keep the purpose in view.
I move between people, process and systems. The tools change with the problem, but the questions I ask stay fairly simple.
Understand the work as it happens.
I look at where information comes from, how decisions are made and where responsibility changes hands. The awkward parts often tell us more than the ideal process does.
Make the next step clear.
I prefer clear ownership, useful records and an obvious next action. I try to reduce duplicate reporting and make it easier to see what needs attention.
Build something that can be checked.
I turn the direction into a working process or product, then check the result against the original purpose. I separate a design decision, a working component and a delivered outcome.
Learn from the result.
I am interested in whether the work helped. When something needs correcting, I look for the underlying cause and make the improvement wherever it applies.
Working with AI
More ways to build.
The same responsibility.
I use AI to help turn ideas into working software, explore options and check implementation. It gives me a practical way to build and learn.
My contribution is the direction: understanding the need, shaping the experience, making decisions and reviewing the result. I remain responsible for what I choose to use, what I accept and what I describe as delivered.
I look for evidence in the actual outcome. A confident answer or a passing component check still needs to be tested against the work it is meant to support.
A useful conversation starts somewhere