Nordic Dynamics

Business analytics and reporting with Power BI

I help companies turn data from spreadsheets, databases, APIs, and business systems into Power BI reports, semantic models, and documented BI solutions.

Discuss a project

Who you would be working with

Welcome, and thank you for visiting my website. I’m Branislav Blatnjak, a Power BI developer and consultant working through my independent practice Nordic Dynamics.

My work is focused on solving complex data and reporting problems with Power BI. I help companies turn data from spreadsheets, databases, APIs, and business applications into well-structured semantic models and high-quality reports that address their reporting needs.

Over the past four years, I have worked in enterprise data and business application environments in Norway. My recent work has focused primarily on Power BI report development, semantic modelling, data transformation, and working directly with the people who use the reports. I can support the full delivery process, from understanding the requirement and reviewing the source data to building, validating, documenting, and presenting the completed solution.

Clients work directly with me throughout the engagement. I take ownership of the work, explain the reasoning behind important decisions, and aim to leave behind a solution that another developer can understand and maintain.

Alongside Power BI, I have practical experience with Microsoft Fabric, particularly governance, architecture, workspace design, training, and adoption. Fabric supports my wider reporting and data work, while Power BI remains the main focus of my services.

I also build software when a problem does not have a sensible off-the-shelf answer. GovernView, for example, is a Microsoft Fabric governance audit tool that I designed and developed to analyse a Fabric tenant and produce a prioritised governance report.

Portrait of Branislav Blatnjak

My skills honestly rated

  • Power BI report development
    Core strength
  • Semantic model design
    Core strength
  • Dimensional modelling (Kimball)
    Specialism
  • Microsoft Fabric governance
    Supporting
  • AI-assisted engineering (Claude Code)
    Supporting
  • SQL
    Supporting
  • Python notebooks
    Supporting
  • Azure Boards
    Supporting

Power BI, reporting, and data services

I support companies through focused delivery projects, independent reviews, and longer consulting engagements. The work may involve building a new Power BI solution, improving an existing model, reviewing a proposed approach, or supporting the Microsoft Fabric environment around it.

Delivery

Power BI report development

I design and build Power BI reports around the information people need to monitor performance and make decisions. The work can include requirements gathering, source-data review, Power Query transformations, semantic model design, DAX measures, report development, validation, documentation, and handover.

Typical deliverables: published Power BI reports, the semantic model behind them, supporting transformation and measure logic, and documentation for future maintenance and development.

Remediation

Semantic model development and redesign

I build new semantic models and improve existing ones where relationships, measures, business definitions, or reporting logic have become difficult to understand or maintain. The objective is a clear model with traceable logic that can support both current and future reporting requirements.

Typical deliverables: a new or redesigned semantic model, documented measures and business definitions, source-to-model mapping, and a record of the changes made.

Advisory

Power BI review and improvement

I review existing reports, semantic models, or planned Power BI solutions and identify specific issues affecting usability, maintainability, performance, or reporting consistency. This can be a focused second opinion before a larger investment or the starting point for improving an existing solution.

Typical deliverables: a written assessment, prioritised recommendations, the reasoning behind each recommendation, and practical next steps.

Governance

Microsoft Fabric architecture and governance

I support workspace and domain design, ownership, naming conventions, access boundaries, governance assessments, and adoption planning in Microsoft Fabric. This is most relevant when Power BI reporting depends on a wider Fabric implementation or when the tenant structure has become difficult to manage.

Typical deliverables: a current-state assessment, prioritised recommendations, and a documented workspace, domain, ownership, and governance model.

Build

Custom data and reporting tools

When a recurring data, reporting, or governance problem is not well served by an existing product, I can design and build a focused software tool. GovernView, for example, analyses a Microsoft Fabric tenant and produces a prioritised governance report. DataBrief tracks Microsoft Fabric product releases and related updates.

Typical deliverables: the working application, its source code where the tool is built for you, setup and operating documentation, and a structured handover.

How we work together

Each project is adapted to its size and purpose, but the working principles remain the same: clear requirements, an agreed scope, visible progress, documented decisions, and a structured handover.

  1. 01

    Introductory call

    We begin with a short conversation about the reporting need, the current situation, and what you would like to improve. There is no charge or obligation. The purpose is to establish whether the work fits my expertise and whether it makes sense to continue.

  2. 02

    Discovery and requirements

    I speak with the people responsible for the data and the people who use the reporting. We review the current reports, source systems, business definitions, and any known problems so that the requirements reflect the actual working environment.

    For a focused assignment, this may be one meeting. A larger delivery project may require several workshops.

  3. 03

    Agreed problem and outcome

    I document my understanding of the problem, the expected result, and the main requirements. We review this together before the delivery scope is finalised.

    This is the point where misunderstandings are corrected, while changes are still inexpensive and straightforward.

  4. 04

    Scope and delivery plan

    Once the requirement is clear, I define the scope, deliverables, sequence, responsibilities, timeline, and cost. For larger projects, the work is broken into visible tasks and tracked in Azure DevOps or the client’s preferred project tool.

    You can see what has been completed, what is in progress, and what comes next.

  5. 05

    Build, review, and handover

    I deliver the work in reviewable increments rather than waiting until the end to present the complete solution. You can inspect the reports, model, or recommendations as the work progresses and provide feedback before the next stage.

    Important decisions are explained and documented. At handover, you receive the completed deliverables and the information needed to use, maintain, or extend them.

Have a reporting or data problem to solve?

Tell me what you are working with, what is currently causing difficulty, and what you would like the result to look like. I will reply personally and let you know whether I am the right person to help.

Email Use the form below