Guiding Helping people to solve your questions asap. Sending your queries, data questions, to people and guarding the status of those questions. Giving a call when response isn’t yet received. Wanting to close data loops as soon as possible. Getting it finished.
Guiding starts with the right questions. Human-to-human questions in a data environment. Seeing people.
Listening When answers aren't returned as quickly as expected, contact to listen. As expected as defined by action guides reaction. When you give asap feedback consistently, people more and more asap respond. Whenever you call for responses not yet received, just tell why you call and listen. Tell why you call and then be quiet. Mouth shut. only listen with the intention to really understand what’s going on for the person you listen to. As soon as you understand what is going on, focus together on how to get the response asap from now. I.e. with extra help, from another person or in another way.
Decisive to close data loops Whatever response received, decide to approve data asap. No response is an answer too that helps you forward. Whatever data response or no response, choose. Choose your action. I.e. resolve the data question in line with modified data or try another way to get a response to your data question. Act. Don’t feed open data loops. The goal of data follow up is to close any incomplete, inconsistent, inaccurate or confusing data as soon as possible. And when it’s clear it’s not possible to get completed data, corrected data or to get a proper explanation, document this as is. It’s true for that piece of data. Cherishing such data loops, hoping there will come a solution eventually, distracts your focus and energy from getting data complete, consistent and logical ASAP. Close open data loops. Harsh, decisively if needed, to win strong data.