EDGEwise Insights

Training a single large model can emit as much CO₂ as five cars over their lifetimes. As AI scales, sustainability becomes strategy.

Compute intensity doubles roughly every six months. Inference—running models, not training them—now dominates total energy consumption as usage explodes.

Developers are responding with model compression, quantization, and parameter-efficient fine-tuning. These reduce compute demand by up to 70 percent.

Hyperscalers are investing in green data centers powered by renewables, liquid cooling, and edge inference that minimizes transmission.

Sustainable AI directly supports ESG commitments. Energy dashboards, carbon accounting, and sustainability SLAs will soon be standard in enterprise AI contracts.

Intelligence must be efficient to be ethical. The next competitive advantage will belong to organizations that align AI innovation with sustainability outcomes.

I’m a Minnesota Vikings fan, which means I live in the strange middle ground between trusting data and trusting vibes. Fantasy football made this worse in the best possible way. It trained my brain to think like a scientist and react like someone who just spilled hot coffee in their lap. I know what EPA is. I also believe in momentum. These two things should not coexist peacefully, but here we are.

Fantasy turned me into a numbers person. I draft based on opportunity instead of names. I watch snap counts the way normal people watch sunsets. I check matchup reports and injury updates like they’re medical charts for loved ones, and then I do the least scientific thing possible with all of that information and start somebody because he “feels right.” Every season the analytics show up confident. Strength of schedule, efficiency trends, projections that sparkle like movie trailers that turn out to be terrible. Mike Tyson once said everyone has a plan until they get punched in the face. Vikings fans don’t even make it that far. Ours usually lands around the opening kickoff.

Sometimes analytics gets it hilariously wrong. The Minneapolis Miracle broke every algorithm known to man. The playoff game in New Orleans was supposed to be a funeral and turned into a jazz parade. For one night, numbers cried and Vikings fans pretended they understood physics.

But sometimes the models get it right and I pretend I didn’t hear them. The NFC Championship against the Eagles came with warning labels everywhere. The defense was held together by hope and duct tape. The offense was riding momentum like a surfer who borrowed a board. The spreadsheets were deeply uncomfortable with our chances. I responded by googling Super Bowl merch and acting like this was all perfectly reasonable behavior.

The Brett Favre sequel season felt the same. The data said the arm was fading and turnovers were on the way. I chose to believe in movie endings instead of spreadsheets. It did not work out.

Then came the playoff game against the Dirty Birds. The matchups were bad, the trends were ugly, and every model in existence quietly shook its head. I ignored all of it. By the first quarter my hat was airborne. By halftime I was pacing the house in two hoodies. By the end I was standing shirtless in my Uncle Dave’s freezing garage with steam rolling off me like I’d wandered into the wrong Marvel movie. That was not analytical thinking. That was a live demonstration of ego, emotion, and bad judgment.

Fantasy football is the reason Vikings fans are still functioning members of society. It lets us win even when we’re losing. When the Vikings fall apart, at least my wide receiver still shows up for me. Fantasy is emotional insurance. It keeps you engaged when your actual team is turning Sundays into personality tests. You learn to live with risk, adjust in real time, manage resources, and accept chaos with a straight face.

Which is why there’s more truth in fantasy football than anyone wants to admit.

I am basically Spock, but if Spock panic-started the wrong flex player and yelled at the TV.

And then there are my Packers friends from Wisconsin — Steven, Trever, Likhita, Victor, and David — who get to treat all of this like a nature documentary. Their team replaces quarterbacks the way normal people replace phones, while I’m over here trying to heal generational trauma with spreadsheets and hope. They nod politely when I explain regressions and matchups, then remind me that they’re “pretty good again” like it’s a law of physics.

But here’s the real point hiding under all of this purple chaos.

Fantasy football and NFL fandom accidentally teach something organizations still struggle with.

It takes both.

Analytics by itself is not wisdom, and instinct by itself is not strategy. The real edge comes from living in the uncomfortable space between them. From knowing how to read a model without surrendering your judgment to it. From trusting your experience without pretending it’s immune to being wrong.

The fantasy managers who win year after year aren’t the ones who blindly follow rankings. They understand what the rankings are actually saying. They know when the data is screaming something important and when it’s just making noise. They don’t get intimidated by dashboards, and they don’t let ego overrule evidence. They respect the model without worshiping it. They trust their gut without confusing it for genius.

That same balance is what separates strong companies from struggling ones.

In the real world, machine learning and analytics now shape how supply chains run. Forecasting systems predict demand. Optimization engines decide how much inventory to carry. Algorithms route trucks, manage suppliers, and flag risk before humans can even spell “disruption.” But containers still go missing. Ports still clog. Weather still laughs at forecasting. Customers still change their minds for reasons no equation understands.

When the model is behind the reality, people make the difference.

The businesses that win aren’t the ones who treat analytics like religion or treat instinct like magic. They build teams that understand both. People who aren’t scared of numbers and aren’t in love with them either. People who listen to data with humility and challenge it with confidence. People who make the call instead of waiting for permission from a spreadsheet.

That’s the same skill fantasy football teaches by accident.

It’s what Vikings fans practice every year.

And it’s what winning organizations eventually figure out.

If you want to outperform competitors, build better forecasts.

If you want to lead, build better judgment.

Now if you’ll excuse me, I have analytics to review…

…and then immediately ignore in favor of vibes.

‍

AI transformation isn’t just about smarter models—it’s about operational maturity. The enterprise now runs on a tri-layered stack linking DataOps, ModelOps, and AgentOps into one continuous feedback system.

DataOps ensures clean, governed pipelines. Without it, models learn from noise. It merges DevOps discipline with data stewardship—versioning datasets, automating validation, and enforcing lineage.

ModelOps manages training, deployment, and monitoring. Tools like MLflow or Databricks Model Registry track experiments and automate retraining. Success depends on continuous evaluation—precision, recall, and fairness tracked like uptime metrics.

AgentOps governs autonomous workflows—how agents invoke APIs, coordinate tasks, and learn from results. It defines approval hierarchies, audit logs, and sandboxed environments.

Data feeds models → models inform agents → agents generate new data → data feeds models again. Each cycle improves accuracy and efficiency. Observability platforms close the loop, turning raw activity into insight.

Organizations that connect DataOps, ModelOps, and AgentOps form a living infrastructure—a self-learning enterprise where improvement is built into the workflow itself.

The past two years introduced millions of professionals to AI through copilots—assistants that draft emails, summarize meetings, or suggest code. But copilots still wait for humans to steer. The next wave of enterprise AI will not. It will act.

AI agents combine reasoning, memory, and action within business workflows. They can open tickets, process invoices, generate reports, or orchestrate multi-step processes without constant human prompting.

A digital co-worker differs from RPA bots. RPAs follow scripts; agents learn context. They reason about goals, ask for missing data, and coordinate with APIs and humans. The enterprise challenge is balancing autonomy with accountability—deciding which tasks agents can perform independently, which require approval, and how to audit results.

Enterprises must implement “supervision loops.” Each agent should operate inside guardrails—role-based permissions, human-in-the-loop checkpoints, and observable logs for every action. Without these, autonomy becomes chaos.

The temptation is to see agents as digital labor. The opportunity is to treat them as digital partners—augmenting teams, not replacing them. Finance agents that reconcile transactions overnight free analysts to interpret trends. Service agents that resolve 70 percent of Tier-1 tickets let humans focus on empathy and escalation.

Agentic AI isn’t about removing people; it’s about expanding organizational capacity. Enterprises that master supervised autonomy will gain 24/7 execution without sacrificing trust or control.

The first metric everyone asks of AI is ROI—and the first mistake is defining ROI as cost savings. The true economics of AI revolve around speed, adaptability, and creativity.

Automation once meant doing the same work faster. AI means doing better work differently. A model that drafts three proposals in ten minutes doesn’t merely save time—it multiplies ideation. The metric becomes “time-to-decision” and “decision quality,” not hours reclaimed.

AI allows organizations to make more informed decisions per day—higher “decision density.” It also increases creative throughput: marketing teams generate dozens of campaigns; engineers test multiple design paths simultaneously. These are new growth levers that don’t appear in a traditional P&L.

Economists describe a phenomenon where productivity rises without corresponding layoffs—the “AI dividend.” Enterprises redeploy capacity toward innovation, not reduction. Measuring this requires new KPIs: rate of experimentation, adoption velocity, and human satisfaction.

CFOs need models that capture compounding value:
• Time-to-value – how quickly a model creates measurable outcomes.
• Adoption ratio – percent of workflows augmented by AI.
• Learning rate – improvement in model accuracy or user output per iteration.

AI’s value compounds through acceleration, not subtraction. Companies that measure for creativity, learning, and adaptability will see the largest long-term returns.

When people ask how Strategic Systems adopted AI, they usually expect to hear about a roadmap or a major initiative. It was much messier and far more practical than that. We didn’t start with a platform strategy. We started with two tools: ChatGPT and Gamma. ChatGPT was where the thinking began. Gamma was where we tried to turn that thinking into something presentable. For a while, that pairing worked well enough. We were moving faster, shaping ideas quicker, and compressing work that used to take days into hours.

We eventually hit the edges of what Gamma was good at, so we moved on to Genspark. The change wasn’t about one tool being “better” than another. It was about learning that whatever we used needed to fit how we work, not the other way around. AI didn’t come into Strategic Systems as a strategy document or a formal rollout. It showed up as a practical response to running a business that was becoming more complex by the month. Between talent services, infrastructure work, application development, advanced analytics, and learning, the pace was increasing while tolerance for bad decisions kept shrinking.

At first, the benefits were obvious but modest. We wrote faster, found information more easily, and summarized documents without as much overhead. Useful, but not transformative. The real change started when we stopped waiting for the work to be clean before involving AI. We brought it into the middle of unfinished thinking: draft plans, half-formed ideas, debates that hadn’t settled yet. It became where we tested logic before it had consequences. We used it to challenge assumptions and stress ideas before they hardened.

Over time, the effect showed up quietly. Meetings became more focused. Writing sharpened. Weak thinking collapsed sooner. Good ideas traveled further before hitting resistance. We weren’t just saving time. We were catching problems earlier when they were easier to fix.

Over time, it became clear that the way we were working no longer fit neatly into separate buckets.

What became obvious inside the company was that adoption, governance, enablement, data architecture, and operating design were not separate conversations. If one moved, the others moved with it. EDGE became the structure around that reality, not because it looked good on a slide, but because it reflected how the work functioned. As that thinking matured, it began showing up in the things we built for ourselves.

SERVE started to connect sales, estimation, and delivery. Once AI became part of that flow, the platform changed in real ways. Estimates became more consistent. Documentation existed when it was supposed to. Patterns across deals surfaced sooner. Issues stopped hiding until late in projects where they were expensive. At the same time, we were wrestling with a different question. How do you move AI from the executive tier into daily work without it becoming something people ignore? That work turned into SAI. Not as a product, but as a way of working. It helped translate experimentation into habits teams could rely on. Instead of selling features, the effort shifted to helping people build confidence and judgment alongside the technology.

That is also why EAT exists. AI does not live by itself. It intersects with automation, analytics, workflows, and infrastructure. People do not feel “AI.” They experience whether work is simpler or harder. EAT became our way of pulling those pieces into one system instead of letting them drift into separate initiatives.

Along the way, something else became clear. What mattered most was not which tools we used, but what stayed with us as the tools changed. The context we built up. The expectations around preparation. The habits around testing thinking instead of assuming it was right. The shared understanding of what “good” work looked like. Changing tools was easy. Rebuilding that was not.

We also learned the hard way that AI does not fix unclear thinking. It reflects it. If strategy is fuzzy, AI produces better-written confusion. If leadership avoids decisions, AI makes avoidance look organized. Used well, it sharpens thinking. Used poorly, it gives confusion better formatting.

Eventually, AI stopped being treated like software and started being treated as part of how leadership works. It did not replace thinking. It raised the visibility of weak thinking. Ambiguity stood out faster. People came into conversations prepared, or it became obvious very quickly when they were not.

There was no rollout plan. No company-wide reset. AI simply became part of the normal flow of work, the same way shared documents and messaging once did. You stopped noticing it until you imagined trying to operate without it. What surprised us most was how quickly the conversation stopped being about tools at all. The work shifted to how decisions were made, how ideas were tested, and how much ambiguity we were willing to tolerate before acting. When output is no longer scarce, advantage starts to show up in quieter places. In judgment. In clarity. In knowing when to push and when to walk away.

Working this way has not solved every problem in the business. What it has done is change how quickly issues surface and how directly we deal with them. Decisions get tested earlier. Weak assumptions do not last as long. And the gap between knowing something is wrong and doing something about it keeps getting smaller. That has been the real value of both the universally available AI and our bespoke AI, for us here at Strategic Systems.

‍

For decades, enterprise infrastructure revolved around two principles: number of users and latency. The goal was always to deliver information to as many people as possible, as quickly as possible. But the rise of AI agents changes everything. These systems don’t wait for humans to act—they act on behalf of humans. They require secure, high-throughput access to data, and they operate across boundaries that traditional architectures were never designed to handle.

The new paradigm is to design around agents and data security, not users. Data has become the gravitational center of architecture, pulling compute, models, and analytics closer to where it lives. That’s why we’re seeing the emergence of what some call the NeoCloud—smaller, AI-optimized infrastructure providers that deliver agility, compliance, and cost efficiency without vendor lock-in. These environments are closer to the enterprise, both physically and operationally.

According to Gartner, by 2027 roughly 60 percent of enterprises will run AI workloads in hybrid or on-prem environments for reasons of performance and data protection. NeoClouds and vClusters enable companies to keep sensitive workloads local while still taking advantage of large-scale compute when needed.

Large language models (LLMs) thrive on unstructured, messy data—but they still depend on trustworthy, well-governed sources. Platforms like Snowflake and Databricks aren’t disappearing; they’re transforming, embedding vector search, semantic indexing, and model serving directly into the warehouse. The future NeoCloud merges data gravity with AI proximity, where governance, structure, and unstructured insight coexist.

The old Bronze/Silver/Gold hierarchy was designed for ingestion and analytics, not understanding. The next generation replaces those tiers with a Unified Knowledge Layer—a governed, semantic repository that allows both humans and machines to access meaning, not just data. Governance, lineage, and embeddings converge; context becomes as important as content.

We’re entering a post-lake, post-API world—where intelligent agents act wherever data lives, anchored by evolving warehouses and unified knowledge layers that bridge structure and reasoning.

People keep telling me I should write a book. Maybe I will.

Right now all I have is a notes app full of half-formed chapters and way too many stories: the alligator in the rental car in Florida, the elevator incident I still get teased about, the RAID arrays sitting on a big-box shelf like they were holiday specials, the cross-country deployment derailed by weather, sickness, traffic, and raw luck, the uncomfortable meeting where I told a CEO, “You’re not ready yet,” the nights arguing with Codex, and the juniors asking, “Is there still space for us?”

And every time I look at that list, I think, How did all of this end up being my career?

But then I remember the thread running through all of it: Technology never saves the day on its own. People do, when they are supported, honest, prepared, and working with the technology instead of against it.

The future belongs to leaders who can do both: use the technology and elevate the people. I have had the privilege of meeting some. I hope we build more.

The regulatory tide has arrived. The EU AI Act, U.S. Executive Order 14110, and ISO 42001 mark the shift from voluntary ethics to mandatory accountability.

Governance 1.0 was about awareness; 2.0 is about enforcement. Organizations must inventory every model, classify risk, document datasets, and prove oversight.

EU AI Act: risk tiers from minimal to unacceptable with penalties up to 6% of revenue.

ISO 42001: management system for AI quality and risk.

NIST AI RMF: standard for trustworthy AI development.

Compliance automation—model registries, explainability dashboards, bias testing—transforms governance from a burden to a business enabler.

Transparent enterprises build faster because regulators, partners, and customers trust them. Governance maturity will soon matter as much as cloud maturity once did.

When AI becomes the interface, design must account for trust, transparency, and tone. Users need to know why a model responded a certain way. Confidence scores, rationale summaries, and replayable context logs turn black boxes into glass boxes.

Work is also becoming multimodal—text, voice, image, gesture. Designers must choreograph these modes seamlessly while preventing cognitive overload.

Great AI UX feels considerate. It apologizes for errors, offers alternatives, and respects user autonomy. Empathy is not decoration—it’s essential to adoption.

Inclusive design ensures outputs are understandable across cultures and abilities. Accessibility—screen readers, explainability, contrast ratios—is ethical design, not optional compliance.

The best AI isn’t invisible; it’s understandable. Designing for augmented work means making intelligence feel human-centric, transparent, and empowering.

The hardest part of AI transformation isn’t the technology—it’s the people. Executives are eager to invest, but employees often hesitate. Fear and misunderstanding slow adoption long before any model is deployed.

To many workers, AI feels abstract and threatening. They worry about replacement, not enablement. Adoption accelerates when employees are included early and see direct value in their own work.

Future teams will need Human-AI Orchestrators—professionals who understand both domain and model behavior, bridging human context with machine capability. When people feel informed and empowered, curiosity replaces compliance, and transformation becomes sustainable.

AI ethics has outgrown its early focus on bias and transparency. The central question now is human impact: How do we deploy AI responsibly while helping people evolve with it?

Each technological wave brings both fear and opportunity. The organizations that thrive treat AI as a human transition, not a headcount reduction. That means investing in retraining, new roles, and transparent communication about how AI augments work rather than replaces it.

Emerging roles of the AI era include:
• Human-AI Orchestrators – coordinating collaboration between people and intelligent systems.
• Prompt Architects – designing natural-language interfaces.
• Data Stewards – safeguarding integrity, fairness, and transparency.

Ethical AI begins with empathy. It demands inclusive design, education, and shared prosperity. The aim isn’t to replace people—it’s to prepare them for what comes next.