The Leap Is Smaller Than You Think

Alex Titze

Why manufacturers stall on technology, and how to take the first step in 90 days

Plant team in safety vests talking on the manufacturing floor

Walk into almost any mid-sized plant and ask the leadership team about technology, and you'll hear some version of the same sentence: "We know we need to modernize. We just don't know where to start."


That sentence is honest. It's also the reason so many manufacturers stay stuck. The problem usually isn't money, and it isn't that the technology is too complicated. It's that "digital transformation" sounds like a single, enormous leap — a multi-year, seven-figure bet on the whole plant. Faced with a leap that big, most sensible operators do the sensible thing. They wait.


Here's the reframe we use at T to Z: the leap is smaller than you think. It isn't one jump. It's a series of short, deliberate steps, and the first one should fit inside a single quarter.


Why "transformation" stalls before it starts

When manufacturers tell us why they haven't moved, the reasons fall into three buckets.


The scope is too big. A leadership team decides they need an Industry 4.0 strategy. They commission a roadmap that touches ERP, MES, quality, maintenance, and the shop floor. The roadmap is impressive. It's also a two-year plan with no clear first move, so nothing happens on Monday.


The starting point is a product, not a problem. Someone sees a great demo at a trade show, or a peer plant mentions their new platform. The conversation becomes "should we buy X?" instead of "what's costing us money?" Tools chosen this way often solve a problem the plant doesn't have.


The floor isn't part of it. Technology gets decided in a conference room and announced to the people who'll use it. Operators, techs and supervisors see one more initiative that will pass if they wait it out. Often, they're right.


None of these are technology failures. They're sequencing failures.


Start with a problem that has a dollar sign on it

The best first step is almost never the most exciting one. It's the one that answers a simple question: what is costing us real money right now, and can we measure it?


Good candidates look like this:


  • A changeover that takes four hours when it should take two
  • A quality escape that keeps coming back because the fix lives in one person's head
  • Downtime that nobody can explain because it's logged on a whiteboard and erased at shift change
  • New hires who take three months to become productive because training is "follow Dave around"


Each of these has a cost you can estimate, an owner you can name, and an outcome you can measure. That's what makes it a good first step: not its size, but its clarity.


The 90-day first step

Once you've picked the problem, the first step follows a simple shape.


  1. Measure a baseline. Before changing anything, capture how bad the problem is today — hours, scrap, defects, days to train. Without a baseline, even a big win becomes an argument.
  2. Name an owner on the floor. Not just an IT sponsor or an executive champion, but a supervisor or lead who lives with the problem every day and wants it gone.
  3. Choose the simplest tool that works. Sometimes that's new software. Sometimes it's a shared tablet, a standardized checklist, or a dashboard on data you already collect. The goal is to solve the problem, not to deploy a platform.
  4. Run it for 60 days on one line or one process. Keep it small enough that the team can adjust quickly and visibly.
  5. Measure again and tell the story. Share the result in plain numbers with the whole plant. A modest, real win — an hour saved per changeover, a defect that stopped coming back — does more for adoption than any kickoff meeting.


Ninety days later, you haven't transformed the plant. You've done something more useful: you've proven that change works here, built trust with the floor, and generated the savings and credibility to fund step two.


Momentum is the strategy

This is the part most roadmaps get backward. They try to design the entire journey before taking a step. But in our experience, the clearest strategy emerges from early wins, not before them.


After your first 90 days, you'll know things no roadmap could have told you: how your people respond to new tools, where your data is actually trustworthy, which systems need to talk to each other, and what kind of vendor partner fits your culture. Step two gets easier and smarter. By step four or five, you have a real strategy — one your plant has already started living.


That's also why it pays to stay vendor-neutral early. When the first step is defined by a problem rather than a product, you keep the freedom to choose the right tool for each stage instead of bending your operation around the first platform you bought.


A few questions to take back to your team

  • What's the one problem we'd fix first if we only had 90 days?
  • Can we put a dollar figure on it this week?
  • Who on the floor would own it — and would they want to?
  • What's the simplest thing we could try that doesn't require a major purchase?


If you can answer those four questions, you're already further along than most manufacturers who are still "working on a strategy."


The leap to a connected, data-driven plant is real. It's just not one leap. It's a first step you can take this quarter.


—


T to Z Consulting helps manufacturers move from where they are to where they need to be: Industry 4.0 assessments, knowledge management, vendor-agnostic software selection and implementation guidance. Not sure what your first step should be? Reach out at atitze@ttoz.io.



By Alex Titze • November 16, 2026
Your most experienced people are a system with a retirement date. A five-step playbook for capturing tribal knowledge in manufacturing before it walks out the door.