Insights · Leadership

Why Disengaged Teams Need Better Workflows

A quality system can satisfy compliance needs while everyday work still breaks down. Larry Mager explains how leaders can connect processes, people and the demand coming from the market.

MedTech + Consumer Health · Stage 4: Proposal to Close / Plan to Start · Leadership

Short answer

How can leaders improve engagement while making the business work more consistently?

Larry Mager says leaders should define the work, build compliance into the process and help people execute it together. He recommends aligning executives around the whole business, connecting revenue signals to operations and giving people clear roles in shared workflows. Listening to the people doing the work is central to that approach.

A business can have a quality department and still make everyday work harder than it needs to be. Larry Mager says compliance is only part of the picture. The way work moves between people, and whether those people understand their role in the outcome, also determines how well the organization functions.

Larry is founder of Mgmt-Ctrl. He spoke with host Terry Coutsolioutsos on the Zero Friction Podcast about applying a process perspective across the business. His examples connect executive alignment, revenue operations and employee engagement, with particular attention to what leaders learn from the people doing the work.

Why isn't compliance enough to make work run well?

Larry distinguishes what he calls big Q quality, focused on compliance, from little Q quality across the business. He wants leaders to look at how well the organization functions, rather than assuming that a quality group owns every problem.

His starting point is a defined process flow. Compliance should be built into that work, so people are executing a process designed to meet its requirements. He then separates variation in the work from variation in the workforce. Defining the process makes one part clearer, while people still need training, skills and support.

He describes business operations, or BizOps, as an area that can receive less attention than manufacturing. The organization may control its physical production well while leaving other workflows fragmented. Larry wants the quality of those processes and the quality of people's participation considered together.

What must the executive team agree on?

Larry says leaders are often promoted because they are strong within a domain. At the executive level, they may still have that function to run. Taking off the domain expert hat and looking across marketing, research, quality and operations can be difficult.

His analogy is a team moving from separate boats into one boat, rowing in the same direction at the same cadence. The point is shared management of the business, rather than parallel functions that happen to communicate.

He connects alignment to the theory of constraints. The part that limits the business most determines how fast the whole system can move. Executives should understand current operational capability, capacity and cost, then identify the main constraint they could improve. That creates a shared target instead of several independent improvement agendas.

How should revenue operations connect to delivery?

Larry defines RevOps as the externally facing work of marketing, sales and customer support. He says companies can invest in growing revenue while failing to build the internal processes needed to meet the demand. The result can be a gap between what the market wants and what the organization can deliver.

He would focus on translating forecast demand into actual demand that operations can use. His manufacturing example is building too much, storing it and eventually throwing product away for financial reasons. The signal from the market has to connect to operational decisions.

He also says some companies contract out manufacturing, leaving business operations as the work they directly manage. Passing a signal straight to the manufacturer can overlook logistics and the sequence of work inside the business. Larry wants that wider chain understood, whether the offer is a product or a service.

What makes a workflow useful across teams?

Larry recommends process flows with defined roles at each step. People should know what they receive, what requirements the incoming work must satisfy, what they do and how their output connects to the next person. That makes the interaction between functions visible.

He gives the example of accepting work that has already been verified against requirements, then completing one's own part within the timing the process needs. The person can see the sequence, rather than thinking only about a task assigned by a boss.

He is also careful about applying the same controls everywhere. Larry describes marketing as less mechanical and says he does not want rigid control placed on its creative work. The process needs the right level of structure for the work being done, while preserving coordination with the rest of the organization.

How does that structure connect to engagement?

Larry cites an employee engagement level of 20 percent while describing the problem. That is a figure he gives in the interview. His response is to focus on both processes and people, rather than treating low engagement as a separate issue for the workforce to solve alone.

He says people need a career, a community and a cause. A process can provide a community because people depend on one another to produce an outcome. He says remote workers can be part of that community too.

The cause becomes clearer when someone sees how their step contributes to the overall result. Larry contrasts that with completing a job only to satisfy a manager. His model gives people a reason to care about requirements, timing and the person receiving their work.

What should leaders listen for before redesigning work?

Larry says he would advise his younger self to spend more time listening to how people do their work. As an engineer, he could focus on the process and assume that a redesigned version would be welcomed. That missed knowledge held by the people performing it.

His example is assembling anesthesia trays with common layouts and many components. Staff complained about how information reached them and how feedback was delivered when they made a mistake. He says those were problems that could have been fixed readily.

People are the most important part of anything.

Larry Mager

He connects ignored complaints with disengagement. The practical work for a leader is to value the input, understand the handoffs staff experience and use it when improving the process. A clearer workflow and a more engaged team are connected parts of the same management task.

Where this fits: stage 4 of the revenue funnel, Proposal to Close / Plan to Start. Read what revenue friction is and how it is measured. See how RevRx AI works with MedTech teams and Consumer Health practices.

Full episode transcriptAbout 4,900 words

From the episode captions, lightly cleaned. Speakers are not labeled, and the text may contain small errors. Time links play the episode from that moment.

0:00 In MedTech, the difference between a good quarter and a great one isn't always the product. It's the friction standing in the way. Broken sales cycles, misaligned teams, deals that stall at the finish line. Every leader feels it, and the best ones know how to remove it. Welcome to Zero Friction, the podcast where we go inside the minds of MedTech's top commercial leaders to uncover the real barriers they face, the decisions they make, and the systems they build to keep the revenue moving. I'm your host, Terry Coutsolioutsos. Let's remove some friction. Well, welcome, folks, to the Zero Friction podcast. My name's Terry Coutsolioutsos, and I have um the great opportunity today to be with Larry Mager.

And Larry is the founder of a company called Mgmt-Ctrl. Larry has been involved in the medical technology space for um a couple decades now, and has had his footprints on the quality and the quality of the products that come into the marketplace. So, so Larry, if you could, just kind of give us a couple minutes about yourself, number one, and then a little bit about your experience, and and a little bit about what you do today. Sure. Thank First of all, thank you. I very appreciative for this opportunity.

As a young engineer working for a Fortune 500 business where I learned engineering, and I learned it from multiple facets, uh quality engineering, manufacturing engineering primarily. But, of course, we always touch on design engineering. Most importantly, in that business, I learned before they really called it Six Sigma, I learned Six and Six Sigma and and Lean methodology. That company, I was lured to Silicon Valley. It was in a couple of different startups, one of which I was the fourth person in. Um I have some patents from that position where I had to do design work, I had to do manufacturing work. Um I had to build the quality system, so I I was able to learn quite a lot about the holistic approach to business. Went back to the Midwest as a um head of quality for another Fortune 500 company, and we had some significant FDA activity across the corporate landscape, and I was the head of quality at one of the 22 manufacturing sites, and the FDA wanted us to have a corporate quality solution,

Not all the fragmented and disparate solutions that were within the business. So, we created one corporate quality solution, and we had to roll that out, and we were able to lift the warning letter in record time. But, I also learned there that there was a whole 'nother aspect to being a leader in quality space at the time, and that was I I didn't want to just sit in any quality system. I wanted to make it work or try to make it work with all its shortcomings. I wanted to help businesses make their systems better.

2:56 And so, from that point in my career, I every role I had was really in some way or another associated with FDA remediation activity. Although, some of the roles I was asked to take internal positions, and I did at executive levels, which was also insightful because um at the executive level, I could see some of the the back room turns, and and it helped me to grow quite a bit. Um I Right, and it's a great story career, and it's built around quality. And those of us that have been in the medical device space for any number of years know that, you know, the world is not perfect, and there's certainly all of these opportunities for improvement. Some of the Six Sigma processes that that you brought to the industry have really kind of helped to shape how quality, and not is not just fixing a problem, but creating a foundational solution for organizations in general, correct?

Yes. So, give us a little bit of history like how you move from like fixing a situation, right? How do you move from the situation to like a broader guideline or corporate stance on how to manage quality, perceive or preserve quality moving forward? Yes. First of all, a lot of organizations, they typically have quality groups that are big Q. I call that big Q. And they're more compliance focused. And sometimes I think the business, the people in the company, and the business leaders will say, "Well, quality is a problem." And that's not thinking quality little Q. And so, the first thing is to get people to understand that the quality of a business is dependent upon how well that business functions. So, the quality of the the work process, typically which is embedded in procedural systems, needs to be transformed into the concept of a process flow where the work is well defined, including compliance.

But if compliance is built in, then what we're looking for is quality execution, I'm sorry, compliant execution from the workforce. So, you're from an engineering perspective, you're locking down one degree of freedom. In In essence, the variation associated with what the work is. And you're managing the variation associated with the workforce. So, good work process, and then work with people. And people are the variation. And much more complicated on the people side than the process side because we're more complicated, people. We have variation between us. We have variation within us. One day we're better than another. And our lives are constantly in flux, and so being able to get an engaged workforce that is skilled, trained, and competent to execute work as it's defined in a compliant manner, to me, that's the ultimate in getting an organization refocused in the way that they have to move.

6:06 Um we had an exciting beginning, too, I think in your career. You talk about the impossible balloon, right? You want to tell us a little bit about that story and um you know, kind of how that probably led you into you know, a new direction, as well? Sure, without a doubt. In that case, there was a um minimally invasive product that was going to be used for what was still an emerging market that eventually created the da Vinci robot, but there were a couple companies back then, and the concept is the robots would do a cardiovascular surgery through a rib cage. And this was when I was in the four-person company. That device was to be inserted in the femoral artery and go all the way up your iliac tree and transcend the aortic arch into the ascending aorta, where a balloon would occlude the aorta, deliver cardioplegia, and and then would also perfuse the patient, so they were stable without cracking open the chest.

What was interesting was of of all the changes for manufacturability, design, things like that, the biggest was the balloon. So, we need a balloon that was a beer can-shaped balloon. And that was very important for the stability of the catheter in the patient. What we found was there were balloons that were created that are called plastic, where they had the primary shape, you can get that kind of barrel shape, but they couldn't flex too much versus a So, those are non-compliant plastic versus balloons that were created from compliant material and we needed something in between and there was a wide gap. So, what we did is we we we didn't actually ignore the limits of the other two, but we were trying to explore what was between because we knew we had to have something in between.

Is it safe to say that this is the first semi-compliant balloon product in the marketplace then? It was labeled people said it was the first uh we called it the beer can shape, but when we showed it to physicians, they were floored. I don't know if it's been done since, it probably has, but it was the first beer can first balloon that could be blown up and retain a beer beer can shape so that it would do what we wanted to do. So, at the time it was novel, we have patent. Um I had about 140 design changes and my name went to the front of that patent because of um So, yeah.

8:41 That's pretty exciting. So, now um So, where did that leave you next then and so, you know, I know you've had some great careers around working for Boston Scientific, you worked for Baxter, some really major what I would consider front edge leading edge companies that in a lot of ways changed the health care the way health care is delivered in a lot of marketplaces. Yeah, and not only that, but those are some of the Fortune 500 level companies, but going to a startup with where I was the fourth person in.

Uh I didn't think about it at the time, but I had a a wide array of experience and I spent a lot of time working with contract manufacturers. I was able to see a lot of manufacturing operations and I really came to an understanding that business is varied and complex and but every every business entity can be in terms of its manufacturing and scale and everything can really be summed up by the technologies that they use. They're all different, but one thing every business has in common is this arena that I call BizOps or business operations and BizOps is shortened for that. So, it's not related specifically to the manufacturing environments which are often far ahead in terms of how they they're managed than the BizOps environment for any company.

And I And I blame some of that again Now, this is med device heavy because I spent a lot of my time in med device businesses, but I blame some of that on the environment of compliance. The quality group and I was the head of quality for various companies, the quality group is charged with compliance. They're not charged with little Q quality. So, that's typically a handful of small subset of processes within the larger subset or the ecosystem of BizOps processes. And so, unfortunately, one of the things that was maybe the biggest learning was that while the manufacturing environment is well taken care of, I won't say the compliance environment is always well taken care of. That's why there's a lot of recidivism, but what was lacking was the concept of building quality into all of the processes within the ecosystem. And then the other big aha moment I had really more later. I was really focused from an engineering mindset on the mechanistic stuff, the processes, and how do you rebuild a

11:15 System? And that's great, but I alluded to the other part which is the people. There's levels of engagement. There's engaged, disengaged, and actively disengaged. And And that's at a high-level. They said the level And you want your employees to be engaged, fully engaged. And that's at 20% right now, which I think is an all-time low in industry. So, what businesses need to do to focus on the quality of the business is to focus on the quality of the processes and the quality of the people. And one last note, this links to the market because the other the other area that I didn't speak to is RevOps. I I break a business down into those three areas.

RevOps is the marketing, the sales, the customer support that is external facing. But often, and I've seen this way too often, you have RevOps initiatives funded by the business to grow revenue. But because the business isn't managing the BizOps area as they would a manufacturing area, they often have disconnect between scalability. Some companies don't even have their own manufacturing. So, BizOps is all it is. You have contracted manufacturing ops. So, businesses that are have not built a well-oiled machine in terms of process, workflow, and people can struggle to meet the demand in the market. And that's when you see a lot of the problems occur, and the worst of which is you failed to meet a market demand, and you you lose that market.

So, there's That's my view of business, what I've learned from this the different businesses I've been in. I think you just you brought up a really good point is that, you know, many times when you talk about control and quality control, everything reverts into the cap environment or the manufacturing environment, and they don't always look at the business environment. And I think you're bringing up a great point that, you know, business operations needs needs its own quality control mechanism as well, which is which leads us into management control, which is your company. And so, give us a little background on what your purpose is as a company from a management control perspective. And then I know that you and I spoke a little bit around the five phases and what that means and and how not only can you help benefit companies from a quality control manufacturing perspective, but also from an operation side of it.

Absolutely. So, I talked about some of the things I learned. And as I was working at executive levels and I mean at the you know executive of corporate as SVP level, but I've worked for organizations with SVPs as well and it was able to interact with the SVP groups. One of the things I recognized is that the reason these organizations don't run themselves end to end in the way I just previously described is because the executive team is not necessarily aligned. My and and this was the biggest gap I had when I went from and every leader goes from being really good in in whatever domain and that's why they get promoted up. They had success at one level, but when you go to that executive level and you're still and often times a VP will sit on the executive team and still have their domain to run.

14:40 It's very hard to take off the domain expert hat and put on a business hat that is cross across the board. So, that the marketing and R&D and quality and operations people are all working together. And the analogy I use is instead of you being in different boats that are rowing in somewhat the same direction, you get your executive team in one boat rowing in one direction and at the same cadence. And it sounds easy, but it's not. Executive alignment is very significant. So, the intent of management control is to be able to provide a solution for businesses to go from where they are today to where they need to be tomorrow. And it most importantly within this digital age of technology, we've had you know, you can go back and look at all the way from Henry Ford in the industrial age and what was prior to that. And then you can look at what these huge shifts that came after that, the internet of things for example was

Another type of segmentation of the ages. And then finally around the twins, there was this digital age of technology. And it really got done well in manufacturing environments. A lot of money was poured into AI-enabled technology and how that could be used and ERP systems. But it really wasn't done well across the business as it was intended. And so that's where there's still work to do that can really make businesses run themselves, help the businesses run themselves better, align the executive team, and make big shifts. For example, instead of everybody doing their own thing more like a John Wayne character, they're working together as an executive team to understand what the theory of constraints is, which is anything that is inhibits your business the most is the fastest your business can go.

And so if if they were in line, they would not only know what is the operational capability, capacity, and cost that consistently satisfies the current market demand, and every business needs that, that's their mission. But they would also know based upon new and upgraded technology what is the systemic operational constraint. And in that way, they can go target that constraint to open it up and create more capability, capacity, and cost that can be sold by the RevOps organization into the market. And again, I think you and I were having a pre-chat just around this topic a couple days ago, and let's talk about something that's maybe closer to the business, and you know, I think manufacturing's always important, too, but for my listeners, a lot of them are commercial leaders, and let's talk about how we can bring quality control mechanisms into the revenue side of business, where there are leaks, and there are there's friction, and there are there definitely opportunities for better processes, better ways to manage

17:52 Things on a consistent basis. Any thoughts there? I would say, first of all, that I am am a believer that revenue ops RevOps um or operations are um they're less mechanistic. And I'm usually don't like to place a lot of rigid control on the creative side of marketing and things like that. Sales obviously gets to be can be very mechanistic. So, putting the right level of process flow and working with those groups, you have to be a little more sensitive than an operational group. But, where I would focus in the RevOps environment is the ability to really translate forecasted demand into actual demand that operations can engage with. And I'm amazed how many times operations is really running off forecast boundaries things of that nature, and then you run into these problems of with a manufacturing operation, for example, um you don't want too much built that you have to store in a warehouse, and then I see companies throw product away, and it's a financial thing. It has nothing to do with the

Product. Um so, I would say the continuity between or coherence between what RevOps is doing in the market and what the operations business is doing needs to be strengthened. The two have to work hand in hand. A lot of people jump right over the biz ops and they think of the product if it's going if it's product. Sometimes it's not even a product, it's service. But if if it's product, they just send a signal to manufacturing. There was a lot of logistics involved and sequence interaction between the business the people in the business and and the work that they did. And I just think while that was a very complex environment, I still don't see that kind of sequence and act and interaction, mainly because you it's the old when I said the John Wayne and stand what I meant and I should have followed on versus say a Jimmy Stewart who would have more of a conversation. I know I'm dating myself.

But it's if if you have a leader that says this is my functional group, my silo, my domain, I'll run it the way I want. You typically have several things going on. So there's while there is communication cuz people do, it's not set out in terms of the the concept of sequence and interaction. What I like to see is process flow with defined roles at each process step. And that gives you a couple of things. It gives you continuity between different functional groups because everybody works in one process within an ecosystem, one process at a time.

20:35 And then it gives you the ability to to look for business outcomes. People need three things and this is tied to that people part, right? They need careers and they get a job and they make money and that's great. They need to work within a community. The community gives them what one of the things people need, but people if they're working on their own in a business, it's also very difficult. So even remote workers can fit in a process community, process level community within the ecosystem community.

And then the final thing is cause. And so now instead of being focused on my job that I do because I'm satisfying my boss, I'm focused on a process workflow that I can see where it is at in terms of its sequence. And when it comes to my step, there's an interaction where I accept work that was verified to be where the requirements were satisfied. And then I can take that work and I do my part and I'm understanding that there's timing to it, tact time in in manufacturing parlance, but there's timing to it. And so I'm invested in working within the boundaries of what that process needs to satisfy my community, to satisfy the outcome the process provides, and it to be a part of the larger sequence and interaction of the ecosystem. So linking RevOps and the signal from the external market to the internal BizOps is really important.

He's said a couple things that resonated with me. Number one, we we talked about teamwork and having teams work together and I think that's one element. The other would be and how do you do that? Even others the subjectivity component with sales and marketing that you brought up where it's more individualistic and less process oriented, but having been involved in the sales and the marketing and the commercial operations aspect for Fortune 500 companies over the last 30 years is that what I've learned is that when you create guidelines and consistent patterns of workflow that it allows for more fractional intake.

You can have people step in and do certain things because there is an SOP. So this is where I really think from a quality management control perspective, there is a place in the revenue side of the business where this can definitely enhance consistency, it can enhance the volume that it can push through. You talked about having fractional support from different areas of the company where people can step in. Well, they can only step in effectively if they actually know what they're doing and when they should do it. And so, this is where these processes really lend itself very well. Yeah, Terry, I like what you said. See, the Rev RevOps arena to me is more fuzzy in terms of the type of work they do.

23:26 But, you said something where revenue goes out the door or revenue leaks because of that. And it it it makes sense. So, operationally revenue can leak from any aspect of the organization. So, I just think that goes back to that screwing down the degree of freedom of saying, "This is the work that we do and this is how we want it done." When you talk about teams and silos and working together, there are two things that I really see in kind of fall apart in Fortune 500 companies. It's number one, very few like if they're all speaking the same language, well, and I mean like definitions. Like everybody when when you say the word blue, everybody sees the same shade of blue, right? And you know, when you use a word like operation, that everybody understands what that word operation means inside of that company. So, again, common language is number one. And most big organizations, by the way, use acronyms and they try to confuse

Everybody. Where I see things fall apart is where communication and not having common knowledge of what definitions are really is where things fall apart. And so, again, it goes back to quality quality control, processes, guidelines, you know, building a glossary of framework of vocabulary that everybody should understand what every word means so that when you're talking and communicating together, that everybody actually understands the same thing. And so, I think these are wonderful things. I think that you brought a lot from a quality control on the manufacturing side that we definitely can bring into our revenue, revenue ops, marketing, and sales processes that can make us all perform more effectively.

If I could address that real quick. So, as I said earlier, quality, big Q, is compliance focused. You see great quality control typically in a manufacturing environment because it's easier tangible to the to the physical product. What we don't see is the quality control across the business operations and including the the RevOps organization as well. And I think that's what's what's missing in the leadership um alignment around a an infrastructure or a framework that gives you a high-performance management system. Executive leaders aren't necessarily the people that want to to solve all the problems, and we typically as people bring them all the problems. They actually need people to bring value in their role.

25:58 And so, what we need to be able to tell executive leaders at a high level is how is it all running? Not necessarily give them all the minutia and allow them to tell us what we should do. And that's a big shift as well that the right kind of high-performance management system can can bring modern digital age technology AI enabled. That's a great point, and thank you for that. As we as we close things up for today, number one, thank you for your time. Larry has been an honor to have you here.

I have a common theme question that I ask every one of my um guests on the pod on the podcast is that if you could go back and talk to your 22-year-old self with the sole purpose of giving yourself advice, what would that advice what what would today's Larry give advice to 22-year-old Larry? That would be more related to people interaction. As an engineer, we're trained to be very mechanistic and you're looking at process and you're looking at machinery and you're looking at requirements. And so, it's it's not flexible.

It's it's rigor and rigid and approach. A lot of things could have gone a lot better for me in earlier roles would have been if I would have spent more time listening to people. And in hindsight, I did spend time, but as I was listening, I don't think I was thinking about how they do their work. I was thinking about what work are they doing, focused on that process. And when people talk to you about how they do their work, I'll give you one example where it's not very mechanistic, it's putting together anesthesia trays and you have common tray footprints with many components that go in there. And the complaints that I would hear from the people that put together, they would complain about how the information came to them. They would complain about how the feedback was provided to them when a mistake was made. They would complain about things that that could have been readily fixed and and I so I would say, when people

Complain, and that's how we get to this level of disengaged workforce and nobody listens, it's bad. So, my younger self, I think I would spend a lot more time trying to focus on voice of the people doing the work. As I'm looking at the process and as I and I would interact back and forth more, I just thought, "I'll know a better way to do it and I'll put it together in a better way and they'll just love it." Well, there's a lot of information that you can't unlock from the tribal knowledge, right? That people have. And I think that's what I would counsel everybody from the beginning. People are the most important part of anything. Businesses don't run with a workforce that is under appreciated and disengaged. And so, that's probably where I would say spend your time really valuing people and their input.

28:59 Great. And I think, you know, every leader has a great appreciation for what you just said, too. So, it's a super reinforcement because without people, there is nothing. You know, just like most companies need three things to to operate. One is you need a product, two is you need processes to get those those products put to market, and the third would be is you need people to make it all happen. And so, that's a a great reminder for us all. So, so Larry, I appreciate the call today and the opportunity to engage you, and we look forward to bigger and better things from you down the road. I know you got a couple books that you've written, and you got some more that you're getting ready to sort of engage with, so we look forward to that next story.

All righty, thank you so much for the opportunity to speak with you today. That's a wrap on Zero Friction, the show built around one simple idea: remove the barriers and the revenue will follow. If today's conversation was valuable, please subscribe and share it with somebody who needs to hear it. That's how we will grow this community. I'm Terry Coutsolioutsos, a revenue architect powered by AI. Come find me at my website, myrevx.com, and let's talk about what friction is costing you and your organization. Until next time, keep removing the barriers and keep the revenue flowing.

This article summarizes views shared on the Zero Friction Podcast. Statements are the guest’s own and are not medical, legal or regulatory advice.

Next step

Is this friction slowing your revenue?

Take the Revenue Scorecard or book a free Discovery Call.

Free 30-minute call: a commercial snapshot of your business (one strength, weakness, opportunity and threat, prepped before we talk) and your top priority fixes.