How can I constructively address a manager who makes project decisions in informal chats with only a select few team members?
The Question
Our manager often finalizes important project updates during casual discussions with just a couple of colleagues. The rest of the team only discovers these changes when our tasks are returned with revisions. This makes it difficult to understand the reasoning behind decisions and prevents us from being proactive. I fully respect the manager's authority, but I want to improve our overall communication. What is the best way to discuss this issue with them without coming across as resentful?
Answer
It is completely understandable that this situation feels frustrating and disorienting. When important project decisions happen in informal side conversations, the rest of the team is left reacting instead of planning, and that can make people feel out of the loop even when everyone still respects the manager’s authority. Wanting clearer communication is not resentment—it is a practical desire for the team to work more effectively.
A constructive approach is to frame the conversation around shared outcomes rather than around who was included or excluded. Ask for a short one-on-one or a brief agenda item in a standing meeting, and open with appreciation for the manager’s decision-making role. Then describe the impact in neutral, process terms: decisions sometimes surface only when work is returned for revision, which makes it harder for the team to anticipate direction, reduce rework, and stay proactive. Emphasize that you are looking for a lightweight way for the full team to hear updates, not for a change in who decides.
Bring one or two concrete suggestions so the discussion is solution-focused. For example, you might propose a short written summary after informal decisions, a weekly five-minute decision recap in the team meeting, or a shared channel or document for confirmed project changes. Offer to help draft a simple template or rotate note-taking so the request does not sound like extra burden on the manager. Ask what format would feel easiest for them, which keeps the tone collaborative.
If you can, check with one trusted teammate first to confirm that the pattern is shared and that you are not the only person affected; a calm, collective interest in clarity often lands better than a solo complaint. In the conversation itself, stick to recent examples of process friction, avoid naming who was in the informal chats, and use “we” language about the team’s ability to execute. If the manager explains that speed is the priority, acknowledge that and ask for a minimum viable update path so speed and transparency can coexist. The goal is not to police casual conversation—it is to make sure decisions that affect deliverables are visible early enough for the whole team to act on them.