Good writing. When we say "Let me know how I can help", we are asking the other person to <i>do work</i> because then they have to think about what/how they need help with. Most of the times, people are lazy and you might be surprised but the fact is that they don't want to do work even for their own requirements. Instead, They want to hear solutions.<p>This even applies to environments at very big companies. At my current client (Fortune 100), we work with distributed global teams and we have those <i>dreaded meetings</i> all the time. In those meetings, we in IT will ask business for requirements which makes sense. However for projects that need quick turnarounds with tight deadlines, we sometimes don't have the luxury of getting detailed requirements. In fact, the more we discuss requirements, the more we are stuck. Asking "how I can help" usually gets a response of "Sure. what are you proposing". You cannot keep going back and forth with "depends on what you want". The reason is that even though we all would like the best solution with all features, it just does not work that way in real world because time/resource/budget is limited. Instead of asking "how can we help", we analyze the current process and then propose multiple options. So in essence, we say "Here is how we can help". It then makes it really easy for business to say "Yea we like Option 1 and if that's the best you have for now, let's go with it". Boom, you just got a decision maker to agree and you are on your way. You are also that guy who got shit done.<p>I used to think that we get big bucks as consultants because we are awesome devs/designers/PMs/BAs whatever. But after a decade in the industry, I got wiser. You are valued as a consultant because you get shit done by taking the initiative to propose solutions to clients. Then you deliver it to them. No one gives a shit about anything else. Really.