Finance wants net revenue redefined in a widely reused certified model, while Sales wants unchanged historical trends. How would you handle the change?

Question

This open-ended senior case assesses decision quality. Treats a semantic change as a contract with downstream users, separates valid alternative definitions from known errors, and balances compatibility against long-term trust and maintenance.

Accepted Answer

Example Answer

I'd establish whether Finance has found an error or proposed a new business definition. Those need different responses. An incorrect figure needs a correction and an explanation of the affected decisions; a legitimate definition change needs an effective date and a decision about historical restatement.

I'd use semantic-model impact analysis to identify dependent Power BI reports and their owners, then check important Excel and other consumers with the teams that use them. I wouldn't assume that the diagram is a complete inventory. I'd show representative periods under both definitions and explain what changed, including comparisons that would become misleading.

If both definitions remain valid for different purposes, I'd publish clearly named measures with documented meaning and an agreed transition. If the old measure is wrong, I wouldn't preserve it as an equally authoritative option just to avoid objections. I'd agree the decision with the metric owner, involve the authorized certification reviewers, and test critical consumers before rollout. I'd communicate the change and retirement date where needed, then check adoption so a temporary compatibility measure doesn't become a permanent second source of truth.

Make it your own

Senior-level, open-ended case. Several approaches can be defensible; explain your assumptions, recommendation, tradeoffs and what evidence would change your choice. Use a metric whose definition you understand and distinguish an error correction from a policy change. Identify who owns the business meaning and who can authorize certification in the organization. Describe historical restatement as a decision to agree, rather than assume every organization uses the same rule. For a mock interview, allow two minutes for your first answer, then 30 seconds to respond to the pressure-test twist. State what changed, your next action and what you cannot safely promise.

Why this works

This open-ended senior case assesses decision quality. Treats a semantic change as a contract with downstream users, separates valid alternative definitions from known errors, and balances compatibility against long-term trust and maintenance.

Interviewer follow-up

Sales refuses to migrate, and both measures are technically correct. Would you remove the old measure anyway?

I'd ask whether the older definition still supports a legitimate decision. If it does, it can remain with a distinct name, scope and owner; it shouldn't silently compete with the company standard. If it is only a transition aid, I'd agree a supported migration path and retirement date. Removal would follow that agreement and dependency checks, rather than surprise users.

Pressure-test follow-up

Finance confirms the old figure is wrong, but Sales says correcting it will change bonus calculations. The board pack is due tomorrow. How does that change your rollout?

I'd stop treating this as two valid definitions. I'd validate the correction for the affected periods and show Finance and Sales which decisions could change. I'd work with the responsible owner to hold affected bonus decisions rather than quietly change them myself. If the model correction isn't ready for the board pack, I'd offer a reviewed adjustment table with the error clearly explained, and agree when the corrected model and dependent reports will be released.

What this tests: A technical correction now affects consequential business decisions; the candidate must preserve truthful reporting while respecting decision ownership and a realistic release process.