Talk to your frontline workers about what actually frustrates them every day. They'll tell you which information gaps and broken processes have become invisible. Design backwards from those pain points to find where AI can listen, suggest fixes, and automate the work.
Definitely. And I think at the same time, the effort is required on a per-function basis to understand the pain points. Because alluding to what Isaac mentioned about pain points and getting used to the pain points, the guys on the ground may be doing this for the last 10 years and they are so used to that and they take it as a norm. Mm-hmm. But I think the effort is required to sit down with them and understand what information is lacking, what information you are missing, what is troubling you at every level, at every function. And then from there, design your process step backwards and look at ways on how do we— right now, I think the AI models are now very smart enough to hear your pain points and to propose solutions to you. And at the same time propose methods and ways that all these steps can be automated.
