Informed ≠ Included
- Kimberly Horvath

- Jul 15
- 2 min read

⛔ A new operating model was developed with limited cross-functional input.
⛔ The implementation plan was distributed with a lack of clarity and fixed milestones.
⛔ Execution is now underway, and teams are asked to adapt, but were not asked to contribute.
You were "looped in" after the loop closed. The real opportunity to shape the work? Already gone. Super frustrating, right?
When this happens, no. one. wins.
𝗪𝗛𝗬 𝗱𝗼𝗲𝘀 𝘁𝗵𝗶𝘀 𝗸𝗲𝗲𝗽 𝗵𝗮𝗽𝗽𝗲𝗻𝗶𝗻𝗴?
Closed-door decision cycles.
Decisions are made in rooms too far removed from day-to-day realities. By the time they reach you, they’re packaged as a plan and not as an opportunity to shape the direction.
Speed over input.
There’s a belief that involving too many voices will slow things down. So only a handful of people weigh in… until it’s too late to fix what’s missing.
𝗪𝗵𝗮𝘁 𝗰𝗮𝗻 𝘆𝗼𝘂 𝗱𝗼 𝘄𝗵𝗲𝗻 𝘆𝗼𝘂’𝗿𝗲 𝗻𝗼𝘁 𝗮𝘁 𝘁𝗵𝗲 𝘁𝗮𝗯𝗹𝗲?
Make feedback visible, not private.
Don't just vent in DMs. When a decision lacks context or creates friction, raise it openly and constructively with your team or project leads. Document where misalignment started.
Build alliances across roles.
Find people in other teams feeling the same pain. When feedback is shared across functions, it shows a pattern, not a personal complaint.
Map the impact.
Before pushing back, show the why. "Here’s where the handoff broke and how it affects the team or client" is more actionable than "We weren’t included." Back it with examples, not emotion.
Shift from blame to better process.
Avoid finger-pointing and shift the focus toward shared ownership and solution-oriented dialogue.
Ask questions that invite improvement, not defensiveness:
"Is there a way we can surface frontline input earlier in the planning phase?"
"What would it look like if we had a shared discovery doc before projects kick off?"
⭐ To any Project Manager or middle manager:
You have more influence than you think.
Your role is the bridge. If you see teams getting sidelined or decisions being made in silos, advocate for inclusive planning, not just inefficient rollouts. Raise flags, start conversations, and create templates for shared context. Even small process nudges make a difference.



