Author: Aditya

  • From Chess Master to Self-Driving Car: Understanding AI’s Big Picture

    From Chess Master to Self-Driving Car: Understanding AI’s Big Picture

    This is a crosspost of my article for The Print

    AI is replacing jobs—but which ones, and why? That question keeps resurfacing as headlines ping between panic and hype. The real answer, though, lies not in broad generalizations but in a deeper understanding of how different types of AI actually work—and more importantly, where they thrive and where they struggle.

    To unpack this, let’s start with a tale of two AIs. One plays chess. The other drives a car.

    The Game That Changed Everything

    Chess was once the gold standard of human intelligence. It required memory, strategy, foresight—surely, we thought, only the brightest minds could master it. Then came Deep Blue, then AlphaZero, and today, chess engines far outstrip the world’s best grandmasters.

    Why? Because chess is a closed world. The board is an eight-by-eight grid. The rules are fixed. Every piece behaves predictably. A knight never surprises you by moving like a queen. And the worst that can happen if the AI makes a mistake? It loses the game. No one gets hurt.

    That’s what makes chess such a perfect domain for AI. It’s highly predictable, and the consequences of error are minimal.

    The Road That Refuses to Be Tamed

    Now think of a self-driving car. Its environment is the polar opposite of a chessboard. The road is full of unpredictable drivers, jaywalking pedestrians, blown-out tires, random construction, rain-slicked asphalt, and sudden GPS glitches. There’s no guaranteed script.

    Worse, a single error can have catastrophic results. A misjudged turn or a missed stop sign doesn’t just mean “game over”—it could mean injury or even death. In this world, low predictability collides with high consequences, demanding an entirely different kind of intelligence—one that machines still struggle to master.

    The Two-Axis Map of AI’s Real Power

    What separates chess-playing AIs from self-driving ones isn’t just technical complexity. It’s the nature of the task itself. And that brings us to the core idea: a two-axis map that helps us understand where AI excels, where it falters, and what it means for the future of work.

    Imagine a graph:

    • On the horizontal axis, you have Predictability. To the right: structured, rule-based tasks like bookkeeping or board games. To the left: chaotic, real-world tasks like emergency response or childcare.
    • On the vertical axis, you have Consequence of Error. At the bottom: low-stakes domains where mistakes are annoying but harmless, like a bad movie recommendation. At the top: high-stakes arenas where a single misstep can cause financial ruin or loss of life.

    Jobs that sit in the bottom-right corner—predictable and low-consequence—are prime targets for full automation. Think data entry, inventory tracking, or sorting packages in a warehouse. Machines handle these with ease.

    But jobs in the top-left corner—unpredictable and high-consequence—remain stubbornly human. Think surgeons, firefighters, diplomats, or yes, even taxi drivers. These roles demand judgment, adaptability, empathy, and accountability. They are much harder, if not impossible, for AI to fully replace.

    Enter the Centaur

    This is where one of the most powerful ideas in AI comes into play: human-AI collaboration. Borrowed from the world of chess, it’s called “Centaur Chess.”

    In Centaur Chess, human players team up with AI engines. The machine crunches millions of possibilities per second. The human brings strategy, creativity, and long-term thinking. Together, they often outperform both lone humans and pure AI systems.

    This hybrid model is the future of many professions. In medicine, AI can scan thousands of X-rays in seconds, flagging anomalies. But a doctor makes the final call, understanding the patient’s story, context, and risks. In creative fields, AI can generate endless design variations, but an artist selects, curates, and gives meaning.

    The centaur doesn’t fear the machine. It rides it.

    Rethinking the Future of Work

    So, when people ask, “Will AI take my job?” the better question is: What kind of task is it? Is it rule-based or fuzzy? Are the stakes low or life-changing?

    AI is incredibly powerful at doing narrow, well-defined things faster than any human. But it is brittle in the face of chaos, ambiguity, and moral weight. And in those very places—where the world is messy and the stakes are high—humans are not just relevant; they are indispensable.

    The future of work won’t be a clean divide between jobs AI can do and jobs it can’t. It will be a layered world, where the most effective roles are those that blend human judgment with machine intelligence. So yes, some jobs will disappear. But others will evolve. And the real winners will be the centaurs.

  • India’s Race Between Demography and AI

    India’s Race Between Demography and AI

    Artificial Intelligence is often framed as a threat to jobs—a disruptive force poised to replace human labour at an unprecedented scale. From call centres to accounting firms, from routine coding to legal research, Generative AI and automation tools are already demonstrating capabilities that once seemed untouchable. The fear of widespread job loss is not unfounded. McKinsey, among others, estimates that nearly a quarter of global work activities could be automated by the early 2030s.

    Yet, there is another equally significant demographic trend reshaping the labour market—the aging of populations. In countries such as Japan, South Korea, Germany, and even China, the working-age population is shrinking. This is not because jobs are disappearing, but because people are. Fertility rates have fallen below replacement levels, and the proportion of elderly citizens is rising sharply. These nations face a paradox: they need more workers but have fewer people available to fill roles.

    AI and Aging: Complementary Forces in Developed Countries

    This is where AI and aging unexpectedly complement each other. In economies that are already greying, AI is less a destroyer of jobs and more a replacement for the labour that no longer exists. Japan, for example, has pioneered the use of robotics and AI-driven systems not to replace young workers, but to stand in for absent ones—care robots for the elderly, AI-assisted diagnostics for hospitals short on doctors, and factory automation for industries facing chronic staff shortages.

    In such societies, the fear of AI taking away jobs is muted by the demographic reality that many jobs would otherwise remain unfilled. AI is effectively stepping into the gap created by demographic decline. For them, the challenge is not managing unemployment but managing the technological transition in a way that sustains productivity and care standards as their populations age.

    India’s Young Advantage—and the Ticking Clock

    India, however, tells a different story. The country’s demographic structure is still overwhelmingly young. Nearly two-thirds of Indians are in the working-age bracket, and the median age is around 28—more than a decade younger than China or the U.S. This “demographic dividend” has been hailed as India’s biggest economic advantage for the next 10–15 years. But this window is finite.

    Demographers estimate that by the mid-2030s, India’s working-age population will peak. After that, the proportion of elderly citizens will start rising sharply. By 2046, the elderly are projected to outnumber children under 14. In other words, India’s advantage will begin to fade just as many advanced economies have already entered the post-dividend phase. If India cannot create enough productive jobs during this critical decade, its youth bulge may turn into a liability.

    AI’s Adoption Curve

    The question is: will AI go mainstream while India’s workforce is still young? Current projections suggest that large-scale AI adoption is still 5–15 years away. Today’s Generative AI tools, while impressive, remain in an experimental phase. They lack reliability, governance frameworks, and cost efficiency at scale. Gartner’s hype cycle places most AI technologies in the “Trough of Disillusionment,” meaning that widespread productivity gains will take years to materialize.

    If this trajectory holds, AI’s mainstream integration across sectors like healthcare, education, law, and public administration may not happen until the 2030s—roughly the same time that India’s demographic dividend starts to decline. This sets up an intriguing scenario where India’s labour market transition and AI’s maturity could synchronize.

    Possible Scenarios for India

    1. The Collision Scenario:

    If AI adoption accelerates too quickly, India’s youthful workforce may find itself competing against machines for jobs before the country has built a strong industrial and service base. Sectors such as BPO, customer service, and low-skill IT roles—once the backbone of India’s outsourcing economy—could see rapid automation. Without massive reskilling efforts, unemployment among young Indians could spike even as the global economy demands fewer entry-level jobs.

    2. The Missed Opportunity Scenario:

    Alternatively, if AI adoption lags too far behind—say, beyond 2040—India could enter its aging phase without having reaped the productivity gains AI promises. By then, the country would face the dual pressures of a shrinking workforce and a delayed technological transition. This would mirror some of the struggles seen in late-industrializing economies that missed the manufacturing wave.

    3. The Synchronization Scenario:

    The most optimistic possibility is that AI and India’s demographic transition align productively. Over the next decade, India could use its young workforce to build, train, and scale AI systems, preparing the ground for when labour shortages begin. By the time the aging curve hits in the 2035–2040 period, AI could step in not as a threat, but as a productivity amplifier—automating routine tasks while humans focus on complex, creative, or empathetic roles.

    This requires a proactive strategy: early investment in AI literacy, creation of AI-enabled jobs (rather than job replacement), and building a global service economy where Indians are not just users of AI, but architects of AI solutions.

    The Decisive Decade

    India’s story in the 2030s will be defined by the intersection of two megatrends: a maturing workforce and a maturing technology. Whether this convergence leads to disruption or opportunity depends on choices made now—in education, infrastructure, governance, and industry adoption. The challenge is to ensure that when AI becomes mainstream, India’s workforce is not left behind but is ready to ride the wave. The 2020s are not just a decade of demographic advantage—they are the runway for an AI-driven, post-dividend future.

  • The Economic Reality and the Optimistic Future of Agentic Coding

    The Economic Reality and the Optimistic Future of Agentic Coding

    After a couple of months deep in the trenches of vibe coding with AI agents, I’ve learned this much: scaling from a fun, magical PoC to an enterprise-grade MVP is a completely different game.

    Why Scaling Remains Hard—And Costly

    Getting a prototype out the door? No problem.

    But taking it to something robust, secure, and maintainable? Here’s where today’s AI tools reveal their limits:

    • Maintenance becomes a slog. Once you start patching AI-generated code, hidden dependencies and context loss pile up. Keeping everything working as requirements change feels like chasing gremlins through a maze.
    • Context loss multiplies with scale. As your codebase grows, so do the risks of agents forgetting crucial design choices or breaking things when asked to “improve” features.

    And then there’s the other elephant in the room: costs.

    • The cost scaling isn’t marginal—not like the old days of cloud or Web 2.0. Powerful models chew through tokens and API credits at a rate that surprises even seasoned devs.
    • That $20/month Cursor plan with unlimited auto mode? For hobby projects, it’s a steal. For real business needs, I can see why some queries rack up millions of tokens and would quickly outgrow even the $200 ultra plan.
    • This is why we’re seeing big tech layoffs and restructuring: AI-driven productivity gains aren’t evenly distributed, and the cost curve for the biggest players keeps climbing.

    What the Data Tells Us

    That research paper—Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity—had a surprising conclusion:

    Not only did experienced developers see no time savings on real-world coding tasks with AI, but costs increased as they spent more time reviewing, correcting, and adapting agent output.

    The lesson:

    AI shifts where the work happens—it doesn’t always reduce it. For now, scaling with agents is only as good as your processes for context, review, and cost control.

    Why I Remain Optimistic

    Despite the challenges, I’m genuinely excited for what’s coming next.

    • The platforms and models are evolving at warp speed. Many of the headaches I face today—context loss, doc gaps, cost blind spots—will get solved just as software engineering best practices eventually became codified in our tools and frameworks.
    • Agentic coding will find its place. It might not fully automate developer roles, but it will reshape teams: more focus on high-leverage decisions, design, and creative problem-solving, less on boilerplate and “busy work.”

    And if you care about the craft, the opportunity is real:

    • Devs who learn to manage, review, and direct agents will be in demand.
    • Organizations that figure out how to blend agentic workflows with human expertise and robust process will win big.

    Open Questions for the Future

    • Will AI agentic coding mean smaller, nimbler teams—or simply more ambitious projects for the same headcount?
    • How will the developer role evolve when so much code is “synthesized,” not hand-crafted?
    • What new best practices, cost controls, and team rituals will we invent as agentic coding matures?

    Final thought:

    The future won’t be a return to “pure code” or a total AI handoff. It’ll be a blend—one that rewards curiosity, resilience, and the willingness to keep learning.

    Where do you see your work—and your team—in this new landscape?

  • The Law of Leaky Abstractions & the Unexpected Slowdown

    The Law of Leaky Abstractions & the Unexpected Slowdown

    If the first rush of agentic/vibe coding feels like having a team of superhuman developers, the second phase is a reality check—one that every software builder and AI enthusiast needs to understand.

    Why “Vibe Coding” Alone Can’t Scale

    The further I got into building real-world prototypes with AI agents, the clearer it became: Joel Spolsky’s law of leaky abstractions is alive and well.

    You can’t just vibe code your way to a robust app—because underneath the magic, the cracks start to show fast. AI-generated coding is an abstraction, and like all abstractions, it leaks. When it leaks, you need to know what’s really happening underneath.

    My Experience: Hallucinations, Context Loss, and Broken Promises

    I lost count of the times an agent “forgot” what I was trying to do, changed underlying logic mid-stream, or hallucinated code that simply didn’t run. Sometimes it wrote beautiful test suites and then… broke the underlying logic with a “fix” I never asked for. It was like having a junior developer who could code at blazing speed—but with almost no institutional memory or sense for what mattered.

    The “context elephant” is real. As sessions get longer, agents lose track of goals and start generating output that’s more confusing than helpful. That’s why my own best practices quickly became non-negotiable:

    • Frequent commits and clear commit messages
    • Dev context files to anchor each session
    • Separate dev/QA/prod environments to avoid catastrophic rollbacks (especially with database changes)

    What the Research Shows: AI Can Actually Slow Down Experienced Devs

    Here’s the kicker—my frustration isn’t unique.

    A recent research paper, Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity, found that experienced developers actually worked slower with AI on real-world tasks. That’s right—AI tools didn’t just fail to deliver the expected productivity boost, they created friction.

    Why?

    • Only about 44% of AI-generated code was accepted
    • Developers lost time reviewing, debugging, and correcting “bad” generations
    • Context loss and reliability issues forced more manual intervention, not less

    This matches my experience exactly. For all the hype, these tools introduce new bottlenecks—especially if you’re expecting them to “just work” out of the box.

    Lessons from the Frontlines (and from Agent Week)

    I’m not alone. In the article What I Learned Trying Seven Coding Agents, Timothy B. Lee finds similar headaches:

    • Agents get stuck
    • Complex tasks routinely stump even the best models
    • Human-in-the-loop review isn’t going anywhere

    But the tools are still useful—they’re not a dead end. You just need to treat them like a constantly rotating team of interns, not fully autonomous engineers.

    Best Practices: How to Keep AI Agents Under Control

    So how do you avoid the worst pitfalls?

    The answer is surprisingly old-school:

    • Human supervision for every critical change
    • Sandboxing and least privilege for agent actions
    • Version control and regular context refreshers

    Again, Lee’s article Keeping AI agents under control doesn’t seem very hard nails it:

    Classic engineering controls—proven in decades of team-based software—work just as well for AI. “Doomer” fears are overblown, but so is the hype about autonomy.

    Conclusion: The Hidden Cost of Abstraction

    Vibe coding with agents is like riding a rocket with no seatbelt—exhilarating, but you’ll need to learn to steer, brake, and fix things mid-flight.

    If you ignore the leaky abstractions, you’ll pay the price in lost time, broken prototypes, and hidden tech debt.

    But with the right mix of skepticism and software discipline, you can harness the magic and avoid the mess.

    In my next post, I’ll zoom out to the economics—where cost, scaling, and the future of developer work come into play.

    To be continued…

  • The Thrill and the Illusion of AI Agentic Coding

    The Thrill and the Illusion of AI Agentic Coding

    A few months ago, I stumbled into what felt like a superpower: building fully functional enterprise prototypes using nothing but vibe coding and AI agent tools like Cursor and Claude. The pace was intoxicating—I could spin up a PoC in days instead of weeks, crank out documentation and test suites, and automate all the boring stuff I used to dread.

    But here’s the secret I discovered: working with these AI agents isn’t like managing a team of brilliant, reliable developers. It’s more like leading a software team with a sky-high attrition rate and non-existent knowledge transfer practices. Imagine onboarding a fresh dev every couple of hours, only to have them forget what happened yesterday and misinterpret your requirements—over and over again. That’s vibe coding with agents.

    The Early Magic

    When it works, it really works. I’ve built multiple PoCs this way—each one a small experiment, delivered at a speed I never thought possible. The agents are fantastic for “greenfield” tasks: setting up skeleton apps, generating sample datasets, and creating exhaustive test suites with a few prompts. They can even whip up pages of API docs and help document internal workflows with impressive speed.

    It’s not just me. Thomas Ptacek’s piece “My AI Skeptic Friends Are All Nuts” hits the nail on the head: AI is raising the floor for software development. The boring, repetitive coding work—the scaffolding, the CRUD operations, the endless boilerplate—gets handled in minutes, letting me focus on the interesting edge cases or higher-level product thinking. As they put it, “AI is a game-changer for the drudge work,” and I’ve found this to be 100% true.

    The Fragility Behind the Hype

    But here’s where the illusion comes in. Even with this boost, the experience is a long way from plug-and-play engineering. These AI coding agents don’t retain context well; they can hallucinate requirements, generate code that fails silently, or simply ignore crucial business logic because the conversation moved too fast. The “high-attrition, low-knowledge-transfer team” analogy isn’t just a joke—it’s my daily reality. I’m often forced to stop and rebuild context from scratch, re-explain core concepts, and review every change with a skeptical eye.

    Version control quickly became my lifeline. Frequent commits, detailed commit messages, and an obsessive approach to saving state are my insurance policy against the chaos that sometimes erupts. The magic is real, but it’s brittle: a PoC can go from “looks good” to “completely broken” in a couple of prompts if you’re not careful.

    Superpowers—With Limits

    If you’re a founder, product manager, or even an experienced developer, these tools can absolutely supercharge your output. But don’t believe the hype about “no-code” or “auto-code” replacing foundational knowledge. If you don’t understand software basics—version control, debugging, the structure of a modern web app—you’ll quickly hit walls that feel like magic turning to madness.

    Still, I’m optimistic. The productivity gains are real, and the thrill of seeing a new prototype come to life in a weekend is hard to beat. But the more I use these tools, the more I appreciate the fundamentals that have always mattered in software—and why, in the next post, I’ll talk about the unavoidable reality check that comes when abstractions leak and AI doesn’t quite deliver on its promise.

    To be continued…

  • A Brief History of Artificial Intelligence: From Turing to Transformers

    A Brief History of Artificial Intelligence: From Turing to Transformers

    This is a crosspost of my article for The Print

    Artificial Intelligence did not begin with code—it began with a question. Could machines think? And if so, how would we even know?

    In 1950, Alan Turing proposed that if a machine could carry on a conversation indistinguishable from a human, it could be called intelligent. This became the Turing Test, and it marked the philosophical beginning of AI.

    The technical beginning followed six years later, at the Dartmouth Workshop of 1956. Organized by John McCarthy, Marvin Minsky, Claude Shannon and others, it launched AI as a formal discipline. The claim was breathtaking: “Every aspect of learning or any other feature of intelligence can in principle be so precisely described that a machine can be made to simulate it.” For a while, that dream held.

    The 1960s and 70s saw AI become a fixture of science fiction. Stanley Kubrick’s 2001: A Space Odyssey imagined HAL 9000, a machine that could speak, reason, and feel—until conflicting objectives caused it to turn rogue. HAL’s breakdown wasn’t madness—it was logic stretched to a breaking point. And that remains one of AI’s deepest warnings: machines may fail not because they malfunction, but because their goals are misaligned with ours.

    From the 1960s to the 1980s, Symbolic AI dominated the field. Intelligence was programmed through logic and rules, not learned from data. Expert systems like MYCIN and DENDRAL mimicked human specialists and briefly dazzled funders, but they were brittle—struggling with ambiguity and real-world complexity. Each new scenario demanded new rules, revealing the limits of hand-coded intelligence.

    The initial optimism faded. Early successes didn’t scale, and by the 1970s and again in the late 1980s, AI faced its winters—eras of disillusionment and vanishing support. The technology wasn’t ready. AI, once hailed as revolutionary, became a cautionary tale.

    Meanwhile, the world of chess provided a battleground for AI’s ambitions. In 1968, computer scientist John McCarthy bet that no machine could beat chess master David Levy in a match within ten years. He was right—but only just. By 1997, IBM’s Deep Blue defeated Garry Kasparov, the reigning world champion. This wasn’t intelligence in the human sense. Deep Blue didn’t think; it calculated—200 million positions per second, guided by rules and brute force.

    If Deep Blue marked a brute-force triumph, the next revolution came from inspiration closer to biology. Our brains are made of neurons and synapses, constantly rewiring based on experience. In 1943, McCulloch and Pitts proposed the first mathematical model of a neural network, mimicking how neurons fire and connect. Decades later, with more data and computational power, this idea would explode into what we now call deep learning.

    A key moment came in 2012. Researchers at Google Brain fed a deep neural network 10 million YouTube thumbnails—without labels. Astonishingly, one neuron began to specialize in detecting cat faces. The machine wasn’t told what a cat was. It discovered “cat-ness” on its own. This was the cat moment—the first clear sign that neural networks could extract meaning from raw data. From then on, deep learning would take off.

    That same year, another milestone arrived. AlexNet, a deep convolutional neural network, entered the ImageNet Challenge, a global competition for visual object recognition. It halved the previous error rate, using an 8-layer network trained on GPUs. This marked the beginning of AI’s rise in vision—powering facial recognition, self-driving cars, and medical diagnostics.

    In board games too, AI moved from mimicry to mastery. AlphaGo’s match against world Go champion Lee Sedol in 2016 stunned experts. Game 2, Move 37—an unconventional, creative move—changed the game’s theory forever. AlphaGo didn’t just compute; it improvised. In 2017, AlphaZero went further, mastering chess, Go, and shogi without human examples—just the rules and millions of self-play games. Grandmasters called its style “alien” and “beautiful.”

    In 2017, the landmark paper “Attention Is All You Need” introduced the Transformer architecture, a breakthrough that changed the course of AI. Unlike earlier models, Transformers could handle vast contexts and relationships between words, enabling a deeper understanding of language patterns. This paved the way for large language models (LLMs) like GPT and ChatGPT, trained on billions of words from books, websites, and online conversations. These models don’t know facts as humans do—they predict the next word based on learned patterns. Yet their output is often strikingly fluent and, at times, indistinguishable from human writing.

    These models don’t understand language the way we do. They predict the next word based on probabilities. And yet, their output often sounds thoughtful, even profound. In 2025, one such model helped save a pregnant woman’s life by identifying a symptom of preeclampsia from a casual health question. This was no longer science fiction. AI was here helping, guiding, even warning.

    This is where the story darkens. Neural networks have millions—even billions—of internal parameters. We know how they are trained, but not always why they produce a particular result. This is the black box problem: powerful models we can’t fully interpret.

    Worse, these models inherit biases from the data they are trained on. If trained on internet text that contains racial, gender, or cultural prejudices, the model may echo them—sometimes subtly, sometimes dangerously. And because their reasoning is opaque, these biases can be hard to detect and even harder to fix.

    AI systems are also confident liars. They “hallucinate” facts, produce fake citations, or reinforce misinformation—often with grammatical precision and emotional persuasion. They are trained to be convincing, not correct.

    As we hand over more decisions to machines—medical diagnoses, hiring recommendations, bail assessments, autonomous driving—we face hard questions: Who is responsible when an AI system fails? Should a machine ever make a life-or-death decision? How do we align machine goals with human values?

    The fictional HAL 9000 chose its mission over its crew, not out of malice, but from a conflict of objectives. Today’s systems don’t “choose” at all, but they still act, and their actions have consequences. Ironically, the most hopeful vision may lie in chess again. In freestyle tournaments, the best performers weren’t machines or grandmasters—but human-AI teams. Garry Kasparov put it best: “A weak human + machine + good process beats a strong human or strong machine alone.” AI doesn’t need to replace us. It can enhance us—if we build it thoughtfully, interpret it critically, and embed it in processes we trust.

  • What the 2025 Mary Meeker AI Report Means for Work, Strategy, and GTM

    What the 2025 Mary Meeker AI Report Means for Work, Strategy, and GTM

    It’s been a while since Mary Meeker’s Internet Trends report provided a pulse check on where technology is headed. The first such report in a while, now focused on AI, does more than describe trends — it lays out a new operating reality.

    This post distills 8 critical insights from the report — and what they mean for enterprise leaders, GTM strategists, product owners, and those shaping the future of work.

    📄 Full Report →


    1. This Time, the Machines Move Faster Than We Do

    The report opens with a bold observation:

    “AI usage is ramping faster than any prior computing platform — even faster than the internet.”

    This isn’t just fast. It’s compounding.

    For teams and organizations, that means:

    • Planning cycles must adapt to faster execution rhythms
    • Feedback loops need compression and real-time recalibration
    • Legacy workflows aren’t built for this pace

    If your GTM or delivery cadence still runs on quarterly inertia, it’s time to rethink.


    2. Time-to-Value Just Got Compressed. Again.

    The biggest unlock from GenAI? Time compression.

    From prompt → prototype

    From draft → delivery

    From insight → action

    This collapse in cycle time transforms:

    • Productivity metrics
    • Product development lifecycles
    • Org-wide alignment rhythms

    🚀 Output velocity is the new KPI.


    3. Your Next Teammate Might Not Be Human

    We’re entering the era of embedded AI agents — not just assistants.

    AI is no longer a tool on the side. It’s part of the team:

    • Summarizing meetings
    • Writing first drafts
    • Managing workflows

    That means:

    • Rethinking team design
    • Clarifying AI vs human task ownership
    • Measuring contribution beyond headcount

    AI is a teammate now. Time to onboard accordingly.


    4. It’s Not Risk Slowing AI — It’s Friction

    One of the most important insights in the report:

    Employees aren’t blocked by fear — they’re blocked by poor UX.

    Adoption stalls when AI:

    • Doesn’t fit into existing workflows
    • Requires tool-switching
    • Has unclear value props

    🛠️ The fix? Product thinking:

    • Reduce toggle tax
    • Integrate into natural habits
    • Onboard like a consumer-grade app

    5. AI Fluency Is the New Excel

    The most valuable skill in 2025 isn’t coding — it’s prompt fluency.

    AI Fluency = knowing how to ask, guide, and evaluate AI output:

    • What to prompt
    • What to ignore
    • How to refine

    Every function — from marketing to HR — needs this literacy.

    We’re in the age of human-in-the-loop as a capability, not a compliance checkbox.


    6. Follow the Money. It’s Flowing to AI

    The report outlines the capital story behind the hype:

    • Enterprise GenAI spend is ramping fast
    • Compute infrastructure is scaling explosively
    • VC and corporate funding is prioritizing AI-native bets

    For leaders, this isn’t a trend — it’s a reallocation cycle.

    Infra budgets, product bets, and partnerships must now align with where the ecosystem is heading — not where it’s been.


    7. Go Deep, Not Just Wide

    Horizontal AI gets you buzz.

    Vertical AI gets you impact.

    The report shows real traction in:

    • Healthcare
    • Legal
    • Education
    • Financial services

    Where AI is tuned to real-world roles and workflows, it sticks.

    If you’re shipping AI without domain context, you’re leaving retention on the table.


    8. Infrastructure Is Strategy. Again.

    The biggest shift in the back half of the report?

    AI is putting infrastructure back in the spotlight.

    From model training to agent orchestration to secure runtimes:

    • The AI stack is now a competitive moat
    • Data pipelines and prompt layers are shaping outcomes
    • Infra is no longer invisible — it’s strategic

    What cloud was to the last decade, AI-native infra may be to the next.


    Final Thoughts

    The Mary Meeker 2025 AI Trends report isn’t just a forecast — it’s a framing device. One that challenges every enterprise leader to rethink:

    • How fast we move
    • What value looks like
    • Who (or what) we collaborate with
    • Where advantage is shifting

    It’s not enough to adopt AI.

    We have to redesign around it.

    📄 You can access the full report here

  • Shadow AI, Friction Fatigue & the Flexibility Gap: 5 Lessons from the Ivanti Tech at Work 2025 Report

    Shadow AI, Friction Fatigue & the Flexibility Gap: 5 Lessons from the Ivanti Tech at Work 2025 Report

    The Ivanti Tech at Work 2025 report isn’t just a workplace tech survey — it’s a mirror to how modern organizations are struggling (and sometimes succeeding) to adapt to the realities of hybrid work, AI adoption, and employee expectations.

    Here are 5 insights that stood out — and why they matter for anyone building teams, tools, or trust in the modern workplace.

    🔗 Read the full report


    1. Shadow AI Is a Trust Problem, Not Just a Tech One

    Nearly 1 in 3 workers admit they use AI tools like ChatGPT in secret at work.

    Why the secrecy?

    According to the report:

    • 36% want a competitive edge
    • 30% fear job cuts or extra scrutiny
    • 30% say there’s no clear AI usage policy
    • 27% don’t want their abilities questioned

    This is more than a governance issue. It’s a cultural signal.
    Employees are turning to AI to be more productive — but doing so under the radar signals a trust deficit and policy vacuum.

    💡 What to do:
    Leaders need to replace silence with structure — with clear, enabling policies that promote responsible AI use, and an environment where value creation matters more than screen time.


    2. The Flexibility Paradox: High Demand, Low Supply

    83% of IT professionals and 73% of office workers value flexibility highly — but only ~25% say they actually have it.

    Even as companies trumpet hybrid work, asynchronous enablement, autonomy, and outcome-based work norms haven’t caught up. The result? Disengagement and frustration.

    💡 What to do:
    Revisit what flexibility really means. It’s not just about where people work — it’s how they work.
    That means:

    • Tools for async collaboration
    • Decision-making frameworks for remote teams
    • Leaders modeling flexible behaviors

    3. Presenteeism Is the New Fatigue

    The report highlights “digital presenteeism”: workers pretending to be active — jiggling mice, logging in early — to appear productive.

    • 48% say they dislike their job but stay
    • 37% admit to showing up without doing meaningful work

    These are signs of unclear expectations and poor workflow design — not disengagement alone.

    💡 What to do:
    Audit for friction, not just lag.
    Look at your workflows, KPIs, and culture. Are people forced to perform busyness instead of real value?


    4. The Digital Experience Gap Is Real

    While flexible work is valued, many workers find it harder to work outside the office. The report notes:

    • 44–49% say collaboration is easier in-office
    • 36–48% say manager access is better in-office
    • 16–26% say apps are easier to use from the office

    💡 What to do:
    Enable remote-first experience, not just policy:

    • Seamless access to tools and systems
    • Integrated collaboration platforms
    • AI-powered support and IT workflows

    5. Redesign for Trust, Not Just Tools

    The big takeaway?

    Workers don’t just need better AI — they need clarity on what’s allowed
    They don’t just need more flexibility — they need workflows that enable it
    They don’t just need faster tools — they need a culture that values trust over control


    Final Thoughts

    The Ivanti Tech at Work 2025 report is a diagnostic — revealing what happens when new tools are bolted onto outdated operating models.

    For leaders, the message is clear:

    We need to evolve not just our tech stack, but our trust stack.

    🔗 Read the full report

  • 🎮 Vibe Coding a Stock Market Game: Why Every GTM Leader Should Build Like This Once

    🎮 Vibe Coding a Stock Market Game: Why Every GTM Leader Should Build Like This Once

    Earlier this month, I did something I hadn’t done in over 15 years:
    I rebuilt a stock market simulation game I had originally created during business school.

    The original was built on Ruby on Rails.
    This time, I went lean — prototyping with HTML, JS, and lightweight AI-assisted dev tools in what I’d call a vibe coding session.

    But this post isn’t about the code.

    It’s about what I learned — and why every founder, product owner, or GTM leader should prototype at least one thing themselves in this way.


    🧪 What Is Vibe Coding, Really?

    The term vibe coding was coined by Andrej Karpathy, but it was a recent post by Strangeloop Canon that captured its essence:

    “If AGI is the future, vibe coding is the present.”

    To me, vibe coding is building with momentum, not perfection.
    No heavyweight specs. No team syncs. Just one person, a rough idea, and tools that let you think through your fingertips.

    You’re not coding to launch. You’re coding to understand.
    And sometimes, that’s exactly what you need.


    🧠 What I Learned From Rebuilding QSE

    1. Building sharpens your strategy lens.
    When you rebuild something from scratch, every interaction becomes a test of friction vs flow. That mindset translates directly into GTM design, onboarding strategy, and product-market fit thinking.

    2. AI is best when it feels smart.
    My game features a basic rules-based AI opponent. Not sophisticated — but just enough to create pressure and tension. It reminded me that AI doesn’t need to be advanced, it needs to feel aligned with the user’s rhythm.

    3. Prototypes create unexpected clarity.
    Tiny design decisions (like how many clicks it takes to place a trade) turned into insights about attention spans, pacing, and simplicity — lessons I’ll carry into larger GTM and transformation conversations.


    🔁 Why This Resonated Beyond the Code

    Rebuilding QSE wasn’t a nostalgia trip. It was a reconnection with creative flow.
    It reminded me of how much clarity you gain when you stop whiteboarding and start building.

    We often separate “strategy” and “execution” as different domains.
    But I’ve found that prototyping collapses that gap. You see things faster. You think better. And sometimes, you spot the real issue — not in the brief, but in the build.

    If you’re leading a product, driving a GTM motion, or exploring AI integration, I genuinely recommend vibe coding — or at least, vibing with your builders more closely.


    🕹️ Curious to try the game I rebuilt?
    👉 Play QSE Reloaded

    The code is available on github

  • From Productivity to Progress: What the New MIT-Stanford AI Study Really Tells Us About the Future of Work

    From Productivity to Progress: What the New MIT-Stanford AI Study Really Tells Us About the Future of Work

    A new study from MIT and Stanford just rewrote the AI-in-the-workplace narrative.

    Published in Fortune this week, the research shows that generative AI tools — specifically chatbots — are not only boosting productivity by up to 14%, but they’re also raising earnings without reducing work hours.

    “Rather than displacing workers, AI adoption led to higher earnings, especially for lower-performing employees.”

    Let that sink in.


    🧠 AI as a Floor-Raiser, Not a Ceiling-Breaker

    The most surprising finding?
    AI’s greatest impact was seen not among the top performers, but among lower-skilled or newer workers.

    In customer service teams, the AI tools essentially became real-time coaches — suggesting responses, guiding tone, and summarizing queries. The result: a productivity uplift and quality improvement that evened out performance levels across the team.

    This is a quiet revolution in workforce design.

    In many traditional orgs, productivity initiatives often widen the gap between high and average performers. But with AI augmentation, we’re seeing the inverse — a democratization of capability.


    💼 What This Means for Enterprise Leaders

    This research confirms a pattern I’ve observed firsthand in consulting:
    The impact of AI is not just technical, it’s organizational.

    To translate AI gains into business value, leaders need to:

    ✅ 1. Shift from Efficiency to Enablement

    Don’t chase cost-cutting alone. Use AI to empower more team members to operate at higher skill levels.

    ✅ 2. Invest in Workflow Design

    Tool adoption isn’t enough. Embed AI into daily rituals — response writing, research, meeting prep — where the marginal gains accumulate.

    ✅ 3. Reframe KPIs

    Move beyond “time saved” metrics. Start tracking value added — better resolutions, improved CSAT, faster ramp-up for new hires.


    🔄 A Playbook for Augmented Teams

    From piloting GPT agents to reimagining onboarding flows, I’ve worked with startups and enterprise teams navigating this shift. The ones who succeed typically follow this arc:

    1. Pilot AI in a high-volume, low-risk function
    2. Co-create use cases with users (not for them)
    3. Build layered systems: AI support + human escalation
    4. Train managers to interpret, not just supervise, AI-led work
    5. Feed learnings back into process improvement loops

    🔚 Not AI vs Jobs. AI Plus Better Jobs.

    The real story here isn’t about productivity stats. It’s about potential unlocked.

    AI is no longer a futuristic experiment. It’s a present-day differentiator — especially for teams willing to rethink how work gets done.

    As leaders, we now face a simple choice:

    Will we augment the talent we have, or continue to chase the talent we can’t find?

    Your answer will shape the next 3 years of your business.


    🔗 Read the original article here:

    Fortune: AI chatbots boost earnings and hours, not job loss


    Want to go deeper? I’m working on a new AI augmentation playbook — DM me or sign up for updates.

    #AI #FutureOfWork #EnterpriseStrategy #GTM #DigitalTransformation #Chatbots #Productivity #ConsultingInsights