Unified Grid: How We Re-Architected Slack for Our Largest Customers
Comments on “Unified Grid: How We Re-Architected Slack for Our Largest Customers”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Slack's engineering blog describes how it rebuilt its client and backend so Enterprise Grid users see all their workspaces in one view, rather than switching between them. The team prototyped first, using it internally, then fixed thousands of APIs and permission checks. It reused existing integration tests under org context, where hundreds of suites initially failed, and capped relevant workspaces at 50 per user. Rollout ran from fall 2023 to March 2024. The performance and bug-reduction benefits are stated as expectations, not measured results.
Why it ranked
No. 11 of 46 with a score of 0.64. The panel rated it highest on new information (0.91) and technical depth (0.78), lowest on audience breadth (0.50). The judges disagreed most on substantiated (spread 0.43), so the story is marked contested. Placed No. 11, No. 10 by score alone: the fourth Programming & dev tools story of the day (−0.020). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Detailed engineering write-up of a large architectural migration with concrete strategies and tooling; substantive and practical for builders, though lessons are specific to one product and no benchmarks are given.
- AI judgeJudge 3gpt-5.6-luna
- A detailed first-party engineering account of migrating a workspace-centric architecture to org-wide unified views, including sharding, APIs, permissions, testing, rollout, and performance trade-offs. It offers broadly useful lessons for large product rewrites.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.64total under rubric v2.3Contestedjudges differ by 0.43 on substantiated
- Significance0.60
- Reader interest0.77
- Audience breadth0.50
- Practical relevance0.73
- Substantiated0.64
- Technical depth0.78
- New information0.91
- Counts against: Promotional0.13
- Counts against: Overclaim0.18
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.61 | 0.40 | 0.78 | 0.60 | 0.38 | +0.24 | +0.143 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.72 | 0.70 | 0.90 | 0.77 | 0.20 | +0.26 | +0.201 |
| Audience breadthHow many people who build technology does it concern? | 0.33 | 0.50 | 0.68 | 0.50 | 0.35 | +0.13 | +0.066 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.77 | 0.60 | 0.82 | 0.73 | 0.22 | +0.22 | +0.161 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.45 | 0.60 | 0.88 | 0.64 | 0.43 , above the contested threshold | +0.05 | +0.032 |
| Technical depthHow technically substantive is it? | 0.79 | 0.70 | 0.84 | 0.78 | 0.14 | +0.05 | +0.039 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.88 | 0.90 | 0.96 | 0.91 | 0.08 | +0.05 | +0.046 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.10 | 0.20 | 0.08 | 0.13 | 0.12 | −0.19 | −0.024 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.21 | 0.20 | 0.12 | 0.18 | 0.09 | −0.11 | −0.019 |
| Sum of contributions | +0.644 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.644 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-09/11/"><img src="https://rubric.hrih.si/badge/2026-11-09/11.svg" alt="Ranked #11 on Rubric, 9 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 1 matches source · 7 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenDate
Slack launched Enterprise Grid in 2017, letting its largest customers divide their organizations into multiple workspaces.
The article gives no link or citation for it.
The article says “This model held until 2017, when we released Enterprise Grid, which lets Slack’s largest customers divide their organizations into multiple workspaces, each with a particular focus”
The source says No source to compare with.
Matches sourceCausal conclusion
With the Vitess migration, Slack began sharding data along axes other than workspace or org ID, so workspace or org was no longer required to route queries to the right shard for the most important tables.
The cited source says the same thing.
The article says “With the Vitess migration, we began sharding data along axes other than workspace or org ID, meaning that the workspace or org was no longer required to route queries to…”
The source says “instead of putting all the messages from every channel and DM on a given workspace into the same shard, we wanted to shard the message data by the unique id…”
Source cited by the article: slack.engineering/scaling-datastores-at-slack-with-vitess
No source givenNumber
Slack capped the number of relevant workspaces per user at 50, with users able to configure the list manually.
The article gives no link or citation for it.
The article says “we decided to cap the number of “relevant” workspaces at 50 and allow users to manually configure this list”
The source says No source to compare with.
No source givenQuote
Former Slack CEO Stewart Butterfield, after trying the prototype, said: "This is obviously better."
The article gives no link or citation for it.
The article says “His feedback summed up how we felt: “This is obviously better”
The source says No source to compare with.
No source givenVersion
Unified Grid became a foundational component of IA4, the Slack client redesign that introduced the Activity, DMs, and Later tabs.
The article gives no link or citation for it.
The article says “Unified Grid became a foundational component of IA4, and with it a top company priority”
The source says No source to compare with.
No source givenNumber
Slack built a parallel integration test suite running existing tests with org context, reusing thousands of tests, and hundreds of test suites initially broke.
The article gives no link or citation for it.
The article says “This let us reuse thousands of tests rather than rewriting them from the ground up. As expected, hundreds of test suites were broken initially”
The source says No source to compare with.
No source givenDate
Slack began rolling out Unified Grid to customers in Fall 2023 and completed the rollout in March 2024, almost two years after the prototype.
The article gives no link or citation for it.
The article says “We began rolling out to customers in Fall 2023 and completed the rollout in March 2024”
The source says No source to compare with.
No source givenCausal conclusion
Unified Grid would improve performance because data for multiple workspaces could be loaded in a single API request, and would eliminate a class of bugs from syncing org-wide data across workspaces.
The article gives no link or citation for it.
The article says “it would eliminate a class of bugs caused by syncing org-wide data across multiple workspaces. And it would improve performance, since data for multiple workspaces could be loaded in a…”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 1 pts, not on front page
Recorded for context only, checked 9 Nov 2026, 05:46 UTC. It played no part in the ranking.