Building Fast Is a Capability. Knowing What Should Be Controlled Is a Responsibility.
## Synopsis
As Artificial Intelligence evolves from a tool that assists people into systems capable of performing tasks independently, businesses are beginning to imagine a future in which digital workers operate alongside human employees. Yet the excitement surrounding AI agents and automated workforces often overlooks a more fundamental challenge: who is responsible for managing the authority, behaviour and consequences of these intelligent systems? Drawing on nearly two decades of entrepreneurship, software development and enterprise transformation, Ts. Lukas J. Tan reflects on the lessons of growing a technology company, the changing meaning of management and the importance of preserving human judgment in an increasingly automated world. He argues that the future of AI leadership will require an unusual combination of qualities: the courage to build quickly, the discipline to govern responsibly and the sensitivity to recognise that behind every piece of data, business process and message lies a human consequence.
## The Entrepreneur Who Wants to Build, and the Voice That Tells Him to Think Again
I have always been attracted to the possibility of building something that does not yet exist. Perhaps it began with my early fascination with computers, when technology still felt like a mysterious world of machines, cables and commands. Over the years, that fascination gradually developed into a professional journey involving software development, business systems, cloud infrastructure and enterprise digital transformation. What has remained consistent is my natural inclination towards execution. When I encounter a promising idea, I instinctively begin considering how it might be transformed into a working application, a practical business process or an entirely new approach to solving a problem. I am rarely satisfied with discussing possibilities indefinitely when there is an opportunity to test them in the real world.
This instinct has become even stronger with the emergence of Artificial Intelligence. For someone who has spent years building software and managing technology projects, AI represents far more than another generation of digital tools. It offers the possibility of fundamentally changing how systems are developed, how information flows through organisations and how work is coordinated. Tasks that once required extensive manual intervention can increasingly be supported by intelligent applications, while processes that previously depended on several employees may be redesigned around smaller teams and automated systems. Naturally, I find these developments exciting. I want to understand what is possible, experiment with emerging capabilities and move quickly enough to turn technological potential into practical value.
Yet there is another side to the way I approach technology, one that may not be immediately obvious to people who associate software entrepreneurs with speed, efficiency and innovation. I am also highly conscious of governance, sensitive to how information is handled and attentive to the consequences of actions that may initially appear insignificant. Sometimes, even a short message can cause me to reconsider a situation. A particular word, an unusual tone or a response that arrives at an unexpected moment may trigger an internal sense that something deserves closer examination. I do not assume that this instinct is always correct, but I have learned that it can be valuable as a reminder to slow my judgment, consider another person's perspective and ask whether there is more to the situation than the words themselves reveal.
These two characteristics may appear contradictory. One encourages me to build, experiment and move forward without unnecessary hesitation, while the other makes me cautious about information, authority and human consequences. Over time, however, I have come to believe that they are not opposing qualities at all. They are complementary disciplines that become increasingly important as technology grows more powerful. The ability to build quickly creates opportunity, but the willingness to examine consequences creates trust. Without execution, ideas remain unrealised; without judgment, even impressive technological achievements can produce outcomes that their creators never intended.
It is from this perspective that I have begun thinking more deeply about the next stage of Artificial Intelligence. As businesses move beyond using AI to generate content and begin allowing intelligent systems to carry out operational tasks, the challenge is no longer simply whether the technology can perform the work. A more difficult question is emerging: if AI becomes part of our workforce, who is prepared to manage it?
## What Managing Forty People Taught Me About the Future of AI
During the earlier years of my entrepreneurial journey, I understood business growth in a relatively conventional way. As opportunities increased, the company needed more employees to manage the expanding workload. Software projects required developers, design work required creative talent, customer relationships demanded attention and everyday operations depended on administration and coordination. What began as a small team eventually grew into an organisation of approximately forty people, a development that represented both an important business achievement and a significant personal learning experience.
Managing a growing organisation taught me that business complexity does not increase in a simple, predictable relationship with the number of employees. A larger workforce introduces additional communication channels, overlapping responsibilities, departmental priorities and decisions that must pass between individuals before reaching execution. The organisation may become more capable, but it can also become slower if its operating structure does not evolve alongside its growth. As a founder, I began spending increasing amounts of time coordinating work rather than directly creating it, and I discovered that managing the organisation itself had become a substantial responsibility.
Like many entrepreneurial journeys, mine did not follow a continuous upward trajectory. The business experienced different stages of expansion, difficulty, restructuring and transformation. At a later point, the team became considerably smaller, and that experience forced me to reconsider assumptions I had previously accepted about the relationship between manpower and business capability. I began questioning whether growth always required additional people, whether every established process genuinely contributed to value creation and whether organisational structures sometimes survived simply because they had become familiar. These were not comfortable questions, but they changed the way I thought about management and technology.
When Artificial Intelligence began demonstrating its ability to support increasingly complex activities, those earlier experiences became especially relevant. I could see the possibility of coordinating work through intelligent systems rather than relying exclusively on traditional departmental structures. Software development, research, administrative support, communications and information analysis could potentially be connected through a different operating model. The attraction was not merely reducing labour requirements. It was the possibility of redesigning how a business functions, removing unnecessary layers of coordination and allowing human employees to concentrate on activities where experience, relationships and judgment create the greatest value.
However, my previous experience managing a human workforce also made me recognise a problem in the growing enthusiasm for AI workers. An organisation that struggles with unclear responsibilities will not automatically become better managed because its tasks are delegated to intelligent software. If the business process is poorly designed, AI may simply execute that process faster. If management does not understand which activities are important, automation may produce more reports, notifications and transactions without improving the quality of business decisions. Technology can reduce certain operational burdens, but it cannot independently determine what kind of organisation a business should become.
This is why I believe that the rise of AI workers requires us to reconsider management before we reconsider headcount. The important question is not how many artificial employees a company can deploy, but how intelligently the organisation can combine human talent, redesigned processes and machine capability. Without that understanding, businesses may reproduce their existing management problems in digital form, creating a workforce that operates continuously without necessarily moving the organisation in a meaningful direction.
## The Difference Between Performing Work and Carrying Responsibility
The expression “AI employee” has become popular because it provides a convenient way to describe intelligent systems that can perform activities traditionally associated with human workers. An AI agent may prepare documents, examine information, assist with software development, communicate through connected applications or coordinate routine workflows. When these capabilities are presented together, it is easy to imagine a digital workforce capable of supporting business operations throughout the day and night. For an entrepreneur who has experienced the challenges of recruiting, training and coordinating employees, the possibilities are undeniably attractive.
Nevertheless, I believe we must be careful about allowing a useful analogy to become an inaccurate understanding of responsibility. An AI system is not a human employee, even when the work it performs resembles a human task. Employees operate within professional, social and organisational relationships. They may understand context through personal experience, recognise subtle emotional signals and exercise judgment based on responsibilities that extend beyond explicit instructions. AI can imitate aspects of these capabilities through sophisticated language processing and pattern recognition, but this does not mean it possesses human awareness, personal accountability or the same capacity to understand the moral weight of a decision.
Consider the way an experienced employee handles a sensitive customer complaint. The employee may read the message, recall the history of the relationship and recognise that the customer is expressing disappointment without stating it directly. Instead of sending an immediate response, the employee may decide to consult a manager, review the underlying problem or contact the customer personally. That decision may depend on information that is difficult to capture in a standard workflow, including the relationship between the individuals involved and the potential consequences of choosing the wrong words.
An AI system may also analyse the complaint, identify possible intentions and generate a response that appears thoughtful and appropriate. In many cases, such assistance can be valuable. The difficulty emerges when we assume that the system's ability to generate a convincing response is equivalent to understanding the full human situation. Language can be ambiguous, emotions are not always expressed directly and even experienced people can misinterpret the intentions of others. Automated systems should not be granted unlimited confidence merely because their responses sound persuasive.
If the organisation authorises AI to communicate directly with customers, modify records or execute consequential actions, the responsibilities associated with those activities do not disappear. A message sent by an AI system still represents the organisation. An inappropriate disclosure can still damage trust. An automated decision can still affect an individual's opportunities or circumstances. The business cannot simply explain an unfortunate outcome by pointing towards the technology that produced it, because the decision to deploy that technology and define its authority remains a matter of organisational responsibility.
This distinction is central to how I believe AI management should develop. Delegating a task is not the same as delegating accountability, and enabling software to perform work does not remove the need to supervise the consequences of that work. The more capable an AI system becomes, the more deliberately we must consider the limits of its authority.
## Why a Single Message Can Matter More Than a Thousand Automated Actions
One aspect of technology governance that receives relatively little attention is the sensitivity of human communication. In software development, we naturally focus on data accuracy, security permissions, system performance and the reliability of automated workflows. These are essential responsibilities, but they do not capture every consequence that technology can create. Sometimes, the greatest impact of an automated process is not a technical failure at all. It is the effect of a message on the person who receives it.
I have become increasingly conscious of this distinction in my own interactions with people. A brief reply can occasionally communicate more than a lengthy explanation, particularly when its tone differs from the pattern of an established relationship. A person may express agreement while feeling uncertain, respond politely while experiencing disappointment or avoid discussing a sensitive matter directly. These possibilities do not mean that every short message conceals an emotional problem, and it would be equally unwise to assume that personal intuition can reliably reveal another person's private thoughts. What matters is recognising that human communication contains uncertainty and that responsible judgment sometimes requires us to examine the context rather than act immediately on an interpretation.
Imagine a customer responding to a company's proposal with the sentence, “It's fine. We can talk about it another time.” A straightforward automated workflow might classify the matter as postponed, update the customer record and schedule a follow-up. An AI system could generate a courteous acknowledgment and complete the administrative process within seconds. From the perspective of operational efficiency, the task appears successful. Yet a human familiar with the relationship might wonder whether the response indicates genuine agreement, hesitation or disappointment. The appropriate response could depend on previous conversations and circumstances that are not fully represented in the immediate message.
For me, this illustrates a broader point about the limits of automation. The value of communication cannot always be measured by how quickly a message is processed, classified or answered. A technically correct response may still be insensitive, while a delayed response made after careful consideration may protect a relationship that is far more valuable than the time saved through automation. This does not mean AI should never communicate with customers. Rather, organisations should understand which situations are suitable for routine automation and which deserve greater attention because the consequences of misunderstanding may be significant.
The same sensitivity applies to personal information. Behind each customer record is a person whose circumstances may not be visible to the software processing the data. A database field may appear routine to a developer, but its contents may be personally significant to the individual concerned. A record that is technically accessible is not automatically appropriate for every business purpose, and information that can be combined across systems is not necessarily information that should be combined without further consideration.
This is one reason I do not regard governance as a subject confined to legal documentation or cybersecurity procedures. Good governance involves understanding how technology affects people, including the effects that cannot easily be measured through system performance statistics. A business may avoid a data breach yet still damage trust through careless communication. An automated workflow may operate exactly as designed yet still create an outcome that management would have questioned if it had understood the human context.
As AI becomes more deeply integrated into business operations, I believe the ability to recognise these distinctions will become an increasingly valuable management quality. Technology can support communication at scale, but scale also increases the responsibility to ensure that the organisation does not lose its sensitivity to the people it serves.
## When Access Becomes Authority
One of the most significant changes introduced by Agentic AI is the growing relationship between access to information and the ability to perform actions. Traditional business applications generally operate according to defined processes, while increasingly capable AI systems may interpret instructions, select tools and coordinate activities across several connected services. This can create substantial operational benefits, particularly when organisations want to reduce repetitive work and allow information to move more efficiently between applications.
However, every new integration introduces questions about authority. An AI assistant that can read a customer database has a different operational role from one that can modify customer information. A system authorised to prepare an email draft is not performing the same function as one permitted to send that email automatically. A tool that analyses financial information has different implications from a system capable of initiating financial transactions. Although these capabilities may appear to be natural stages in the development of increasingly useful AI, each involves a different relationship between technical possibility and organisational permission.
I find this distinction especially important because software development naturally encourages us to explore what can be connected. Once an application is working, the next question often concerns additional functionality, improved integration or reduced manual intervention. With modern AI, it can become technically straightforward to expand a system's reach across business applications. The danger is that organisations may treat these integrations as ordinary functionality enhancements without recognising that they are also expanding the operational authority granted to the system.
A company may introduce an AI assistant to prepare reports, then allow it to retrieve information directly from internal systems. Later, the same assistant may receive permission to update records or trigger business workflows. No individual development step may appear particularly dramatic, yet the cumulative result could be an AI system with substantial influence over daily operations. If management has not reviewed the purpose and boundaries of these additional capabilities, the organisation may discover that it has delegated more authority than originally intended.
This is why I believe the governance of AI cannot focus exclusively on the protection of information. Personal data protection remains essential, but the increasing ability of AI systems to act creates an additional need to understand what actions are authorised, under what circumstances and with whose approval. The distinction is not an argument for avoiding AI integration. It is an argument for designing integration with a clearer understanding of responsibility.
In my own approach to technology, I want systems to become more capable, but I also want the authority granted to those systems to remain deliberate. I do not regard these objectives as competing priorities. Appropriate boundaries can make advanced automation more dependable by reducing ambiguity about what a system should do and what should remain under human control. The objective is not to restrict every action, but to ensure that expanding technological capability does not quietly become unrestricted operational permission.
## A Workforce That Never Sleeps Still Needs Management
The prospect of AI systems operating continuously is particularly attractive to business owners. Tasks can be processed outside normal office hours, information can be prepared before employees begin work and routine activities can be coordinated without waiting for manual intervention. For smaller organisations, these capabilities may create opportunities that previously required larger teams and more extensive administrative resources.
Yet continuous operation introduces its own management challenges. Human organisations contain natural pauses through meetings, working hours and supervisory reviews. These are not always efficient, but they provide opportunities for people to notice mistakes, reconsider priorities and intervene when something appears unusual. An automated workflow can operate at a pace that removes many of these pauses, potentially completing large numbers of activities before anyone examines the results.
When the workflow is well designed, this speed can create substantial value. When the process contains an error or operates under inappropriate assumptions, the same speed can amplify the consequences. A mistaken update to a single customer record may be inconvenient, but an automated process that repeatedly applies the same mistake across many records can create a much larger problem. Similarly, an AI system that continuously generates unnecessary reports and notifications may increase information overload rather than improve decision-making.
This leads to a question I believe deserves greater attention in business discussions about AI productivity. Are we measuring how much work technology performs, or are we measuring the value that work creates? A system that produces hundreds of outputs may appear productive, yet those outputs may require extensive checking, create unnecessary distractions or fail to influence any meaningful business decision. The quantity of automated activity should not be confused with the quality of organisational outcomes.
I have become increasingly convinced that businesses should reconsider their processes before automating them. Many activities survive within organisations because they were introduced at a particular moment and subsequently became routine. Reports are prepared because management requested them years earlier, information is passed between departments because the workflow was designed around an older organisational structure, and employees repeat administrative tasks because nobody has questioned whether those tasks remain necessary.
AI provides an opportunity to challenge these habits. Instead of simply automating every existing process, organisations can reconsider why particular activities exist, what decisions they support and whether the same objectives could be achieved more effectively through a redesigned operating model. Sometimes the greatest improvement does not come from executing a task faster, but from discovering that the task can be simplified or eliminated altogether.
For me, this is the difference between introducing AI tools and genuinely transforming a business. One approach makes the existing organisation faster. The other asks whether the organisation itself should operate differently.
## The Management Structure Behind an Intelligent Organisation
If AI becomes an increasingly important part of everyday business operations, companies will eventually need to reconsider how responsibility is assigned. Traditional management structures establish reporting relationships between employees, supervisors and organisational leaders. These arrangements are intended to ensure that activities are coordinated, important decisions are reviewed and responsibilities remain identifiable.
AI systems introduce a different form of delegation, but they do not remove the underlying need for accountability. A business may deploy several intelligent agents to support different functions, yet someone must still understand why each system exists, what it is permitted to accomplish and how its performance should be evaluated. Without this clarity, organisations risk creating a collection of automated activities that operate independently without contributing to a coherent business objective.
I do not believe every company requires a large governance department or an elaborate management hierarchy for AI. Such an approach would be impractical for many SMEs and might undermine the flexibility that makes AI attractive in the first place. Instead, governance should reflect the nature of the activities being performed, the sensitivity of the information involved and the potential consequences of an incorrect action. A system preparing routine administrative summaries does not necessarily require the same level of supervision as one participating in consequential employment or financial decisions.
What matters is that responsibility should remain clear. When an AI system performs an activity, the organisation should understand who owns the process, who determines the permissible boundaries and how concerns are escalated when the outcome requires further attention. Effective management does not mean approving every individual action. It means establishing a structure in which authority is appropriately delegated and important consequences do not disappear into the complexity of automated systems.
This is also why I believe the management of AI cannot belong exclusively to technical teams. Developers understand the capabilities and limitations of software, but business leaders understand the objectives, relationships and priorities of the organisation. Responsible implementation requires these perspectives to work together. The technical ability to create a workflow does not automatically establish whether the workflow is commercially appropriate, ethically acceptable or consistent with the organisation's responsibilities.
As AI becomes more capable, leadership will increasingly involve deciding not only what technology can perform, but what work should be delegated, what judgment must remain human and how the organisation evaluates the consequences of that delegation. In this sense, AI does not make management obsolete. It changes the questions that good management must answer.
## Governance Is Not the Opposite of Innovation
There is a perception that governance slows down progress, particularly among organisations eager to experiment with emerging technology. Policies, approval processes and risk assessments are sometimes viewed as obstacles that prevent innovative ideas from reaching implementation. I understand why this perception exists. As someone who enjoys building software and moving ideas into execution, I have experienced situations in which excessive procedures created unnecessary complexity without improving the final result.
However, I do not believe the choice is between moving quickly and acting responsibly. That is a false distinction. Well-designed governance should help an organisation understand which activities can proceed rapidly, which require additional safeguards and which involve consequences that justify closer examination. It should support proportionate decisions rather than impose identical restrictions on every application of technology.
A minor adjustment to a website interface can usually be tested and reversed without significant consequences. An automated action involving sensitive customer information deserves a different level of consideration because the impact of an error may be more difficult to undo. The appropriate response is not to slow every development activity to the same pace, but to recognise the difference between reversible experimentation and actions that can affect people, finances or trust.
This is particularly relevant for Malaysian SMEs, many of which are eager to adopt AI but operate with limited technical and administrative resources. Governance frameworks that are excessively complicated may discourage responsible adoption or create compliance requirements that smaller organisations struggle to understand. At the same time, vague guidance may leave businesses uncertain about how to manage the risks associated with increasingly autonomous applications.
Malaysia's proposed Artificial Intelligence and Personal Data Protection Framework reflects an important effort to address the responsible processing of personal information through AI systems. The draft acknowledges the importance of security, organisational oversight, risk assessment and controls throughout the AI lifecycle. As these discussions develop, I believe practical perspectives from software developers, business operators and technology implementers can help ensure that governance remains both meaningful and achievable.
The objective should be to encourage innovation that businesses and individuals can trust. Strong governance, when implemented intelligently, is not simply a legal obligation or administrative requirement. It can become part of the foundation that allows organisations to deploy technology more confidently and sustainably.
## The Human Judgment We Must Not Surrender
Beyond the questions of technology and business management, I believe AI raises a deeper concern about the way human beings make decisions. As intelligent systems become more convenient, there is a natural temptation to rely on them without examining their recommendations as carefully as we might have done in the past. An answer that arrives instantly and appears professionally written can feel convincing, even when its assumptions are incomplete. An automated decision may appear objective because it is produced by software, even though the system may rely on imperfect information or inappropriate criteria.
The greatest risk may not always be an AI system making an obvious mistake. It may be an organisation becoming so accustomed to automated output that fewer people feel responsible for questioning it. When technology prepares every report, we may gradually stop examining the purpose of the reports. When AI drafts every customer response, we may become less attentive to the subtleties of communication. When intelligent systems coordinate entire workflows, we may overlook the assumptions embedded in the processes they execute.
This is where my own sensitivity to information and communication becomes especially relevant to how I think about AI. I value efficiency, but I also recognise the importance of that internal moment when something does not feel quite right. Sometimes it is a discrepancy in data; sometimes it is an unusual message or a decision whose consequences seem inconsistent with the stated objective. That feeling does not provide an answer, but it can prompt an important question. It reminds me that human judgment begins with awareness and must be followed by evidence, context and careful consideration.
I would not want technology to remove that habit of questioning from the way I work. On the contrary, I want AI to create more space for meaningful thinking by reducing unnecessary administrative burdens. The purpose of intelligent automation should be to strengthen our ability to make informed decisions, not to encourage us to abandon responsibility for those decisions.
As machines become more capable, the value of human leadership may increasingly reside in the ability to establish direction, recognise uncertainty, understand consequences and decide when an action requires more than technical confidence. These are qualities that cannot be measured simply through processing speed or the number of tasks completed.
## Building an Organisation That Can Move Fast Without Losing Its Conscience
Looking back over my entrepreneurial journey, I see how much my understanding of technology has changed. In the beginning, I was fascinated by what computers could do. Later, I became interested in how software could help businesses operate more efficiently. As my company grew, I learned that technology alone could not solve every organisational problem and that management structure, communication and human relationships were just as important as technical capability.
Today, Artificial Intelligence brings these lessons together in an unexpected way. It gives us the opportunity to develop systems that can perform increasingly complex work, but it also forces us to reconsider how responsibility should be distributed between human beings and technology. The question is no longer simply how many people a business needs or how many tasks can be automated. It is how the organisation should be designed so that intelligent systems contribute to genuine value while remaining subject to appropriate human judgment and control.
I want to continue building. I want to experiment with new technologies, develop practical AI applications and explore ways for smaller organisations to achieve capabilities that were previously beyond their reach. I believe entrepreneurs should have the courage to move forward rather than wait until every uncertainty disappears. Progress has always required experimentation, and technological leadership demands a willingness to challenge familiar assumptions.
But I also want to remain sensitive to the responsibilities that come with that ambition. I want to recognise when personal information deserves additional protection, when a message requires more thoughtful handling and when an automated action could produce consequences that are not immediately visible to the system executing it. I want the companies I help to become more capable without losing their sense of responsibility towards customers, employees and the people whose information they hold.
To me, this is not about choosing between innovation and governance. It is about recognising that responsible governance is part of building technology well. A capable AI system may help an organisation move faster, but a thoughtful management structure determines whether that speed serves a worthwhile purpose. The future belongs not simply to companies that deploy more AI, but to organisations that understand how to combine machine capability with human judgment.
## The Next Conversation I Want to Have with Business Leaders
As more companies begin exploring AI workers, I believe the most valuable discussion is not about how quickly another agent can be deployed. It is about understanding the organisation that will receive that agent, the authority it will be given and the responsibilities that must remain with people. This is where my experience as a software developer, entrepreneur and business transformation practitioner comes together. I am interested not only in explaining what AI can do, but in helping organisations examine what they are trying to achieve and how their systems should be designed to support those objectives responsibly.
I welcome opportunities to engage with business leaders, industry organisations and technology stakeholders who recognise that AI adoption is entering a more demanding stage. Developing an application is one challenge; integrating it into real operations is another. Establishing the boundaries within which it can operate, protecting sensitive information and maintaining trust require an additional level of thinking that deserves attention from the beginning rather than after a problem has occurred.
My approach has always been practical. I prefer ideas that can be developed, tested and implemented, and I believe progress should be visible in how an organisation actually operates. Yet I am equally convinced that effective implementation must be accompanied by appropriate governance, clear accountability and a sensitivity to human consequences. Technology should help businesses move forward without making them careless about the people who depend on them.
Perhaps that is the kind of leadership the AI era will increasingly demand: leaders who are ambitious enough to build what has not existed before, disciplined enough to define the limits of what they create and thoughtful enough to recognise when the human element matters more than another automated action.
We are entering a period when companies may be able to build an AI workforce more quickly than they can develop the management practices required to supervise it. The organisations that recognise this imbalance early may be better prepared for the changes ahead. They will understand that intelligence is not the same as wisdom, execution is not the same as judgment and the ability to delegate work does not remove the responsibility to govern its consequences.
For me, the objective is clear. I want to keep building, keep learning and keep moving forward, but never become so impressed by the speed of technology that I forget the importance of responsibility. As AI becomes part of our workforce, the central challenge will not simply be teaching intelligent systems how to perform more work. It will be ensuring that the people leading those systems remain conscious of why the work matters, what consequences it may create and who must ultimately answer for the results.
The day AI becomes part of our workforce should not be the day we surrender management to machines. It should be the day we become more deliberate about what responsible leadership truly means.
---
Ts. Lukas J. Tan is the Founder & CEO of OPERiON Ecommerce & Software Sdn Bhd. A software development and enterprise digital transformation practitioner since 2007, he writes about Artificial Intelligence, business transformation, responsible innovation and the evolving relationship between human judgment and intelligent systems. His work focuses on translating emerging technologies into practical business applications while promoting thoughtful governance and accountability.
For industry dialogue, enterprise AI implementation and discussions on responsible AI adoption, visit www.lukastan.com or contact [email protected].