Background - I'm the technical lead on a software project. I came up from software engineering and I am responsible for technical interaction with the customer, other vendors, the software product team, and I still get to write some code. I work under a project manager.
Problem/Challenge - Frequently there will be seemingly simple questions from the customer. I'll consult with my experts, and let my PM know this came up. Frequently its a relatively simple answer or action to address my customers question. Despite this, my PM very frequently responds "I can email $CUSTOMER_PM and $CUSTOMER_TECH_GUY and 3 other people and have a meeting". I don't feel a meeting is necessary, its something that can be handled offline, is not urgent, and in fact is better expressed in writing than a phone meeting.
Meetings can be good, but I feel that they are often called when they aren't needed. It wastes my time and creates extra work for more people.
- Is there something I'm missing, from a general project management perspective, where calling a meeting is a default action? Is there a reason for this?
- How can I politely, clearly, and properly explain that this doesn't really warrant a meeting? If the action is in scope I can simply iron it out man to man with my technical counterparts.