The Jedox Design System, and the principles behind good reports
· Jedox
Jedox published a design system for reports. Here is what it is, and the principles worth taking from it.
Jedox shipped something, with little announcement, that every Jedox report builder should look at: a full design system for reports, published at design-system.cloud.jedox.com. As someone who builds Jedox reports for clients, I think it is a bigger deal than it first appears. Below I go through what it contains and which principles I would take from it.
What it is
It is a modular toolkit for designing reports that are both functional and beautiful. Instead of every report being a one-off built from scratch, the design system gives you a shared set of foundations and ready-made components, plus guidance on how to use them. In other words, a single source of truth for what a good Jedox report looks like and how it behaves.
Built like Lego: atoms, molecules, organisms
The part I like most is the structure. It follows atomic design, building complexity out of small reusable pieces:
- Atoms are the basic building blocks: buttons, links, checkboxes, labels, table cells, text inputs, tooltips.
- Molecules combine atoms into useful groups: filters, combo boxes, analytical panels.
- Organisms assemble molecules into whole sections: headers, dialogs, forms, tables.
This matters because it changes how you work. You stop reinventing a filter or a header on every report and start composing reports from a kit you trust. It is faster, it is more consistent, and it is far easier to maintain.
Foundations first
Under the components sit the foundations: colour, typography, iconography, layout, navigation, data visualization and stylesheets. These are the quiet decisions that make or break a report. Get them right once and every component inherits them; change one and everything updates together. For finance users who live in these reports during close, consistent foundations are the difference between a tool they can read at a glance and one they have to decode.
The principles worth taking
Whether or not you use the Jedox kit exactly, the principles travel:
- Consistency is a feature. When every report speaks the same visual language, users trust the numbers faster and learn the tool once, not once per report.
- Reuse beats rebuild. Components built once and reused everywhere mean faster delivery and fewer small bugs.
- Foundations before flourishes. Nail colour, type, spacing and layout first; decoration second.
- Data visualization is the message. In a finance report the table or chart is the point, so design it for clarity, not decoration.
- Functional and beautiful are not a trade-off. A report can be both, and the good ones are.
Why it matters for the work
When I build a Jedox solution for a client, aligning to a design system makes the deliverable feel native and professional, keeps every report in a project consistent, and makes the whole thing quicker to build and cheaper to maintain. It turns "each report is a craft project" into "reports compose from a shared, tested kit." That is the same shift good software teams made years ago, and it is good to see it reach the reporting world.
If you build Jedox reports, spend an afternoon in the Jedox Design System. Even if you only borrow the principles, your reports will be better for it.