When Your Team Stops Seeing Each Other's Work, Everything Gets Harder
When Your Team Stops Seeing Each Other's Work, Everything Gets Harder — The Cyr Method
When Your Team Stops Seeing Each Other's Work, Everything Gets Harder
A few years ago I was brought in to work with a company that had three distinct teams: developers, operations, and front-facing staff. By every visible measure, the organization was functioning. Deadlines were being met. Clients were being served. Nobody was in open conflict.
But the energy in the building was quietly corrosive. Each team believed they were carrying more than their share. Each team had a theory about why the others had it easier. Nobody was saying it out loud. Everybody was feeling it.
The problem had a name, it just hadn't been identified yet. The teams couldn't see each other's work.
Why Growing Companies Develop Blind Spots
There's a well-documented pattern in social psychology that explains what was happening. Ask two people who share a household what percentage of the chores they each handle. Research by Michael Ross and Fiore Sicoly found that people reliably overestimate their own contributions, because those are the contributions they can actually see. Their combined estimates routinely exceed 100%.
The same dynamic plays out across departments in a growing company. Developers couldn't see what operations was absorbing daily. Operations had no window into what front-facing staff were managing from customers before it ever reached them. Front-facing staff made assumptions about how straightforward everyone else's job was.
Nobody was lying. Nobody was being difficult. They each had accurate information about their own work and almost none about anyone else's.
McKinsey research found that employees in siloed organizations can lose up to 20% of their workweek searching for information or support from other teams. Gallup's 2023 research found disengaged employees, with communication breakdown as a leading driver, cost the global economy $8.8 trillion in lost productivity annually. A 2024 Axios HQ report found senior employees lose as many as 63 working days per year to ineffective internal communication.
For HR managers and operations leaders in Halifax, those numbers have a local translation: the friction your teams are carrying right now has a dollar value, and it's higher than most people estimate.
The 20-Minute Fix That Changed the Building
The intervention wasn't a retreat. It wasn't a new project management platform. It was a single 20-minute Friday session.
Each team sent one person. That person had one job: show what your team accomplished this week, and explain why it mattered to the people in this building.
The first few weeks were a little awkward. People were unused to presenting their work to colleagues outside their own department. By the third or fourth session, something had clearly changed. Developers saw how their releases landed on operations' plate. Operations understood what the front-facing team was absorbing from customers before complaints ever reached them. Front-facing staff saw the complexity behind decisions that had previously felt arbitrary or indifferent.
People stopped filling the gaps with frustration because they finally had enough information to stop guessing.
Research published through the National Institutes of Health found that 95% of employees in siloed environments want to break those silos down. The barrier is rarely willingness. It's structure. People want to connect. They need a container that makes it easy.
What Visible Work Actually Does to a Team
When effort becomes visible, something happens that no onboarding document or values statement can manufacture: people start to respect each other's load.
When effort is invisible, the gap gets filled with interpretation. The developer thinks operations is slow. Operations assumes the sales team overpromises. The project manager decides the technical team is being difficult. None of these conclusions require bad intent. They're just what happens when people are working without enough information about the people beside them.
The Friday session made effort visible. Visible effort built respect. Respect changed the tone of every other conversation in the building.
That's the thing about communication as a productivity tool. It doesn't just reduce wasted time and duplicated effort, though it does both. It changes the quality of every interaction downstream.
The Skill Layer That Structure Alone Can't Replace
The Friday demo is a structure. It works because it's low-stakes, regular, and gives people a reason to look at each other's work. But structure only carries a team so far.
The moment visibility increases, new conversations open up. Some of them are easy. Others are ones people have been sitting on for months. A developer who now understands why a customer complaint matters still has to find a way to talk about it with the person who brought it to them. A project manager who sees that their definition of done is someone else's starting problem still has to navigate that conversation without losing the relationship.
Those conversations ask something of people. They require the ability to speak clearly under pressure, to listen past the first thing someone says, and to hold a position without shutting the other person out. These are learnable skills. Most team development programs skip them in favour of process and tools, and then wonder why the new process isn't working.
One structured approach worth exploring is the Designed Alliance, a practical agreement between two people or two teams that maps communication preferences, working styles, and expectations into something shared and explicit. It gives the skill layer the same kind of container the Friday demo gives visibility.
Where to Start This Week
If any of this is familiar, the starting point is simpler than most people expect.
Put a 20-minute Friday session on the calendar. One person per team. Show what was accomplished. Explain why it matters to the people in the room. Do it for a month and watch what it does to how people talk about each other the rest of the week.
The second layer, building the communication and negotiation skills to handle what surfaces once visibility improves, is what turns a better-feeling team into a more effective one.
If communication and team productivity training is something you are exploring for your Halifax or HRM team, the best first step is a 20-minute conversation.
Sources
Ross, M. & Sicoly, F. (1979). Egocentric biases in availability and attribution. Journal of Personality and Social Psychology. https://www.researchgate.net/publication/232540187_Egocentric_biases_in_availability_and_attribution
McKinsey Global Institute (2012). The Social Economy: Unlocking Value and Productivity Through Social Technologies. https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/the-social-economy
Axios HQ (2024). Internal Communications Statistics. https://www.axioshq.com/insights/internal-communications-statistics
Gallup (2023). State of the Global Workplace. https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx
National Institutes of Health / CDC (2024). Breaking Down Silos in the Workplace. https://pmc.ncbi.nlm.nih.gov/articles/PMC11419935/
