There was a time when the purpose of an Excel workbook seemed almost self-evident. Data was entered into cells, formulas performed calculations, charts visualised the results, and perhaps a PivotTable or two summarised the information for management. Larger workbooks might incorporate VBA macros to automate repetitive tasks or import data from external systems, but the underlying role of the workbook remained unchanged. It was, first and foremost, a spreadsheet.
For decades, that mental model served us well. Yet if you compare a modern Microsoft 365 workbook with one built even ten years ago, the difference is striking. It is not simply that Excel contains more functions than it once did, nor that calculations execute more quickly. The application itself has evolved into something fundamentally different. Without much fanfare, Excel has become capable of performing many of the tasks traditionally associated with data transformation tools, lightweight programming environments, and analytical platforms. The spreadsheet has quietly become a data processing engine.
Recognising this shift is perhaps the single most important step an advanced Excel user can take, because once you begin to see Excel in this way, the way you design workbooks changes entirely.
Traditional spreadsheet design is heavily influenced by the physical grid. Rows contain records. Columns contain attributes. Individual cells contain calculations. As additional requirements emerge, more formulas are copied, more helper columns are introduced, and more worksheets appear to accommodate intermediate results.
This approach is entirely logical when the worksheet itself is viewed as the primary working surface. The calculations exist because the cells exist. The physical layout largely determines how the workbook develops, and over time the structure of the workbook becomes increasingly intertwined with the calculations it performs.
Many of us learned Excel this way, and for many years there was little reason to think differently.
Modern Excel encourages an altogether different perspective. Instead of beginning with the worksheet layout, we increasingly begin with the transformation itself.
What information do we need?
How should it be filtered?
How should it be reshaped?
Which business rules should be applied?
What should the final output contain?
These questions describe a process rather than a layout.
Functions such as FILTER, SORT, UNIQUE, LET, LAMBDA, MAP, BYROW, and TEXTSPLIT make this possible because they operate naturally on collections of data rather than isolated cells. Rather than instructing Excel how to fill hundreds of rows, we describe how an entire dataset should be transformed. The worksheet becomes the destination of that transformation rather than the mechanism through which it is achieved.
One of the defining characteristics of modern Excel is its gradual movement towards declarative thinking. Traditional spreadsheet models often describe how calculations should be performed. Copy this formula. Extend it to the next row. Insert a helper column. Repeat the calculation for each record.
Modern formulas increasingly describe what the result should look like.
A formula such as
contains no notion of repetition, copying, or iteration. It simply states that the required output consists of the rows where the region equals "North". The mechanics are left entirely to Excel. This distinction may appear subtle, but it fundamentally changes how solutions are designed. Instead of constructing processes manually, we define relationships between datasets.
Perhaps the greatest beneficiary of this shift is business logic itself. Historically, the logic within many workbooks became fragmented across helper columns, hidden worksheets, intermediate calculations, and supporting VBA routines. Understanding how a result had been produced often required navigating through multiple layers of the workbook, tracing dependencies from one location to another. Modern Excel encourages the opposite.
Functions such as LET allow calculations to be structured clearly within a single expression. LAMBDA enables reusable business rules to be defined once and reused throughout the workbook. Dynamic arrays remove much of the scaffolding previously required to support intermediate calculations. As a result, the workbook becomes organised around business rules rather than worksheet structure. The calculations no longer exist because the cells require them. The cells exist because they present the results of well-defined logic.
One of the more interesting consequences of this evolution is that the worksheet itself becomes less important than it once was. This is not to suggest that the grid is disappearing. Far from it. Rather, its role is changing. Increasingly, the worksheet serves as an interface through which information is viewed, entered, and presented. The real work occurs within the transformations defined by the formulas themselves. This mirrors developments in software engineering, where graphical interfaces are increasingly separated from the logic that powers them. Users interact with screens, but the underlying application operates independently of the interface. Modern Excel is gradually moving in the same direction.
For experienced VBA developers, this change can initially feel surprising. Many forms of automation that once demanded procedural code can now be achieved declaratively through formulas. Data can be filtered dynamically, reshaped automatically, cleaned using native text functions, and transformed through reusable LAMBDA functions without writing a single line of VBA.
This does not diminish the importance of macros. Rather, it allows VBA to concentrate on the aspects of automation for which it is uniquely suited: interacting with external systems, coordinating workflows, manipulating files, and integrating with the wider Microsoft Office ecosystem. The workbook performs the analysis, the macro performs the orchestration. The distinction has become clearer than ever.
One of the recurring themes throughout this series has been simplification. Not simplification of business problems, which continue to grow in complexity, but simplification of workbook architecture. Modern Excel encourages fewer helper columns, fewer duplicated formulas, fewer hidden worksheets, and fewer procedural workarounds. Instead, calculations become centralised, transformations become reusable, and datasets become dynamic. The resulting workbooks are often easier to understand precisely because they contain less structural clutter. Complexity has not disappeared - it has simply been relocated into well-structured logic.
Perhaps the most significant consequence of modern Excel is that it encourages spreadsheet users to think increasingly like software developers. This does not mean writing code, it means designing systems.
The emphasis shifts towards abstraction, reuse, maintainability, and separation of concerns. Business rules are encapsulated. Calculations become reusable components. Data transformations are defined explicitly rather than performed manually. These are principles that software engineering has embraced for decades, and they now apply equally well within sophisticated Excel workbooks. Ironically, Excel has become more approachable by becoming more structured.
Where this evolution ultimately leads remains to be seen. Microsoft continues to invest heavily in the formula language, introducing new functions that would once have seemed entirely out of place in a spreadsheet application. At the same time, Excel's integration with Power Query, Power Pivot, Python, cloud services, and the wider Microsoft 365 ecosystem continues to deepen.
Each of these developments reinforces the same underlying trend. Excel is no longer simply a place where calculations happen. It is becoming an environment in which data is acquired, transformed, analysed, modelled, and presented using increasingly sophisticated yet remarkably accessible tools. The spreadsheet has not disappeared - it has simply grown into something much larger.
This series began by introducing dynamic arrays as a new way of thinking about formulas. Along the way, we explored spill ranges, modern lookup functions, reusable logic through LAMBDA, higher-order functions, advanced text manipulation, workbook architecture, and the changing relationship between formulas and VBA. Viewed individually, each feature represented an incremental improvement. Viewed together, they reveal a much broader transformation.
Excel is evolving from a calculation tool into a declarative analytical platform, one in which formulas describe relationships, transformations, and business logic rather than merely computing individual values. For those willing to embrace this change, the reward is not simply shorter formulas or cleaner workbooks. It is a fundamentally different way of thinking about Excel itself. And in many ways, that may prove to be the most important feature Microsoft has introduced in years.
Cat On A Spreadsheet