<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Spreadsheet Confession</title><link>https://spreadsheetconfession.com/</link><description>Recent content on Spreadsheet Confession</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sat, 31 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://spreadsheetconfession.com/index.xml" rel="self" type="application/rss+xml"/><item><title>Case Study: Rebuilding an Operations Process from a 12-Tab Workbook</title><link>https://spreadsheetconfession.com/case-studies/case-study-rebuilding-an-operations-process-from-a-12-tab-workbook/</link><pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/case-studies/case-study-rebuilding-an-operations-process-from-a-12-tab-workbook/</guid><description>Northfield Rentals hires out staging, furniture and lighting for corporate events. Forty people, around 150 bookings a month, and one workbook called &amp;ldquo;Bookings MASTER v14 (USE THIS ONE)&amp;rdquo; with twelve tabs, 9,000 rows and a colour legend at the top of tab one that nobody followed.
Northfield is a composite of several real migrations, with names and numbers changed and details blended. Every mistake in it happened to somebody.
The before The tabs told the story of the business&amp;rsquo;s growth.</description></item><item><title>Backups, Exports and Exit Plans: Protecting Your Data in Someone Else's Cloud</title><link>https://spreadsheetconfession.com/guides/backups-exports-and-exit-plans/</link><pubDate>Wed, 28 Oct 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/backups-exports-and-exit-plans/</guid><description>The email arrives on a Thursday afternoon. Your no-code platform has been acquired, the product is being &amp;ldquo;sunset&amp;rdquo; in 90 days, and customers are &amp;ldquo;encouraged to explore&amp;rdquo; the new owner&amp;rsquo;s offering at roughly double the price. Your entire order process lives in it.
Whether that email is a mild annoyance or a crisis depends almost entirely on what you did before it arrived.
The risks are ordinary, not exotic When you move a process into someone else&amp;rsquo;s cloud, you&amp;rsquo;re trusting them with it.</description></item><item><title>Avoiding Tool Sprawl: How Not to Trade Spreadsheet Purgatory for SaaS Purgatory</title><link>https://spreadsheetconfession.com/guides/avoiding-tool-sprawl/</link><pubDate>Sun, 25 Oct 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/avoiding-tool-sprawl/</guid><description>Two years ago, your operations team ran on one enormous spreadsheet. Now it runs on a project tracker, a no-code database, a forms tool, two automation platforms, a separate approvals app and a dashboard nobody remembers building. Customer details live in four of them, and they disagree.
Congratulations: you&amp;rsquo;ve escaped spreadsheet purgatory and arrived somewhere with nicer fonts and higher monthly bills.
How sprawl happens Nobody sets out to buy eleven tools.</description></item><item><title>Training Users Without a 40-Page Manual</title><link>https://spreadsheetconfession.com/guides/training-users-without-a-40-page-manual/</link><pubDate>Thu, 22 Oct 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/training-users-without-a-40-page-manual/</guid><description>Somebody, at some point, wrote a 40-page manual for the last tool your company rolled out. It had screenshots, a table of contents and a version history. It was opened by four people, three of whom were checking whether their name was in it.
Busy teams don&amp;rsquo;t learn tools from documents. They learn by doing the task they already have to do, with someone nearby to unstick them. Your training plan should be built around that.</description></item><item><title>Getting Buy-In: Pitching an Internal Tool to Leadership</title><link>https://spreadsheetconfession.com/guides/getting-buy-in-pitching-an-internal-tool-to-leadership/</link><pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/getting-buy-in-pitching-an-internal-tool-to-leadership/</guid><description>You have spent three months nursing a workbook that runs half of fulfilment. You know it is fragile, you know it eats your team&amp;rsquo;s week, and you have a fix in mind. Then you get ten minutes in the leadership meeting, talk about &amp;ldquo;better data integrity&amp;rdquo;, and watch the room nod politely and move on to the next agenda item.
The problem usually isn&amp;rsquo;t the idea. It&amp;rsquo;s that you pitched a tool when leadership wanted to hear about a business problem.</description></item><item><title>Why Your Team Keeps Going Back to the Spreadsheet</title><link>https://spreadsheetconfession.com/guides/why-your-team-keeps-going-back-to-the-spreadsheet/</link><pubDate>Fri, 16 Oct 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/why-your-team-keeps-going-back-to-the-spreadsheet/</guid><description>The new system has been live for six weeks. The usage numbers look fine. Then you open the shared drive and find a file called &amp;ldquo;tracker_actual_USE_THIS,&amp;rdquo; last edited yesterday, with 300 rows that don&amp;rsquo;t exist anywhere in the new tool.
Your team hasn&amp;rsquo;t rejected the new system out of spite. They&amp;rsquo;ve gone back to the spreadsheet because, for some part of their job, it still works better for them. Your task is to find out which part.</description></item><item><title>Reporting Without Exports: Getting Dashboards from Your New System</title><link>https://spreadsheetconfession.com/guides/reporting-without-exports/</link><pubDate>Tue, 13 Oct 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/reporting-without-exports/</guid><description>You spent four months moving the order process into a proper system. Clean data, defined statuses, sensible permissions. Then the head of finance asks for the monthly numbers, someone clicks &amp;ldquo;Export,&amp;rdquo; and by the end of the week there&amp;rsquo;s a file called orders_report_FINAL_v3 being emailed around with its own hand-edited corrections.
The export button is the gateway back to purgatory. Not because exporting is evil, but because a habit of exporting for every report quietly rebuilds everything you just escaped.</description></item><item><title>Connecting Your Tools: A Plain-English Guide to APIs, Webhooks and Integrations</title><link>https://spreadsheetconfession.com/guides/connecting-your-tools-apis-webhooks-integrations/</link><pubDate>Sat, 10 Oct 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/connecting-your-tools-apis-webhooks-integrations/</guid><description>Your new order system works beautifully. Then you realise someone still has to retype every confirmed order into your accounting software, and post a message in your chat tool so the warehouse knows. The data is out of the spreadsheet, but a person is still acting as the cable between systems.
Connecting tools is how you remove that human cable. You don&amp;rsquo;t need to write code to make good decisions here, but you do need to understand a few terms well enough to ask the right questions.</description></item><item><title>Automations That Actually Save Time (And the Ones That Just Create Noise)</title><link>https://spreadsheetconfession.com/guides/automations-that-actually-save-time/</link><pubDate>Wed, 07 Oct 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/automations-that-actually-save-time/</guid><description>Three months after the new system went live, the operations channel gets 140 automated messages a day. Nobody reads them. Last week a genuinely urgent alert about a failed shipment sat unread for two days, buried between &amp;ldquo;Record updated&amp;rdquo; and &amp;ldquo;Record updated.&amp;rdquo;
Automation is one of the main reasons to leave the spreadsheet behind. It is also the fastest way to make a good system unpleasant to live with. The difference comes down to choosing what to automate and building it so it keeps working.</description></item><item><title>Permissions That Make Sense: Who Should See and Edit What</title><link>https://spreadsheetconfession.com/guides/permissions-that-make-sense/</link><pubDate>Sun, 04 Oct 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/permissions-that-make-sense/</guid><description>Somebody in sales sorted the shared customer sheet by region last quarter and didn&amp;rsquo;t notice that two columns weren&amp;rsquo;t selected. For three weeks, every account had someone else&amp;rsquo;s renewal date. Nobody was malicious. The sheet simply let anyone with the link do anything to everything.
When you move a process into proper tooling, permissions are one of the biggest upgrades you get. They are also one of the easiest to get wrong, either by copying the spreadsheet&amp;rsquo;s free-for-all or by overcorrecting into a system where nobody can do their job without filing a ticket.</description></item><item><title>Approvals Without Email Chains: Building a Request-and-Approve Process</title><link>https://spreadsheetconfession.com/guides/approvals-without-email-chains/</link><pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/approvals-without-email-chains/</guid><description>Someone needs a new laptop. They email their manager, who forwards it to finance, who replies-all asking for a quote, which arrives as an attachment in a different thread. Three weeks later the laptop is still not ordered, and nobody can say whose turn it is.
Approval by email works right up until you need to know what was approved, by whom, and why. Then it falls apart. Here is how to build something better, using purchase requests as the worked example.</description></item><item><title>Replacing the "Status" Column: Designing Real Workflows with States and Transitions</title><link>https://spreadsheetconfession.com/guides/replacing-the-status-column/</link><pubDate>Mon, 28 Sep 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/replacing-the-status-column/</guid><description>Open almost any operational spreadsheet and you will find a column called Status. In it: &amp;ldquo;In progress&amp;rdquo;, &amp;ldquo;in prog&amp;rdquo;, &amp;ldquo;WIP&amp;rdquo;, &amp;ldquo;Done&amp;rdquo;, &amp;ldquo;done?&amp;rdquo;, &amp;ldquo;Waiting on Mark&amp;rdquo;, and one cell that just says &amp;ldquo;see email&amp;rdquo;. Some rows are green, some are yellow, and one is a shade of orange nobody can explain.
That column is trying to describe a workflow. It just has no rules. Moving to proper tooling is your chance to give it some.</description></item><item><title>Migration Day Checklist: Retiring a Business-Critical Spreadsheet</title><link>https://spreadsheetconfession.com/guides/migration-day-checklist/</link><pubDate>Fri, 25 Sep 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/migration-day-checklist/</guid><description>The new system has been running for weeks. People mostly use it. And yet the old spreadsheet is still sitting in the shared drive, still editable, still getting the occasional &amp;ldquo;quick fix&amp;rdquo; from someone who forgot. Until you formally retire it, it is not retired.
Migration day is the moment you close the door properly. It should be boring. This checklist is designed to make it so.
Before the day: confirm you are actually ready Do not schedule migration day just because the project plan says so.</description></item><item><title>How to Run the Old Sheet and New Tool in Parallel (Without Losing Your Mind)</title><link>https://spreadsheetconfession.com/guides/run-old-sheet-and-new-tool-in-parallel/</link><pubDate>Tue, 22 Sep 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/run-old-sheet-and-new-tool-in-parallel/</guid><description>The new tool is live. The old sheet is also live. On Tuesday, someone updates a customer&amp;rsquo;s address in one and not the other, and on Thursday an order ships to the wrong warehouse. Everyone agrees parallel running was a good idea in theory.
Running two systems side by side is one of the safest ways to migrate, and one of the easiest to make miserable. The difference is almost entirely in the rules you set before it starts.</description></item><item><title>The Strangler Pattern for Spreadsheets: Migrating Without a Big-Bang Cutover</title><link>https://spreadsheetconfession.com/guides/strangler-pattern-for-spreadsheets/</link><pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/strangler-pattern-for-spreadsheets/</guid><description>You have a workbook with nine tabs, four of which matter, and the whole operations team touches it every day. Someone proposes a &amp;ldquo;cutover weekend&amp;rdquo;: build the new system, flip the switch first thing on the next working day, delete the sheet. Everyone nods. Nobody sleeps well.
There is a calmer way. Software engineers have used it for years to replace old systems without shutting them down, and it works just as well for a spreadsheet.</description></item><item><title>Cleaning Your Spreadsheet Data Before Migration: A Practical Guide</title><link>https://spreadsheetconfession.com/guides/cleaning-spreadsheet-data-before-migration/</link><pubDate>Wed, 16 Sep 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/cleaning-spreadsheet-data-before-migration/</guid><description>You open the client sheet to start the migration and scroll to the &amp;ldquo;Country&amp;rdquo; column. It contains &amp;ldquo;UK&amp;rdquo;, &amp;ldquo;U.K.&amp;rdquo;, &amp;ldquo;United Kingdom&amp;rdquo;, &amp;ldquo;england&amp;rdquo;, &amp;ldquo;GB&amp;rdquo;, and one cell that just says &amp;ldquo;see email&amp;rdquo;. There are 1,400 rows. Somewhere in there, the same client appears three times under slightly different names.
Import that as it is, and your shiny new tool will faithfully preserve every one of those problems. Clean first. It&amp;rsquo;s tedious, but it&amp;rsquo;s the cheapest moment you&amp;rsquo;ll ever have to do it.</description></item><item><title>Self-Hosting Your Internal Tools: When It Makes Sense and What It Really Costs</title><link>https://spreadsheetconfession.com/guides/self-hosting-internal-tools/</link><pubDate>Sun, 13 Sep 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/self-hosting-internal-tools/</guid><description>Someone on your IT team has found an open-source internal tool platform. It does most of what the subscription product does, the licence is free, and they can have it running on a spare server by Thursday. The pitch is compelling: no per-seat fees, your data stays in-house, nobody can triple the price at renewal.
All of that can be true. But &amp;ldquo;free to download&amp;rdquo; and &amp;ldquo;free to run&amp;rdquo; are different things, and the gap between them is where most self-hosting decisions go wrong.</description></item><item><title>Choosing an Internal Tool Platform: The Questions Vendors Won't Answer for You</title><link>https://spreadsheetconfession.com/guides/choosing-an-internal-tool-platform/</link><pubDate>Thu, 10 Sep 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/choosing-an-internal-tool-platform/</guid><description>Every platform demo goes the same way. A sample project-tracking app appears in four minutes, a form populates a table, an automation sends a message to your chat tool, and everyone nods. Nobody asks what happens when you have 80,000 records, or when you want to leave.
The feature grid tells you what a platform can do on a good day. This checklist is about the other days.
Can you get your data out, completely?</description></item><item><title>Buy, Configure, or Build? A Decision Framework for Internal Tooling</title><link>https://spreadsheetconfession.com/guides/buy-configure-or-build/</link><pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/buy-configure-or-build/</guid><description>You&amp;rsquo;ve documented the process, you know the spreadsheet has to go, and now three people have three opinions. Finance wants to buy the specialist software their old company used. Someone in ops has already built a prototype on a no-code platform over a weekend. And an engineer has offered to &amp;ldquo;knock something together&amp;rdquo; in a couple of sprints.
All three can work. All three can also go badly wrong. The trick is matching the option to the problem rather than to whoever argued loudest.</description></item><item><title>Process First, Tool Second: Documenting a Workflow Before You Build It</title><link>https://spreadsheetconfession.com/guides/process-first-tool-second/</link><pubDate>Fri, 04 Sep 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/process-first-tool-second/</guid><description>You&amp;rsquo;ve had the demo. The new platform looked clean, the salesperson was charming, and someone in leadership said &amp;ldquo;great, let&amp;rsquo;s just move the onboarding sheet into that.&amp;rdquo; Three months later, the new tool has a column called &amp;ldquo;Notes (old)&amp;rdquo;, two status fields that disagree with each other, and a side spreadsheet that people use &amp;ldquo;just for now.&amp;rdquo;
That&amp;rsquo;s what happens when you migrate a spreadsheet instead of a process. The tool is new.</description></item><item><title>From Rows to Records: How to Think About Your Data Like an Application</title><link>https://spreadsheetconfession.com/guides/from-rows-to-records/</link><pubDate>Tue, 01 Sep 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/from-rows-to-records/</guid><description>Open your team&amp;rsquo;s client tracker and look at row 47. It&amp;rsquo;s Brightwater Dental. Columns A to H describe the practice. Columns I to N describe the main contact. Columns O to AJ describe their three projects, squeezed in side by side as &amp;ldquo;Project 1 Name&amp;rdquo;, &amp;ldquo;Project 1 Status&amp;rdquo;, &amp;ldquo;Project 2 Name&amp;rdquo; and so on. When they signed a fourth project last month, someone added a note in the comments.
That&amp;rsquo;s not a tracker.</description></item><item><title>When a Spreadsheet Is Actually the Right Tool</title><link>https://spreadsheetconfession.com/guides/when-a-spreadsheet-is-actually-the-right-tool/</link><pubDate>Sat, 29 Aug 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/when-a-spreadsheet-is-actually-the-right-tool/</guid><description>This is a blog about escaping spreadsheet purgatory, so you might expect us to say every sheet should be burned. We won&amp;rsquo;t. Some of the most useful work in your company happens in spreadsheets, and replacing it with a rigid tool would make it slower and worse.
The trick is knowing which sheets are doing the job they were built for, and which ones have quietly become something else.
The line: analysis versus process Here&amp;rsquo;s the distinction that does most of the work.</description></item><item><title>Who Owns This Sheet? Mapping the Shadow Processes in Your Company</title><link>https://spreadsheetconfession.com/guides/who-owns-this-sheet-mapping-shadow-processes/</link><pubDate>Wed, 26 Aug 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/who-owns-this-sheet-mapping-shadow-processes/</guid><description>A logistics manager once told me her team had &amp;ldquo;about five&amp;rdquo; important spreadsheets. Two weeks later, after actually counting, the list stood at 31. One of them calculated driver bonuses. Nobody in finance knew it existed, and it lived in the personal drive of someone who had moved to a different department.
You can&amp;rsquo;t fix what you can&amp;rsquo;t see. Before you migrate a single sheet, you need a map of the ones your business quietly runs on.</description></item><item><title>The Hidden Cost of "It's Just a Spreadsheet"</title><link>https://spreadsheetconfession.com/guides/hidden-cost-of-its-just-a-spreadsheet/</link><pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/hidden-cost-of-its-just-a-spreadsheet/</guid><description>When someone suggests replacing the order tracker with a proper tool, the first objection is usually the price. &amp;ldquo;We&amp;rsquo;d be paying per seat for something we already do for free.&amp;rdquo; And it&amp;rsquo;s true that nobody sends you an invoice for the spreadsheet.
But &amp;ldquo;free&amp;rdquo; is doing a lot of work in that sentence. The sheet costs you every week. You just pay in hours, mistakes and risk instead of in a line item, which makes it easy to ignore and hard to argue about.</description></item><item><title>The 7 Signs Your Spreadsheet Has Become a Database (And Is Failing at It)</title><link>https://spreadsheetconfession.com/guides/7-signs-your-spreadsheet-has-become-a-database/</link><pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate><guid>https://spreadsheetconfession.com/guides/7-signs-your-spreadsheet-has-become-a-database/</guid><description>Somewhere on your shared drive there is a file called Client_Tracker_FINAL_v7_USE_THIS_ONE. Next to it sits Client_Tracker_FINAL_v7_USE_THIS_ONE (2), and nobody is sure which one the finance team is reading from. You open it, scroll right past column BZ, and find a tab called &amp;ldquo;OLD - DO NOT DELETE&amp;rdquo; that three formulas still depend on.
Congratulations. You are running a database. It just happens to be a very bad one.
That isn&amp;rsquo;t an insult to spreadsheets.</description></item></channel></rss>