The reasoning behind a decision is almost always in the Slack thread where it was argued, not in the doc that announced it. To surface it for a new hire, start from the rule, find the date it changed, read the channel around that date, and write down the decision, the reason and a link to the thread.

Why is the "why" always in Slack?

Because that's where the argument happened.

A decision has two halves. The outcome gets recorded properly: the price list is updated, the routing rule is changed, the Confluence page gets a new line. The reasoning doesn't get recorded anywhere on purpose. It was typed into a channel over two days by five people, one of whom has since left.

So every company ends up with the same split. The docs say what. Slack says why. And the why is the half a new hire needs, because it tells them whether a rule is load-bearing or just old.

Without it they have two options. Leave the odd-looking rule alone, in case it matters. Or change it, and find out. Neither is a good use of someone you hired for their judgment.

What does a new hire do today?

Three things, in this order.

  1. Search. They type the name of the rule into Slack and get four hundred results, most of them people mentioning it in passing.
  2. Scroll. They open the oldest plausible thread and read upward, trying to work out who these people are and which of them still works here.
  3. Ask. They give up and message someone who was there. That person explains it from memory, mostly correctly, in between two meetings.

Knowledge workers spend, on average, 2.8 hours a week looking for or requesting information to do their jobs (APQC, 2022). That's the figure for people who know where things are. A new hire is doing the same work with no map and no idea which channel was renamed.

None of this is anyone's fault. It's context archaeology, and it's the default way reasoning gets passed on.

How do you find the decision behind a rule?

There's a manual method that works. A manager can use it today for the three or four decisions a new hire will trip over.

  1. Start from the rule, not the topic. Pick something concrete: the discount cap, the routing rule, the reason one customer has a different contract. "Pricing" is a topic. "Why annual-only for enterprise" is a rule.
  2. Find the date it changed. Look at when the doc, the config or the CRM field was last edited. That date is your anchor.
  3. Read the channel around that date. Go to the channel where that team talks and read the two weeks before the change. The decision thread is usually long, has more people in it than usual, and ends with someone saying "ok, going with this".
  4. Write three lines and a link. What was decided. Why, in the words used at the time. What was considered and rejected. Then link the thread.

Step four is the one that matters. An explanation without the link is one more person's memory. With the link, the new hire can read the original, see who was in it, and judge whether the reasons still apply.

When does the manual method stop scaling?

Quickly.

Four steps for one decision takes about an hour if you were there, and longer if you weren't. A role touches dozens of decisions. A company hires for several roles at once. And the manager doing the digging is the same manager covering the open seat.

There are three places it breaks:

This is the point where teams try a search tool or a chatbot on top of Slack. Those are good at finding a thread once you know to look for it. A new hire doesn't know the rule has a history, so they never type the question. Firstweek vs. Glean goes through that difference.

Meanwhile the new hire is on payroll, digging. The onboarding cost calculator works out what that costs with your own numbers.

What does a cited "why" look like?

Here is one, for a company that doesn't exist. Everything in it is invented.

Why enterprise contracts are annual-only. In March the team moved enterprise customers to annual billing after two mid-year disputes over usage charges. Monthly billing was kept for the self-serve tier. A quarterly option was discussed and rejected because finance couldn't reconcile it. Source: #pricing-decisions thread, March 12.

Four sentences. A new AE who reads that knows what the rule is, why it exists, what not to offer a customer, and where to look if a customer pushes back. They didn't have to know to ask.

That is what Firstweek writes, across everything a role touches. It reads Slack and the tools around it through read-only connections, summarizes at ingest so raw messages are never stored, and writes one cited onboarding artifact for each new hire. Every claim links to the thread, page or record it came from. The hiring manager approves it before day one, which is where a decision that was later reversed gets caught.

What Firstweek reads from Slack, and what it never stores, is on the Slack connection page. The sample artifact has a full set of cited claims like the one above. And the security page answers what a reviewer will ask.

FAQ

How do you surface knowledge buried in old Slack threads?

Start from a specific rule, find when it changed, read the team's channel around that date, and write down the decision, the reason and a link to the thread. The link is what makes it checkable.

Why isn't the reasoning in our documentation?

Docs record outcomes. The reasoning happened in conversation, and nobody is asked to copy an argument into a wiki after it's settled.

Can a new hire just search Slack for it?

Only if they know the decision exists. In week one they don't, so the search never happens.

Does Firstweek store the Slack threads it reads?

No. Raw messages are processed in memory and never stored. Only summaries persist, with citations linking each claim to its source.

Sources: APQC, KM Makes Knowledge Workers More Productive and Less Stressed Out (2022), listed with its link on the onboarding statistics page.

Run it on your next hire. 30 days. Then we talk. Start a pilot or see a sample artifact. How it works for scaling teams.