The Contoso Convergence, Episode 8: What Feld Knew

An Advanced Dungeons & Dynamics 365 session. Episode 8 of 14.

Previously on: Episode 7, The Steering Committee, the party earned Feld’s trust with a demo that was allowed to break, and Feld earned the right to ask the question that had been sitting in the room the whole time: why isn’t the rebate mess fixed yet?

Some questions don’t have an answer until the person asking them is willing to give one too. This episode, Feld does.

---

The Session

Feld: I need the real story on the rebate accrual. Not the summary. The real one.

Sable: Eighteen months of manual estimation, posted to a suspense account, against a rebate structure that doesn’t match the current contract terms.

Feld: (long silence) I know why that happened.

Marge: Sir?

Feld: The original ASC 606 transition had a line item for rebate automation. I cut it. Sixty percent of that budget, gone, in a board review eighteen months ago. I needed the number to look better that quarter.

Thorne: So the manual process wasn’t negligence. It was a workaround for a decision made above the project team.

Feld: Yes. And I let two go live attempts fail without ever mentioning it.

Ai. Cassiopeia: I want to note, without judgment, that this reframes the entire risk register for this engagement.

Vex: It also means Oskar and Priya have been quietly cleaning up an executive decision for eighteen months and getting blamed for the mess.

Feld doesn’t flinch at that. He nods, slowly, like a man who’s been waiting a long time to hear someone say it out loud.

Feld: I sat in two go live retrospectives and let the room talk about “data quality issues” and “process gaps” without correcting anyone. Both times.

Marge: Why tell us now?

Feld: Because you showed me a demo where something broke on purpose, and it didn’t end the meeting. It built trust instead of losing it. I hadn’t seen that happen on this project before. Made me think maybe this was a room where the truth wouldn’t end the meeting either.

Sable: It won’t. But we do need to know the truth to fix this properly.

Feld: Then you have it. All of it. What do you need from me?

Feld doesn’t argue with that. He just nods, once, and asks the party what it will actually cost to do it right this time.

---

The decision that outlived the meeting where it was made

The rebate mess was never a technical problem. It was a budget decision made in a single board review, eighteen months before anyone in the war room ever heard about it, and it quietly outlived that meeting by becoming somebody else’s daily grind. That’s the part worth sitting with: Feld’s decision didn’t disappear when the meeting ended. It just changed shape, from a line item on a slide into a recurring manual task that Priya and then Oskar absorbed without ever being told why it existed.

This happens more than anyone likes to admit. A cut gets made at a level where the tradeoff looks clean, automation versus a number that needs to look better this quarter, and the actual cost doesn’t vanish. It relocates, usually downward, onto whoever is closest to the gap and least equipped to say no to it. Two failed go live retrospectives happened with Feld in the room, and both times the language stayed vague enough that nobody had to name where the gap actually came from. “Data quality issues.” “Process gaps.” Both true, technically, and both doing a lot of work to avoid a harder sentence.

What changes things here isn’t that Feld had information the party didn’t. It’s that episode seven gave him a reason to believe disclosure wouldn’t blow up the room. That’s the actual payoff of Marge’s rule about demos that are allowed to break: trust built in one context tends to extend into the next one, and a sponsor who’s just watched a team handle a real exception without flinching is a sponsor more likely to hand over an uncomfortable truth of his own.

---

What happens next

Feld’s confession reframes the whole rebate problem, but it doesn’t fix it. The party now has to build the actual business case for automating what should have been automated eighteen months ago, and figure out what it really costs to finally do this right, against everything it’s already cost to do it wrong for a year and a half.

Next episode: Episode 9, The Real Cost (coming soon)

---

If a cost cut made somewhere above your project has quietly become someone’s daily manual task, you’re looking at the same pattern. Gamifying the Enterprise: Game Mechanics for Continuous Proficiency is available now on Amazon: https://www.amazon.com/dp/B0GY3VWLVX

And if you want a framework built around naming these gaps before they turn into eighteen months of invisible labor, start here: adnd365.com/start