How to maintain your edge—and your humanity—as AI redefines the workplace.

Eighteen months ago, most business leaders were still debating whether AI could write a convincingly human-sounding email without hallucinating. Today, artificial intelligence systems are managing codebases, conducting research, screening contracts, and operating as autonomous agents inside enterprise workflows. Some capabilities that senior technologists expected to arrive in three to five years have arrived in months. At the same time, capability scaling in other areas has lagged expectations. No one working seriously in this space is confident they know what the technology will be able to do two years from now—let alone five or 10. Yet strategic decisions, such as investments in infrastructure, evolving business models, or commitments to workforce development, play out over exactly those horizons. Leaders are forced to make long-range choices in an environment in which the technology moves faster than the planning cycle.

Uncertainty, though, is only part of the challenge. With it comes a whole host of deeper risks. The same tools that make work faster also make it easy to stop doing the things that keep a leader sharp: deciding what matters, thinking in our own words, having the difficult conversations ourselves instead of prompting our way around them. AI does not take these capabilities from you. It simply makes them optional—and capabilities that become optional tend to erode.

There is no way to eliminate the uncertainty or remove the temptations. But there are capabilities you can develop that will serve you well regardless of how the technology evolves—precisely because they are the ones it tempts you to neglect. Here are the six essential skills every leader will need if they are to maintain their edge—and their humanity—as AI redefines the workplace.rather than possess—earned in the doing, carried in the person, and yours in a way a stock of facts never was.

Thriving in uncertainty

AI makes confident answers cheap and easy to access. But the most consequential challenges you face as a leader are not the ones for which an answer to your problem is already available and you just need it faster. They are the ones for which the answer does not yet exist. For instance, a reorganization might be underway and no one knows how it will land. A market could be on the move but the signals about the long-term direction of travel contradict each other. Or a technology is advancing fast enough to make your current strategy either visionary or obsolete, and you cannot yet tell which.

In the face of sustained uncertainty, humans tend to catastrophize, freeze, or latch onto a premature answer and then build an explanation to justify that decision after the fact. All three moves can feel like action, but none of them are rationally grounded. The capability that matters here is not the ability to eliminate uncertainty—whether we have secure knowledge about the future is largely out of our hands—but the composure to act clearly and well while uncertainty remains. This means learning to separate what you can control from what you cannot, catching which reactive patterns are driving your behavior, and holding yourself in a way that you will look back on as reasonable regardless of how things turn out.

Deciding what matters

Holding yourself steady under conditions of uncertainty is an important first step. But it does not remove the need to make choices. You still need to decide how to act (and deciding to do nothing for now counts as a decision). This is where AI changes the nature of the challenge. AI is extraordinarily good at doing things—drafting texts, analyzing data, scheduling meetings, executing certain types of tasks. What it cannot do is tell you which things are worthwhile in the first place. As Peter Drucker put it, efficiency is doing things right; effectiveness is doing the right things.

Effective judgment is a practiced skill, not an innate trait. It requires the discipline to externalize your reasoning rather than letting it run unchecked in your head. You need to build the strongest case possible against your own position before committing to it, identify the specific biases that are most likely to distort your thinking, and stress test your conclusions before you act on them. Most people do none of this systematically. Building a deliberate practice around decision-making means slowing down at the moments that matter and thinking in a deliberate and structured way rather than relying on instinct.

Preserving cognitive self-reliance

Good judgment depends on skills that erode if you stop using them. And AI makes it effortless to stop. When a tool can draft your analysis, summarize your reading, and structure your argument, the path of least resistance is to let it. No single act of delegation feels consequential. But over time, the person who lets AI handle their thinking becomes someone who can no longer do the thinking without AI.

The response is not to reject the technology. Much of the friction AI removes is genuinely unproductive. We can all survive happily without administrative busywork and mechanical tasks that teach us nothing. The discipline lies in distinguishing between effort that merely delays you and effort that develops you. Writing in your own words is how you discover what you think. Working through a problem yourself is how you learn to see its structure. These are not inefficiencies to be optimized away. They are the processes through which competence is built and maintained. Every leader should be asking: Which of my capabilities am I still exercising, and which have I started to outsource without making a deliberate choice?

Sustaining connections

AI makes human connection easier to avoid than ever and it does so in ways we are only beginning to register. You can use an AI tool to draft your way around a difficult conversation, letting the tool find diplomatic phrasing that spares you the discomfort of saying what you mean. You can let AI summarize what your colleagues said in a meeting rather than being present for the discussion yourself. You may even find yourself turning to AI as a tool for emotional processing, getting the sense of being heard without exposing yourself to the vulnerability of actually being known.

But there is a difference between communication and connection. Real connection requires presence, directness, and a willingness to be uncomfortable. The difficult conversation you have been deferring is almost always the one the relationship needs most. Learning to close the distance, to say the honest thing directly rather than letting a tool soften it into nothing, is one of the most valuable capabilities a leader can develop.

Ethical reasoning

AI will give you a confident, well-structured justification for almost anything you want to do. That is not a hypothetical concern—it is how the tools work. Ask for a case in favor of a decision you have already made, and you will get one that sounds rigorous and dispassionate. This makes it easier than ever to skip the part where you examine whether the decision is actually right.

Ethical reasoning is about seeing what you would rather not see: the real motive behind a decision you have already rationalized or the person who carries the cost of a choice you have framed as purely strategic. It is about stripping away the alibis and asking whose hands are actually responsible for the outcomes. The leaders who earn lasting trust are not the ones who never make hard ethical choices. They are the ones who do not look away when they do.

A distinctive point of view

AI now produces a passable version of almost any output of knowledge work. The temptation is to accept that output and call it a day. Most people will succumb to that temptation, which means the edge lies in resisting it. The good news is that closing that gap is possible. The work starts with identifying what is generic about the output AI has handed you. Does it lie in the obvious framing? The safe take? The formulaic phrasing? Whatever it is, the discipline is to push past it and convert the output from something generic to a product that is unmistakably yours.

Closing the gap once improves a deliverable. Doing it habitually gives you something more important—an instinct for where the generic hides, and an ability to produce work that no one else could. Ultimately, that’s the real return, because as AI makes competence cheap, competence stops being a differentiator. What’s left is having a distinctive point of view.

Conclusion

These six capabilities compound. Composure under uncertainty makes better decisions possible. Good judgment depends on cognitive skills you have to keep exercising. Connection, ethical reasoning, and narrative ownership all require the willingness to do the harder thing when an easier option is available. None of them can be taken for granted—they are disciplines, built through deliberate practice. The AI era will keep accelerating. The technology will keep shifting. What will not change is the value of a leader who can think clearly, connect directly, and truly own what they say.

[Photo: BlackJack3D/Getty Images]

Original article @ Fast Company. 

The post 6 skills everyone needs in the AI era appeared first on FaisalHoque.

These two specific types stand out.

For some professions, “AI is coming for our jobs” is no longer a vague threat about future events. Timothy McKeon, who spent years translating to and from Irish for the European Union, knows this better than most. As machine translation has improved, the ability to produce a text that is “good enough” has taken a huge bite out of his livelihood—costing him roughly 70% of his income as his EU work dried up. “The more it learns, the more obsolete you become,” he told CNN. And McKeon is not an outlier. 43% of translators have seen their incomes drop thanks to the increasing presence of AI alternatives in the marketplace.

What is happening to translators is an early sign of an evolution that is now underway across the knowledge economy. For decades, much of the value produced by white-collar work rested on a straightforward proposition: you knew things or could find things or assemble things that most people could not, and others were willing to pay to gain the benefits of that knowledge. AI is collapsing the value of a broad swath of this market. In an increasing number of fields, a chatbot can now deliver in seconds work that is close to, or in some cases better than, that of an average professional. The bulk of the knowledge economy, the broad base of competent-but-unremarkable cognitive work, is being priced downward toward zero.

It is tempting to think that the threat stops at the door of the merely average —that deep, specialized expertise is safe in a way that ordinary competence is not. That is only half right. The useful question is no longer whether AI will reshape knowledge work; it plainly will. It is which kinds of knowing hold their value when the machine can do so much.

The way things were

For most of the modern era, your market value as a professional came from your stock of knowledge: the tax code you had memorized, the case law you could marshal, the market data you had at your fingertips, the language you had spent a decade learning to render fluently. The work was, in large part, knowing things other people did not and being paid to retrieve and apply them. AI has learned to imitate that work in an increasingly convincing way. A frontier Large Language Model has read more tax code, more case law, and more market reports than any individual ever could, and it can hand most of it back on demand, fluently and instantly.

The once-widespread idea that knowledge workers will be saved by the tendency of AI models to hallucinate is falling away. Once commonplace, hallucinations are becoming increasingly rare, and they can be mitigated in many contexts by effective prompting. Reliable LLM access isn’t quite free or frictionless, but when compared to human labor the cost is becoming negligible.

The natural move for many knowledge workers in the face of these developments is to retreat upmarket: cede the simple work to the machine and stake their future on depth. Specialized expertise, the thinking goes, is the high ground. And there is real evidence for this. Translators, for example, have found that the surviving work is migrating upward: the volume jobs have gone to the machine, but the literary translators and the high-stakes legal and diplomatic interpreters—the people whose errors carry real consequences—still find their phones ringing. The specialists look safe . . . for now. But the ground they are standing on is less solid than it appears, and the line between the work AI can take and the work it cannot is not where most people assume it to be.

Two kinds of knowing

The problem is that depth of this kind is only a temporary refuge. To a machine, rare knowledge is nothing special, and there is no reason it can’t drill down to it so long as it is made available in a recorded form. The obscure corner of tax law is, to an LLM, just another corner. To ensure that your knowledge holds a more enduring type of value, you can’t rely on depth or rarity. You need different types of knowledge altogether. Two stand out.

The first is contextual judgment. A seasoned consultant’s value was never just the industry detail in her head; it was knowing which detail mattered for this client or that board, which background fact guided how to read the problematic balance sheet, how to understand the half-articulated fear the CEO mentioned in passing. Deep expertise, however rare, involves reasoning over material that exists in the record (the obscure corner of tax law is written down somewhere), and that is something these models now do well.

Contextual judgment is different. The decisive cue—what this silence means, why this board will balk—isn’t something that’s in the record precisely because this situation has never arisen in quite this form before. This kind of judgment relies on something real but fleeting, something the individual reads from the room in that specific moment. That can’t be looked up, and current models are far less reliable at this type of inference than at the recorded-knowledge reasoning they have already mastered. It may not stay out of reach forever, but it is not the threat knowledge workers face today.

The second is procedural knowledge. Some philosophers make a useful distinction between “knowing that” and “knowing how.” You can know every proposition in every physics textbook and still be unable to keep your balance on a bicycle. You can absorb everything ever written about music theory and still not be able to play the violin.

The same holds in business. A comprehensive store of facts and opinions about leadership is not enough to make someone a great leader. Reading every book on negotiation doesn’t translate into the ability to hold your nerve, time the concession, and keep your footing when the other side pushes. This kind of knowing lives in the doing: it can be acquired only through practice and experience, and at the highest levels it is bound up with things—trust, authority, the ability to read and relate to other humans—that exist only between people. That is not a stock of facts anyone could hand you, and it is not work you can hand off without becoming the bottleneck you were trying to remove.

Neither of these types of knowledge can be downloaded. But both can be built deliberately. And that is where the serious effort of career development now belongs.

Building survivable knowledge

Here are three moves that can help put you on the right side of this historic change in what it means to be a knowledge worker.

• Own outcomes, not outputs. An AI model produces outputs: a draft, an analysis, an answer. So stop building your career around competing on this front. Audit what you’re actually paid for—your core value proposition—and strike everything that a good model can now do in minutes. What’s left are the outcomes only you can deliver: the messy problem carried from the initial diagnosis through to a result you can stand behind or the insight into what the client really needs that goes beyond what he says. Reorganize your role or your offer around these outcomes. Results—not a stock of facts—are your real moat.
• Build judgment in the room, not on the page. Situation-specific judgment can only be picked up firsthand by being present for consequential decisions and watching how they actually turn out. It resists mechanical replacement because what mattered in those rooms can never be fully summarized and passed into the kind of record an LLM can read. The people who advance fastest won’t be the ones who can store the most information, but the ones who find ways to improve their contextually grounded judgment.
• Delegate the routine; protect the practice. Procedural know-how lives in the doing, so the work you hand entirely to AI is work you stop getting better at. Push the genuinely rote tasks onto the model but keep doing the high-skill work yourself—the negotiation, the argument you think through—even when the model could turn out a passable version faster. Convenience now is paid for in capability later.

Conclusion

Timothy McKeon’s verdict about AI—the more it learns, the more obsolete you become—holds for certain types of knowledge, and those are the types that most professionals have built their careers around for decades. But there are other types of knowledge that are less vulnerable. Some may even be impervious to AI, at least in the forms available today. That kind of knowing can’t be downloaded. It is knowledge you embody rather than possess—earned in the doing, carried in the person, and yours in a way a stock of facts never was.

[Source Image: Magnific]

Original article @ Fast Company. 

The post What kinds of knowledge will save you from AI? appeared first on FaisalHoque.

Wisdom doesn’t arrive on demand. It arrives in the space we stopped leaving for it. A century ago, Hesse wrote about a man who had everything and felt nothing—and the way out.

Key Points

• Hesse’s Siddhartha draws a distinction our age has collapsed: Knowledge transmits, wisdom cannot.
• AI makes knowledge free. The un-transmittable—judgment, presence, discernment—is now the rarest capacity. 
• Siddhartha’s detour through wealth mirrors our optimization culture; his recovery is practice, not platitude.

This week, over dinner, a friend and I started talking about Hermann Hesse’s Siddhartha –a book we had both read several times over the years, at different ages, for different reasons. Somewhere between courses, the conversation shifted. While the subject remained the same, we were no longer discussing a novel. We were discussing the world today. And by the time the plates had cleared, we agreed that a book written over one hundred years ago described our present moment more clearly than most things written this year—and that it had something very important to tell us about living in that moment. 

In the novel, the eponymous hero Siddhartha is a handsome young man who leaves home in search of enlightenment. Together with his friend Govinda, he attempts a variety of spiritual techniques and paths. And eventually, as one tends to do in 6^th century BCE India, they meet the Buddha. The Buddha is clearly enlightened, and the Buddhist philosophy is radiantly wise. Govinda is enraptured and becomes the Buddha’s disciple. 

Siddhartha, however, walks away. 

Why?

Not out of arrogance or even misunderstanding. Siddhartha knows the Buddha is enlightened, he knows that he has just met a supreme teacher of the very thing—the only thing—that he longs for, the thing that he has destroyed his previously comfortable life for. 

So, again: why? 

Because Siddhartha understood something we are in serious danger of forgetting: The most important things cannot be handed to you. They can only be lived into. 

The Buddha’s enlightenment was real—but it was the Buddha’s. Siddhartha would have to achieve his own enlightenment by himself, because enlightenment is not the sort of thing that can be transmitted by teaching. It must always be individually and independently realized. 

Decades later, when Siddhartha and Govinda meet again by a river as old men, it is Govinda who is still restless, still searching, still asking strangers whether they might have the secret. He spent a lifetime in possession of perfect answers, and they never became his. The seeker who outsourced his path never finished walking it.

The Kamaswami Years

Siddhartha’s own path runs through a long detour. Midway through the novel, he abandons the spiritual search and becomes a merchant for a trader named Kamaswami. He becomes rich, gets good at the game; and as he plays it, he develops what he calls the habits of the “childlike people”—acquiring, comparing, anxiously checking whether he is winning.

This spiritual fall is not the result of one big decision; rather, it is the compounding power of a thousand smaller movements. Eventually, Siddhartha turns into a man he neither recognizes nor respects, and he goes down to the river ready to drown himself.

Siddhartha is saved. But before we turn to his redemption, it is instructive to understand his failure. Siddhartha does not lack intelligence or knowledge. He does not lack determination or discipline. He lacks one thing only: wisdom. He is able to pursue his goals successfully, but he lacks the wisdom to understand which goals are worth pursuing.

The Anti-Teacher

Siddhartha is taken in by a ferryman named Vasudeva, and it is through Vasudeva that Siddhartha finally achieves enlightenment. It is tempting to call Vasudeva the teacher Siddhartha finally accepts.

He isn’t. Hesse is explicit: Vasudeva insists he is not a teacher or a sage, only a ferryman. He transmits no doctrine and corrects no error. His one talent is that he listens—not as technique, but without waiting to speak, without sorting, the way the river receives everything and rejects nothing. Vasudeva offers no content at all, only conditions: attention, silence, a witness, a river. And even then, what finally breaks Siddhartha open isn’t anything that Vasudeva says; it is his own son abandoning him exactly as he once abandoned his father. 

So actually, it is not Vasudeva who delivers enlightenment to Siddhartha. It is life. It is the river. Siddhartha’s instinct was right all those years ago. Enlightenment can only be lived into.

The Mechanical Buddha

Hesse’s novel turns on a single distinction: Knowledge can be transmitted; wisdom cannot. For a century, that read as mysticism. It now reads as a technical specification—because we have built machines that occupy one side of that divide completely.

A large language model is the apotheosis of transmittable knowledge: every doctrine, every framework, delivered instantly and fluently. We have built a mechanical Buddha—a flawless transmitter with nothing realized behind the words. It can articulate the eightfold path. But it has never sat by a river.

This is not a criticism of the technology but a clarification of what it makes scarce. When transmission becomes free, the bottleneck moves to everything transmission cannot carry: presence, judgment tested against experience, the discernment to know which of 10 correct answers is yours. 

The real danger in our brave new world is not that we will have the wrong answers. It is that we will have the right ones—endlessly, brilliantly, dazzlingly, compellingly right—and that having them will make us do what Govinda did: bow the head and take the robe.

What This Asks of Each of Us

I am not suggesting we abandon our tools. I build with these systems daily. The question is what kind of human is operating them—whether you are running a company, raising a child, or working a night shift to fund a dream. What I am suggesting is that we learn to live with them, not through them. Here are three disciplines for doing so, taken straight from the novel:

Refuse secondhand certainty. Use AI to gather knowledge. But when the output arrives, ask the question Siddhartha asked the Buddha: This may be true, but is it mine? Have I tested it against lived experience, or am I outsourcing my judgment along with my research?

Audit the Kamaswami drift. Every few months, ask: Which of my current habits would the younger, clearer version of me not recognize? Erosion is silent. The audit cannot be.

Sit by the river. Literally, if you can. Build unmediated time into the week—no input, no output, no optimization target. Wisdom does not arrive on demand. It arrives in the space we stopped leaving for it.

The Threshold

Hesse wrote Siddhartha in the aftermath of a world war, a personal breakdown, and a civilization’s crisis of meaning. He understood that when external systems grow powerful, the inner life doesn’t become optional. It becomes urgent.

The machines will keep getting better at dispensing knowledge; that part is settled. What remains unsettled is us: whether we become Govindas, devoted followers of the perfect transmitter, or ferrymen who have learned that the answer is never handed to you across the water.

Or, worst of all, perhaps, merchants who forgot why they crossed the river in the first place.

[Feature Photo Source: SaengTawan/Shutterstock]

Original article @ Psychology Today.

The post You Can Have Every Answer and Still Feel Lost appeared first on FaisalHoque.

Here’s how to build the new capabilities.

“The pursuit of greater profits cannot justify choices that systematically sacrifice jobs, because the human person is an end, not a means, and the economic order must remain subordinate to human dignity and the common good.” —Pope Leo XIV, Magnifica Humanitas

According to the people building today’s most powerful AI models, the CEO will soon be obsolete. Sundar Pichai, head of Google’s parent company Alphabet, has called the CEO role “one of the easier things” for AI to handle. Sam Altman has said he would be embarrassed if OpenAI were not the first major company to be run by an AI CEO. These are provocative statements, not only for their bold predictions about future AI capabilities but also for the assumptions they make about the nature of leadership. Ultimately, these views rest on the premise that every part of the senior leadership role can be reduced to a set of algorithmic operations.

This idea has deep roots. Milton Friedman distilled a long-standing view of the role that a business leader should play when he argued that a business’s sole responsibility is to maximize returns for shareholders while operating within a limited set of social norms. In this view, business is a game with a defined goal, a fixed set of rules, and objectively better and worse decisions that can be determined by analytical processes. The ideal CEO, then, is the one who makes the right bets and follows the optimal strategy. And if that is all leadership is, then there is no part of the role that cannot, in principle, be performed by an algorithm. Pichai and Altman would be right that a sufficiently advanced AI could fully replace the human CEO.

Rethinking business purpose

But there are other traditions that have at least as strong a claim on how we should understand business. For instance, Peter Drucker, widely regarded as the founder of modern management theory, identified the corporation not as an economic machine that just happens to exist within society but as a fundamentally social institution. Indeed, for Drucker, the corporation is the defining social institution of the modern age and one of the primary structures through which humans organize their collective lives.

In Drucker’s view, making a profit is a necessary condition for the survival of a business just as oxygen is necessary for the survival of the individual human. But it is not the purpose of a business any more than breathing is the purpose of a human life. An algorithmic approach to business can help us pursue goals and analyze trade-offs. But they cannot by themselves determine what is worth pursuing. That question turns on human judgments about value, meaning, and the ends that individuals and communities choose to serve.

The choice between Drucker’s picture and that advanced by Friedman is itself an example of such a decision. So, if defining and refining the purpose of a business is part of the CEO’s role, Pichai and Altman are wrong: There is at least one component of leadership that no algorithm can perform.

A new danger

When CEOs and board members make decisions about questions like this, they start from basic assumptions. Leaders carry around assumptions about what things really are—about what a company is, what a customer is, what an employee is. They carry assumptions about what can be known and what counts as evidence. They carry assumptions about what is right and how competing obligations should be weighed. Most hold these assumptions unconsciously, treating them as a matter of common sense rather than the result of a conscious choice. But when they go unexamined, they create blind spots that no amount of strategic sophistication can compensate for.

AI is making these blind spots dangerous in a new way. Every AI tool a company adopts arrives with built-in philosophical commitments—assumptions about communication, evidence, causation, and risk. Some of these are consciously chosen by developers who may never encounter the organizations that use their products. Others emerge from the processes by which algorithms interact with their training data. At a moment when shared assumptions about core values are already fracturing across society, CEOs and board members who cannot interrogate these embedded assumptions will find their organizations adopting philosophical commitments that they never examined and never chose. This is exactly the kind of foundational risk that boards exist to oversee. Yet most boards are not even aware it is happening, let alone equipped to do anything about it.

The ability to surface philosophical assumptions, interrogate them, and reason about them can undoubtedly improve business decision-making. A recent, widely read article titled “Philosophy Eats AI” made the case that philosophical thinking can sharpen strategy and improve the bottom line. This may be true. However, the assumptions that leaders and boards need to examine most urgently are not those that are limited to optimization problems. They are the foundations on which the business itself is built.

If leadership involves making judgments that cannot be outsourced to algorithms, then leaders need a discipline that equips them to make those judgments well. Business leaders do not need to become academic philosophers. But they do need to develop a working capacity to recognize, interrogate, and reason about the foundational assumptions that shape their decisions. And boards need this capacity at least as urgently if they are to act as an effective oversight layer for their companies. If a CEO is adopting AI tools that encode philosophical commitments that the board cannot even identify, that is a fundamental governance blind spot. Building the kind of philosophical proficiency that can surface these issues is as essential today as basic tech and financial literacy were to previous generations of leaders.

What boards can do now

So what does building this capacity look like in practice, particularly at the board level? Here are three starting points.

1. Treat philosophical literacy as a board competency. Most boards audit their composition for financial expertise, industry knowledge, and operational experience. Few ask whether anyone around the table has the capacity to interrogate foundational assumptions—about what the company owes its employees beyond a salary, about where the boundary sits between acceptable and unacceptable uses of its products, or about what kind of entity the company actually is. This is a governance gap, and it will widen as AI embeds more and more philosophical choices into business operations. Closing it does not necessarily mean appointing a philosopher to the board. But it does mean ensuring that someone is asking these questions—and that the board takes them as seriously as it takes the numbers.

2. Require a purpose and principles impact assessment when scrutinizing major AI implementations. Before approving any significant AI tool or platform, the board should require a brief statement of the philosophical assumptions it encodes. What does it assume about your customers—are they sources of extractable data or parties to a relationship? What does it optimize for, and what does it treat as acceptable trade-offs? Whose values shaped the system’s default settings, and do you share them? These are not technical questions, and they should not be left to the technology team. If no one on the leadership team or the board can answer them, the organization is adopting philosophical commitments it has never examined. Boards would not approve a major investment without understanding the financial implications. They should not approve a major AI implementation without understanding the philosophical commitments it is importing into the company.

3. Conduct an annual alignment review. Once a year, have the board examine a single foundational question: Who are we accountable to, and for what? What do we believe about the people we serve? What would we refuse to do even under financial pressure? Then compare the answer to the assumptions actually embedded in the tools, partnerships, and processes the company has adopted over the previous 12 months. Where these diverge, the organization’s philosophical commitments are drifting—not because anyone chose to change them, but because nobody was watching.

The real risk is not that AI replaces the CEO. It is that AI is already replacing the leadership competency that matters most—the judgment calls about what the organization is, what it stands for, and what it treats as true. These are the decisions that no algorithm can make, and they are the decisions that boards exist to oversee. Leaders and boards that cannot see this shift happening have already begun to lose control of it.

[Source Image: Eugene Mymrin/Getty Images, NikolaVukojevic/iStock/Getty Images Plus]

Original article @ Fast Company. 

The post Boards of directors have critical new responsibilities in the AI era appeared first on FaisalHoque.

Six 90-day plans that provide a comprehensive roadmap for AI transformation.

In 2024, Boston Consulting Group surveyed more than 1,000 C-suite executives and found that just 4% of companies were generating substantial value from artificial intelligence. A year later, that figure had risen to 5%. It is tempting to read this 25% year-on-year increase as the beginning of liftoff, the start of a series of compounding increases that will eventually drive AI-powered efficiency gains in every corner of the economy. But we should be wary of this tale, and not just because of the well-known danger of extrapolating a trend from two data points.

The last time a new technology upended old certainties and changed the business world, the impact on the bottom line was small for most businesses. The digital transformation took decades to complete and, while most companies eventually posted some productivity gains from their technology investments, these were typically modest. The real story of the digital revolution was not broad-based improvement but extreme concentration. Research by the Organization for Economic Cooperation and Development found that the top 5% of “frontier” firms captured productivity gains more than four times larger than those of the remaining 95%. The technology was available to everyone. The gains were not.

One of the results of this concentration has been that the businesses that failed to harness the new technology have been left in the dust by those that succeeded. We can expect to see the same pattern emerge with AI—not a broad-based transformation but a concentrated one in which the companies that adapt quickly will grow their market share while those that do not will fade into irrelevance.  

The key question is, how can you ensure that your business reaps the benefits of the AI frontier rather than falling by the wayside as one of the laggards? That is the challenge this series of articles has set out to address. Over the past six weeks, we have published six 90-day plans, each targeting a distinct dimension of the organizational transformation that AI demands. Taken together, they form a comprehensive program for becoming the kind of company that will capture real value from AI.

The six dimensions break down into three broad groups. An AI innovation pipeline and a systematic approach to responsible AI governance together form the engine of transformation—the machinery that generates, funds, and governs AI initiatives over time. The technology architecture provides the essential technical foundation without which nothing can scale. Leadership, culture, and workforce capability, meanwhile, are the three critical human dimensions that determine whether AI is adopted or resisted, used well or used badly.

There is no single correct starting point. Some organizations will already have solid foundations in certain areas and gaps in others. Some will choose to build the transformation engine and the technology infrastructure first, then develop their people on that foundation. Others may prefer to prepare their leadership, culture, and workforce before starting their implementation journey. These decisions are matters of judgment, shaped by the circumstances, culture, and leadership philosophy of each organization. What is important is that all six dimensions are addressed. Weakness in any one of them will eventually constrain all the others.

The innovation pipeline

AI innovation fails when good ideas have nowhere structured to go. Organizations either bet everything on a single transformative initiative or scatter resources across dozens of underfunded experiments with no mechanism for deciding what advances, what gets killed, and what gets funded next. This plan builds the machinery that turns AI ambition into a managed discipline. It starts by diagnosing the organization’s relationship to change and auditing what is already being spent on innovation—an exercise that typically surfaces a scattering of disconnected initiatives and significant money going to projects that aren’t delivering. From there, it establishes clear ownership, decision rights, and incentive structures, then builds a scored and balanced portfolio of AI initiatives with stage-gated funding that rewards progress and kills inertia. By the end of the 90 days, the first cohort of experiments is live, and the governance needed to sustain a continuous innovation cycle is in place.

For the full plan, see How to jump-start your company’s AI transformation in 90 days.

Responsible AI governance

Every AI system deployed without a governance framework creates reputational, legal, and operational risk—and those risks compound over time. This plan builds the structures that keep AI deployment ethical, accountable, and subject to meaningful human oversight. It begins by mapping the organization’s full AI footprint, which is almost always larger and less governed than leadership believes, and forcing worst-case conversations about what could go wrong. From there, it develops an ethical framework grounded in the organization’s values, establishes clear ownership and decision rights for AI governance, and builds the technical infrastructure needed to monitor what AI systems are actually doing. A structured assessment process ensures that every deployment is evaluated against defined risk thresholds, with the highest-risk systems reviewed first. By Day 90, governance is no longer a separate initiative—it is woven into operations, with exit plans in place for every AI system and a recurring rhythm of review that treats responsible AI with the same rigor as financial performance.

For the full plan, see Here’s how to jump-start your company’s responsible AI governance in 90 days.

Enterprise architecture

AI systems are only as good as the infrastructure they run on, and most enterprise architectures were designed for a different era. This plan addresses the five layers of the AI technology stack—data and storage, compute and acceleration, model and algorithm, orchestration and tooling, and application and governance—because weakness at any layer limits what every other layer can accomplish. It starts with a comprehensive mapping exercise that involves inventorying the data estate, cataloging integration points, auditing identity and access controls, and stress testing the architecture against scenarios in which AI systems operate autonomously. From there, it builds the critical foundations—a data governance operating model, API-first integration standards, zero-trust identity frameworks for both human and AI agents, a managed model layer, and the monitoring capability needed to explain what happened when something goes wrong. By Day 90, the first real AI use case has run end-to-end through the new architecture, a standing governance body is in place, and the gap between the architecture you designed and the one you actually built is visible and actionable.

For the full plan, see Your architecture is the ceiling on your AI strategy. Here’s how to raise it in 90 days.

Leadership

When two of America’s most successful CEOs—Coca-Cola’s James Quincey and Walmart’s Doug McMillon—independently stepped aside because they concluded the AI era demanded a kind of leadership they could not provide, they made the challenge personal. But organizations cannot step aside and replace themselves. They have to develop the leadership they need, systematically and at scale. This plan starts with an honest assessment of where the leadership team actually stands—not where they think they stand—measuring AI fluency, behavioral readiness, and decision-making patterns against what the AI era demands. It then builds targeted development through direct use of AI tools, decision simulations that force leaders to confront the calls they are avoiding, and structured exposure to the technological frontier. By Day 90, leadership evaluation criteria have been realigned to reflect AI-era demands, succession planning has been rewired against new benchmarks, the board itself has a structured AI education program underway, and the hard personnel conversations are backed by evidence rather than intuition.

For the full plan, see Your leadership team isn’t ready for AI. Here’s a 90-day plan to change that.

Culture

When IgniteTech’s CEO decided that AI was an existential threat and mandated company-wide transformation, the result was not radical adoption but active resistance. Employees skipped training, refused to use the tools, and deliberately sabotaged the transformation effort. The CEO’s eventual solution was to replace nearly 80% of the workforce. It worked, but at enormous cost. This plan offers a less destructive path. It begins by diagnosing the culture the organization actually has—surfacing the gap between stated values and lived behavior, measuring psychological safety, mapping the informal power structures that will accelerate or block change, and having direct conversations about what employees fear. From there, it rewires the mechanisms that shape behavior day to day: what gets rewarded, how meetings run, whether experimentation is safe or career threatening, and whether the people raising hard truths are protected or sidelined. By Day 90, the culture metrics identified in the diagnostic phase are being tracked and published internally, and culture has become a standing question in every AI deployment decision.

For the full plan, see Culture is where AI strategy goes to die. Here’s how to jump-start an AI-ready culture in 90 days.

Workforce capability

In a recent survey of senior leaders at large professional services firms, 61% said they had abandoned at least one AI project in the past year because their people lacked the skills to deliver it. This plan addresses the gap through a four-layer capability stack: the technical depth to build and maintain AI systems, the domain expertise to apply AI where it creates real business value, the general fluency every knowledge worker needs to use AI tools productively, and the organizational learning infrastructure that sustains the other three. It begins by mapping current capabilities against the demands of the AI strategy already in play, then prioritizes ruthlessly—closing the gaps that will most directly constrain the initiatives already in flight. From there, it launches targeted hiring, structured reskilling tied to real roles, and a broad fluency program, while making managers directly accountable for the capability development of their teams. By Day 90, capability is being tracked with the same rigor as financial performance, and the first newly developed skills have been stress tested under real operational conditions.

For the full plan, see Your AI strategy is only as strong as the people who run it. Here’s a 90-day plan to start building the capability you need.

Conclusion

No single 90-day sprint will complete a transformation of this magnitude. But collectively, these six plans provide a structured starting point across every dimension that matters—the innovation engine, the governance framework, the technology foundations, and the leadership, culture, and workforce capabilities on which successful AI deployments depend. Budgets and technology alone will not get you there. What separates the 5% of companies at the frontier from the rest is their willingness to transform comprehensively—to do the hard organizational work that most companies find easier to defer. The Frontier 5% is not a fixed club. You write your own entry ticket. The question is whether you will do what it takes to join.

[Source Image: Eugene Mymrin/Getty Images, NikolaVukojevic/iStock/Getty Images Plus]

Original article @ Fast Company. 

The post Real enterprise transformation with AI requires six foundations, not one. Here’s how to build them all appeared first on FaisalHoque.

Following on from our Brain Circuit on the risks that can arise from your own implementation of AI, here’s how to defend against external disruption.

by Faisal Hoque, Paul Scade, Pranay Sanklecha

Navigating enterprise risk in the AI era 

While you are carefully managing your AI innovation portfolio, other companies may be building new AI capabilities that have the potential to render your entire business model obsolete. The speed of AI-driven disruption means the next existential threat to your organization could come from a traditional competitor that suddenly leapfrogs you with AI-powered innovation, or from an AI-native challenger three industries away that discovers how to serve your customers better, faster, and cheaper. This is enterprise risk in the AI era: not gradual erosion of market share, but the danger of sudden strategic irrelevance akin to falling off a cliff.

Managing AI enterprise risk requires systematic environmental scanning that goes beyond tracking immediate competitors and extends to monitoring AI developments both in adjacent industries and across multiple dimensions. This includes paying attention to technological breakthroughs that might enable new business models, regulatory changes that could reshape competitive dynamics, shifts in consumer expectations driven by AI experiences in other industries, and the emergence of AI-native startups that bypass traditional industry barriers and disrupt the entire market. 

You also need to develop the tools required to respond effectively to emerging threats. Meeting these dual challenges requires governance structures that are designed specifically for the severity of the enterprise threats that AI may pose.

Key actions for managing enterprise risk

• Implement systematic environmental scanning beyond your industry

Establish quarterly PESTLE reviews (assessing Political, Economic, Social, Technological, Legal, and Environmental risks) calibrated for AI and monitor adjacent industries for spillover threats – AI advances that seem irrelevant to your sector today could reshape it tomorrow. 

• Create board-level AI risk governance with rapid-response capabilities

Establish a dedicated AI risk committee reporting directly to the board with clear authority to trigger strategic reviews and mobilize resources when threats escalate from possibility to probability. 

• Build strategic optionality through parallel experimentation

Develop multiple paths forward. Experiment with AI-enabled business models, partner with potential disruptors, and build internal AI capabilities that could enable rapid pivots when needed.

The window for developing these capabilities is narrowing rapidly, and the cost of inaction grows steeper with each passing quarter.

Conclusion

Besides the pursuit of disciplined portfolio management for internal initiatives (see part 1), strategic risk management in the AI era requires that organizations scan for and respond to external AI threats. Those who fail to do both will not get a second chance.  

Further reading

The dual challenge of AI: Innovating and building while preparing to defend

The three-year test: Will accountability remain when the agency goes?

Bosses: Stop telling staff that AI won’t take their jobs

Two Frameworks for Balancing AI Innovation and Risk

Original article @ IMD.

The post Stop developing an obsolete AI strategy part 2: Enterprise risk appeared first on FaisalHoque.

You’re the one everyone leans on. So why does it feel so lonely at the top of everyone’s list? A look at the cost of being needed—and the courage it takes to be seen.

Key points

• Everyone needs you. No one knows you. Being depended on can quietly replace being seen.
• The person everyone leans on is the person nobody checks on.
• The way out isn’t being needed less. It’s being seen: Show your uncertainty, not just your competence.

A few months ago, a member of my team messaged me on WhatsApp. It wasn’t about a project or a deadline. It was much simpler than that.

“How are you doing?” he asked. “Because it’s a lot right now—work, family, the whole roller coaster of life’s journey.”

That was it. Just that. There’s a lot going on. How are you? 

I did what I always do: I turned the conversation back outward. I reassured him. I told him I was good. I told him that keeping my eye on the prize kept me motivated, and that making my team successful made me happy.

Every word in my answer was and remains true. But it’s also just the type of response that leaders learn to give. Because leaders need to have the answers. And when they don’t, they need to be able to bear the weight of the uncertainty—alone. Their team needs to feel: He’s got this. We’re going to be alright.

It’s just part of the role to perform competence and calm and cheerfulness, especially when you don’t feel it. And most leaders I know don’t complain about this. They just do it. But they pay a price for doing it, one that is easy to ignore because at first glance it doesn’t look like there’s a price at all.

The price is loneliness.

The Invisibility of the Everyday Caregiver

We know by now that loneliness is very harmful. The U.S. Surgeon General’s 2023 advisory declared loneliness a public health epidemic, with health risks comparable to those “caused by smoking up to 15 cigarettes a day.” But those warnings describe the loneliness of the disconnected—empty rooms, unanswered calls. And at first glance, that seems to be the exact opposite of the life of a busy leader. Leaders are rarely disconnected. Their calendars are full, and they’re the first person called when something happens. So why do I say the price of leadership is loneliness?

Because there is another kind of loneliness: the loneliness of being the person everyone depends on.

And this isn’t a burden faced only by leaders. It is the condition of anyone who takes care of others. The parent who holds a family together, the nurse at the end of a double shift, the partner who never breaks down, the friend everyone calls first. Every day, people in all walks of life become the person others lean on. And every day, they carry what no one thinks to ask them about. The corner office has no monopoly on being needed. Anywhere there is someone on whom others count, there is someone at risk of being unseen.

The late social neuroscientist John Cacioppo, who spent decades studying loneliness, showed that loneliness is not simply a matter of being physically alone. It is better understood as perceived social isolation: the subjective sense that our connections are insufficient or insecure or unreciprocated. This perception can distort how we read the world and how we behave toward others. It can even change how our bodies function. Loneliness, on this account, is not a function of how many people surround us. Rather, it is about how we feel about the relationships we are in and how we bring our presence to them—or not.to use the systems effectively while refusing to let them use you.

For the indispensable, this is the danger. Leaders may be surrounded by people who need and admire them, who consult and depend on them—and yet they can still feel unseen. Indeed, the former may help cause the latter, because the more people rely on a leader, the less room there seems to be for uncertainty, unfinishedness, or simple tiredness.

I’ve spent decades working with leaders of various kinds. And what I’ve observed again and again is that the people others depend on most are often the least likely to be asked how they are doing—and the least likely to answer honestly if they are. Instead of expressing vulnerability, they perform certainty. And this is not because they’re emotionally insensitive. They feel the vulnerability acutely. Just, when everyone else is vulnerable, too, the leader steps up to hold it, which can mean putting their own feelings to the side.

Maybe I can put it like this: The more skillfully we carry others, the less anyone suspects we might need carrying ourselves.

Becoming Visible

The Zen teacher Thich Nhat Hanh taught that “the most precious gift” we can offer someone we love is our “true presence.” I’ve thought about this often since that WhatsApp message. My colleague offered me his true presence—he made contact without an agenda, without needing anything from me. It was a small act of generosity that cut through the noise of everything else. And it made me wonder how often leaders receive that gift—and how often they’re too deep in the role to even notice it’s being offered.

Now, it’s important to say that being present and being reliable aren’t flaws. The problem arises when those virtues become rigid prisons in which we trap ourselves, when being needed becomes the only way we allow ourselves to be connected. That’s when leading turns into loneliness.

The path out of this loneliness is not to become less needed. It is to become more visible. And that requires practices most that indispensable people find deeply uncomfortable:

1. Let someone see you struggle. Not a curated confession. Just the honest admission, once, to someone you trust: “I don’t know what I’m doing right now.” Notice what happens when the world doesn’t end.
2. Ask for help when you don’t technically need it. The point isn’t efficiency. It’s to practice receiving, the muscle that atrophies first in people who are always giving.
3. Notice when you’re performing certainty. Pause and ask: Am I being strong right now, or am I hiding? There is a difference, and only you can feel it.
4. Protect one relationship in which you are not the helper. Find at least one bond in which your role is not to solve, fix, or hold things together. Just be.

The Courage to Be Known

Being needed is a gift. But it is not the same as being known. And being needed without being known is what causes the peculiar loneliness of leadership—and of every life spent taking care of others. That loneliness does not heal by becoming more useful. It heals by becoming more visible. And visibility, unlike indispensability, requires not strength but courage.

If I could reply to that WhatsApp message again, I’d say the same thing—that I’m motivated, that I care for my team, that the work matters.

But I might add: “And it is lonely sometimes. Thank you for asking.”

[Feature Photo Source: pronoia/Adobe Stock]

Original article @ Psychology Today.

The post The Loneliness of Being Needed appeared first on FaisalHoque.

AI poses dual threats to organizations. Here’s how to manage the negative consequences that can arise from your own implementation of AI.

by Faisal Hoque, Paul Scade, Pranay Sanklecha

Internal vs external risks

AI greatly amplifies the uncertainty that characterizes today’s business environment. Leaders must understand a critical distinction to manage AI risk effectively: the difference between project risks and enterprise risks. Project risk relates to the negative consequences that can arise from your own implementation of AI,; such as technical failures, integration challenges, user rejection, and ROI shortfalls. Enterprise risk emerges from what others are doing with AI,; such as the development of new models, competitor breakthroughs, industry disruptions, regulatory shifts, and fundamental changes in how value is created and captured in your sector. 

How to manage project risk: the portfolio lens

Managing AI project risk requires a fundamental shift in how you approach AI innovation. Treating AI initiatives in isolation often leads to their risks being treated as a series of disconnected ‘go/no-go’ decisions. This can stifle innovation because it separates the innovation process into a series of disconnected projects. Adopting portfolio-management principles that approach AI investments as a unified innovation pipeline enables you to balance risk and reward profiles across the entire portfolio.

This approach recognizes that some AI projects should be high-risk moonshots that could transform the business,; while others should be reliable workhorses that deliver steady added value with tightly circumscribed risk levels.  

It also enables you to calibrate the organization’s overall risk exposure while maintaining the innovation velocity necessary to compete in an AI-driven economy,; transforming risk from a constraint to be minimized into a strategic variable to be optimized.

A portfolio approach can also help set and manage risk levels across functions within the business, creating nuanced risk profiles that are both industry-specific and reflect your unique position. The key is that a portfolio-management approach allows these decisions to become conscious, strategic choices rather than accidental outcomes.

Key principles for implementing portfolio management

• Set explicit portfolio targets based on strategic context

Define your desired mix of risk levels across the portfolio. This mix should reflect your competitive position, industry dynamics, and organizational risk appetite. 

• Evaluate projects based on portfolio contribution

When reviewing AI initiatives, assess not only whether the project is worth pursuing based on an internal risk/reward calculation, but also how it affects your overall portfolio risk profile.  

• Create integrated governance systems that manage risk and innovation together

Replace separate risk and innovation review processes with unified portfolio reviews that consider both dimensions simultaneously.  

Conclusion

Strategic risk management in the AI era requires the simultaneous pursuit of disciplined portfolio management for internal initiatives and the development of robust structures for identifying and responding to external threats. 

Further reading

The dual challenge of AI: Innovating and building while preparing to defend

The three-year test: Will accountability remain when the agency goes?

Bosses: Stop telling staff that AI won’t take their jobs

Two Frameworks for Balancing AI Innovation and Risk

Original article @ IMD.

The post Stop developing an obsolete AI strategy. Part 1: Project risk appeared first on FaisalHoque.

Here’s a 90-day plan to start building the organizational capability you need to succeed.

In a recent survey of senior leaders at large U.S. and U.K. professional services firms, 61% said they had abandoned at least one AI project in the past year because their people lacked the skills to deliver it. Deloitte’s “2026 State of AI in the Enterprise” report, based on a survey of more than 3,200 business and IT leaders across 24 countries, found that insufficient worker skills are now the single “biggest barrier to integrating AI into the business.”

There is no quick or easy solution to this problem. While it is possible to bring in new hires or contractors with the short-term capabilities you need, this approach is not sustainable in the long term as it is both expensive and creates critical dependencies. And it is equally impossible to flip a switch to develop these capabilities in-house overnight. But businesses can start the vital process of building those skills systematically. And there is no better time to begin than now. Organizations that get ahead of the pack in this critical area will build an advantage over their peers that will compound every quarter.

The capability stack

Organizational AI capabilities emerge from four mutually reinforcing layers of expertise.

Technical depth. This is the specialized engineering capability that builds and maintains AI systems: machine learning engineering, data engineering, AI security, model evaluation, and related disciplines. Without sufficient technical depth, the wrong things get built and bought, and the organization creates risk that it doesn’t understand.

Domain application. This layer is where AI strategy meets business reality. It consists of the capability to apply AI within a specific business function. And it relies on people who understand not just what the technology can do, but where it creates value in a particular operational context.

General workforce fluency. This is the baseline capability that every knowledge worker needs: sufficient understanding to use AI tools productively, to recognize when outputs are unreliable, and to contribute usefully to conversations about how AI is being deployed in their area. Without this general fluency, adoption stalls, misuse spreads, and employees remain dependent on a small group of specialists.

Organizational infrastructure for learning. This is the layer that sustains the other three: the systems, incentives, and management behaviors that determine whether capability grows or erodes. It includes how learning is funded, how time for development is protected, how reskilling pathways connect to real roles, and how managers are held accountable for the capability development of their teams. Without this layer, every investment in the first three decays.

The 90-day plan that follows works through all four layers simultaneously.

The 90-day plan

Days 1-30: map

The goal of this phase is to understand what you have, what you need, and where the gap between them will hurt you first.

1. Define the capability model. Use the capability stack to define what AI capability means for your organization. Be specific. What does technical depth mean in your business? Which roles require domain application? What level of AI fluency should every knowledge worker have? The shared model needs to be explicit and agreed on.

2. Identify the workforce baseline. Assess existing employees against the capability model. Use a combination of self-assessment, manager assessment, and skill validation—and treat all three with appropriate skepticism. None of these tools is perfect, but that’s okay: the goal is not a perfect picture, just a better one.

3. Map capability demand to the strategy. Take your AI strategy and the innovation portfolio it has produced, and decompose them into the specific capabilities required at each layer of the stack. This is the demand side of the equation, and it is typically missing from AI strategies altogether. Organizations approve ambitious AI portfolios and then discover, months later, that they don’t have the people to staff them. The demand map prevents that discovery from arriving as a surprise.

4. Identify the highest-leverage gaps. The gap between current state and required state will normally be large. You will not close it completely in a quarter, and attempting to do so will dilute the impact of investment across the board. Prioritize ruthlessly. Identify the handful of capability gaps that will most directly constrain the AI initiatives already in flight or about to launch. If your innovation pipeline has three experiments ready to go and two of them require data engineering capabilities that you don’t have, then that’s where the first thirty days of investment should be directed.

5. Audit how learning currently works. Map the current state of organizational learning. The infrastructure layer of the capability stack depends on it. Flag the parts of the system that will scale into the AI era and the parts that need to be rebuilt or replaced.

For a practical guide to building the AI innovation portfolio against which capability requirements should be mapped, see “How to build an AI innovation pipeline that creates real long-term value.”

Days 31-60: build

In this phase, the organization begins closing the gaps previously identified while also laying the foundations for ongoing and systematic workforce development.

1. Launch the core technical hiring push. For the small number of roles that the organization genuinely cannot develop internally on the required timeline, run a focused external hiring effort. Be disciplined about which roles you select. Reserve external hiring for the positions where internal technical expertise of the required depth truly cannot be developed in the available window. For everything else, build from within.

2. Stand up the reskilling program. For the much larger population of employees who can move into AI-adjacent roles with the right investment, build a structured reskilling program tied directly to the capability model. The program should connect to real roles on the other side. Reskilling efforts fail when they become training programs with no path to a new job.

3. Drive baseline fluency across the workforce. Roll out a broad AI fluency program for the general knowledge-worker population. Tie completion to specific behavioral expectations, not just attendance.

4. Build the partner ecosystem. Identify the external partners—universities, training providers, specialist consultancies, managed service providers—that can accelerate the building of capabilities where internal investment alone cannot move fast enough. Partnerships should be structured with clear deliverables and explicit transfer-of-capability expectations. A partner that builds your capability is an investment, while a partner that performs the work without transferring the capability is a dependency-in-waiting.

5. Redesign the highest-leverage roles. Select two or three of the roles that will be most comprehensively transformed by AI in your organization. Redesign them deliberately, working with the people who do that job today. Ask practical questions. What parts of the job should AI take on? What parts should the human retain and do better? What new responsibilities emerge when routine work is automated? The redesigned role can serve as a template for the broader workforce transformation and as a concrete demonstration that capability development leads somewhere real.

6. Make managers accountable for capability development. Your middle managers are the transmission mechanism for every capability program you launch—if their teams aren’t developing, the programs aren’t working. So make your managers accountable for success. Success needs to be specific and measurable: employees reskilled into new roles, team fluency levels achieved against the capability model, learning time protected against competing demands, and internal moves into AI-critical positions. Managers who consistently develop their teams’ capabilities should be recognized and rewarded. The signal this sends through the organization is more powerful than any training program.

For more on why AI reskilling demands organizational transformation rather than individual training, see “What AI reskilling really requires.”

Days 61-90: embed

Now it’s time to lock the changes into the operating fabric of the organization so that building workforce capabilities specific to AI becomes a permanent discipline rather than a one-off initiative that fades when the next priority arrives.

1. Operationalize capability reviews. Make capability a recurring item in talent reviews, business reviews, and board reporting. Build a capability dashboard, updated on a defined cadence, that tracks the state of each layer of the capability stack against the demand map from Phase 1. This turns a set of programs into a managed discipline, with the same rigor as that applied to financial performance or operational metrics.

2. Make learning a standing expectation. The test of whether an organization is serious about capability development is what happens when learning time collides with operational demand. In most organizations, learning loses. The fix is structural: Define the learning time expectation, make it visible, and hold managers accountable when it isn’t protected.

3. Track the flow of capability, not just the snapshot. If you only measure the stock of capability, you will miss the trends that determine whether you’re building momentum or losing ground. Track the indicators that reveal direction: internal moves into AI-critical roles, retention in those roles, reskilling throughput and placement rates, external hires converted to productive contributors, and the rate at which fluency programs change actual behavior rather than just accumulating completions.

4. Stress-test the capability with real work. Deploy the newly developed capability on an active AI initiative from your innovation pipeline and watch what happens. Where the capability holds under operational pressure, scale the playbook that produced it. Where it breaks—where the reskilled engineer can’t handle production complexity, where the fluent marketer still can’t evaluate model outputs—fix the upstream investment before you scale it.

5. Treat AI-critical roles as organizational infrastructure. Every AI-critical role in your organization is, to some degree, a new role—one that didn’t exist five years ago and may not have an established internal talent pipeline. That means every such role is a potential single point of failure. If your lead ML engineer leaves and there’s no one behind them, you don’t just have a vacancy—you have a capability collapse that can stall an entire portfolio of initiatives. Build succession depth for these roles the way you would for any other critical piece of infrastructure: Identify the successors, invest in their development, and make the pipeline visible.

6. Iterate. By day 90, the data is available. Which hires worked? Which reskilling pathways produced employees ready to do the job? Which fluency programs changed behavior rather than just generating completion certificates? Use the evidence. Reshape the next cycle based on what you’ve learned.

For a deeper look at how AI is redefining the management roles on which capability development depends, see “AI and the death (and rebirth) of middle management.”

Conclusion

This 90-day plan will not solve every capability problem. But what it will do is get you started on building the system that keeps capability growing long after the initial push. And this is more important than ever, because in the AI era, the workforce you have today is never the workforce you will need tomorrow.

[Source Image: Adobe Stock]

Original article @ Fast Company. 

The post Your AI strategy is only as strong as the people who run it appeared first on FaisalHoque.

The question isn’t whether to use AI; every serious person in every serious field will. The question is how to use it in a way that keeps the human element alive.

Key Points

• AI is embedded in how we work—and that’s a good thing.
• But AI’s fluency can lull us into deferring to it rather than directing it.
• Using AI well means staying in the driver’s seat, and that takes deliberate practice.

I came to America from Bangladesh at the age of 17, with very little money in my pocket and even less of an idea of what I was walking into. What I did have —and what I’ve leaned on for every decision I’ve made ever since—was a capacity I had developed early in life: the ability to work out what I actually thought, and then to act on it even when no one else agreed with me.

There’s a word for that capacity. Judgment. And it’s the thing I’m most worried about losing right now.

The reason I am worried about it is because I use AI every day. I use it to build applications, develop frameworks, design visual assets, and research what’s happening at the edges of the fields I need to understand. I use it to stress-test arguments before I bring them to my team or to a client. I use it to think through how a message will land before I send it. In raw output, I’m more productive today than a team of 10 would have been five years ago. And it isn’t just speed; the work is objectively better. 

Right now, I’m still one of the early adopters. But pretty soon, this will be the reality in every job. Very few people will have a choice about whether or not they use AI, just as few people get to choose whether they use computers or email or the internet today.

So this isn’t an article about whether to use AI. It’s about how to hold onto your judgment while you do.

The Core Skill Behind Using AI Well

AI is extraordinarily powerful, but it’s powerful in what we might call a generic way. While a generative AI model will be trained on all the insights of all the sciences, all the works of the great artists and the brightest business thinkers, it generally does not and cannot know what matters in your particular situation. It does not know what trade-offs you’d accept, what your experience tells you about how something will actually land, or what the right call is given everything you know that the machine doesn’t. That knowledge is yours, and using it is what turns AI’s general capability into something that works for you.

Without your judgment, AI gives you fluent but generic output. With it, you get something that couldn’t have come from anyone else. And the combination of AI’s general power and your judgment is far greater than either alone—but only if you’re actively in the conversation, thinking alongside the tool rather than deferring to it.

This means that using AI well is not fundamentally about writing better prompts or knowing which model to use. Rather, it’s about staying actively engaged with what comes back. It’s that simple.

The principle might be simple; the practice is not quite so straightforward. The sheer ease with which AI models respond to requests and create outputs leads to a phenomenon known as cognitive offloading. Offloading our mental load is precisely the attraction and the promise of AI: By delegating some tasks we are freed to think more deeply and effectively about other things. The risk, though, is that we offload the wrong things—that we outsource our higher judgment about what matters, the ultimate meaning of a piece of work or the creative design. If this happens, we stop using AI to support our own thinking and instead begin deferring to the machine.

How to Use AI Well

These aren’t rules for avoiding using AI. They’re practices for getting the most out of it—by making sure you’re always the one in the driving seat.

• Develop the idea before you write the prompt. You can’t delegate effectively to an AI model if you aren’t fully in control of the task. If you start with a topic you’re interested in and ask the machine what to think about it, you begin by deferring to it. Instead, come to it with a developed position you’re willing to defend. That doesn’t mean you shouldn’t ask the AI to challenge your view or help you strengthen it. But the strategic intent must be yours before you type the first word. That’s what makes you the architect of the output rather than turning you into an agent of the AI.
• Define the destination before you delegate the execution. Don’t hand an AI model a blank canvas. Give it a defined problem that includes a sketch of your destination and then use it to help fill in the details. That way, the architecture—the requirements, the dimensions, the logic—remain yours. If you can’t explain what you’re asking for before you ask, you’re not ready to use the tool. The result will be an output that looks finished but that isn’t really yours.
• Use AI to find the research. Interpret it yourself. AI is extraordinarilly good at surfacing studies, mapping out a field, and pointing you toward evidence that can confirm or challenge a view. Use it for all of that. But don’t accept its summary of what the results it digs up mean. The interpretation—where the evidence leads, what it confirms, where it falls short—has to be your own.
• Notice when you’re reaching for AI to avoid the uncomfortable. Sometimes we prompt AI because we want help with the processing burden of a task. Other times, we reach for it because it offers an easy way around something uncomfortable. The discipline is to identify and lean in to the type of difficult that creates friction and to follow where it leads. This is as true when you are crafting a business strategy, working on an article, or building a product.

The Human Edge

The practices above are not rules for limiting how or whether you use AI. They are the tools I use to ensure I stay in the driver’s seat while I use it, rather than becoming a passenger being moved about by a very capable machine.

The central skill of the AI age, then, is the willingness to do the driving yourself. To be the architect or orchestrator of the process rather than a storm-tossed ship on a sea of machine reasoning. It means knowing where you’re going before you start out and never letting go of your vision.

The most powerful technology ever built will not save anyone who has stopped thinking for themselves. The discipline required for the AI age has two parts: learning to use the systems effectively while refusing to let them use you.

[Feature Photo Source: JKLoma/Adobe Stock]

Original article @ Psychology Today.

The post We All Use AI. Here’s How to Use It Well appeared first on FaisalHoque.