Automating Intuition: Concurrency's Nathan Lasnoski on How Manufacturers Should Approach AI

Open on YouTube ↗
Overview

This episode of Manufacturing Happy Hour was recorded at Central Waters Brewing in Milwaukee. The taproom sits in a former chapel on the old Pabst Brewery grounds, a short walk from the Marquette University campus that both the host and the guest attended. The guest is Nathan Lasnoski, Chief Technology Officer at Concurrency, and the conversation turns on one question: what does productive, real-world AI look like inside a manufacturing business, as opposed to AI pursued for its own sake?

22 min read

Lasnoski's answer rests on a few ideas. AI should be tied to the mission of the business. Return on investment should guide every project. The best results come from pairing AI with human judgment. He also argues that the larger opportunity is not only producing more but freeing people from monotonous work so they can be more creative.

Putting on the "AI glasses"

Asked what it means to focus on productive AI, Lasnoski starts with the company's mission. Every business exists for a reason and aims to have some impact on the world. With AI, he says, businesses are going through "a new translation" of that mission and need to "put on the AI glasses" to ask how it changes who they are.

In his experience, these conversations often start out abstract. Many people still feel AI is "a little bit of science fiction" and aren't sure what it means for their business. He describes Concurrency's job as turning that abstraction into something tangible. In his framing, the value usually comes from one of two places:

  • New revenue, either through AI-enabled products or through how the company sells and creates opportunities with customers.
  • Operational savings in how the company produces.

On the revenue side, he describes customers building AI into boating products. The features help boat owners decide where to go on the water and where to tie up, see what the weather will be, and learn whether their boat's battery will last the month. These are layered on as premium services. On the operational side, he points to the balance between supply and demand. Many customers, he says, are still "banging away at spreadsheets" to match what customers need with what they must produce. He sees a chance to use AI "to solve a really old problem in a new way."

He calls the space "opportunity-rich," but only if companies make ROI their primary guiding light. At the same time, he wants them to step back and think broadly about the mission before narrowing into specific use cases.

Eight years in, and a memorable interview

Lasnoski says he is "not a Johnny-come-lately" to AI. Concurrency has been doing AI work for about eight years, and he hired the company's first data scientist around the time it started. He calls that "the coolest interview" he has been part of. The candidate had been using AI to predict how neurons fire in the brain, with the goal of helping treat tinnitus. Lasnoski remembers thinking it was "crazy and awesome all at the same time," and says it convinced him that AI could be "a vehicle to exponentially multiply the capabilities of the human person."

He says adoption was slow at first. In those years, companies had to "put a lot of chips on the table." Committing to AI meant staking their reputation and their relationship capital inside the organization. Concurrency's first project was supply-demand inventory forecasting. The next was what he calls "old school NLP" applied to quoting, to shorten the time it took to get quotes to customers. These projects showed him that AI was not only for academics or large efforts like weather forecasting. It was "real for a middle-market manufacturer."

Once the ChatGPT wave arrived, he says, those earlier stories became easier to share with companies trying to make AI real. After 22 years in IT consulting, he says he has never seen a technology move so quickly "to the heart of every organization." The envisioning sessions he runs are not held with a group of IT people. The president, CFO, VP of Sales, and COO attend, and they ask where the organization will be in one to five years and how AI changes the way they carry out the mission.

A forecasting case: $50 million in inventory efficiency

The host asked for a concrete example, and Lasnoski described a company that remanufactures ink cartridges. He calls it one of the largest in the United States, and it also handles cell phones. Its customers range from giants like AT&T down to small cell phone exchanges, so orders come in both large blocks and many small pieces. Someone behind all of that has to work out how many orders will arrive this week, where to produce them, and how much raw material is needed.

Lasnoski says every manufacturer faces some version of this problem: what am I selling, what do I need to make it, what did I pay for the inputs, and where do I store them? In his view, ERP providers have not solved it well. Most companies export the data to Excel or a third-party tool and work on it there.

He gives two reasons why that manual approach falls short:

  1. Intuition is sometimes the enemy. What feels like the right decision can turn out to be the opposite. He compares it to pulling money out of the stock market during a crash, when that may have been the moment to buy. Emotion, or pressure from the people around us, pulls decisions in the wrong direction.
  2. People aren't that good at math. Someone may know the business well, including seasonal swings and macroeconomic effects, but can't hold all the factors in their head and reach the needed precision.

AI, he says, can combine what people have intuition about with the pure data they can't have intuition about, and produce a more accurate forecast of incoming demand and the materials and costs needed to meet it. He reports that this company, at about $2 billion in revenue, saved roughly $50 million a year in inventory efficiencies and could redirect that money elsewhere in the business.

The timing mattered in his telling. The project started before the pandemic, when demand was fairly normal. When the pandemic hit, the company could use the model to tell a story: this is coming, so what do we do? It did the same on the way out. Lasnoski says this let the company go beyond predicting and prescribing to modeling possible future choices and how each would affect efficiency.

"Automating intuition" and the human-AI partnership

The host suggested that AI provides "objective intuition." Lasnoski said Concurrency uses a similar phrase, "automating intuition." He says there is nothing wrong with human intuition. Often it is just another input to the model. Someone who has worked at a company for 42 years knows things about how the business runs, and the question is how to feed that knowledge into the forecast.

In his view, the best results will always come from an AI-human partnership, not from either one alone. Projects like this one tend to prove that the model plus human intuition beats either by itself. The team does this by comparing the new predictions against the ones the company would have used before.

He adds a finding he considers important: most companies don't measure how accurate their demand and inventory forecasts are. "Vast majority of companies we talk to aren't," he says. So the first step is often just getting them to measure. After that, they notice that the model's output is "objectively better" than the choices they would have made. Then they start using it in planning exercises, and eventually it becomes the default.

At that stage, he says, the human's role shifts to validating and "shepherding" the model and adding data it lacks. Forecasting models "don't have eyes and ears." A model won't know that war has broken out in Ukraine and could affect sales somewhere. A person has to bring that factor into the model's "storytelling," and that combination, he argues, gives a stronger result.

The host linked this to themes the show often covers, such as the Internet of Things and digital transformation, where connecting separate systems lets companies measure and decide on things they couldn't see before. In the host's view, fear of AI often comes from headlines and ignores the small, steady improvements that new technologies bring.

The parallel to the Industrial Revolution

The host brought up a video in which Lasnoski described how the Industrial Revolution turned craftspeople into workers putting "a square peg in a square hole," removing the creativity they had brought to their work. The host asked how the AI revolution resembles that moment.

Lasnoski says the main similarity is that both take something that used to be done one way and replace it, sometimes gradually and sometimes abruptly, with an increasingly automated version. He uses the chair in front of him as an example: it was once built by hand from raw wood. Books were copied by hand before the printing press. Such activities needed a great deal of human effort. Automation let society produce "exponentially more," which lowered prices, put goods within reach of more people, and raised the general standard of living. He expects AI to do the same.

His example is a company with more than 600 sales reps. A customer would email a request for a quote on a complex product, and a rep would spend hours writing it up. In that business, he says, time to quote is one of the top predictors of winning the deal. The company used AI to take in the customer's request and automatically generate the quote, cutting the time from hours to a couple of minutes. For Lasnoski, the difference from the Industrial Revolution is that AI speeds up not just physical production but human processes, taking productivity further "than what machining had accomplished in the past."

The host said the parts of their own work they enjoy are creating, storytelling, and podcasting, not quoting or forecasting the next three to six months. If AI lets people focus on outcomes rather than non-core tasks, the host said, "I'm all for it."

Fear, monotony, and unlocking creativity

The second half of the host's question was how AI could unlock more human creativity. Lasnoski says you first have to deal with fear. Take any process AI can automate, such as someone matching a contract to an order and then to something else. The first question, he says, is how the person doing that job will see the change, just as a chair-builder turned peg-inserter would have asked how the change affected who they were.

He argues this needs a wider view than businesses currently take. Even with AI everywhere, the business leaders he talks to think in use cases, and sometimes in terms of their mission. They rarely consider that every employee will be affected, positively or negatively. He calls it a duty to make this "an opportunity to turn every person into the best version of themselves."

Over time, he says, people have come to see repetitive tasks as their job, and in some cases have "almost forgotten how to be creative." Many are uncreative at work and then go home to build things, make art, or knit. He sees that as the creative spirit escaping a monotonous job, and expects businesses to change as AI "eats up" the monotony so people can bring what makes them special to work. Exponential growth in production is good, he says, but maybe the real goal is whether everyone "can be the best versions of themselves." He believes that would open up new possibilities for manufacturers in how they serve customers and carry out their mission. It will only happen, though, if companies think about what their business will look like in five years, not just about one use case.

The host put this in Jesuit terms familiar to Marquette graduates: returning to one's vocation and what brings fulfillment. The host also connected it to side hustles. While living in the Bay Area and working at Rockwell, the host had enough income but still worked as a craft beer tour guide in Haight-Ashbury, visiting three breweries and talking about neighborhood history and the Grateful Dead. The host hoped AI might let people bring that side-hustle creativity and energy into their day jobs.

The questions executives should ask first

Asked what executives should be asking about AI now, Lasnoski again starts with the mission. Companies often get caught up in "how" before settling "why" and "what," he says. They need to begin with the why and the what.

Next, executives should separate incremental from disruptive opportunities. Incremental means doing what you already do, only faster: cutting quoting from four hours to five minutes, automating an hour-long task down to five minutes, or improving demand and inventory forecasts. He calls this a rich area and usually the first place companies go, "but it's not the moonshot."

The disruptive questions are more existential. He proposes a thought experiment: imagine starting the company from scratch, with no facilities, products, or employees, only the mission. How would you carry out that mission with AI as an asset? How would it change the way you go to market, sell to customers, and work with employees?

"The biggest thing that keeps us from disrupting is ourselves," he says. Companies that are profitable, shipping products, and delivering value find it hard to disrupt themselves. It only takes one competitor without their sunk costs and entrenched habits to reach customers in a transformative way, perhaps with a less feature-rich offering that meets them "exactly where they're at." He believes AI will enable that disruption, in the product itself or in how a company thinks about its product, and he wants companies to bring it to market rather than have it done to them.

A food distributor that becomes a service provider

His example of disruptive thinking is a global food distributor moving billions of dollars of food to restaurants, convenience stores, and similar customers. He describes the business as low-margin and cutthroat on price, and not very sticky, since a customer can switch distributors and get largely the same products.

Lasnoski says this company realized it is not only in food distribution. Through what it distributes, it knows what successful restaurants look like: what they buy and when, how their menus are built, and how they interact with customers. Restaurants turn over constantly, and he frames their survival as a problem of efficiency, presentation, and sales. The distributor can use its data to tell restaurants what they should be doing, adding a set of services that makes it more of a service provider than a distributor.

He says that service capability is much more profitable for the distributor and more useful to the restaurant. A restaurant can get food anywhere. A partner that can help more restaurants stay in business, and prove it against competitors, has "completely disrupted" how the industry thinks. The host added that the restaurant industry is known for high failure rates, while saying they couldn't recall the exact statistic.

Before applying AI: broaden the tent

Asked what companies should do before applying AI to specific problems, so they aren't pursuing "AI for the sake of AI," Lasnoski first stressed involving employees. Alongside executive alignment, companies need to "broaden the tent." He says many are afraid to bring the wider workforce into discussions about where AI could take the business, yet he believes every business should do exactly that. Employees need to help shape how today's business becomes tomorrow's, and many ideas should come from the grassroots.

The most successful leaders he has seen went "all in." They told the organization AI was part of the strategy and held broad envisioning sessions with accounting, finance, sales, production, and other areas to explore what's possible and generate ideas. A company may pursue only a small share of those ideas, and the moonshots may come from a select few. In his view, though, the process draws on the organization's creative power and "lowers the threat threshold" for everyone else, so they can focus on the opportunity.

Three requirements: sponsor, ROI, and data

Once a company starts choosing ideas, both disruptive and incremental, Lasnoski says each one needs three things.

A sponsor. Every idea needs a sponsor in the business area that will realize the ROI. Ideas don't go into production overnight and need ongoing support from that area.

ROI. Concurrency tells customers it won't take on projects that lack a return on investment, because there is "too much opportunity" to waste effort on AI scenarios that don't pay off. He says now is a good time to articulate, measure, and prove ROI, and that Concurrency has spent considerable time building ROI calculation tools to speed up proving it to customers.

Data, tied to the use case. He specifically rejects the "waiting for Godot" idea that all data across the organization must be ready first. He says some executives claim they aren't ready for AI because their data isn't ready, and he sometimes sees that blanket statement as a cop-out. Moonshot use cases may need deliberate work to prepare data, and he supports doing that. Meanwhile, many incremental ideas have data ready to use, such as the manuals supply chain reps use to resolve customer issues, or internal HR use cases. The question should be whether the data is ready for a particular use case. He argues this makes the data strategy "centric to value," unlike the "if we build it they will come" approach many companies took in the past.

From POC to production, and planning for scale

After use cases are chosen, Lasnoski says companies need realistic expectations about the proof-of-concept, pilot, and production cycle. Along the way they will need to iterate to improve accuracy and make the system suitable for real production use, and the ROI case is what justifies that work. "It's easy to put together a POC, it's hard to put something in production," he says. Once something is in production, ROI can actually be measured.

Last, he urges companies to think about scale. Linking one use case to ROI or the mission is easy. What surrounds all of them is the question of architecture at scale: how to govern it, apply safety, and secure it. He warns against two failures. Some organizations worry so much about governance before doing anything that they stall. Others get too far without building these controls into their process. He says governance should "come along for the ride" and be an area of investment, especially in large organizations that may run hundreds of use cases and need a consistent pattern.

The host summarized the points: ideas from the front line, a sponsor, ROI, use-case-driven data, and planning for scale. The host tied this to other guests' ideas, including doing a "lighthouse" instead of a pilot, and the "pilot purgatory" that trapped many projects in the past decade, where something was proven but couldn't scale. Lasnoski noted that the host was echoing previous guest Brian Evergreen, author of Autonomous Transformation, and his "pilot purgatory steamroller."

The bar to entry has dropped

In closing, Lasnoski made a point about accessibility. A few years ago, companies had to commit heavily to their first AI scenario. It still takes effort, he says, but the bar to get started has "been lowered dramatically." Now, he argues, even medium and smaller organizations can turn repeatable processes into automated ones sized to their scale, freeing their people "to be more." In the past, he felt he could only talk to enterprises, because only they could afford the investment and hire data scientists. Now, he says, more individuals are becoming AI practitioners using commodity tools.

"Rising tide" productivity, and the spell check analogy

His second closing point was that the conversation had focused on mission-driven use cases, those tied directly to what a company does, such as building boats, selling them, and helping customers enjoy the water. Alongside these, he says, AI will affect every organization through general productivity gains, a "rising tide floats all boats" effect that may matter less on the shop floor but will reach every other part of the business.

He compared it to spell check. Without it, you'd look up each word in a dictionary and retype it, or just keep sending misspelled emails. With it, errors get fixed automatically, sometimes without you noticing. The host said spell check is what they think of whenever they wonder whether AI is taking away skills people were proud of. They grew up with spell check, are probably a worse speller than their parents, and don't miss having to know every spelling.

Lasnoski called spell check a very basic form of AI and extended the idea to what Microsoft, Salesforce, Google, and others are doing for general productivity. How long does it take to write an email, build a presentation for a customer meeting, or put together a report? Can you ask your data a question and get an answer, instead of spending a day and a half building a dashboard to infer it? He says executives shouldn't overlook these gains, because they turn into percentages of freed-up time that leaders then need to help employees use well.

Training that goes beyond technical skills

Lasnoski's last argument returns to people. He says all of these gains, both general and mission-driven, depend on enabling employees "to be able to be more," which requires training that isn't only about technical skills. He thinks this is where efforts to move people forward break down: organizations treat AI as something to learn through colleges and courses. There is some technical skill-building involved, he acknowledges. More important, in his view, may be helping people "reawaken" interpersonal, creative, literary, or envisioning skills they haven't used in a while and need help unlocking.

He says that means looking at AI differently than organizations have looked at technology education in the past, where the aim was a technical skill for doing a job. In his framing, AI adoption is less about teaching a technique and more about helping people become more than they are now. That idea, from the Industrial Revolution parallel to the call to broaden the tent, runs through the whole conversation.