Electronic Spreadsheets and the Paradox of Flexibility

Arguably, the electronic spreadsheet is one of the most flexible end-user information systems ever created. In many organizations, the electronic spreadsheet is not just a spreadsheet; it is a database, reporting engine, modeling platform, workflow tool, a planning application, a project management tool, a calculation engine, dashboard system, integration layer, and sometimes important critical aspects of an ERP system that the ERP system simply cannot itself handle well.

Most organizations rely on spreadsheets for their most important operational activities, including budgeting, forecasting, financial reporting, reconciliations, and performance management. Yet these critical processes are often built on tools that were designed to be maximally flexible rather than operationally controlled. The electronic spreadsheet's greatest strength is its almost unlimited adaptability, but that same flexibility introduces risk when spreadsheets become systems of record upon which organizations depend.

From a process control perspective, this challenge can be understood in terms of degrees of freedom. From the perspective of process control; a degree of freedom represents a variable that a business system user can independently manipulate. Electronic spreadsheet applications like Excel and Google Sheets expose an enormous number of degrees of freedom: users can modify formulas, restructure data, create new calculations, redefine relationships, and alter business logic at any time pretty much in any arbitrary way that they choose.

While this freedom enables innovation and rapid problem solving, it also makes consistency, governance, auditability, and trust more difficult to achieve.

But what if there were a different sort of tool. Flexibility and control are usually in tension with one another. Ease of use is another important consideration.

How do we preserve the electronic spreadsheet's flexibility while at the same time add the rigor, provenance, semantics, and controls required for trustworthy accounting, reporting, auditing, and analysis?

What if you built a system with precisely the correct "degrees of freedom" for doing 80% or maybe even only 20% of what people are trying to do with electronic spreadsheets; a specialized tool for creating mission critical and important operational spreadsheets at scale.  What if you could use this new purpose-built spreadsheet environment to replace those shadow spreadsheets.   How useful would that be?

Personally, and as an accountant and auditor that has made extensive use of electronic spreadsheets; I think that could be enormously valuable, and arguably it's one of the biggest unsolved opportunities in business software.

The goal is not to replace electronic spreadsheets like Excel or Google sheets.  Those are obviously very useful tools with the number of users in the billions.  Let's identify the subset of spreadsheet behavior that is mission critical, that exists in those operational spreadsheets, that are used in those shadow spreadsheets, and provide exactly the controls needed to make that subset reliable, trustworthy, and useful in this era of artificial intelligence.

The goal of this purpose-built operational spreadsheet environment is not to eliminate flexibility, but to intentionally engineer that flexibility. Instead of providing every possible capability, the system would expose only the degrees of freedom that are necessary for users to perform their work. Operational decisions, assumptions, inputs, scenarios, and approvals remain flexible, while structural elements such as information models, validation rules, business logic, and controls are governed and protected. We also make this purpose-build operational spreadsheet semantic oriented by design, not a proprietary format but rather based on global open industry standards. And we make this purpose-built operational semantic spreadsheet as easy to use as Lego bricks.

This design approach mirrors the principles of modern process control systems. Effective control systems do not provide operators with unlimited ways to manipulate a process. Rather, modern process control systems provide precisely the controls needed to achieve desired outcomes safely, reliably, efficiently, and predictably. By limiting unnecessary degrees of freedom, complexity is reduced, behavior becomes more predictable, and the resulting system becomes easier to monitor, govern, and audit.

Such a platform should not be viewed as an "Excel replacement" or "Google sheets replacement". Instead, it is a specialized operational environment optimized for a specific class of mission critical spreadsheet applications. It embraces the familiar spreadsheet paradigm while embedding provenance, traceability, trackability, workflow, version control, validation, semantic definitions, and auditability directly into the architecture. The result is a system that retains the productivity and accessibility users value while providing the rigor and trustworthiness required for many, if not most, enterprise operations and are certainly requirements for accounting, reporting, auditing, and analysis.

Ultimately, the central design principle is simple: a well-designed operational system does not maximize flexibility; it provides exactly the degrees of freedom required to achieve its objectives and no more. By deliberately engineering the balance between freedom and control, organizations can preserve the strengths of spreadsheets while eliminating many of the risks that emerge when critical business processes depend on unrestricted flexibility.

From what I can tell, my proposed system of discrete stable units of information or what I call my digital information organisms have many of these characteristics. XBRL International's Project Tavi nudges the XBRL global open industry standard in that same direction. The Object Management Group's (OMG) Standard Business Report Model (SBRM) which is very aligned with XBRL does also.

This is not about deciding whether XBRL, JSON-LD, RDF, PROLOG, YAML, GQL, SQL is the better physical technical format. Technical formats come and go and enterprises have multiple different technical architectures.  We need to think bigger picture.  We need to create a reliable tool that will be good enough to serve the demands of financial accounting, reporting, auditing, and analysis which has an irrefutable need for zero tolerance for error.  Other enterprise systems have similar requirements. That is the baseline.

Additional Information:


Comments

Post a Comment

Popular posts from this blog

Internationalized Resource Identifier (IRI)

Image
An Internationalized Resource Identifier (IRI) is a standard proposed by the IETF ( RFC 3987 ).  An IRI is a unique sequence of characters that identifies a resource.   IRIs are a generalization of URIs ( RFC3986 ) that permits a wider range of Unicode characters. A  Uniform Resource Identifier (URI) is a unique sequence of characters that identifies an abstract or physical resource.  The difference between an IRI and a URI is that IRIs use the more modern  Universal Character Set (a.k.a. UNICODE)  and URIs use the older ASCII character set. The newer IRI format is compatible with the older URI format. The most  current version of RDF  uses IRIs to identify resources. Don't confuse IRIs with URLs and URNs.  A URL is a web address. A URN is a Uniform Resource Name. This Venn diagram shows the relationship between these different tools: Why are IRIs and URIs important?  If you are thinking in terms of a single database, a silo ...
Read more

Example Financial Statement Holon

Image
As I have mentioned in other posts on my blog, a financial statement is a formal semantic structure , in fact a financial statement is a special type of formal semantic structure referred to as a holon . As I mentioned in my blog posts, Kurt Cagle and Chloe Shannon are providing a lot of very good information about holons on their substack. ( Here is Kurt Cagle's and Chloe Shannon's answers to my questions. Here is an example Kurt Cagle created of a financial statement as a DataBook.) I have provided a bunch of good examples of financial reporting frameworks and reports   In this blog post I want to focus on one specific financial statement and see if I can explain that a financial statement is a "container" of  blocks of information and the "information blocks" that the financial statement contains. Cagle and Shannon point out that a holon is made up of four distinct knowledge graphs that maximize coherence and operationalize the holon which are: The Sc...
Read more

Inhabiting Babel, A Manifesto for Responsible Meaning Engineering

Image
Inhabiting Babel, A Manifesto for Responsible Meaning Engineering is a book written by Nicolas Figay . This book is very practical and easy for a motivated business professional to read. For me, this book has both tempered my expectations as to what is possible and also reassured me of the real possibilities that exist if you do the required work. Accountants and auditors tend to be on the conservative side of the spectrum.  Me included. I am  actually rather conservative in terms of what technology might bring to the table for accounting, reporting, audit, and analysis. I have learned how to "cut the cards" when dealing with sales people and software vendors. What this book does is bring the wisdom from the experiences of an expert in system interoperability, enterprise architectures, and complex systems to helps motivated business professionals and technical professionals that truly want to understand artificial intelligence, cutting through the rhetoric and hype. This boo...
Read more