The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Update the workbook’s external links to the new server path and refresh all linked tables and…
Execute — do the immediate task
+Update the workbook’s external links to the new server path and refresh all linked tables and queries. Confirm that the SalesData connection now points to \fileserver02
eports
evenue.csv and that the currency conversion sheet pulls the latest exchange rates. After refresh, save a copy as Linked_Update_2026-07-17 and report any broken queries or errors.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I hand this to the operations team, make the link migration obvious and low-risk: list every…
Improve — make it easier to accept
+Before I hand this to the operations team, make the link migration obvious and low-risk: list every external connection and its current path, replace the old server path with \fileserver02
eports
evenue.csv, run a full refresh, flag any tables that changed row counts, and create a rollback copy named Linked_Rollback_2026-07-17. Give a one-paragraph summary of risks and the steps to revert.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+I swapped the data source to the new server and the workbook refresh now fails citing missing…
Decide — diagnose the stuck moment
+The refresh failed with errors about missing fields
I swapped the data source to the new server and the workbook refresh now fails citing missing fields in SalesData. I am worried downstream calculations are broken and I cannot tell if the source schema truly changed or if the connector mapped wrong. How should I quickly diagnose which is true and what safe next step gets me back to a consistent dataset before COB today?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Every time we change servers or file locations, linked workbooks break and we lose hours fixing…
Become — change the pattern
+We keep breaking links after migrations
Every time we change servers or file locations, linked workbooks break and we lose hours fixing queries and updating formulas. I want to stop this cycle. Recommend one governance rule and one technical habit for managing external links so migrations are predictable and repair time is minimal.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other spreadsheet work people do in Microsoft Excel.
Translate data into another languageTranslate formulae into processesTranslate industrial ecology theories into practicesTranslate the research results into industrial production processesTypes of metalUse computational modeling and simulation toolsUse data validation listsUse Goal Seek to solve valuesUse keyboard shortcuts efficientlyUse Power Query to transform data
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.