Kabir saheb has been on the same post for twelve years, the eastern end of the Mohakhali flyover railing where the curve straightens out and cars come down off the slope going faster than they should. He leans his elbows on the railing at half past six every evening with a lined notebook and a stub of HB pencil he keeps sharpened on a piece of brick under the sentry stool. The whistle on a faded green cord around his neck is, he has worked out over twelve years, an instrument he reaches for only when nothing else has worked. The working instrument, the one that actually tells him what the road is doing, is the notebook.
A paragraph at the top of each evening's page lists the four lanes painted on the tarmac below, two in each direction, yellow line down the middle, dashed white lines marking the divisions. That is the org chart of the road, painted by a contractor the government paid eleven crore taka in 2009. Underneath the official paragraph he draws a second diagram with seven or eight lanes depending on the evening, and tallies which one each car is actually in. By eight o'clock the second diagram has six to nine lanes, and the official paragraph at the top of the page reads like a press release from a different city.
A Slack workspace, looked at by a new VP on their first morning, is the painted lanes. Channel names with an #eng prefix, names with a #marketing prefix, a private #leadership channel pinned at the top, a #general nobody posts in any more because the companywide meeting moved to Lattice. The workspace looks tidy, the way the flyover looks tidy at three in the morning when there are no cars on it, and it looks like that for about as long as it takes the new VP to open the third channel down. That's the moment the painted lines stop being the structure and the real lanes start showing themselves.
What you actually want to read, on the morning you're trying to figure out who runs anything, is the same set of things Kabir saheb is reading at half past six. Channel age, message density, reply counts, who's getting tagged with an @ at three in the morning when the alert for whoever's on call fires, which DMs spike on a Friday and which die on a Monday. The metadata is the org. The channel names are decoration painted so the road would look official from the helicopter.
Most of the signals that pay back the time you spend reading them are visible from the channel sidebar without your opening a single message. Start with channel age. A channel created in 2019 that still has traffic in 2026 is a wall that carries weight, and you find out how much weight only once somebody tries to knock it down. A channel created last quarter with 300 members and a dozen messages a day is a fault line where somebody is routing around the official structure on purpose. A channel from 2022 with no message since January is a project that died without a funeral, and somebody on payroll is still listing it as their main responsibility on LinkedIn. Will Larson calls a version of this in his org essays the gap between a team's stated charter and what they're actually shipping, and the Slack archaeology is the version of that same gap you can read for yourself in an afternoon, without waiting for a reorg memo to confirm it.
Reply density comes next. A channel where every message gets two replies is a working group. A channel where messages are evenly spaced with almost no replies is a broadcast feed, somebody using it as a newsletter that only runs one way, and the readers have learned not to engage. A channel with a handful of monster threads, forty replies on one and three on everything else, is where the political fights happen. Open the monster threads and write down who shows up, because those are the people with an actual stake in whatever the channel is supposedly about.
cars counted
n=12“The official lanes painted on the road are how the contractor explains the road to the people who paid for the contractor, while the lanes the cars are actually in are how the road explains itself to itself, and it's the second diagram, not the first, that decides whether anyone gets home in time for iftar.
”
← K.S., eastern post
The third signal, the one most people miss, is the DM graph. You can't see it from inside Slack without admin exports, but you can infer most of it from who replies to whom at odd hours and who gets tagged with an @ in incidents without official ownership of the system on fire. Lara Hogan has written for years about mapping these informal trust networks before any organisational change, because the DM graph is the graph that actually shows how decisions get made. The reorg the leadership team is about to announce will route around the DM graph rather than reshape it, and inside two months the DMs will have quietly regrouped into something that looks suspiciously like the previous org, just with new titles stapled on top.
What does this mean for anyone who is not a paranoid reader of channel sidebars? It means you cannot reorg a company without first reading the workspace honestly, because the chart you are reorganising is at most half of what is actually running. Rands wrote in Managing Humans that the most expensive mistakes a new leader makes are treating the printed structure as the working structure. The team they thought they were giving more authority to was already informally reporting elsewhere, and the team they thought they were sunsetting was holding up three systems that carried real weight through a private channel nobody told them about. By the second week the workspace has rerouted itself back to what it was doing before the announcement, and the only person surprised by that is the one who drew the slide.
So the move in your first month is to spend two evenings the way Kabir saheb spends his shift on the railing. Open the channel sidebar, sort by recent activity, look at what was created last quarter and what hasn't moved since 2023. Read three threads at random in the channels with the highest reply density and write down who shows up in all three. Find the #incident-2025-march channel nobody archived, and read its last forty messages slowly. You will come out with a map that contradicts the org chart in three or four specific places, and those are the ones that decide whether the next thing you ship makes it to production or quietly dies in somebody's DMs.
The light has gone now over Mohakhali. The sodium lamps along the flyover come on one at a time, each buzzing into life two seconds after the one before it. Kabir saheb closes the notebook, slips it into the inside pocket of his uniform shirt, and tucks the pencil stub behind his ear. The official four lanes are still painted on the tarmac. The seven the cars have actually been using all evening are not painted anywhere, and they will be there again tomorrow at half past six with one or two new merges the morning shift will have to discover for itself. He nods at the younger constable taking over for the night shift, who still trusts the painted lines, and says nothing about it. The notebook in the pocket will say it for him by the end of next week.