S6 Episode 7 The Spreadsheet Vs. Workflow Thesis

A spreadsheet can record what happened. It can’t make sure the next step happens. In this episode of The LowCode Podcast, we explore the difference between using software as a static system of record and using it to actually run an operation. Using Rising Ground, a New York nonprofit with 1,600 employees, as a case study, we look at what happens when asset tracking, onboarding, and offboarding depend on spreadsheets, emails, and people remembering what to do next.

We break down how Rising Ground replaced that manual process with an active workflow that manages the full lifecycle of every employee asset. Requests are automatically routed to the right department, managers approve or reject individual items, equipment handoffs are backed by digital signatures, and notifications prompt the right people whenever action is required. When an employee leaves, every active asset assigned to them surfaces automatically so the organization can close the loop instead of searching through spreadsheet rows and inboxes.

The bigger lesson goes far beyond asset tracking: storing data and running a process are two different jobs. A spreadsheet can tell you who was issued a laptop, but it can’t enforce approvals, assign responsibility, trigger follow-ups, or make sure that laptop comes back during offboarding. We explore why growing organizations eventually need to move critical processes out of people’s heads and into workflows with clear owners, statuses, rules, and accountability, and why that shift can turn a fragile manual process into a reliable operating system.