What the first 90 days really look like, and how to make them count

Most manufacturing rollouts begin with genuine ambition. Better visibility, faster follow-up, a stronger foundation for improvement work. The goal is usually clear.

What’s less clear is how to get from “system is live” to “system is actually part of how we work.”

That gap is where most initiatives lose momentum. The technology itself is rarely the problem. What tends to be missing are the organizational conditions for adoption, or they were never properly set up to begin with.

McKinsey’s research on the Global Lighthouse Network found that at least 70% of manufacturers end up stuck, unable to scale digital initiatives beyond the pilot stage. Company culture is consistently identified as the biggest obstacle, alongside missing fundamentals like strategic direction, the right capabilities, and clear incentives for people to make the change happen.

The first 90 days are where those fundamentals either get built or get skipped.

‍

What the best rollouts have in common

Through years of deploying Factbird, a pattern emerges. The sites that see the biggest gains in their first 90 days aren’t necessarily the ones with the most data. They’re the ones that consistently do five things.

• They create one source of truth. Everyone, from operators to managers, speaks the same language and understands what the data means for their part of the operation.

• They trust the data. Teams are trained early to report downtime accurately and measure performance against real baselines, not optimistic ones.

• They use data in a structured way. Data lives inside meetings and problem-solving sessions. Those meetings stay short and focused.

• They act on what they find. They identify their biggest losses first, go after the quick wins, and fix root causes rather than symptoms. Improvements are tracked through the data itself.

• And their leaders are visibly engaged. Gemba walks happen, wins get celebrated, and feedback loops close. When management is present on the shop floor using the data, improvements accelerate.

‍

Why the early stage is harder than it looks

A rollout doesn’t gain traction simply by installing the software. It earns its place when people start using it to understand performance more clearly, and when that understanding starts shaping their daily decisions.

That sounds straightforward. In practice, it involves three groups of people with different stakes and different definitions of success. They don’t always agree on why this is happening or what good looks like.

Leadership wants evidence that the investment is paying off. Plant and operations managers want something that helps the line run better without adding overhead. Operators and line teams want less confusion, not another system to feed.

If those expectations aren’t addressed early, the gap shows up fast. Supervisors keep running shifts from whiteboards, and the new system gets treated as an administrative burden rather than a source of truth. Getting all three groups on the same page before the rollout begins is the single most underrated part of early success.

‍

The conversations that need to happen first

Before you define scope, configure dashboards, or go live on a line, five questions need clear answers across your team.

1. What problem are we actually solving?

Name a specific problem that people at every level already recognize. A recurring source of downtime. Stop reasons that vary from shift to shift. Output that gets discussed every week but never gets measured consistently. A concrete starting point gives the rollout weight. It connects the system to something people are already motivated to fix, which is what separates engagement from compliance.

Push for the one or three problems that, if fixed, would make the biggest difference. Getting specific here forces clarity and creates alignment before a single change is made.

2. What will actually improve?

Most rollouts skip this step. Setting a KPI, a baseline, and a real target turns vague ambitions into something you can measure. It’s also the moment where teams start believing improvements are possible. Without it, success stays undefined, and undefined success is easy to simply declare or simply abandon.

3. What could slow this down or get in the way?

Bad data, skeptical leaders, a meeting culture that doesn’t stick. Identifying obstacles early is a promising sign of good preparation. The sites that surface these honestly before go-live move faster than the ones that discover them after.

4. Who owns what?

A rollout without clear ownership will drift. Change management is consistently treated as an afterthought in manufacturing organizations, even though it’s where adoption is actually won or lost.

Ownership means specifics: who is responsible for keeping definitions consistent across shifts, who reviews losses weekly, who escalates when the data stops making sense, and who has the authority to act on what the data shows. These questions need answers before go-live, not after.

5. What does success look like at 30, 60, and 90 days?

“Improved OEE” is too abstract and too slow to serve as early feedback. Early success looks more like: registration is consistent across shifts by week three. Weekly follow-up is happening and producing actions. The top three recurring losses have named owners by day 45. The team is reviewing the same numbers and drawing the same conclusions, rather than debating the data in every meeting.

Those are the signals that tell you whether the rollout is gaining traction, long before you get anywhere near a meaningful OEE movement.

‍

What gets in the way on the shop floor

Even when those conversations go well at the management level, adoption can still stall on the floor. Three patterns show up repeatedly.

The first is registration friction. If stop registration takes more than a few seconds, operators under pressure will find shortcuts. And operators are always under pressure. Inconsistent registration means inconsistent categories, which means each shift ends up with its own interpretation of the data. You still get numbers, but they don’t mean the same thing across shifts, so you can’t follow a loss from one day to the next.

The second is scope creep. Scaling often proves a bigger hurdle than getting started, and it’s a key reason digital projects fail. In the early phase, the temptation is to connect more lines, add more dashboards, and track more things. Coverage looks like progress, but that’s rarely the case. The real measure of a rollout is whether the data is shaping how people work on the lines already live, not how many lines are connected.

The third is the absence of a follow-up rhythm. Data without follow-up is just a report. The teams that build momentum early establish a short weekly cadence around their top recurring losses, assign owners, and actually close the loop. The cadence doesn’t need to be elaborate, but it has to happen every week.

‍

What experienced operators know that leadership often misses

Experienced operators resist change for specific reasons, and those reasons are usually valid. They’ve seen past initiatives launch with enthusiasm, only to watch them disappear six months later. They know which problems actually matter and which metrics are being watched for the wrong reasons. Their endorsement carries more weight with peers than any management directive.

When experienced operators are involved in the design of a rollout, rather than just informed of it, adoption rates climb significantly. Involving them early, in naming the problem, defining stop categories, and testing the registration workflow, does two things.

First, it improves the quality of the setup. Operators know things about how the line actually runs that never make it into planning documents.

Second, it turns potential resistors into advocates. People support what they help build.

The short-term gain is better data, faster. The longer-term payoff is a team that holds the system to a higher standard because they understand why they’re registering and what happens with the data, rather than one that registers because they have to.

The 90-day window is the whole game

The reason the first 90 days matter more than most teams expect is that they set the conditions for everything that comes after. A rollout that builds trust in the data and a consistent follow-up rhythm in the first three months can sustain and expand. One that skips those steps, racing to more lines, more metrics, more coverage, tends to plateau and then requires a difficult reset.

We looked at data across hundreds of production lines and found that OEE typically moves from around 45% at baseline to over 53% within 90 days when the early fundamentals are in place. The operational changes behind that number are concrete: around 34 minutes less downtime per day, production speed up roughly 9%, cycle time down 8%. Those gains come from teams using the system to see what’s actually happening and doing something about it consistently, week after week.

That’s what the first 90 days are really about. A team that trusts the data, knows what to do with it, and has built the habit of closing the loop.