I love meeting people, I love brainstorming ideas and revenue paths, I love hearing new perspectives, I love going out of my way to try to help people. When someone pings me for a meeting, I get excited and rearrange my schedule to get together. Maybe I can introduce them to a key contact, or help with some specific engineering challenge, or point out an unconsidered customer acquisition path. It's amazingly disappointing when I finally ask "so, how can I help you?" the answer is "join our engineering team."
If I could filter out all meetings that are secret recruiting initiatives, I'd be a happier person.
Don't take meeting when you have work to do. If someone is asking for a meeting so someone can be a witness to their existence, push it to the weekend and take only the most interesting.
If there's something concrete you can fill them in on, or be helped with, be concise, clear and direct about it. There's a lot about startups that you can, and should be learning on your own all the time.
Work meetings can be doubled up during events, lunch, or coffee. Keep it on topic and on time. Getting together after work is an option too, it doesn't interrupt working time.
I've heard people call this "office hours" too.
managers that want meetings simply because that is what they are supposed to do are not giving enough consideration to everyone's time. sometimes a meeting can simply be a managers way of giving an over worked team a break (hey let's watch this TED talk) but the pointlessness there, again, has its purpose.
So where's the middle ground? Usually, I find that my default stance is 'no'. I have work to do, and I have to guard my time. So I'll only take meetings that are interesting. But I think after reading this, I'll have to also add 'need genuine help' to the criteria.
I think something that Stammy could have added under "Workdays are Sacred" is how to say 'no'. What if it's a warm intro to someone that doesn't heed genuine help?