The graduation lesson named the signals: a workbook that’s really a shared operational tracker — assets, requests, onboarding steps, the team’s who-has-what — being co-edited into chaos. The first rung of that graduation ladder deserves its own lesson, because it’s the one an Excel person can climb in an afternoon: Microsoft Lists — in most 365 licences, sitting unexplored next to Forms.
What a List is
A List looks like
a Table
that moved out and got its own place: columns with enforced
types (choice, person, date, number, yes/no), rows, views.
The resemblance is deliberate — Create a list → From Excel
imports your existing Table, mapping each column to a real
type. The differences are exactly the ones your shared-tracker
pain has been begging for:
- Types are law, not advice. An Excel date column hopes
(validation
helps; pasting defeats it). A List date column cannot hold
"next Tuesday ish". The cleaning stage of the path exists because spreadsheets accept anything; Lists is what refusing at the door looks like. - Nobody can sort it wrong. Rows are records, not cell ranges — the scrambled-column catastrophe is structurally impossible, as is overtyping a formula column.
- Views replace copies. “My open items”, “overdue by site”, a grouped board — each is a saved lens on the same records. The FINAL_v7 disease was people needing different views and making copies to get them; Lists makes views free.
- Per-item everything: version history, comments, attachments, and — via Power Automate, where Lists is a first-class citizen — “when a row’s status changes, notify the owner” in three clicks. Rules that took a checks row plus goodwill in Excel become properties of the system.
What you give up (the honest column)
Lists is a record-keeper, not a workspace. No real formulas
— calculated columns exist but are a thin dialect; anything
SUMIFS-shaped
or model-shaped
doesn’t belong there. No pivots, no
charts worth the name,
clumsy bulk editing
(grid view helps, but Excel it is not), and a few thousand
items is comfortable where
the data model shrugs at millions.
The division of labour writes itself, and it’s the same one as
every graduation on the path: Lists holds the truth; Excel
asks it questions — Data → Get Data → From SharePoint List
connects the query,
and every pivot, chart and
dashboard you’ve
built still works, refreshable, against records nobody can
scramble.
The test for whether a tracker should make the move is one question deep: is this data operated on by several people, or analysed by one? Operated → List. Analysed → Table. Both — which is most of them — List for the operating, Excel connected for the analysing.
Your Table grew up, moved out, and got a door policy. It still comes home for the analysis — and honestly, the relationship has never been better.