Why the Maersk Design System won’t become Excel, and why that’s a good thing
TLDR
- MDS receives regular requests to add complex Excel-like capabilities to the table component.
- The original intention was to provide a lightweight table foundation with flexible extension points, not a full data grid.
- The table has matured significantly but is nearing its intended scope limit.
- The 2026 roadmap strengthens fundamental table patterns rather than expanding into high complexity features.
- Teams that need rich data grid behaviours should continue using third-party solutions, supported by MDS guidance and theming where appropriate.
The context
Across Maersk, we frequently receive requests to support more advanced, Excel-like features in the Maersk Design System (MDS) table component. Formulas, spreadsheet style calculations, dynamic cell interactions, and other complex grid behaviours come up often. These requests reflect real product needs and highlight just how central tabular data is across the organisation.
A brief history of the MDS table
The following explains how the MDS table got here, why we have made the design choices we have, and what our direction looks like going forward.
A simple foundation, by design
When the MDS first introduced a table, the mission was simple and intentional:
Provide a lightweight, flexible foundation that ensured visual consistency while giving teams complete freedom to extend and innovate.
The first iteration delivered exactly that. It was (and still is) a set of foundational CSS classes offering:
- Direct control over native table semantics
- A visually aligned MDS experience
- Full customisability for bespoke or advanced interactions
This approach prioritised performance, simplicity, and extensibility.
Evolving into a web component
As needs evolved, we introduced the mc-table web component. It built on the foundational classes and added the core capabilities most teams needed for common use cases:
- Data binding
- Column definitions
- Sorting
This provided a faster path to production while still allowing custom logic and extensions.
Growing with real product needs
Over time, mc-table has expanded to meet common enterprise requirements. Today it supports features such as:
- Sticky or locked rows and columns
- Row selection
- Cell truncation
- Grouped headers
- Expandable rows
- Pagination
- And many others
We also highlight extensibility examples in our documentation, including:
- Draggable rows and columns
- Column resizing
- Editable cells
The component has come a long way, always guided by the principle that it should be lightweight but flexible, not a full spreadsheet or data grid.
Where we stand today
The MDS table is now reaching its natural limits.
Building spreadsheet level functionality is not only complex and expensive to maintain, it also falls outside the mission and scope of a design system. More importantly, it would divert time and resources away from improving the broader system and set unrealistic expectations for what MDS should provide.
In short, trying to replicate Excel inside a design system component would weaken the system rather than strengthen it.
Where we are going next
1. Strengthening table fundamentals
The roadmap for 2026 focuses on refining and improving the core table experience, not expanding into Excel-like capabilities.
This includes:
- Standardising column filter patterns
- Improving bulk action patterns
- Strengthening accessibility and interaction consistency
- Ensuring API clarity and long-term stability
These improvements make MDS tables more predictable, scalable, and reliable across products.
2. Supporting richer use cases through third party solutions
Some products genuinely require advanced data grid functionality. This includes:
- Multilevel grouping
- Spreadsheet style editing
- Formula support
- Pivoting and summarisation
For these scenarios, purpose built third-party grids remain the right tool.
To support teams who need this, we are exploring:
- Clear guidance on when to use a third-party grid
- Theming recommendations for visual alignment
- Possible best practice integration patterns
This ensures teams get the power they need without trying to force the MDS table into a role it was never designed to fill.
Closing thoughts
The MDS table has evolved significantly while staying true to its original purpose. As it approaches the natural boundary of what a design system table should be, our focus is on strengthening fundamentals, ensuring consistency, and guiding teams toward the right tools for more complex needs. By doing this, we protect the clarity, scalability, and long term health of the Maersk Design System while still enabling the rich grid experiences some products require.