How Toyota earns a halo across its service ecosystem. A continuation of “Formula One Has a Mission Assurance Problem”

By Shawn Kroon, Founder and Chief Services Officer at Whyze Byte.

Unveiling the Toyota GR GT. Born in the spirit of “Toyota’s Shikinen Sengu,” which is its own tradition of renewal. (Photo GR)

Key Takeaways

• A halo cannot be bought. It is value proven in use, and it lives in the system that makes the product, not in the product that wears the badge.
• The system was forged from humiliation. Toyota’s chairman spent thirty years refusing to let a public wound close; the pain became telemetry, the telemetry became capability, and the capability became the thing the internet now mistakes for a design win.
• Value does not travel by itself. The discipline that keeps a strategy connected to the people who run it and to the moment it is used is Mission Assurance.

A Prius Just Embarrassed a Ferrari

Ten years ago, the sentence would have been absurd. A Prius looks more like a Ferrari than Ferrari’s newest car does.

That was the joke after Ferrari pulled the cover off the Luce, its first fully electric car, in Rome. Not the range. Not the power. The shape. The internet did the rest.

The joke landed, and the easy story writes itself. Toyota finally out-Ferraried Ferrari. The badge slipped. The upstart won the day.

I do not believe that story.

I do not think this is a design story. I think it is a service story wearing a carbon-fibre body, and the embarrassment in it is real. It just is not Ferrari’s.

A word on why I read it that way. I have spent 25 years inside enterprise service lines, from the service desk to the executive table, watching strategies look perfect in governance while the people running them quietly absorbed the gap. Value gets decided where the work is lived, not where it is announced. Toyota is the cleanest public case I have seen of a company closing that gap on purpose, so stay with the cars for a while; nearly every move in this story has a desk-job twin, and I will point at a few as we pass them.

The embarrassment that matters here did not start in Rome. It started about thirty years ago, inside Toyota, and the man it belonged to has spent his whole career refusing to let the wound close.

A Flagship Born of Humiliation

Thirty years ago, two men at Toyota cared about car-making the way racers care about it. One was Hiromu Naruse, the company’s chief test driver. The other was Akio Toyoda, who would one day run the company, and who at the time could not drive anywhere near well enough to satisfy Naruse. The older man told him so, bluntly; stop talking about cars you do not even know how to drive. Toyoda did something unusual for a future chief executive. He took the rebuke as an instruction and trained under Naruse for years.

The two of them kept at it while the rest of the company looked the other way. At the Nürburgring, the world’s hardest proving ground, their cars were the slow ones. Toyoda describes those years simply; they were constantly being overtaken. When the Lexus LFA was finally finished, Naruse smiled in a way Toyoda had never seen and said it was the first time he was able to drive the Nürburgring just looking ahead.

The humiliation did not end there. The LFA was a limited run. The wins were class wins. Plenty of cars were still faster, and the paddock said the quiet part out loud. No way that you guys at Toyota could build a car like this.

Toyoda’s own words, published with the launch of Toyota’s new flagship, carry the next part better than any paraphrase could. “I will never forget that feeling of humiliation. And that pain is definitely the force that drives me even now.”

Sit with who is saying that. The chairman of the largest car company on earth, introducing his halo car, leads not with the specifications but with his own shame, named as the engine of the whole program.

Toyota’s chairman, Akio Toyoda, speaking on the left and strapped in on the right; in the middle, the flagship in camouflage.

When Naruse died, Toyoda inherited the Master Driver title from him, along with what he calls the secret sauce for making cars, a sauce he says was made from their pain of humiliation, and a few colleagues who shared the agony. They used the pain as fuel and focused on one phrase, ever-better cars. The GR86, the GR Supra, the GR Yaris, the GR Corolla. The hydrogen engine, Super Taikyu, the Nürburgring, year after year. He still races, under the name Morizo, so he can line up with the enthusiasts instead of above them.

Most organizations bury their humiliations. Morizo industrialized his.

That sentence is the real differentiator in this story, and it is worth more than any styling comparison. So, hold a question while we walk through the system he built.

What would your organization do when it gets embarrassed in public? Not what the communications plan would say. What the operating system would do.

You Cannot Buy a Halo

Here is the distinction the whole piece runs on, and it is worth thirty seconds.

Two marketing scholars, Stephen Vargo and Robert Lusch, named it in 2004, in what became one of the most cited papers in the history of marketing. They called it service-dominant logic; a firm move away from goods and product dominance.

Strip away the academic language and it says something a service desk agent already knows in their bones. There are two kinds of value. There is the value you can buy and price. The badge, the design signature, the signed contract, the platform that went live on schedule.

And there is the value that only shows up later, when a real person uses the thing, in their own world, on their own terms. Vargo and Lusch called the first one value-in-exchange and the second one value-in-use. You can purchase the first. You cannot purchase the second. It is co-created, and it is co-created by the service system around the product, not by the product itself.

The same researchers later inverted a piece of conventional wisdom, and it is the sharpest tool in this whole piece. We are taught that progress comes from invention. Vargo and Lusch argued that an invention is a wasted resource until it is wired into a system of people who can finally do something with it; that wiring is innovation. The car is an invention. The halo is an innovation. One you can build in a factory. The other only emerges from the system.

Toyota says the same thing in four words from its own founder. Monozukuri is Hitozukuri. Making things is making people. The car is the thing you can buy. The skill and the people who make it worth buying are the thing you cannot. And the second one is the point.

A sale is not value. A reveal is not value. Value is what survives contact with the person who has to live with it.

I wrote a piece about Formula One that was the failure version of this. A rational strategy, a sound plan, and a service ecosystem that broke because the signal from the people closest to the work could not reach the people with the authority to act. This is the same lesson read forward, through a company that built the chain on purpose, because its chairman knows exactly what it costs to be on the wrong end of it.

The car is only the case study. The same four links decide whether a platform, an AI program, a vendor model, or a transformation creates value once it reaches the people who run it. Hold that thought. We will come back to it.

The Man Who Signs Off the Car Also Races It

Start with the link Formula One snapped. Signal reaching authority.

Akio Toyoda is the chairman of Toyota. He is also the Master Driver. He tests the GR cars himself, signs them off, and races them in anger. He did not award himself the title; Naruse gave it to him, after years of making him earn it.

Read what that means. The person who feels the car first is not three layers down the org chart. He is at the top of it. He does not read a report about how the car behaves at the limit. He takes it through his own body, through the harness strapped to his chest, through his hands and his neck, and then he decides.

Operator signal is telemetry, not resistance. A report is not telemetry.

Swap the cockpit for a service desk and the sentence still holds. The agent on the worst queue in your company is taking your operating model through their own body, every day, at full load.

The Master Driver title is doing something subtle that service scholars have a precise word for. It is an institution. Not the building kind. The shared-rule kind, a norm everyone in the company understands and acts on without being told. Vargo and Lusch, in their later work, argued that institutions like this are the real glue of any system, the thing that lets a thousand people coordinate without a meeting.

Toyota built an institution whose entire job is to keep the highest-resolution signal in the room with the highest authority. And notice where the institution came from. It was not designed by a committee. It was forged by a test driver who refused to flatter his future chairman, and a future chairman who chose to hear it.

That is the exact link Formula One could not close. The signal existed. It could not reach authority in time. At Toyota, the signal and the authority are the same man.

Most companies cannot put the chief executive in the cockpit, and they should not pretend the structure copies cleanly. The principle copies fine. The more layers a signal has to cross, the easier it is to flatten into noise, and the more likely you are to learn in public what your operators already knew in private.

They Build the Car and Then They Break It

A halo is not a one-time achievement. It rots if you stop earning it.

Toyota’s answer is a renewal discipline it traces to Shikinen Sengu, the Japanese tradition of tearing down the Ise shrine every twenty years and rebuilding it. The point is not the building. The point is that the only way to keep the skill to build it alive is to use it.

Let twenty years pass without rebuilding, and the people who know how retire, and the knowledge leaves with them. Toyota named its new flagship program an embodiment of that idea; the veterans who built the LFA are passing the core skills of car building to the next generation of engineers while the technology around them changes. The secret sauce is being deliberately handed forward, which is the only way a sauce made from one generation’s pain survives the people who earned it.

The operating version is blunter. Toyota describes building the car, driving it to failure on purpose, and repairing what broke, over and over, before anyone outside ever sees it. They build it to break it, so the next one is better. The desk-job twin is rehearsing the failover before the outage picks the date, and retiring the runbook nobody has exercised in years before you find out the hard way that nobody can run it.

A halo cannot be kept alive on history. It decays unless something keeps putting it under load.

There is a quiet inversion hiding in that ritual, and most organizations get it exactly backwards. We worship efficiency, doing more with less. Vargo and Lusch point out that efficiency is a producer’s idea; effectiveness, whether the thing actually works in the user’s hands, comes first, and without it, efficiency is a moot point.

A company can be magnificently efficient at producing something nobody experiences as valuable. Shikinen Sengu refuses that trade. The corporate version is the discipline of exercising a capability on purpose, under real load, so it does not quietly decay into legacy debt while the dashboard still says everything is fine.

One Platform for Three Machines

On December 5, 2025, Toyota and Lexus revealed three machines built from one race-bred platform. The GR GT, a road-going flagship. The GR GT3, a customer race car built from it. And the Lexus LFA Concept, the battery-electric expression of the same program. The GR GT rides on Toyota’s first all-aluminium frame and pairs a twin-turbo V8 with a hybrid system for more than 640 horsepower. Toyota frames the three as one program across two brands, and the lineage it claims for the flagship runs Toyota 2000GT, Lexus LFA, GR GT.

Left to right, the Lexus LFA Concept, the GR GT, and the GR GT3. One race-bred platform, three machines.

This is not three products. It is one development system, and that is the tell.

Because the road car and the race car share structure, the racing program and the road program are not a chain where one hands down to the next. They are a network. The race car teaches the road car. The road car funds the racing. The electric Lexus carries the knowledge across the hardest jump of all, the move to batteries, so the capability survives a change of technology instead of dying with the engine that carried it.

Look at how the flagship was actually developed, because it is the cleanest description of value co-creation you will find outside an academic journal. Master Driver Morizo, three professional racers, and a gentleman driver pushed the car at its limit while the engineers, in Toyota’s own words, listened closely, understood the drivers’ intent with precision, and shaped it into reality.

The people who will live with the car at full load sat inside the development loop, not at the end of it. Toyota calls it a united pursuit of a driver-first philosophy between drivers and engineers. A service scientist would call it beneficiaries integrated as co-creating actors. The two sentences describe the same machine. The desk-job twin is users inside the build, shaping the service before go-live, instead of surveyed about it after.

And the customer race teams extend that loop into the market. Service researchers, Vargo among them again, make a point that sounds obvious once you hear it and that almost every company violates anyway.

Marketing should not be done to customers. It should be done with them. Every team that races a GT3 runs it harder than any factory test, trying to win, and what they learn flows back into the system. They are not sensors Toyota reads. They are actors Toyota builds with.

The cars are not the mission. The three machines are the visible vehicles. The mission is the capability they keep alive and the value the owner finally gets to feel.

Eventually, if the halo is eroded enough, a brand comes to rely more on its history than its earned legitimacy.

A Partnership Built to Move Capability Not Logos

If this were only halo cars, it would be marketing. It is not, and the rest of the company shows why.

In 2026 Toyota Gazoo Racing became the title partner of the Haas Formula 1 team, building on a technical partnership it began in 2024. Toyota does not describe it as a logo deal. It frames it around three words. People. Product. Pipeline.

Young Japanese drivers, engineers, and mechanics get real Formula 1 experience. The teams do joint work on parts and aerodynamics. A new driver-in-loop simulator is coming online at the team’s UK base. The point is not visibility. It is capability, and the capability is built to travel home into the road cars.

Notice what Toyota did not do. It did not try to buy or run the team. Co-creation is not acquisition. You can build capability with a partner without owning them, and the partner stays a partner instead of a possession. That is what a vendor relationship looks like when it is designed to move capability home instead of invoices out.

Years earlier, the GR Yaris had already proven the loop at a tenth of the price. Born from Toyota’s World Rally program, engineered so the rally car and the road car shared real hardware rather than a name, and its early allocations sold out.

Pressure, signal, transfer. The loop is the same whether the output is a rally hatchback or a six-figure flagship.

Ownership Is Where the Value Shows Up

This is the link the design press almost always misses. Value realized in use.

Toyota is reportedly vetting buyers for the GR GT, which is expected to start above 225,000 US dollars. The director of the program said the purchase will feel closer to an interview than a transaction. Buyers are paired with trained specialists Toyota calls GR Meisters, who stay with them past the sale, and owners are expected to actually learn the car, on track, not park it. In the United States the car will not run through ordinary Toyota showrooms at all. It will go through select Lexus dealers, prepared at a dedicated training facility in Texas.

Toyota has been open that it is trying not to repeat the mistakes it made launching the Lexus LFA a decade ago, which is the humiliation discipline applied to its own commercial history; even the wound from its proudest car gets metabolized into the next design.

Be skeptical where skepticism is fair. Buyer vetting can curdle into exclusion theatre, and any process that doubles as gatekeeping deserves a hard look.

But the logic holds. A supercar sealed in a climate-controlled garage has been delivered and never used. No driving. No owner learning the car. No community putting miles on it. No signal coming back to drive continuous improvement. Toyota is not only selling the car. It is shaping the world the car gets driven in, because that is where the value it is selling actually appears.

Most companies measure the sale and assume the value. Toyota is governing the experience, so the value is real. That is value assured in use, not assumed at delivery.

None of this means Toyota has won. Dealer readiness, owner selection, resale behaviour, racing results, and long-term support will decide whether the system works in practice. The point is not that Toyota has already won. The point is that the system is visible, and it is built around the right things.

Ferrari Is the Comparison

None of this makes Ferrari the villain. Ferrari has heritage almost no one can match, and heritage is real value. Early reaction to a car is not the verdict on it.

And let me hedge the pile-on itself, because it deserves hedging. My guess is that the majority of the internet blowback came from people who were never going to be in the market at this price range anyway. Outrage is free; a deposit is not. A bystander’s joke and a collector’s cancelled order are different instruments reading different things, and a system that wants to learn from the noise has to know which one it is listening to.

The Luce is a serious car, Ferrari’s first fully electric model, with more than a thousand horsepower and a design led by Jony Ive’s studio. Its reveal split the room hard. A former chairman warned the company risked destroying a legend and said he hoped the prancing horse would at least come off the car. Ferrari’s shares fell as much as about eight percent before recovering to around six on the day.

The stock move does not prove the design failed. It proves the market reacted to a reveal that asked Ferrari’s audience to accept a different kind of Ferrari.

And here is the fair version of the contrast. Service-dominant logic does not say the old way is wrong. It says the old way is a special case of the new one. Building a product and selling it is real. It is just the narrow case. The general case is a system co-creating value in use. Ferrari, for the Luce, made an outside design signature the headline, an identity bought and presented at a reveal.

Toyota made development pressure the headline, an identity forged by drivers, under load, before the public ever saw it. Neither is cheating. One is competing at the level of the artifact. The other is competing at the level of the system. The audience can feel that difference even when it cannot name it.

There is also a symmetry here worth saying plainly. Ferrari just lived through its most public embarrassment in years. Toyota lived through decades of being the joke at the Nürburgring, the brand nobody believed could build a driver’s car. The interesting question is never whether a company gets humiliated; every serious one eventually does. The question is what the system does with the signal.

Toyoda answered it by getting into the cockpit. The reactions to the Luce, the stock move, the forums, the former chairman, the collectors Ferrari says are already at the door, all of it is the market co-authoring what the Ferrari halo now means, in real time.

Loud early reactions are signal. They are not destiny. When Ferrari revealed the Purosangue, the same crowd called it heresy, and demand outran supply. What decides the next decade is whether that signal carries weight into how Ferrari adapts, or whether it is ridden out as noise. Legitimacy is settled in use, the way value always is.

This Is Not Just About Cars

I have been pointing at the desk-job twins the whole way through. Here is where they live.

You have seen the enterprise version. The platform went live. The vendor hit the SLA. The project closed green. The steering committee moved on. And the people who actually use the thing had a workaround by Friday.

Same failure. Green governance, red reality. And now you can name the disease precisely. The organization optimized for efficiency, the producer’s number, the thing that glows on a dashboard. It never secured effectiveness, the user’s number, whether the thing works in the hands of the person who depends on it. The strategy looked coherent in every meeting while the value quietly failed to arrive in lived experience, because the connection between what leadership intended and what operators lived was never built.

Every enterprise has its own Nürburgring years. The outage that made the news. The platform that flopped in front of the board. The transformation that became a cautionary tale at town halls. Most organizations turn those moments into folklore, stories told to justify caution, or they bury them in a lessons-learned deck nobody opens.

Toyoda’s example points somewhere harder and better. The humiliation is operating fuel. It tells you exactly which capability you lack, and it supplies the energy to build it, for as long as you refuse to let the wound close on its own terms.

That connection between intent and lived reality has a name. Enterprise Service Management (ESM) is not ITSM with a bigger portal. It is the discipline of making services coherent across platforms, vendors, workflows, service owners, governance, data, and the people on the end of them. It is where strategy either reaches the operator or dies on the way. ESM is also one of the fastest-growing disciplines in the enterprise. Mordor Intelligence sizes the IT service management market underneath it at about 15 billion US dollars in 2026, on its way to roughly 32 billion by 2031, a compound annual growth rate above 16 percent, and the discipline keeps spreading beyond IT as the capability is being moved to the enterprise level. The growth has an unglamorous explanation; it works when done correctly and drives tremendous value. Doing it correctly is the challenge, and specialized experience is a strategic necessity.

The four links that make Toyota’s halo credible are the same four that decide whether any strategy survives contact with the people who run it.

For a CxO, this is why green governance can still hide red reality. For a delivery partner, this is why assurance cannot stop at go-live. For an operator, this is why the same complaint raised three times is data, not noise.

AI Raises the Stakes

AI does not fix any of this. It accelerates it.

The people who built the field of service science saw this coming. In their book on service in the AI era, Jim Spohrer, Paul Maglio, Stephen Vargo, and Markus Warg frame artificial intelligence not as a thing that creates value on its own, but as a booster bolted onto whoever is already there.

Their shorthand is X plus AI. The AI is only ever as good as the X, the person, the team, the system it is paired with. Drop it onto a coherent service line and it amplifies capability, speed, and judgment. Drop it onto a fragmented one and it accelerates the fragmentation faster than governance can contain it. Bad knowledge moves faster. Unclear ownership moves faster. The dashboard looks smarter while the lived reality gets harder to trust.

They ask the sharpest question I have read on the subject. Is AI a bicycle for the mind, which makes you stronger as you use it, or a car for the mind, which takes you further while your own legs get weaker? The answer is not in the model. It is in the system you drop it into.

Coherence comes before automation. That is why AI governance is an operating-model question, not only a policy one. Toyota appears to be making the system coherent before it scales the halo. A great many organizations try it the other way around, then wonder why the automation magnified the seams.

One Question Worth Sitting With

The lesson is not that Toyota wins and Ferrari loses. That is too simple, and probably wrong.

Three service researchers, Vargo, Akaka, and Vaughan, defined value in a way that sounds abstract until you sit with it. Value, they wrote, is a change in the viability of a system. Read that again. Value is not a thing a product carries. It is a measure of whether the whole system is getting healthier or sicker. By that definition a halo is not awarded, and it is not bought.

A halo is what a healthy system gives off. The system is the halo.

And this particular system runs on an unusual fuel. The halo Toyota wears today was forged from the exact feeling most organizations spend their energy hiding. Thirty years of being overtaken, doubted, and laughed at, converted on purpose into telemetry, capability, and renewal, by a man who still introduces his proudest car by naming his humiliation first.

Value does not travel by itself. It moves through people, platforms, partners, operators, customers, governance, and use. When that system is coherent, a strategy compounds. When it is fragmented, a strategy can look rational in every meeting and still bleed value before anyone notices.

So, the question worth sitting with is plain. When the people closest to your work raise a signal, how many layers does it cross before it reaches someone who can act? And when your organization gets embarrassed in public, does the wound become folklore, or fuel?

That is the Mission Assurance question. Service-dominant logic has been the most cited idea in service for two decades, and for most of that time it stayed inside the journals. Mission Assurance is what it looks like when you run it. The product gets the attention. The service ecosystem earns the halo. Build the system that earns it. Or rent a badge and hope the market does not notice the difference.

The Last Mile

One more thing, said plainly, because it explains why this piece exists.

A big reason service-dominant logic or service science isn’t mainstream corporate discussion is that the source material is hard to read. The thinking is brilliant. The journals are dense. The leaders who could use it most will never wade through it, so forty years of proof sits in a library while service lines bleed value in the dark. That gap between brilliant research and a Tuesday operating decision is the same gap this whole piece is about.

Closing it is the work Whyze Byte does. We take what the scholars proved and distill it until an executive, an operator, or a vendor can run it. This article is the method in miniature; if you got this far with zero schooling in service science and it all felt obvious, that was the job.

And here is my hedge, stated as plainly as the rest. I think the Chief Services Officer becomes a regular seat at the executive table, scoped across internal and external service delivery, for exactly the reasons this article outlines.

Enterprises already run on services that span IT, HR, finance, vendors, and platforms; the value lies in use; AI is raising the stakes faster than governance can absorb them; and nobody currently owns the end-to-end connection. I could be wrong on the timing. I am not wrong on the gap; it is sitting in plain sight on every org chart, between the CIO and the COO, leaking value.

That prediction is also the seat I offer today, sized for organizations that feel the gap but cannot yet justify the full-time chair. A Fractional Chief Services Officer brings the role before the org chart catches up, and the Gravity Audit is the bounded first step; it finds where legacy debt, friction, and unmanaged spend are blocking the mission, and where the recovered cost can fund the work to fix it, so the role pays for itself.

So, if your dashboards are green and your gut says otherwise, reach out; I am easy to find on LinkedIn. We will talk about how Enterprise Service Management turns the noise in your service line into signal, connects the line to the people it exists to serve, and lets them co-create the value your strategy promised.

And if a conversation isn’t your speed yet, use the closing question in your next operating review instead. It costs nothing, and it tells you plenty.

Shawn Kroon is the Founder and Chief Services Officer of Whyze Byte. He helps leaders close the gap between strategic intent and operational reality through Enterprise Service Management, Service Value Assurance, AI Governance, and Mission Assurance. He has spent 25 years working from the service desk to the executive table and built Whyze Byte to close the gap between them.

Appendix. Sources and Further Reading

The ideas in this piece stand on the work of the scholars who built service-dominant logic and service science. Credit is theirs.

• Vargo, S. L., & Lusch, R. F. (2004). Evolving to a New Dominant Logic for Marketing. Journal of Marketing, 68(1), 1-17. (value-in-use vs value-in-exchange, operant vs operand resources, value co-creation).
• Vargo, S. L., & Lusch, R. F. (2016). Institutions and Axioms: An Extension and Update of Service-Dominant Logic. Journal of the Academy of Marketing Science, 44(1), 5-23. (institutions as the coordinating glue of service ecosystems).
• Vargo, S. L., & Lusch, R. F. (2014). Inversions of Service-Dominant Logic. Marketing Theory, 14(3), 239-248. (innovation over invention, effectiveness over efficiency, goods logic nested in service logic).
• Chandler, J. D., & Vargo, S. L. (2011). Contextualization and Value-in-Context. Marketing Theory, 11(1), 35-49.
• Wieland, H., Koskela-Huotari, K., & Vargo, S. L. (2016). Extending Actor Participation in Value Creation. Journal of Strategic Marketing. (all actors co-create; marketing with, not to).
• Vargo, S. L., Akaka, M. A., & Vaughan, C. M. (2017). Conceptualizing Value: A Service-Ecosystem View. Journal of Creating Value, 3(2). (value as a change in the viability of a system).
• Spohrer, J., Maglio, P. P., Vargo, S. L., & Warg, M. (2022). Service in the AI Era: Science, Logic, and Architecture Perspectives. Business Expert Press. (X plus AI; augmentation; the bicycle and the car for the mind).
• Toyota’s own words. “Message from Morizo, A Flagship Born of Morizo’s Humiliation,” TOYOTA GAZOO Racing GR GT site (toyotagazooracing.com/gr/grgt/wp/); the Naruse history, the LFA Nürburgring line, the “no way that you guys at Toyota” line, the humiliation quote, the secret sauce, the Shikinen Sengu framing, the driver and engineer development method, and the 2000GT to LFA to GR GT lineage all come from this message and are quoted or closely paraphrased from it.
• Automotive and market facts. Toyota and Lexus December 5, 2025 world premiere, Toyota Global Newsroom and TOYOTA GAZOO Racing. The Haas title partnership and People, Product, Pipeline, Haas F1 Team and Formula1.com. GR GT pricing (over 225,000 US dollars, final price unannounced), buyer vetting, GR Meisters, and the Lexus dealer routing, Autoblog, Carscoops, Motor1, and autoevolution, reported. The GR Yaris sell-out, Toyota UK media. The Ferrari Luce reveal, design, price, power, share movement, and the former chairman’s remarks, CNBC, Yahoo Finance, designboom, and PlanetF1. The ESM market sizing, Mordor Intelligence, IT service management market report. All sources confirmed live June 10, 2026; reconfirm immediately before publication.