Transparency

In an organization where information collects at the top, decisions don't get made anywhere else. Deciding requires knowing what's at stake, and without that material every judgment call gets sent upward. Delegation becomes impossible even when someone wants to delegate. The bottleneck isn't unwillingness — it's that the material the decision needs lives somewhere the decider can't reach.

The gap doesn't stay empty either. People fill what they don't know with guesses. Two months without a job posting and word goes around that money must be tight, and since there's no way to check, the story grows. When a decision to cut a feature arrives as an announcement with no reasoning, the person who built it reads it as a verdict on their work. The actual judgment was that the market was too narrow, and one line would have settled it.

Transparency is the commitment to not leave those gaps. What was decided and why gets shared in the same place, and quarters with bad numbers get shared at the same speed as good ones. It's a decision to stop holding information like authority, which makes it something you build rather than something that appears.

Default to open, attach reasoning to decisions, deliver bad news at the same speed as good, and decide in advance what stays closed.

1. Make open the default. Create documents and meeting notes open, and name only the things that get closed. Do it the other way around and closed documents keep accumulating, until the only person who knows where anything is, months later, is whoever wrote it. Naming the closed set takes minutes — personnel files, unfinished offers, contract terms — and it costs far less than auditing hundreds of closed documents later.
2. Attach reasoning to decisions. Record only the outcome and the next person facing a similar call reruns the entire discussion from the start. One line saying the team judged that the reasons to choose this product over a competitor had narrowed is what gets read first when the same proposal comes back next quarter.
3. Deliver bad news through the same channel at the same speed. A venue that only carries good news loses its audience's belief within two or three sessions. A company that says plainly it hit 62 percent of target gets taken at its word the next quarter when the news is good. The asymmetry is what people watch for, and a team works out inside two quarters whether bad results get the same airtime as good ones.
4. Decide and publish what stays closed. Individual pay, personnel moves that aren't final, anything bound by a customer contract: opening these increases guessing rather than reducing it. Writing down what isn't shared and why turns the boundary itself into a reason to trust the rest.
5. Make it findable. Being open and being reached are different things. A dashboard nobody can locate is functionally closed, so the places to look belong in one index, and important changes get pushed rather than waiting to be found. One index page that is actually maintained beats four that are almost right.
6. Build the conditions for speaking. Without psychological safety — the sense that raising a mistake or a disagreement carries no penalty — opening every file produces no questions. Miss that and you get information that is public and unused.

The recurring venue is the all-hands, where the whole company hears what the quarter will include and what didn't happen last quarter, in the same words. If six or seven people out of forty-five sit in the planning meeting, this is how everyone else hears what the company decided.

It also shows in how metrics get handled. A company that puts revenue, user counts and progress against target on a screen anyone can open has different meetings than one that packages the same numbers monthly for executives. In the first, no time goes to establishing what the numbers are, and the conversation starts at why. It also changes who spots a problem: with the screen open, a support lead can see conversion sliding a week before the monthly package would have said anything.

For organizations trying to grant autonomy — how much people decide their own approach — it's a precondition. Hand the method to someone who doesn't know what's at stake and whoever handed it over can't predict the outcome either.

Hiring and compensation use a bounded version. Publishing salary bands per role narrows unexplained gaps between people doing the same work, while opening individual amounts without any bands in place just exposes differences nobody can account for.

"I see the decision, but the document doesn't say why."

An outcome alone can't be reused for the next judgment.

"This isn't final yet, and publishing it now just fuels guessing. We'll announce it in one place once it is."

What gets opened and when has to be decided together.

"The numbers are open and nobody looks at them, because nobody knows where they are."

Being public and being reached are separate problems.

At Pagedeck, Grace puts target and actual side by side at the quarterly all-hands. Last quarter that meant showing a paid conversion target of 8 percent against a result of 5. When the practice started a few people worried it would hurt morale; what actually happened was different. Everyone understood why hiring had slowed, and the guessing stopped.

The same person went the other way once. Grace mentioned an unfinished team reorganization in a meeting, and for the two weeks it took to settle, conversation circulated about who was moving where. After that the rule became that personnel changes get announced once, after they're final.

The most common assumption is that transparency means opening everything, since not hiding sounds identical to not withholding. But deciding what stays closed is part of the same practice. Open individual salaries or unfinished personnel moves and you add fuel for speculation rather than information; open what a customer contract covers and the company is the party that loses trust. Openness started without boundaries tends to snap all the way shut after the first incident. A workable boundary list is short and specific, and rereading it once a year keeps it from quietly expanding.

Believing that uploading material makes an organization transparent is nearly as common. Opening access is a visible action, so it feels like the job. But what people actually read is what reached them. Thirty documents in a shared folder and a dashboard left open still leave the informed and uninformed exactly as far apart, unless someone says where to look and what changed last week. Opening it and pushing a summary of it are one task, not two.