{"id":70268,"date":"2026-07-31T05:25:11","date_gmt":"2026-07-31T12:25:11","guid":{"rendered":"http:\/\/www.enxmag.com\/twii\/?p=70268"},"modified":"2026-07-31T05:25:13","modified_gmt":"2026-07-31T12:25:13","slug":"what-happened-to-marco-in-1991-is-everybodys-business","status":"publish","type":"post","link":"https:\/\/www.enxmag.com\/twii\/dealers-choice\/2026\/07\/what-happened-to-marco-in-1991-is-everybodys-business\/","title":{"rendered":"What Happened to Marco in 1991 is Everybody\u2019s Business"},"content":{"rendered":"\n<p>I joined Marco in 2001, so I didn\u2019t experience what happened in 1991 firsthand. But it\u2019s not a story the company keeps quiet, and it\u2019s not one I\u2019d want to, either.<\/p>\n\n\n\n<p>Here\u2019s the unvarnished truth. In 1991, the U.S. went through a short but significant recession, and Marco failed to turn a profit for the first time. The bank threatened to call our loan. For a business that had already spent nearly two decades building something real, it was the kind of moment that forces a decision: cut your way to survival, or commit to building something that doesn\u2019t put you back in the same position. Not ever.<\/p>\n\n\n\n<p>Marco wanted to take the second path. Fortunately, around that time, a Japanese business philosophy called Kaizen was gaining attention in American manufacturing. The idea was straightforward\u2014continuous and incremental improvement, applied consistently, compounds over time. Toyota had built an entire operational culture around it. Marco decided to give it a try.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"610\" height=\"610\" src=\"https:\/\/www.enxmag.com\/twii\/wp-content\/uploads\/2026\/07\/Kaizen.jpg\" alt=\"\" class=\"wp-image-70269\" srcset=\"https:\/\/www.enxmag.com\/twii\/wp-content\/uploads\/2026\/07\/Kaizen.jpg 610w, https:\/\/www.enxmag.com\/twii\/wp-content\/uploads\/2026\/07\/Kaizen-300x300.jpg 300w, https:\/\/www.enxmag.com\/twii\/wp-content\/uploads\/2026\/07\/Kaizen-100x100.jpg 100w, https:\/\/www.enxmag.com\/twii\/wp-content\/uploads\/2026\/07\/Kaizen-150x150.jpg 150w\" sizes=\"(max-width: 610px) 100vw, 610px\" \/><\/figure>\n\n\n\n<p>The numbers turned around. More importantly, a way of thinking took hold that didn\u2019t leave when the crisis did.<\/p>\n\n\n\n<p>I bring this up not because it\u2019s a great origin story\u2014though it is\u2014but because I think the pressure dealers are feeling right now rhymes with what Marco felt in 1991. Margins compressing. Volume declining. The easy path visible and tempting. And the same question underneath it all: do you cut to survive, or do you build through it, think creatively and focus on continuous improvement?<\/p>\n\n\n\n<p>Continuous incremental improvement isn\u2019t always glamorous work. It\u2019s also difficult to do the opposite of what everyone else is doing, especially when times get hard. But continuous improvement is what we\u2019re still dedicated to. So I wanted to share a few more notable ways we\u2019ve gone about that over the past few years.<\/p>\n\n\n\n<p><strong><span class=\"has-inline-color has-vivid-cyan-blue-color\">A Creative Solution to the \u201cUnsolvable\u201d Technician Problem<\/span><\/strong><\/p>\n\n\n\n<p>This won\u2019t come as news: the copy\/print technician shortage has been with us since pre-COVID, but it\u2019s gotten worse. Experienced field techs are retiring. Fewer people are going into this line of work, and the pipeline of people who can replace the depth of knowledge required for advanced equipment is already at a breaking point.<\/p>\n\n\n\n<p>Most of the industry is struggling with it\u2014hiring where possible, stretching capacity where necessary, feeling helpless when they can\u2019t always meet their historic response times and losing clients as a result.<\/p>\n\n\n\n<p>We decided to approach it as a workforce design problem rather than a hiring problem.<\/p>\n\n\n\n<p>Our technicians now use smart glasses in the field. When a newer tech encounters something outside their experience, they can show exactly what they\u2019re seeing to a more experienced colleague in real time. The experienced tech guides them through it remotely. The job gets done, and the client doesn\u2019t feel the gap.<\/p>\n\n\n\n<p>What that changes operationally is also significant. We can put someone in front of a problem on day one who can handle it effectively, not because they\u2019ve seen everything but because they have real-time access to someone who has. It doesn\u2019t eliminate the shortage, but it changes what the shortage costs us and what we can promise a client about the consistency of service.<\/p>\n\n\n\n<p>The investment here wasn\u2019t just the technology. It was the commitment to building a service model that doesn\u2019t depend on a supply of experienced technicians that may not exist in five years. It was an investment and a significant change in how our techs operated. But we made it early and committed fully.<\/p>\n\n\n\n<p><strong><span class=\"has-inline-color has-vivid-cyan-blue-color\">Investments in Predictive Maintenance<\/span><\/strong><\/p>\n\n\n\n<p>For most of this industry\u2019s history, service has been reactive by definition. Something breaks, you dispatch. The metric is response time: how fast can you get someone there?<\/p>\n\n\n\n<p>We\u2019ve been moving toward a model in which the goal is to not need the dispatch in the first place. Predictive maintenance means monitoring devices, identifying failure patterns before they become problems and staying ahead of supply needs before the client runs out. The proof of it shows up in calls that never happen, which is genuinely hard to point to but very easy for a client to feel over time.<\/p>\n\n\n\n<p>Committing to this operationally required upgrading our software so we could offer this service to a broader range of devices. We\u2019re not the only ones who made this change, but we were one of the first. That means we invested before the return was visible\u2014and before clients expected it.<\/p>\n\n\n\n<p>That\u2019s a hard thing to justify in a tight quarter. It\u2019s a very easy thing to justify when you look back five years later at what it achieved.<\/p>\n\n\n\n<p><strong><span class=\"has-inline-color has-vivid-cyan-blue-color\">Infrastructure To Support Long-Term Service Goals<\/span><\/strong><\/p>\n\n\n\n<p>Late last year, we opened our 100,000 square foot logistics center in Des Moines, Iowa. The primary goal was to ensure two-day shipping to clients across the country, but we also wanted to create a better cushion to smooth out supply chain issues.<\/p>\n\n\n\n<p>That enormous building is a real commitment for a company that could\u2019ve kept operating the way it always had. But we\u2019ve learned over 50-plus years that the gap between what you promise a client and what your infrastructure can actually deliver has a way of becoming visible at the worst possible time. We\u2019d rather close that gap on our terms than discover it on the client\u2019s.<\/p>\n\n\n\n<p><strong><span class=\"has-inline-color has-vivid-cyan-blue-color\">Making Our Work More Visible<\/span><\/strong><\/p>\n\n\n\n<p>The investment I find most interesting to talk about is also the hardest to explain quickly. We\u2019ve designed an app that gives our managed services clients real-time visibility into their own tech infrastructure. It includes what they\u2019re running, how it\u2019s performing, what we recommend and data about our own performance. It\u2019s easy to see exactly how quickly we\u2019re resolving tickets and what devices are causing most of them.<\/p>\n\n\n\n<p>What changes when a client has that visibility? The very nature of our relationship with them. We\u2019re not asking them to trust our read on their environment; we\u2019re showing them their own numbers and helping them act on what those numbers say. The conversation shifts from a client taking our word for it to a client making decisions based on their own data.<\/p>\n\n\n\n<p><strong><span class=\"has-inline-color has-vivid-cyan-blue-color\">What Connects All of It<\/span><\/strong><\/p>\n\n\n\n<p>Smart glasses, predictive maintenance, a logistics hub, a client-facing data platform\u2014these look like separate decisions made at different times for different reasons.<\/p>\n\n\n\n<p>But they share a philosophy. Each one is an answer to the same question: what does it take to improve our services at a level that compounds over time?<\/p>\n\n\n\n<p>None of them were urgent when we made them. The technician situation was manageable. Service was working. Clients weren\u2019t asking for fleet data. The distribution network we had was adequate.<\/p>\n\n\n\n<p>The urgency came later. It always does. When COVID hit in 2020, businesses scrambled to stand up remote work infrastructure almost overnight. We\u2019d already built it. Not because we saw a pandemic coming but because we\u2019d been investing in IT capabilities for remote work scenarios well before anyone was asking for them. When the moment arrived, we were ready.<\/p>\n\n\n\n<p>In 1991, the easy path was to cut. I\u2019m proud to say that Marco took the harder path, and it has ever since. What came from it wasn\u2019t just a return to profitability\u2014it was a way of thinking about the business that\u2019s shaped every significant decision since.<\/p>\n\n\n\n<p>The dealers who are going to be standing in 10 years aren\u2019t necessarily the ones with the best margins right now. They\u2019re the ones who are still building something incrementally and consistently, even when the pressure is pointing the other direction.<\/p>\n\n\n\n<p>That\u2019s what Kaizen actually means in practice. Not a program. Not a quarter. A commitment to keep improving regardless of what the moment is asking for.<\/p>\n\n\n\n<p>We\u2019re still at it. <\/p>\n","protected":false},"excerpt":{"rendered":"<p>I joined Marco in 2001, so I didn\u2019t experience what happened in 1991 firsthand. But it\u2019s not a story the company keeps quiet, and it\u2019s not one I\u2019d want to, either. Here\u2019s the unvarnished truth. In 1991, the U.S. went through a short but significant recession, and Marco failed to turn a profit for the first time. The bank threatened to call our loan. For a business that had already spent nearly two decades building something real, it was the kind of moment that forces a decision: cut your way to survival, or commit to building something that doesn\u2019t put you back in the same position. Not ever. Marco wanted to take the second path. Fortunately, around that time, a Japanese business philosophy called Kaizen was gaining attention in American manufacturing. The idea was straightforward\u2014continuous and incremental improvement, applied consistently, compounds over time. Toyota had built an entire operational culture around it. Marco decided to give it a try. The numbers turned around. More importantly, a way of thinking took hold that didn\u2019t leave when the crisis did. I bring this up not because it\u2019s a great origin story\u2014though it is\u2014but because I think the pressure dealers are feeling right now rhymes with what Marco felt in 1991. Margins compressing. Volume declining. The easy path visible and tempting. And the same question underneath it all: do you cut to survive, or do you build through it, think creatively and focus on continuous improvement? Continuous incremental improvement isn\u2019t always glamorous work. It\u2019s also difficult to do the opposite of what everyone else is doing, especially when times get hard. But continuous improvement is what we\u2019re still dedicated to. So I wanted to share a few more notable ways we\u2019ve gone about that over the past few years. A Creative Solution to the \u201cUnsolvable\u201d Technician Problem This won\u2019t come as news: the copy\/print technician shortage has been with us since pre-COVID, but it\u2019s gotten worse. Experienced field techs are retiring. Fewer people are going into this line of work, and the pipeline of people who can replace the depth of knowledge required for advanced equipment is already at a breaking point. Most of the industry is struggling with it\u2014hiring where possible, stretching capacity where necessary, feeling helpless when they can\u2019t always meet their historic response times and losing clients as a result. We decided to approach it as a workforce design problem rather than a hiring problem. Our technicians now use smart glasses in the field. When a newer tech encounters something outside their experience, they can show exactly what they\u2019re seeing to a more experienced colleague in real time. The experienced tech guides them through it remotely. The job gets done, and the client doesn\u2019t feel the gap. What that changes operationally is also significant. We can put someone in front of a problem on day one who can handle it effectively, not because they\u2019ve seen everything but because they have real-time access to someone who has. It doesn\u2019t eliminate the shortage, but it changes what the shortage costs us and what we can promise a client about the consistency of service. The investment here wasn\u2019t just the technology. It was the commitment to building a service model that doesn\u2019t depend on a supply of experienced technicians that may not exist in five years. It was an investment and a significant change in how our techs operated. But we made it early and committed fully. Investments in Predictive Maintenance For most of this industry\u2019s history, service has been reactive by definition. Something breaks, you dispatch. The metric is response time: how fast can you get someone there? We\u2019ve been moving toward a model in which the goal is to not need the dispatch in the first place. Predictive maintenance means monitoring devices, identifying failure patterns before they become problems and staying ahead of supply needs before the client runs out. The proof of it shows up in calls that never happen, which is genuinely hard to point to but very easy for a client to feel over time. Committing to this operationally required upgrading our software so we could offer this service to a broader range of devices. We\u2019re not the only ones who made this change, but we were one of the first. That means we invested before the return was visible\u2014and before clients expected it. That\u2019s a hard thing to justify in a tight quarter. It\u2019s a very easy thing to justify when you look back five years later at what it achieved. Infrastructure To Support Long-Term Service Goals Late last year, we opened our 100,000 square foot logistics center in Des Moines, Iowa. The primary goal was to ensure two-day shipping to clients across the country, but we also wanted to create a better cushion to smooth out supply chain issues. That enormous building is a real commitment for a company that could\u2019ve kept operating the way it always had. But we\u2019ve learned over 50-plus years that the gap between what you promise a client and what your infrastructure can actually deliver has a way of becoming visible at the worst possible time. We\u2019d rather close that gap on our terms than discover it on the client\u2019s. Making Our Work More Visible The investment I find most interesting to talk about is also the hardest to explain quickly. We\u2019ve designed an app that gives our managed services clients real-time visibility into their own tech infrastructure. It includes what they\u2019re running, how it\u2019s performing, what we recommend and data about our own performance. It\u2019s easy to see exactly how quickly we\u2019re resolving tickets and what devices are causing most of them. What changes when a client has that visibility? The very nature of our relationship with them. We\u2019re not asking them to trust our read on their environment; we\u2019re showing them their own numbers and helping them act on what those numbers say. The conversation shifts from a client taking our word for it to a client making decisions [&hellip;]<\/p>\n","protected":false},"author":278,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[4690],"tags":[],"_links":{"self":[{"href":"https:\/\/www.enxmag.com\/twii\/wp-json\/wp\/v2\/posts\/70268"}],"collection":[{"href":"https:\/\/www.enxmag.com\/twii\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.enxmag.com\/twii\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.enxmag.com\/twii\/wp-json\/wp\/v2\/users\/278"}],"replies":[{"embeddable":true,"href":"https:\/\/www.enxmag.com\/twii\/wp-json\/wp\/v2\/comments?post=70268"}],"version-history":[{"count":1,"href":"https:\/\/www.enxmag.com\/twii\/wp-json\/wp\/v2\/posts\/70268\/revisions"}],"predecessor-version":[{"id":70270,"href":"https:\/\/www.enxmag.com\/twii\/wp-json\/wp\/v2\/posts\/70268\/revisions\/70270"}],"wp:attachment":[{"href":"https:\/\/www.enxmag.com\/twii\/wp-json\/wp\/v2\/media?parent=70268"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.enxmag.com\/twii\/wp-json\/wp\/v2\/categories?post=70268"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.enxmag.com\/twii\/wp-json\/wp\/v2\/tags?post=70268"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}