The "Small Change" That Turned Into a Full Data Model Overhaul.

Stakeholders think it's one small change. Power BI developers know it's never just one small change.

Author

Glenda Carnate
August 21, 2026

Read time: 2.5 minutes

Stakeholder: “It is just a small modification.” Power BI developer: “I shall turn on the model now.” And the gap between perception and reality is huge.

The stakeholder made a minor request. The developer opened the model. Tables, relations, measures, DAX, and all the areas were modified. The developer sighed. The modification wasn't small. Stakeholders reach out with requests like this quite often.

3 Methods to Handle "Minor Change" Requests in Power BI

1. Ask what "minor" entails before you begin.
❌ Accepting vague requests.
✅ Inquiring: "What needs to be changed specifically? Which areas will be affected?"
Clarifying prevents scope creep.

2. Understand dependencies before implementing changes.
❌ Believing any change does not affect anything else.
✅ Reviewing all dependencies, relationships, and measures possibly impacted.
One change creates a domino effect.

3. Provide expectations to stakeholders at the outset.
❌ Claiming that it is an easy fix.
✅ Stating the following: "This involves multiple aspects of the model, so it will take time to implement."
Being honest helps avoid surprises.

💡Key Takeaway: 

Stakeholders will tell you it’s a small change. But developers know there’s no such thing as a small change. Set expectations before releasing the model.

👉 LIKE this if you have ever heard the phrase “small change” but knew it wasn’t small.

👉 SUBSCRIBE now to our weekly Power BI content to know the truth about stakeholders.

👉 Follow Glenda Carnate to avoid being caught in the "small change" trap.

👉 COMMENT "SMALL" with the craziest “small change” request you ever experienced.

👉 SHARE this with a Power BI developer who needs support with boundaries.

Reply

or to participate.