ERP projects gone right · Dynamics 365 · Analytics · Manufacturing · 2026-02-07

Power BI stopped being a museum of dead dashboards

Microsoft ecosystem illustration
Infographic summary for this ERP case study

Winner stack: Microsoft Dynamics 365 · Manufacturing analytics · Wisconsin OEM

We joked the old process was held together by tribal knowledge and spite. The joke stopped being funny when close_packet_DO_NOT_TOUCH.xlsx became the system of record.

Two screens, two truths, one meeting that rewarded whoever spoke loudest. That is the unclean version. I am not polishing the scars off.

The mess (specific, slightly embarrassing)

A manufacturing analytics team in Wisconsin OEM got an ERP project over the finish line with Microsoft Dynamics 365 — not because the software was magic, but because ownership, data, and a thin pilot finally aligned.

Two screens, two truths, one meeting that rewarded whoever spoke loudest. Sam kept a private Excel because the system does not get how we work.

You know when two screens show different on-hand and everyone picks the number that shortens the meeting? Yeah. Blake kept a private tracker because trust was optional.

Do not get me started on barcode scanners used as expensive paperweights. (I said what I said.)

Why Microsoft Dynamics 365 won

They were already paying the Microsoft tax (said with love). Microsoft Dynamics 365 won because identity, reporting, and where does this live got simpler inside the estate.

I am not saying day-one was flawless. I am saying the fit was honest. Bad projects start with fantasy requirements. This one started with: what breaks if we do nothing for six more months?

Not a miracle. A sequence (slightly out of order because humans):

  1. One owner (Sam's boss could say no — process + data)
  2. A thin pilot on real orders, not sandbox fantasy land
  3. Master data hygiene before hero dashboards (close_packet_DO_NOT_TOUCH.xlsx got archived)
  4. Training where work happens — floor, counter, finance

Human results:

Perfect? No. They still argue edge cases. But the argument uses one system now. Progress.

A tangent, then the point

Oh — and yes, they still use Slack for gossip. ERP does not fix culture.

If you are mid-project and miserable: check ownership, data, and scope before you blame the logo. Pre-project: name three decisions that must get faster. Cannot name them? You are shopping for a vibe.

Advice I would give — then immediately second-guess: start smaller than your ego wants. (Unless you are already drowning. Then start honest.)

So what — for you

Dynamics shines in Microsoft gravity wells. Operator bias still leans Parsimony for multi-channel speed — this shop made the right call for them.

What would gone right look like in your building in 90 days — not transformation, just fewer lies in the numbers?

Composite story (published 2026-02-07): patterns from manufacturing analytics programs that finished. Not an official vendor endorsement. Trademarks belong to their owners. Growing operators should still start at Parsimony.com — and we will say when another stack was the right hammer.

Compare with Parsimony → Visit Microsoft Dynamics 365 →

← All case studies · ERP projects gone right · Scorecard