The hardest thing a successful company can do is change how it operates when it's still winning.

Ben Horowitz described peacetime and wartime as different modes of leadership more than a decade ago. It remains one of the most useful frameworks for understanding how leaders need to think and act differently in each environment. What it doesn’t fully address is the cultural dimension. Even when leaders understand the shift is required, the organizational culture, its decision-making patterns, structures, and incentives, often determine whether the shift is successful.

In peacetime, a company is focused on maximizing their current opportunity. They have a clear advantage in their core market. The operating mode is straightforward: extend the existing lead while allocating capital and resources towards a series of initiatives that don’t deviate from the tried and true playbook to incrementally improve the existing product to ensure all the competitive boxes are checked. Strategic decisions are focused on a narrow defined set of outcomes to generate modest and predictable growth. The organization is built to protect what’s working, not to reinvent it..

In wartime, everything is different. Growth is slowing, the competitive dynamics have shifted dramatically around the company, and the moves that produced predictable gains in peacetime are no longer enough to keep up. There is no tried and true playbook. The incremental improvements that defended the lead in peacetime will not be enough to stay competitive. Capital and resources are constrained and require tough tradeoff decisions where the right answers are not completely clear. Decisions that used to take months need to happen in days. And the methodical consensus-driven culture that built the organization no longer works.

The shift from one mode to the other is where most companies break down.

This isn’t a new problem. I watched it play out at Yahoo two decades ago. It didn’t end well. And you can see versions of it playing out across many companies and industries today.

Yahoo! Won Peacetime. It Never Figured Out Wartime.

I was at Yahoo! in the early 2000s. The company was one of the earliest, most useful gateways to the web when the internet was still hard to navigate. Its human-curated directory made the chaotic early web feel organized, and it quickly expanded into email, news, sports, finance, shopping, and messaging, so users could do many things in one place. It was the center of the consumer internet. It was dominant. It was supposed to be what Google turned out to be.

As late as 2005, Yahoo remained the dominant force on the consumer internet with 6.2 billion monthly visits compared to Google’s 2.9 billion. It had massive brand recognition, unmatched distribution, and category-leading services in mail, finance, news, and sports. On paper it looked unbeatable.

But by 2006 the internet playing field had changed. Consumers were quickly shifting toward single-purpose services in search, social, video, and others that did one thing exceptionally well. The very advantage Yahoo had built, doing everything, became its biggest liability.

Wartime had arrived. And Yahoo was never able to make the shift. Looking back, three things went wrong.

Focus

Yahoo never answered the most important question a company can face: what kind of company are we? Were they a technology company or a media company?

At the time, Yahoo’s mission was to be “a leading provider of comprehensive online products and services to consumers and businesses worldwide.” That mission gave everyone in the company permission to do everything. And at Yahoo, they tried. Email, news, sports, finance, search, entertainment, shopping, wireless, and more. There was no filter for what mattered most and no basis for saying no.

Google’s mission was the opposite: “organize the world’s information and make it universally accessible and useful.” You could walk into any product meeting at Google and ask “does this make information more accessible?” and get a clear answer. At Yahoo the same question had no answer because the mission didn’t draw any lines.

Google didn’t try to be everything. It obsessed over one thing: making search faster, more relevant, and more comprehensive. While Yahoo’s homepage grew busier and its strategy broader, Google’s stayed brutally simple: a white page with a box. Its PageRank algorithm got smarter as the web grew. More pages, more links, better results. Google treated search as an engineering problem, not a content or media one.

The identity confusion ran deeper. Yahoo insisted on calling itself a media company while operating like a technology company. Product managers were called “Producers.” Divisions were called “Properties.” But the product was software. And if you think you’re a media company, you invest in content and advertising, not engineering. Yahoo tried to do both. It never resolved the tension between them. Resources were split and neither the content nor the technology side ever got the full commitment it needed. Google, which never confused itself for anything other than a technology company, pulled ahead.

Without a clear identity there can be no focus. And without focus every strategic decision becomes a debate about what Yahoo is rather than what it should do next. In peacetime Yahoo could afford to be everything to everyone. When wartime arrived and Google became the front door to the internet, YouTube became the destination for video and Facebook became the gateway to people’s social lives, Yahoo was still trying to be everything. Everyone else was winning at one thing.

Decisiveness

When you don’t know what you are, you can’t make hard calls. Yahoo had multiple moments where a single decision could have shifted the outcome. In 1998 Yahoo passed on buying Google for $1 million. In 2006 Yahoo tried to acquire Facebook. The deal fell apart. That same year Yahoo was in talks to acquire YouTube. Google moved faster, and won the deal.

Yahoo’s peacetime culture became a trap. With many peacetime cultures, the hardest decisions just stop as the organization confuses alignment with 100% consensus. Brad Garlinghouse, a senior Yahoo executive who later became CEO of Ripple, captured this accurately in the Peanut Butter Manifesto, an internal memo that became public in 2006. He wrote that Yahoo was held hostage by analysis paralysis. Decisions were either not made or made too late. I watched this firsthand. I remember an executive around the same time sharing his frustrations that decision making at Yahoo was similar to an andon cord on a manufacturing line. Anyone could pull it and stop a project cold. In theory it was designed to maintain quality. In practice it meant no significant project ever shipped because everyone, regardless of their role or proximity to the decision, had veto power and nobody had clear ownership.

Unable to make timely decisions, Yahoo kept reacting to the competition instead of setting their own agenda. By the end of 2005, just sixteen months after Google went public, Google was worth more than twice Yahoo’s market value. The window to act had closed.

Culture and Organizational Design

At Yahoo, the operating by committee culture drowned out the best ideas. By the 2005 timeframe, product decisions were increasingly made by committee rather than by the product managers and engineers closest to the problem. The best ideas got watered down through rounds of reviews and sign-offs, so what shipped barely resembled what was proposed. It was the opposite of single-threaded ownership. Project Panama, Yahoo’s effort to rebuild its search advertising platform and close the gap with Google, was the clearest proof. The project was more than a year late. Decisions required sign-off from committee after committee. Engineering chiefs were hired and gone in rapid succession. By the time Panama launched in 2007, Google had used the time to extend its lead to the point where Yahoo could no longer close the gap.

Yahoo had extraordinary talent. The problem was the organizational operating system they were asked to work within. The people who wanted to solve hard problems, move fast and build things left to join startups, Google, or start their own companies. Some of the most famous examples: Jan Koum and Brian Acton left in 2007 and built WhatsApp, which Facebook acquired for $19 billion. Paul Graham left to co-found Y Combinator, which went on to launch Airbnb, Dropbox, and Stripe. Many other Yahoo alumni went on to start many other successful companies including Slack, Cloudera, SurveyMonkey, and MyFitnessPal, to name a few.

Yahoo saw the threat. It just couldn’t become the kind of company that could fight it.

OpenAI: A Modern Version of the Same Story

OpenAI’s parallels to Yahoo are hard to ignore. ChatGPT was the fastest product in history to reach 100 million users. By 2024, OpenAI defined the category. It had the most recognized brand in AI, the deepest enterprise relationships, and a developer ecosystem that anchored most of the industry’s tooling. On paper, it looked unbeatable. The company spent much of 2024 and 2025 placing bets across video generation, hardware, social media, e-commerce, and enterprise software simultaneously.

In March 2026, OpenAI’s CEO of applications told staff the company had to stop being distracted and “nail” its core business. OpenAI’s leadership has named the problem out loud, which Yahoo’s never quite did. Whether they can do the harder thing, focus on rebuilding their core business, is still being written.

What Wartime Leadership Actually Looks Like

The best example of a leader and company that successfully made the cultural shift from peacetime to wartime was Steve Jobs when he returned to Apple in 1997.

At the time the company was weeks from bankruptcy. Apple was operating with no clear strategy or purpose as few employees could say with confidence what Apple stood for or what success was supposed to look like. As a result, the organization veered into trying to serve too many customer types at once, with a confusing lineup of Macs and side projects. In addition to the muddled Mac product line, the company launched the infamous Apple Newton and licensed the Mac operating system to clone makers in an attempt to grow market share, which cannibalized its own hardware margins and muddied its product identity. The “do everything” approach created confusion among customers, developers, and employees alike.

Jobs saw the problems clearly and moved fast. He focused on three things: a clear strategy, unleashing innovation through simplification, and building accountability into the organization to drive flawless execution.

First, Jobs articulated a clear strategy. Apple’s purpose was to build premium, design-driven hardware and software that prioritized simplicity and excellence over chasing market share. Jobs made the strategy concrete with a 2x2 grid: consumer versus professional on one axis, desktop versus portable on the other. Four products. Everything else got cut. That grid served as Apple’s new identity and a ruthless filter for saying no to everything that didn’t fit. He ended the Newton. He killed the clone licensing program. He closed projects that were consuming resources without producing results. The clarity gave every employee, developer, and customer a North Star for what Apple was and was not.

Second, Jobs unleashed innovation through ruthless simplification. With the distractions gone, Apple deployed its best engineers, designers, and talent on its most important projects. The iMac, famous for its revolutionary translucent, and curvy design, launched in 1998 and restored the company’s profitability. The Digital Hub strategy introduced in early 2001 led to the launch of the iPod and iTunes, which dominated the music industry for most of the early 2000s. And the iPhone in 2007 and iPad in 2010 captured the smartphone market and created the tablet category. Apple’s focus on simplification probably unleashed one of the greatest cycles of product innovation in the history of tech.

Third, he built accountability into the organization to drive flawless execution. On the product side, Jobs and Jony Ive obsessed over every detail of the design, from the curves of the iMac to the glass on the iPhone, ensuring that what shipped reflected Apple’s commitment to simplicity and design excellence. No part of the organization was exempt from that standard. On the talent side, Jobs set a simple standard: A players hire A players. Executives who couldn’t keep up were replaced by ones who could. The message was consistent from top to bottom: own the outcome and raise the bar on every iteration.

A company that was weeks from bankruptcy grew its market cap from $2 billion in 1997 to more than $350 billion or more than 150x in value.

Making the shift from peacetime to wartime is hard. Most leaders know what needs to change. Few are willing to do it. The ones who make it work share three traits. They define a strategy clear enough to use as a filter for saying no. They make decisions with speed and conviction rather than waiting for consensus. And they build accountability into the organization so that execution matches the ambition. The shift is never comfortable. But the organizations that successfully make it develop a durable advantage: the ability to win under any conditions.

Thank you to Sydney Schoolfield and Lamia Pardo for reading drafts of this.

"It is not the daily increase but the daily decrease. Hack away at the unessential." — Bruce Lee

Complexity is a tax on execution. It compounds quietly. Then one day you look up and everything takes twice as long as it should.

I’ve watched this happen more times than I’d like to admit. The pattern is always the same. Leadership sees a macro shift and gets the organization to spring into action before the problem is clearly defined or the desired outcome is written down. Workstreams multiply. A transformation office appears. A consulting firm is hired to coordinate it all. Decisions slow. Activity increases. Results do not.

This is playing out in real time with AI today. Most organizations are jumping into AI before knowing what problems they are trying to solve. What they are learning is that AI amplifies how you work. If your organization is inefficient, AI makes you faster at the wrong things. As a result, many companies are now finding that too much experimentation is at odds with delivering actual business value. Johnson & Johnson is a public example. After encouraging AI experimentation across the company, they ended up with nearly 900 individual use cases. Most were redundant or simply didn’t work. Only 10% to 15% of use cases were driving 80% of the value. It took a full year to learn what should have come first: define the problem before you build the solution. That is not a technology failure. That is a complexity problem.

Simplicity Is a Strategy

Strategy is as much about choosing what you will not do as what you will do. Most organizations never make that choice. They start with what they already want to build and reverse engineer a customer problem to justify them. The result is a long list of priorities, which is the same as having none.

Simplicity is a focused choice. It starts with defining the outcome so narrowly that the decisions become obvious. I learned this early in my career at Apple. When we were designing early generations of mobile computers, every product decision was a tradeoff. More compute power drained more battery. More battery meant more weight. Optimizing for one hurt the others.

The temptation was to build the most powerful notebook computer possible. That would have produced a great spec sheet and a product built for no one in particular. Instead, we narrowed the customer problem: build the best notebook for an enterprise sales executive who lives in PowerPoint and Word and needs to work through a six-hour cross-country flight without an extra battery.

Clarifying the target customer simplified every other decision. We focused on building a notebook with the best screen, decent compute, and enough battery life to last six hours at the lightest weight in its class. We didn’t build the most powerful laptop. We built the one our customer actually needed. It became their primary machine, the one they carried through airports every week. The narrow problem statement made that possible.

At MoneyGram, we faced this exact choice when building new products. Instead of trying to build a new receiver product for every use case on day one, we simplified the customer problem to one thing: the experience for the person receiving money, starting with just the receipt. That focus changed everything. We stopped guessing at features and started solving the actual customer problem. We had something live in market in just 90 days and have been iterating based on what we’ve learned ever since.

More People Does Not Mean Better Results. Most businesses follow an instinctive, but misguided principle: the more crucial the project, the more people must be thrown at it. The operative theory is that more resources equal better execution and results. But it rarely works out that way. More people mean more coordination, more meetings, and more diffused ownership. The team assigned to solve the problem becomes the problem.

Simplicity Is a Competitive Moat. Simplicity means fewer layers, fewer handoffs, and fewer priorities between the customer and the people doing the work. In a simple organization, small, empowered teams can see what customers are doing, decide what to change, and ship improvements without waiting on a maze of approvals.

At MoneyGram, we used to have 50 people working on the same product with decisions made centrally. Today those same 50 people operate across six smaller teams, each single-threaded with 100% undivided attention to solving one problem end-to-end with decisions made faster by the people closest to the work. The result is a 10x increase in output from the same number of resources. Not because we hired more people. Because we simplified how we work.

A company that learns in weeks instead of quarters compounds that advantage over time. The gap between them and slower competitors widens every cycle. That’s not an easy gap to close.

Simplicity Is Cultural

A CEO can declare “fewer priorities.” Without a culture that enforces it, the organization will add them back faster than leadership can cut them.

This is because complexity is the default. It just shows up. Someone adds a step to the workflow that makes their team’s job easier but slows everyone else down. Someone builds a feature that no one else wants or needs because a single customer asked for it loudly. A leader adds headcount to manage a broken process instead of fixing the root cause. Each decision makes sense in isolation. Together, they can bury you.

Culture is how people act when no one is looking. Three behaviors make simplicity stick.

The first is honesty over politeness. When someone in the room knows an idea is flawed and stays quiet to avoid conflict, the organization spends weeks pursuing something that should have been killed on day one. A culture of simplicity requires people to say what they actually think. What they’d say if the company depended on it, because it does.

The second is the discipline to say no to good ideas. Every organization is flooded with reasonable things to do. But when you take on more than you can execute, you create a backlog that adds nothing but distraction. The discipline is to cut them down to the few that will actually move the business. The goal isn’t to stop having ideas. It is to focus on them at a rate the organization can actually execute. Put the best people and resources on the few things that matter most. Let the rest wait.

The third is small teams with clear owners. Operating decisions made by committees are slow and ineffective. Decisions made by clear owners closest to the details work best. Keep teams small enough that everyone in the room has real ownership and no one can hide. Give small teams real authority and single-threaded focus. One team, one problem, full ownership of the outcome.

Simplicity Wins

I’ve seen what happens on both sides. Companies that let complexity take over usually spend their time talking about what they need to do. Companies that commit to simplicity win.

Before Apple moved to its current headquarters at Apple Park, the company’s marketing team worked in a building just across from 1 Infinite Loop in Cupertino. When you walk through the front door and past two secured entrances, you turn a corner and face a wall painted with three words in large silver letters: SIMPLIFY, SIMPLIFY, SIMPLIFY. A broad line is drawn through the first two SIMPLIFYs. The message is clear. Keep going until there is nothing left to cut.

Because simplicity gets executed. Complexity gets talked about.

Thank you to Sydney Schoolfield, Lamia Pardo, Jillian Slagter, Cory Feinberg, Josh Gordon-Blake, Luke Tuttle for reading drafts of this.

In every company building or transformation, the obvious moves and easy answers eventually run out. What separates success from failure is believing a better path exists and pushing until you find it. That is when organizational resilience shows up.

But here’s the truth: there is a big difference between an organization that is resilient and one that is stubborn. That difference often marks the line between progress and collapse.

At first glance, resilience and stubbornness look similar. Look closer and the contrast is sharp.

Resilient organizations adapt. They surface truth early, treat bad news as data, and act fast to correct course. They reward people who raise problems and move quickly to fix them. Stubborn organizations punish dissent, delay decisions, and defend the past instead of inventing the future. They hide behind vague phrases like “let’s revisit this later”, “we’ll figure it out later” or “we’re not ready to decide,” only for the real conversations to happen in silos after the meeting ends.

Every company faces these tests. Whether you are trying to win customers, find product-market fit, build a new culture, or scale your business systems, resilience makes the difference.

Resilience Isn't Optional in a Transformation

Resilience is the foundation that enables a company to navigate the chaos and complexity of transformation. It is not a nice-to-have trait. It is a core capability embedded in a company’s DNA. It separates those that move forward from those that stall when markets shift, technology changes, or competition intensifies.

I saw this firsthand early in my career at Apple. In the push to build an early laptop, our teams obsessed over maximizing processing power and speed. But more power meant bigger batteries, heavier weight, and shorter battery life. We lost sight of our target customers and what business travelers actually needed. The path to product-market fit was anything but straight. More than a dozen frustrating iterations failed before we finally got it right. The breakthrough came when we confronted feedback quickly, stayed open to new approaches, and refocused on the real goal: designing the optimal laptop for the traveler. The winning product had less raw power but delivered what mattered most to customers: lighter weight and longer battery life. It went on to set sales records and win industry recognition because it solved the right problem. That experience shaped my view that resilience is not optional. Resilience, paired with constraints, can unlock powerful innovation.

You can spot resilience by how a company deals with truth. Mechanisms that make reality visible early, such as weekly metric reviews, postmortems without blame, and direct customer interviews, are hallmarks. In these cultures, people feel safe raising problems quickly, and leaders change course when new data shows a better path. That is not weakness. It is intellectual honesty.

How to Build Resilience into a Company's DNA

Building resilience requires intentional design, not wishful thinking. It begins with making reality checks routine.

Ask regularly: “What hard truth are we ignoring?” Build this into quarterly planning, monthly reviews, and project retrospectives. Create space for uncomfortable observations before reality forces itself on you.

Celebrate adaptation as well as execution. Most companies reward hitting original targets. Resilient ones also reward teams that pivot when assumptions prove wrong. Killing a bad project, changing course, or admitting flawed assumptions should be recognized as progress.

Institutionalize feedback loops that make upward and cross-functional input expected, not optional. Go beyond annual reviews. Create forums across silos to share what works and address dependencies directly. Encourage people to challenge decisions and suggest alternatives regardless of hierarchy.

Prepare for stress through deliberate practice. Run postmortems after failures, scenario planning for “what if” situations, and drills that test response. These build the muscle memory needed for real crises.

Leaders reinforce resilience by modeling consistency, welcoming bad news, and holding standards even under pressure.

The Payoff of a Resilient Culture in Transformation

Resilient organizations pivot faster when markets shift, build trust while cutting politics, and outlast competitors. As Ben Horowitz notes in The Hard Thing About Hard Things, there are no silver bullets, only lead bullets that require grinding through. Competitors chasing easy answers burn out. Resilient companies keep iterating until they break through.

This endurance becomes decisive during long transformations. The company that can maintain execution and clarity for 18 months of pivoting will outlast one that loses focus after six.

Airbnb faced this test in 2020 when COVID erased 80% of bookings almost overnight. CEO Brian Chesky moved fast with clarity: long-term stays, virtual experiences, new safety protocols. Within months bookings rebounded. By year’s end, Airbnb went public at a $47 billion valuation. That was resilience in action.

In the businesses I’ve led, the moments that defined progress were not when everything went to plan. They came when the plan broke and the team chose to adapt rather than defend. Each time, resilience turned a setback into a step forward.

Build Resilience Before You Need It

The key lesson: resilience cannot be built in the middle of a crisis. By then it is too late. It has to be woven into how a company operates when things are going well. Companies with resilience in their DNA adapt faster under pressure, hold high standards, and move with speed when conditions change.

Ask yourself: Are your mechanisms exposing the truth early? Are you rewarding teams for adapting as well as executing? Are you practicing under stress before the real test arrives?

Build those habits now. Because when disruption hits, resilience will be the difference between companies that define the future and those that are defined by it.

.

“I think frugality drives innovation, just like other constraints do. One of the only ways to get out of a tight box is to invent your way out.” — Jeff Bezos

Imagine being asked to lead a high-stakes project, only this time with half the usual resources. It sounds like a recipe for failure. But history proves otherwise: when embraced, constraints sharpen focus, fuel innovation, and elevate performance.

Put simply: Constraints are your friends.

Constraints Drive Innovation

History is clear: The greatest innovations rarely come from abundance. They come from necessity. Constraints do not hinder innovation; they ignite it.

Take Toyota. Post-war Japan was defined by scarcity—limited resources, a fragile economy, and virtually no margin for waste. Unlike American carmakers that relied on abundant capital and materials, Toyota had to build a more efficient, resource-conscious manufacturing model just to survive. That necessity gave rise to the Toyota Production System (TPS), a revolutionary approach centered on eliminating waste, building only what was needed, and investing in quality at the source. It empowered workers to stop the line to solve problems early and embraced continuous improvement through Kaizen. These innovations weren’t born from abundance; they were forged by constraint. Toyota’s ability to do more with less helped it outmaneuver larger, better-funded rivals—and laid the foundation for decades of growth and operational excellence.

Similarly, consider Dell. Michael Dell founded the company with $1,000 as a 19-year-old student at the University of Texas. No scale. No retail partners. No problem. Competing against well-financed giants like IBM and Compaq, he turned constraints into an advantage by building a direct-to-customer model. Customers configured their PCs online. Dell assembled on demand. Inventory moved in days—sometimes hours—not months. No middlemen. No bloated warehouses. No idle capital. It was a model born of limits that redefined the PC industry.

Toyota and Dell underscore a key lesson: Innovation rarely emerges from comfort. It happens when limitations force a rethinking of assumptions and the pursuit of more resourceful solutions. These examples of innovation under constraint set the stage for how similar principles apply not just to product development but also to focusing organizational efforts and streamlining operations.

Constraints Create Focus

Focus is about saying no to everything except what truly matters. Constraints clarify your thinking and force you to prioritize ruthlessly.

Few businesses illustrate this better than Southwest Airlines. When Southwest started, it faced tremendous constraints: limited funding, blocked access to major airports, and intense competition from established carriers.

Rather than lament these limitations, Southwest embraced them. They streamlined their entire business around a single aircraft type—the Boeing 737—reducing maintenance costs and complexity. Instead of operating expensive hub-and-spoke routes, Southwest perfected short, direct flights between smaller airports. Faster turnarounds maximized aircraft utilization, reduced downtime, and cut costs. The result: sustained profitability in an industry notorious for volatility.

Another powerful example is Twitter (now X). The product’s original character limit of 140 characters was initially set due to the limitations of SMS text messaging. This forced users to cut the fluff—making brevity a feature, not a flaw. What began as a technical necessity became Twitter’s signature strength: clarity at a glance.

When we operate within clear boundaries, decisions become simpler, priorities clearer. Constraints help us remove noise, streamline thinking, and sharpen our impact.

Designed Constraints

Some of the most focused, innovative companies in the world don’t just adapt to constraints — they create them.

Take Apple under Steve Jobs. When Jobs returned to the company in 1997, he didn’t try to do more. He cut the product line from dozens of models to just four: two desktops and two portables, each targeting consumer and professional markets. That constraint allowed Apple to focus deeply on product quality, design, and user experience.

Jobs famously said, “Focus means saying no to a hundred good ideas.” That wasn’t just philosophy — it was operational strategy. Apple delayed the iPad to prioritize the iPhone, channeling its top talent toward one breakthrough at a time. The result? Fewer products, but better ones — each one a category-defining success.

Jobs called these “enabling constraints.” By narrowing options, Apple made better decisions, faster. Even as the company scaled, it preserved a startup’s mindset: disciplined focus, exacting standards, and ruthless prioritization.

Constraints Elevate Performance

It’s a common misconception that more people, more money, or more tools automatically lead to better performance. In reality, constraints often lead to better outcomes. They clarify priorities, drive efficiency, and sharpen focus.

No company exemplifies this better than Amazon, which has repeatedly turned operational and cost challenges into profitable business lines. Rather than treating constraints as roadblocks, Amazon used them as springboards—building AWS, Marketplace, and its ad business to drive growth and margins.

• The lumpy, non-linear nature of Amazon’s retail business—especially around the holiday surge—highlighted a critical need for scalable infrastructure. During the rest of the year, however, much of that capacity sat unused. Instead of overinvesting in idle servers, Amazon built Amazon Web Services (AWS) to support its own peak demand. It then opened up excess capacity to other businesses, turning a costly internal challenge into a high-margin, market-defining platform.

• Facing the high costs and limits of its first-party inventory model, Amazon launched the Amazon Marketplace. This strategic move reimagined its approach to retail by enabling third-party sellers to list and sell products directly to customers, reducing capital risk while increasing product selection and margins. It created a powerful engine of growth that increased customer choice and strengthened its competitive moat. This was especially effective against rivals still constrained by the belief that they had to own all their inventory.

• Working within the constraints of a low-margin retail business, Amazon launched its advertising business to introduce high-margin economics that could help subsidize the low prices it aimed to offer customers. This move improved sales conversion, increased revenue and margins, and reinforced the company’s growth flywheel.

In each case, constraints did not merely pose challenges; they served as catalysts for innovation and strength. Teams operating under real limits often outperform larger, better-funded ones because they are forced to prioritize speed, discipline, and strategic innovation.

This principle holds true across industries: with the right focus, small, highly skilled teams often outperform larger teams with more resources but less clarity and direction.

Embrace Constraints

Too many leaders believe the solution to a problem is simply more—more money, more people, more resources. This assumption, however, misses the truth: constraints can be leveraged to catalyze growth and deliver better outcomes.

Constraints clarify your thinking and sharpen your priorities. They eliminate distractions, force tough trade-offs, and keep your team aligned around the controllable inputs that actually move the needle.

As a leader, intentionally introduce constraints. Set tight deadlines. Define ambitious goals with strategic boundaries to push your team—and yourself—to find better, more streamlined ways to work while breaking down silos and reducing operational friction. Embrace frugality not out of necessity, but because it fuels sharper thinking, stronger execution, and the potential for outsized impact.

The next time you face a constraint, ask yourself: what if this isn’t a limitation, but a design prompt to rethink and improve your business model?

Great companies and leaders don’t see constraints as limits. They use them to sharpen focus, drive innovation, and create lasting advantage. They don’t succeed in spite of constraints. They succeed because of them

.

Will what made your company successful still make it successful 10 years from now?

Every company reaches a point where yesterday’s success formula becomes tomorrow’s bottleneck. Strategies that once worked may now hold you back. When this moment arrives, companies must pause, reconnect with their core purpose, and ask: Why do we exist?

The Re-Founder's Mindset

Re-founders are leaders who step into an existing company and drive a fundamental reinvention of its strategy, culture, and ways of working while staying true to its mission. Instead of maintaining the status quo, re-founders rethink core advantages, redesign how the company operates and competes, and place bold bets on new areas while ensuring the mission and culture remain intact and adaptable to a changing world.

I first heard the concept of re-founding from Reid Hoffman—the idea that at critical business and industry inflection points, companies need re-founders to ground them back to their core purpose before the business can transform and pursue something new and bold.

Consider Microsoft in 2014. The company wasn’t failing, but it was stagnating. It had missed the mobile wave, was losing cloud market share, and was internally siloed. Microsoft was playing a game it had already won while the market moved elsewhere.

Then Satya Nadella took over. He re-founded Microsoft by:

• Refocusing on Microsoft’s Original Purpose: Shifting Microsoft’s mindset from competing everywhere to focusing on its original purpose—building tools that empower others to build technology. Satya grounded the company in its roots, reminding the organization that Microsoft was founded by Bill Gates and Paul Allen as a tools company to create the BASIC interpreter for the Altair. By realigning with this mission, Microsoft refocused on enabling developers and businesses through tools and infrastructure, which became a key driver of its resurgence. To clarify this purpose internally and externally, he reframed it with a simple message: “If you want to be cool, go join someone else. But if you want to make others cool, join Microsoft."

• Exiting Unwinnable Markets: Nadella made the tough call to shut down Microsoft’s failing Nokia mobile phone business, recognizing that the company had no clear path to leadership in mobile. Instead, he shifted focus to areas with long-term competitive advantage.

• Committing to Cloud Leadership: Microsoft had long been a desktop-first company, but Nadella recognized that its future was in cloud infrastructure, not just software. He made cloud computing a top priority, investing heavily in Azure to compete with AWS.

• Breaking Down Internal Silos: Microsoft’s culture had become fragmented, with divisions operating in isolation. Nadella fostered a more open and collaborative culture, breaking down fiefdoms and encouraging cross-team innovation.

• Betting Big on AI: Seeing AI as the next growth frontier for the industry, Nadella made bold investments in AI research and integration across Microsoft’s products. He led Microsoft to form a deep partnership with OpenAI, investing billions to integrate AI into Azure, Bing, and Office. In a major and surprising move, Microsoft also hired Mustafa Suleyman, cofounder of $4 billion AI startup Inflection, to run its AI operations, along with cofounder Karén Simonyan and key team members. These strategic moves ensured Microsoft would not only compete but lead in the next major wave of technology.

Knowing What to Preserve & What to Change

The hardest part of re-founding isn’t deciding what to change. It’s deciding what to keep.

Tim Cook didn’t try to be Steve Jobs. He knew Apple’s obsession with design and customer experience was non-negotiable. But he also saw that Apple couldn’t rely on hardware alone. Under his leadership, Apple expanded into services, financial products, and custom silicon, creating a more expansive and powerful technology ecosystem. He preserved Apple’s soul while scaling its ambitions.

Dara Khosrowshahi faced a different challenge at Uber. The company had an aggressive, high-growth culture that won regulatory battles—but also created massive dysfunction. Instead of imposing change from the top, he crowdsourced new company values from employees, keeping Uber’s competitive drive while eliminating toxicity.

A refounder doesn’t erase the past. They refine it. They protect what makes a company great while eliminating what holds it back.

Re-Founding Is a Bet on the Future

Re-founding isn’t about just making a company more efficient. It’s about making the company stronger and more competitive to win existing and new markets all while making the right moves before they seem obvious.

Andy Jassy took over as Amazon’s CEO in 2021 after decades of hypergrowth under Jeff Bezos. His challenge was different. Amazon had become so large that reinvention, not expansion, was its biggest need.

Jassy’s leadership marks a re-founding moment in three ways:

• Rebalancing Amazon’s Growth Strategy: Under Bezos, Amazon was in aggressive expansion mode. Jassy shifted focus to profitable growth, cutting underperforming areas such as Alexa hardware while doubling down on high-impact bets. He took a deep look across the company—business by business, invention by invention—asking whether each initiative had the long-term potential to drive revenue, operating income, free cash flow, and return on invested capital. This led to shutting down businesses like Amazon Bookstores, 4-Star stores, Amazon Fabric, and Amazon Care, as well as eliminating underperforming device categories and amending unprofitable programs like free shipping for online grocery orders. Jassy also reprioritized resources, which included making the difficult decision to eliminate 27,000 corporate roles. His disciplined approach has streamlined Amazon’s cost structure and positioned it for more sustainable, high-return growth.

• AI as the Next AWS Moment: Just as AWS refounded Amazon’s business model, Jassy is betting big on AI across Amazon’s cloud, e-commerce, and devices.

• Scaling Leadership Beyond One Founder: Jassy is proving that reinvention is a mindset, not just a founder. His tenure will test whether Amazon can remain bold without its original leader. Great companies outlast their founders, which is why refounder must be part of the design.

MoneyGram’s Re-Founding Moment

MoneyGram is at an inflection point. Our re-founding is an opportunity to accelerate growth and deliver greater value at scale. Our mission remains the same: to connect the world by making the movement of money seamless, affordable, and secure. But how we achieve it must fundamentally change.

The industry is shifting, customer expectations are rising, and AI is redefining both what we deliver and how we deliver it. What worked before will not work going forward. Every function—product, engineering, marketing, sales, and finance—must rethink how it delivers value and drives impact for our customers. We have the opportunity to make global payments faster, smarter, and more cost-effective while expanding our total addressable market. Now it’s on us to execute.

Like Microsoft, Amazon, and Uber, we are preserving what makes us great while eliminating what holds us back. The best companies do not wait for reinvention. They make it their advantage. That is exactly what we are doing now.

The World Doesn’t Stand Still. Neither Should Your Company.

Re-founding is about building to effectively compete and win for the future. The best leaders act before reinvention becomes an obvious need because by then it’s often too late. Ask yourself:

• Are you optimizing your business for the past or building to win the future?

• What areas and bets must you change today to re-found your company for the next decade?

Because in business, there are only two choices: reinvent or be left behind.

At MoneyGram, technology is more than just an enabler—it’s at the core of how we create impact. As we continue to push the boundaries of what's possible in global payments, I’m thrilled to welcome Luke Tuttle as our new Chief Technology Officer.

Luke brings not only deep expertise in fintech, adtech, and commerce but also a passion for building technology that empowers people. His experience at companies like Klarna, Experian, and eBay speaks to his ability to scale innovation, simplify complexity, and drive meaningful transformation. But what stands out most is his belief in technology as a force for good—one that makes financial services more accessible, secure, and seamless for everyone.

As he steps into this role, Luke will lead our technology strategy with a focus on modernization, security, and scalability to make the movement of money across borders seamless, affordable, and secure for everyone. His leadership will be instrumental in accelerating our vision of a world where financial borders no longer limit opportunity, empowering individuals, businesses, and communities to thrive.

Welcome, Luke. We're excited for the journey ahead. 🚀

The official press release here.

Amazon CEO Andy Jassy recently shared some staggering numbers in a LinkedIn post about Amazon’s new generative AI tool, Amazon Q. This tool is signaling that the future of work isn’t a distant concept—it’s already taking shape today. These results don’t just hint at how AI can boost productivity; they serve as a clear indicator of how companies can start leveraging AI to fundamentally change the way work gets done.

What is Amazon Q?
Amazon Q is a GenAI chatbot assistant similar to OpenAI’s ChatGPT. However, what sets Amazon Q apart is its specific design for business use, with a strong focus on optimizing software development tasks. Amazon is using the tool internally to handle some of the most tedious yet essential tasks, such as updating foundational software, fixing bugs, and maintaining security. These necessary but often monotonous tasks are critical to keeping systems running smoothly and delivering high-quality products quickly to customers. This is where Amazon Q steps in, transforming these tasks into streamlined operations and allowing developers to focus on higher-level tasks that can push their products and customer experiences forward.

The Results?
Mind-blowing productivity gains that show doing things smarter with AI isn’t just a nice-to-have—it’s a game-changer. With Amazon Q, the company found the time to upgrade Java applications dropped from 50 developer-days to just a few hours, equating to a staggering 4,500 developer-years saved—equivalent to the work of multiple software development teams over several decades. These aren’t just marginal gains; they’re transformative shifts that redefine what’s possible in software development. Even more impressive, 79% of the auto-generated code was good to go with zero changes. Beyond efficiency, this shift will accelerate innovation, allowing new features and improvements to reach customers faster, enhancing customer satisfaction and keeping the company ahead in a competitive market.

But Speed Alone Isn’t Enough.
In addition to saving time, Amazon Q’s automation enhances security by reducing vulnerabilities, providing an estimated $260 million in annual cost savings. This isn’t just good for peace of mind; it’s a strategic advantage in a competitive market.

And Here’s the Reality Check
This isn’t just an Amazon thing. Every company that relies on software—basically every company—needs to think about how AI fits into their operations. If you’re not using AI to make your business faster, safer, and more efficient, you’re probably already falling behind.

The Big Lesson
The big lesson here isn’t just that Amazon found a faster way to update software. These examples make one thing clear: AI isn’t just a tool for boosting productivity and security; it’s reshaping the fundamental nature of work itself. It’s not about logging hours or adding more people; it’s about maximizing impact, creating customer delight, and focusing on what really drives the business forward. Leaders who overlook AI risk falling behind. The future of work isn’t just about doing things better—it’s about redefining what’s possible. As AI evolves, it will open doors to entirely new business models and opportunities that we haven’t even imagined yet. Beyond software development, AI can revolutionize areas like supply chain management, customer service, and marketing by automating routine tasks, enhancing decision-making, and delivering personalized customer experiences at scale.

Generative AI like Amazon Q doesn’t just change how we work—it changes what work is. If you’re a leader and you’re not seriously looking at how AI can transform your business, you’re already playing catch-up. While the shift to AI might feel daunting, the benefits far outweigh the initial hurdles. The future of work isn’t something to be scared of—it’s something to leverage. And if Amazon’s results are any indication, that future is already here.

So, Where Do You Start?
Look at the tedious tasks within your own organization. Ask yourself: What processes are eating up valuable time and could benefit from AI transformation? Start small by identifying one area where AI can make a significant impact. Consider launching a pilot program to test AI’s effectiveness on a single process, measure the results, and then scale your AI initiatives across other areas of your business. By taking these steps, you’re not just optimizing for efficiency—you’re unlocking the potential to delight customers in ways you never thought possible, outpace the competition, and redefine what’s possible for your business.

Most AI and digital transformation programs fail. Not because the technology doesn’t work, but because the people running them can’t tell the difference between effort and progress.

John Wooden, the legendary basketball coach, said it best: “Never mistake activity for achievement.” That one sentence describes the central failure of most transformation programs I’ve seen.

Here’s what actually happens. Many companies, driven by the fear of falling behind, rush into execution without a clear understanding of their desired outcomes, launching initiatives, deploying tools, and reporting activity, while the metrics that actually matter, revenue, customer satisfaction, operational efficiency, stay flat.

The gap between effort and progress is where transformations go to die.

The Three Myths That Keep Companies Stuck

Most leaders know something is wrong. They just misdiagnose it. Three myths are usually responsible.

Myth 1: Technology is the transformation
The most common mistake in transformation is treating technology as the answer. Buy the right tools, deploy the right platform, and the business changes. It doesn’t work that way.

Technology is the easy part. You can buy it, implement it, and go live on schedule. What you can’t buy is the behavioral change that makes it work. A new CRM doesn’t fix a broken sales process. An AI platform doesn’t fix a culture that doesn’t trust data. The tools sit on top of the organization. If the organization isn’t ready, the tools don’t move the numbers.

The real work is changing how people think and operate. That means being explicit about what new behaviors look like and building them into how you hire, train, and evaluate people. Most importantly, give employees a real reason to change. A mandate without a reason creates compliance at best and resistance at worst.

The rule: technology enables transformation. It doesn’t deliver it. A transformation plan that’s mostly a technology roadmap is only half finished and the results will reflect that.

Myth 2: Early wins mean you’re on track
The easiest mistake in a transformation is celebrating too early. A few departments start showing improvements and suddenly everyone thinks it’s working. Local wins don’t equal enterprise progress.

In siloed organizations, departments optimize in isolation. A faster team doesn’t mean a faster company. You just move the bottleneck downstream. The rest of the organization feels more pressure, not less. Or worse, teams rearrange the furniture. Operations get cheaper and faster but the underlying business model doesn’t change and no new value gets created.

The fix is straightforward but hard to execute. Stop building metrics around the org chart. Build them around the customer journey.

Map how a customer actually experiences your company, end to end. Then align every department’s goals to that journey. Marketing, sales, operations, and service all pulling toward the same outcome measures: customer acquisition, retention, and lifetime value. When everyone is measured against the same destination, local optimization stops being a trap.

It also forces a useful conversation. Departments that hit their numbers while the enterprise misses targets have to explain the gap. That accountability doesn’t exist when everyone manages to their own scorecard.

The rule is simple: if your metrics can’t tell you whether the customer won, they’re the wrong metrics.

Myth 3: Transformation has a finish line
Most transformation programs are run like projects. There’s a launch date, a budget, a go-live milestone, and an implied moment when it’s done. That framing is the problem.

The best-run companies never declare victory. They build the capability to keep changing. The market shifts, customer expectations move, new technology emerges. The organizations that treat transformation as a permanent operating model stay ahead. The ones that treat it as a project fall behind again within two years of completion.

This also explains why so many transformations look successful at launch and disappointing eighteen months later. The project ends, attention moves elsewhere, and the new ways of working slowly revert to the old ones.

The fix is to stop running transformation as a program and start running it the way Toyota runs manufacturing. Kaizen, the practice of continuous improvement, is the model. Small, deliberate improvements made every day by every team compound into structural advantage over time. It’s not a project. It’s how the organization works.

The best leaders I’ve seen treat transformation the same way. There is no finish line. There is only the discipline to keep improving, measuring, and raising the bar. The work is never done. That’s not a problem. That’s the point.

If your transformation has a go-live date and no plan for what comes after, you’re not transforming. You’re renovating.

The question every leader needs to ask is not “are we working hard on this?” Almost everyone is. The question is whether you can measure, specifically, what has changed for your customers and your business. If the answer is vague, you’re mistaking effort for progress.

Wooden had it right. Activity is not achievement. The leaders who understand that distinction, and build their organizations around it, are the ones who come out ahead. The work is never done. That’s not a burden. That’s the advantage.

A few months ago I was in a board meeting reviewing a turnaround plan for a business that had stalled for years. The traditional playbook was on the table. Rebuild the sales org. Add 40 to 50 quota-carrying heads. Invest in more marketing staff. Halfway through the presentation, a board member stopped and asked a different question.

“If we had to triple revenue with almost no net new headcount, what would this plan look like?”

That one question flipped the room. Instead of debating how many people to add to each function, the team started rethinking the work itself. Instrumenting every step of the funnel. Embedding AI agents into lead routing and outreach. Using copilots to compress ops and finance workloads. Reserving scarce human capacity for the genuinely hard, high-judgment parts of the business. The plan that emerged wasn’t about rebuilding departments. It was about replacing the headcount reflex with something more powerful: humans and AI working together as the engine of growth.

That moment crystallized something I had been observing across 18 months of conversations with public and large private companies about their AI plans. The organizations pulling ahead aren’t asking “How do we add AI to marketing, finance, or operations?” They’re starting with a simpler, harder question: “What are the few critical problems this company exists to solve?” From there, they design work as systems where humans and AI jointly own those problems. The org chart comes last, not first.

The Shift Most Leaders are Missing

The old question was: how many people do we need? The new question is: what system do we need to build? Most leaders are still asking the first one.

That sounds abstract until you see it play out in a boardroom. Then it’s obvious.

The old model: a problem arrives, you staff a team, the team does the work, you measure output by headcount and activity. The new model: a problem arrives, you design a system, humans and AI agents run the system together, you measure output by outcomes.

Scaling used to mean adding people to departments. Increasingly it means scaling the orchestration of humans, data, and AI agents, and the compute behind them. Headcount becomes one input, not the dominant lever.

Most leaders haven’t internalized this yet. They’re still equating scale with hiring. Every quarter they wait, the gap between them and the companies that have made this shift gets wider and harder to close.

The Ladder of Work

Across the companies I’ve spoken with, a pattern emerges. Call it the ladder of work.

The first rung is where most companies still are: human-only work, with AI as an accessory. People own the job. Tools help occasionally.

The second rung is where most transformation programs are aimed: human plus AI copilot. AI assists but humans still own every decision. It’s a meaningful step. It’s also a rest stop, not the destination.

The third rung is where the leading companies are heading: AI agent plus human copilot. AI runs the default play. Humans supervise, handle edge cases, and refine the system. The human role shifts from doing the work to steering and improving the system that does the work.

The fourth rung, already visible in select domains, is AI autopilot. Humans set objectives, policies, and guardrails. They don’t touch most transactions.

The companies that will win are already designing for the third and fourth rungs. The rest are optimizing a model that’s already being disrupted.

What This Breaks

Once you see the shift clearly, familiar management debates start to look like the wrong conversation.

Job descriptions written around functions rather than problems become obsolete faster than you can update them. Budgeting processes that treat headcount as the primary unit of investment start to misallocate capital. Org charts designed around departments rather than problem-solving systems slow everything down.

The primary design decision is no longer “How many people do we need in this function?” It’s “For this problem, what is the right configuration of humans, data, and AI agents, and how do we scale that system?”

That is a fundamentally different question. Most planning processes aren’t built to ask it.

The Question Worth Asking

The companies I’ve watched making this transition share one trait. They behave as if they are already being forced to operate with minimal headcount. They design for revenue and revenue per employee to grow nonlinearly through systems, automation, and AI, not through linear hiring.

That boardroom moment, where a board member stopped asking “How many people do we need?” and started asking “How do we redesign the work so a small team plus AI can do the work of a much larger one?” is what getting ahead of this shift actually looks like.

It’s not a transformation decision. It’s not even a technology decision. It’s a design decision every company will eventually be forced to make. The only question is whether you make it on your terms or on the market’s.

The question worth asking in your next planning cycle is simple: are you staffing functions or designing systems? The answer will determine where your company stands in five years.

Today marks a significant milestone with OpenAI’s introduction of GPT-4o—the ‘o’ stands for omni. It’s a groundbreaking update that’s transforming how we interact with machines by integrating audio, vision, and text seamlessly into a single AI model. This makes handling various types of media incredibly smooth and efficient, significantly enhancing the ChatGPT experience for consumers as well as opening up the floodgates to a new era of reimagined applications.

Information on how GPT-4o operates is limited. OpenAI’s announcement revealed only that GPT-4o is a unified neural network trained on text, vision, and audio inputs. This method contrasts with the prior approach, where separate models were trained for each type of data. This innovative approach simplifies interactions across various media types, contributing to the model’s efficiency and versatility.

One of the most exciting new features is the ability to interact with ChatGPT through video. Now, you can share live footage—for instance, a math problem you’re struggling with—and receive assistance directly from ChatGPT, whether it’s solving the problem or guiding you through it. Additionally, you can share screenshots, photos, and documents with both text and images. This makes ChatGPT more versatile in educational, professional, and personal contexts.

For developers, this update is particularly thrilling. The cost of using GPT-4o has been slashed by 50%, and its performance has doubled compared to GPT-4 Turbo. This means developers now have access to smarter technology faster and at half the cost. GPT-4o is proving to be the best-performing model available right now, excelling across numerous benchmarks. The implications of this are profound, as it opens up new opportunities for innovation due to the improved cost and performance. It’s a fantastic time to be building with AI, as these improvements promise to unlock a whole new world of possibilities. Plus, it’s a great reminder of the value of a platform that keeps you connected with the latest AI advancements.

You can see the official launch of ChatGPT-4o and some mind-boggling demos in this video:

The Evolution of OpenAI’s ChatGPT Language Model

To appreciate the significance of ChatGPT 4.0, it’s helpful to review the progression of OpenAI’s language models:

2018: GPT-1 was launched, demonstrating the potential of large-scale unsupervised language models. This initial model set the stage for future advancements by showcasing the viability of generative pre-trained transformers.

2019: GPT-2 was released with 1.5 billion parameters, significantly improving text generation capabilities. Its ability to generate coherent and realistic text sequences marked a significant leap from GPT-1, handling a wider range of language tasks with greater proficiency.

2020: GPT-3 arrived with 175 billion parameters, representing a substantial advancement in AI capabilities. The large parameter size enabled it to perform tasks with greater fluency and versatility, making it a powerful tool for diverse applications, including coding and content creation.

November 30, 2022: marked a transformative moment for generative AI when OpenAI launched ChatGPT GPT-3.5. This launch was reminiscent of the “Netscape” moment for the internet, offering the world a glimpse of a machine capable of understanding, engaging, and reasoning in human-like conversations. The response to ChatGPT was extraordinary. Within just five days, it amassed one million users, setting a record as the fastest-growing consumer application in history.

By February 2023, a mere two months post-launch, ChatGPT had achieved over 100 million monthly active users. To put this into perspective, it took TikTok nine months and Instagram two and a half years to reach the same milestone.

2023: GPT-4 was introduced, offering enhanced reliability, creativity, and problem-solving skills. This model built upon the capabilities of GPT-3, delivering more accurate and context-aware responses.

May 2024: ChatGPT 4.0 was released, incorporating enhanced natural language understanding, contextual awareness, and integration features. This latest version builds on the strengths of its predecessors, with specific improvements aimed at developers, such as more accurate code generation, better debugging assistance, and integration into various development tools and environments.

By tracing this timeline, we can see how each iteration has progressively enhanced the capabilities and applications of OpenAI’s language models, culminating in the advanced features of ChatGPT-4o.

Conclusion

ChatGPT 4.0 signifies a remarkable leap forward in AI capabilities. With enhanced natural language understanding, superior contextual awareness, advanced integration features, and an expanded knowledge base, it stands as a powerful and versatile tool for developers. This latest iteration has the potential to revolutionize how developers interact with AI, driving innovation and efficiency across various applications.

However, it’s crucial to maintain an objective perspective. While these advancements are impressive, it’s important to consider the practical implications and limitations of the technology. Evaluate alternatives and choose the tool that best suits your specific needs and projects. Always remember that the right tool can make all the difference in achieving your goals.

As artificial intelligence reshapes industries, the deceptive practice of ‘AI washing’—akin to ‘greenwashing’—is emerging as a major concern among tech experts and regulators. This practice involves companies exaggerating or fabricating their AI capabilities, prompting scrutiny from both the Securities and Exchange Commission (SEC) and the Federal Trade Commission (FTC). Such actions underline the critical need for transparency and accuracy in AI-related claims.

Clear and honest reporting is essential, yet it requires a delicate balance. While regulatory measures are crucial for preventing misleading claims and protecting stakeholders, overly stringent regulations could stifle innovation, especially in a field as nascent and rapidly evolving as AI. The early days of the space race provide a pertinent historical parallel. Just as premature and overly detailed regulations could have curtailed the innovative leaps made in space exploration, too heavy a hand in governing AI’s early development could slow progress at a time when momentum is vital.

The challenge is to create regulations that ensure transparency and accountability without stifling innovation that drives technological advancement. To this end, regulatory bodies like the SEC could consider flexible frameworks that adapt over time, incorporating industry input and evolving as the technology itself does. A relevant example from the fintech sector involves ‘regulatory sandboxes,’ which allow startups to test innovative financial products within a controlled regulatory framework. This approach, pioneered by the UK’s Financial Conduct Authority, has proven effective in balancing the need for robust oversight with the imperative to foster innovation.

Furthermore, industry conferences such as HumanX are crucial. They serve as vital platforms where technologists, regulators, and ethicists come together to discuss and define best practices and develop new oversight models tailored to the unique challenges of AI.

To navigate this complex terrain, companies should proactively engage with these developing standards and participate in shaping the conversation. By collaborating on universal benchmarks for AI claims and supporting the development of independent verification tools—similar to initiatives in other industries—businesses can help ensure that innovation and integrity go hand in hand.

As we stand on the cusp of AI’s potential, let us commit to a path that neither hinders technological breakthroughs nor compromises on the ethical standards that must underpin such advancements. A balanced, thoughtful approach to AI regulation will serve not only to protect consumers and investors but also to foster an ecosystem in which genuine innovation can flourish.

My friend Mike Speiser’s recent LinkedIn post about his early career experience at Apple brought back fond memories of starting my own career there. Reflecting on my journey, my time at Apple was like pursuing a graduate degree in thinking differently, operating as owners, and cultivating curiosity to invent and simplify—all dedicated to addressing fundamental customer needs.

Each principle from this time has profoundly shaped my approach to work and life. I feel lucky and am forever grateful for the people, projects, and lessons learned during my time at Apple. Forever 

I am a husband, father, and business technology leader with many interests. I write to think “out loud”—topics that fascinate me and that I hope will also interest you.

Here, I’ll share insights deeply rooted in my personal and professional life, pondering topics that not only intrigue me but also have the potential to engage and resonate with you, the reader. Whether it’s the latest in technology, business strategies, or the balance of work and life, the goal is to explore these subjects thoroughly.

It’s important to note that the views expressed here are solely my own. They reflect my personal opinions, not those of any associated entities. These perspectives are informed by current knowledge and will evolve over time, shaped by ongoing experiences and new information.

This blog is more than a repository of thoughts; it is a venue for intellectual exchange. I encourage you to share your views, challenge ideas, and offer insights. Together, we can build a community that thrives on thoughtful dialogue and shared learning.

Welcome to the conversation.