What's the difference between transparency and visibility at work?

Transparency means information isn't hidden—anyone can access it. Visibility means the right people can actually see the work that matters from where they sit. You can be completely transparent and barely visible: a public channel no one reads is transparent but invisible. Visibility is transparency plus arrangement—deciding what surfaces, where, and for whom. That arrangement is the sightline.

Why can't I see what my remote team is working on?

Usually it isn't secrecy; it's the sightline problem. The work is scattered across tools, channels, and docs, so it's technically available but not positioned where you'd naturally look. The fix isn't demanding more status updates—it's arranging where important work surfaces so seeing it doesn't require a search.

What are the downsides of radical transparency?

Radical transparency can create information overload, performance anxiety, and "transparency theater"—where everything is public but nothing is actually seen. Openness makes information available; it doesn't guarantee the right people notice the things that matter. Used alone, it can bury the signal under more hay rather than surfacing it.

How do you reduce information overload on remote teams?

Stop broadcasting and start blocking. Decide who needs to see each piece of work to act, and put it where their attention already is. Consolidate where work lives, surface decisions and blockers in context, and let the work be legible in the place it happens—so people aren't paying a constant context-switching tax just to stay informed.

How do you keep a remote team aligned without micromanaging?

Design sightlines instead of surveillance. Make work visible by arranging where it shows up—shared canvases, contextual summaries, clear ownership—so you can see progress without tracking keystrokes or demanding constant reports. The goal is a stage everyone can see, not a camera pointed at everyone. ---

The Sightline Problem: Why Transparency Isn't Visibility

In 1999, two psychologists asked people to watch a short video and count how many times a team passed a basketball. Halfway through, a person in a gorilla suit strolled into the middle of the frame, thumped their chest, and walked off. In most groups, half the viewers never saw it. They were staring right at it.

That experiment—now famous as the "invisible gorilla"—is the best description of modern remote work I know. Your team isn't short on information. It's drowning in it. And the most important work is the gorilla: in plain view, and completely missed. I call this the sightline problem, and it's quietly breaking distributed teams that believe they already solved visibility by being "transparent."

One quick note before we go further: this isn't about theater-seat sightlines, stadium design, or the sustainability think tank with the same name. The term is borrowed from stagecraft—and once you see how a director thinks about who can see what, you can't unsee it in your own team. Here's why transparency and visibility are not the same thing, and how to design one instead of mistaking it for the other.

Transparency Isn't Visibility

Most leaders treat these two words as synonyms. They aren't.

Transparency means nothing is hidden. The document exists, the channel is public, the decision is logged somewhere anyone could find. Visibility means the right people can actually see the work that matters—from where they sit. The first is about availability. The second is about arrangement.

You can have total transparency and almost zero visibility at the same time. A public Slack channel that no one has joined is transparent and invisible. A wiki with 4,000 pages and no map is transparent and invisible. A "single source of truth" that is genuinely true and genuinely unread is transparent and invisible. Nothing is hidden. Nothing is seen.

The data backs this up in a way that should haunt anyone proud of their open culture. Atlassian's State of Teams 2025 found that leaders and teams "waste 25% of their time just searching for answers." Their summary of the era is brutal: "Teams have more information than ever, but they've never been less informed." Availability went up. Visibility went down. That gap is the sightline problem.

What Theater Gets Right About Sightlines

In a theater, a sightline is the unobstructed path from a seat to the action on stage. Architects design entire buildings around them. Seats with a blocked view are explicitly classed as "restricted view" and, in some venues, not sold at all. Nobody pretends a bad seat is a good one just because the stage is technically in the same room.

But the deeper craft isn't the architecture—it's blocking, the director's deliberate choreography of where actors stand and move. As one stagecraft guide puts it, "the audience is free to look wherever they want," so the director's job is "to help guide the audience and focus their attention." Good blocking keeps the important action on the angles every seat can see—it protects the sightlines.

Notice what a director does *not* do. They don't make the play more transparent by handing every audience member the full script and a flashlight. They arrange the stage so the right thing is visible from every seat. That single move—designing the view instead of dumping the material—is exactly what remote teams skip. We publish the script and turn up the house lights, then wonder why nobody's watching the scene that matters.

More Information, Less Informed

If transparency alone worked, the most documented teams would be the most aligned. They're often the most lost.

Look at where the time actually goes. Asana's research found knowledge workers spend 58% of their time on "work about work"—communicating about work, searching for information, switching between apps, chasing status—and only 33% on the skilled work they were hired to do. That coordination tax has a name and a real cost, and it's its own coordination crisis worth understanding on its own terms.

Now add the volume. Microsoft's 2025 workplace research clocked the average employee at 153 Teams messages every weekday, on top of 117 emails most people skim in under a minute. The channels keep multiplying—more apps, more places a piece of work could be, more "did you see my message?" Asana found that this app sprawl leaves more than a quarter of workers *more* likely than the year before to miss actions and updates entirely.

Here's the part leaders miss: none of that is a transparency failure. Every one of those 153 messages was visible. The blocker that sank the launch was posted. The decision that reversed last week's decision was logged. It was all in view—and functionally invisible. The work was the gorilla. That's not a transparency failure; it's a sightline failure. This is also why simply switching to async communication doesn't fix it: async makes everything available across time zones and assumes someone will look. Availability without sightlines just spreads the gorilla over more screens.

Radical Transparency's Hidden Condition

I want to be fair to the open-by-default movement, because it got something profoundly right.

Radical transparency tore down walls that deserved to fall. GitLab runs a 2,000-plus-page public handbook that lets a new hire in any time zone onboard without asking permission. Bridgewater built a famous culture around it. Buffer published its salaries. Default-to-open kills politics, speeds onboarding, and lets good ideas travel without a gatekeeper. I am not arguing for secrecy.

But there's a condition hiding inside the gospel of "just write it down," and almost no one says it out loud: transparency makes information available; it does nothing to make it seen. A single source of truth that no one is positioned to look at isn't a source of truth. It's a warehouse. And when you respond to confusion by publishing *more*, you can make the sightline problem worse—you're adding hay to a haystack people already can't search, not signposts to it.

There's a name for what's left when the openness is real but the seeing is fake: transparency theater. Everyone can technically access everything, so everyone *feels* informed—right up until the gorilla walks across the stage and the post-mortem reveals the warning was in a channel for three weeks. The openness was genuine. The visibility was a performance. That is the sightline problem wearing the costume of a healthy culture.

How to Design Sightlines, Not Dump Information

The market keeps selling two answers to the sightline problem, and both are wrong. One camp says *track more*—surveillance dashboards, activity scores, keystroke logs. The other says *publish more*—another wiki, another all-hands, another status template. Surveillance treats visibility as something you extract. Transparency treats it as something you upload. Theater treats it as something you *arrange.*

Designing sightlines is a craft, not a setting you switch on. So block the scene. Here's what that looks like in practice:

Block it, don't broadcast it. Before you post, ask who specifically needs to see this to act—and put it where their attention already points, not in a channel they have to remember to check. Broadcasting is hoping. Blocking is deciding.
Give the important work center stage. Decisions, blockers, and changes should surface where the team already looks, in context, not get buried in a feed where the urgent and the trivial scroll at the same speed.
Make the work show itself. The strongest visibility isn't a status update someone has to write and someone else has to find. It's the work being legible in the place it actually happens—so seeing it costs no one a search.

This is where the medium does the heavy lifting. A live conversation on a shared canvas—where the work sits in the center of the frame and a contextual AI surfaces the right history to the right person at the moment they need it—creates a sightline by design instead of by luck. That's the bet behind Coommit: put the work on stage in the room the team is already in, rather than scattering it across a dozen tools and a unified workspace people still have to assemble in their heads. It's the difference between a canvas everyone is looking at and a grid of faces talking past the work.

You don't need a new tool to start, though. You need a new question.

Conclusion

Transparency was the right instinct for the last decade of distributed work. It pulled down the walls that hid information and gave everyone a key to the building. But handing out keys is not the same as arranging the seats. The sightline problem is what's left over: a team with nothing hidden and almost nothing seen.

The leaders who win the next phase of remote work won't be the ones who publish the most. They'll be the ones who think like a director—deciding what belongs center stage, and arranging the sightlines so every seat can see it. So this week, take your single most important piece of work and ask the better question. Not "is it written down?" That's transparency, and you've already won it. Ask: "Who can actually see it from where they sit?" That's visibility—and it's the only kind that moves work forward.