This guide gives UK SME teams a practical implementation path: start with the business question, check the data or workflow, build the smallest useful version, then document what has changed.
This guide gives UK SME teams a practical implementation path: start with the business question, check the data or workflow, build the smallest useful version, then document what has changed.
Understand when to add calculated columns vs measures for optimal performance.
March 28, 2026 6 min read Matty Hatton, founder of Digital AdaptionUnderstand when to add calculated columns vs measures for optimal performance.
Power BI mastery here means turn messy reporting into trusted decision system.. This guide is written for analysts, finance teams, operations leaders needing trusted dashboards.
Published guideThis guide is live on Digital Adaption and aligned to the Power BI content track.
In This GuideAnalysts, finance teams, operations leaders needing trusted dashboards.
Your model is slow. Reports take 30 seconds to load. You probably used calculated columns where you should have used measures.
Mastery focusBuild the smallest repeatable workflow that removes friction first, then scale once the output is trusted.
Calculated columns: compute once when data refreshes, store as static values in the table, like an extra Excel column. Measures: compute on-the-fly when visual renders, like a pivot table calculated field. Column: one value per row. Measure: one value per visual context.
Use when: (1) You need to use the result in a slicer or as axis/legend. (2) The calculation is simple and doesn't change based on user filters. (3) You need to categorize data: Category = IF([Amount] > 1000, 'High', 'Low'). (4) You need to create a relationship - use calculated column as the key.
Use when: (1) The value changes based on what the user filters/slices. (2) You're doing SUM, AVERAGE, COUNT, or any aggregation. (3) You need to compare values across time periods. (4) You're calculating ratios, percentages, or rolling totals. Example: Total Sales = SUM(Sales[Amount]) - this recalculates per visual.
Open Performance Analyzer (View > Performance Analyzer). Click Start recording. Click refresh on your visual. Look at the DAX query time. If it's over 1 second for a simple visual, check if you're using calculated columns that could be measures instead.
If you have: Category = IF(Sales[Amount] > 1000, 'High', 'Low'), convert to measure: Category = IF(SUM(Sales[Amount]) > 1000, 'High', 'Low'). The key difference: columns see one row, measures see the filtered set of rows.
Using calculated columns for aggregations.
Putting calculated columns in visuals that already have implicit measures.
Forgetting that columns are static, measures are dynamic.
Fast reports that respond instantly to filters.
Once the first version is trusted, fold it into the weekly or daily operating routine that owns the outcome. A guide without a standing cadence becomes a forgotten document.
If you need the workflow mapped, validated, or turned into a working report/app/process, use the linked service page to start the conversation.
Talk through a Power BI problemThe best owner is the person who understands both the business pain and the operational decision that must improve after the guide is used.
Run the proposed steps against a handful of live examples, then confirm the output with the team that already trusts the current process or source system.
It should answer a real operational problem with a repeatable workflow, clear ownership, and an outcome the reader can measure.
Matty Hatton is the founder of Digital Adaption, an ERP and data consultancy based on the Wirral. He has spent 15 years delivering ERP transformations for manufacturers, including leading the data migration on a £4.5m consolidation of four legacy systems onto a single Infor LN cloud instance for a 220-user group. He holds an MSc in Digital Transformation and IT Strategy from Manchester Metropolitan University and is Microsoft PL-200 certified.
Start with a 30-minute data risk call