How Do You Respond to Requests?

580773_dont_be_lateI am in a constant state of “meeting avoidance mode,” especially for those meeting requests that don’t directly relate to revenue generation. However, I just finished an interesting IM conversation with a friend of mine. It went something like this:

Him: “What are you doing on Friday afternoon? We want to bounce some ideas off of you before you go to Beer and Blog at 4pm.”

Me: “Sure, let’s meet for lunch”

After we disconnected from IM, I noticed that I never even bothered to ask him what he wanted to talk about, and I realized that this is a recurring pattern with this person. He has introduced me to so many great people and projects over the years that I’ve stopped asking what and why and started skipping right to when.

Maybe this is how some people handle requests for meetings, but it’s not my usual strategy. I get many requests for meetings, ranging from people wanting to discuss my consulting services, to people wanting to pick my brain about some online community topic, to those who want to talk to me about one of my many side projects. I get more requests than I can reasonably handle, as I have a chronic calendar problem of having too many events, meetups and meetings with random people, while not having enough time for paying client work. As a result, I normally try to avoid extra meetings, and I have a few meeting avoidance techniques that I use.

I combine efforts whenever I can. I try to get people to meet me at existing events that I am planning to attend anyway, and this works great for those first meetings where someone just wants to talk to me about a new project. If we are going to need a little more time, I schedule meetings with people for right before or after events like Beer and Blog to combine activities into blocks of time.

Diversion is another good strategy. I tend to grill people with requests for details about why they want to meet while secretly hoping that I can make an introduction to a better person for them to meet with about their topic. I avoid the meeting, and they still get to talk to someone about their project. It’s not that I don’t want to meet with interesting people, but I can only allocate a certain amount of time to meetings and business development activities without jeopardizing my client work.

Just say no. This one is the hardest, but sometimes you just need to tell someone that you can’t make the time to meet with them. If the topic isn’t interesting to you or if you can’t make the time, sometimes you just have to let people know that a meeting isn’t going to work. In this case, honesty really is the best policy. Let them know that you aren’t passionate about the topic or that you don’t work on the type of projects that they want to talk to you about. If you don’t have any time to spare and are on a tight timeline, you are better off letting them know rather than avoiding their email or phone calls, which can make you seem unresponsive or unprofessional. I don’t use the “just say no” option often enough.

I suspect that this is a common problem for many web workers, especially those of us who rely on consulting or other freelance work as our primary source of income. I love meeting with smart people where we can both share information and learn from each other, and it’s a great feeling to walk out of a good meeting with a potential new client. Spending time meeting with new people is an important step toward finding new clients, and it is a fantastic way to stay energized with new ideas.

How do you handle requests for meetings? How do you “just say no”?

Image by user Avolore


Comments have been disabled for this post