Thanks for the response. I'm with you. Sometimes, as techies, we get caught up in the "how we do it" to the detriment of "what we do". Whenever one of my team

Thanks for the response. I'm with you. Sometimes, as techies, we get caught up in the "how we do it" to the detriment of "what we do". Whenever one of my team members comes to me with a question, I always start with "what are we trying to do here?", in spite of knowing what they are working on. It helps me with the context switch from my own work, assures me that they understand the task, and it helps me to make sure we have a good reason for doing what we do. I always look for a non-technical answer first. Few (lucky?) people get to work on technology for the sake of technology.