By Ts. Lukas J. Tan — Founder of ScamAlert Junior™ | CEO of OPERiON | AI & Digitalisation Strategist

Over the past few years, I have had the opportunity to work closely with businesses, schools, government agencies, technology professionals, educators, and parents through various digitalisation, artificial intelligence, and cybersecurity initiatives. While every organisation has different priorities, one concern has become increasingly common — the digital world is evolving much faster than our ability to prepare people for it. Cybersecurity is no longer a topic reserved for IT departments or large corporations. It has become a life skill that affects every individual, regardless of age.

As technology becomes more accessible, children are also entering the digital world earlier than any previous generation. They learn through smartphones, communicate through messaging platforms, play games online, and increasingly interact with artificial intelligence without fully understanding the risks that may exist behind every screen. This observation led me to a simple but important question: are we preparing our children early enough to navigate the digital world safely? That question eventually became the starting point of ScamAlert Junior™, an educational intellectual property created to help children develop critical thinking, responsible digital habits, and the confidence to make better decisions before they encounter online threats.

The Digital Childhood Has Changed

Childhood today looks very different from what many parents experienced growing up. Previous generations spent most of their free time outdoors, interacting face-to-face with friends, reading physical books, or learning through direct conversations with teachers and family members. Today's children, however, are growing up in an environment where digital technology is seamlessly integrated into almost every aspect of daily life. Smartphones, tablets, online classrooms, social media platforms, streaming services, artificial intelligence, and multiplayer games have become part of their normal routine from a very young age.

While these technologies provide incredible opportunities for education, creativity, and communication, they also introduce new challenges that many children are not yet equipped to recognise. Fake online identities, phishing attempts, scam advertisements, misleading information, cyberbullying, and AI-generated content are becoming increasingly sophisticated. Children are naturally curious, trusting, and eager to explore new experiences — qualities that make them wonderful learners but can also make them more vulnerable in digital environments.

The digital world itself is not the problem. Technology is one of the greatest tools humanity has ever created, opening doors to knowledge and opportunities that previous generations could only imagine. The real challenge lies in ensuring that children develop the judgement, awareness, and critical thinking needed to use these technologies responsibly. Just as we teach children how to cross a busy road safely, we must also prepare them to navigate the digital world with confidence rather than fear.

Why Traditional Scam Awareness Is No Longer Enough

For many years, scam awareness campaigns were designed primarily for adults. The focus was often on financial fraud, investment scams, phishing emails, or identity theft targeting working professionals and senior citizens. Children were rarely considered part of the conversation because they were perceived as having limited financial resources and relatively little online independence. That assumption is changing rapidly.

Today, children are exposed to online interactions much earlier than before. They receive messages from strangers while gaming, watch influencer content across multiple platforms, click advertisements without understanding their intent, and sometimes unknowingly share personal information through quizzes, apps, or social media. Modern scams are no longer limited to stealing money. They can involve manipulation, deception, emotional exploitation, identity misuse, or attempts to build trust before targeting other members of a family.

This means digital safety education cannot begin only after an incident has occurred. Waiting until a child becomes a victim is similar to teaching road safety only after a traffic accident. Prevention has always been more effective than recovery. Instead of relying solely on warnings such as “don't click suspicious links” or “don't talk to strangers online,” we need to help children understand why certain situations are dangerous and how to think critically before making decisions.

The future of scam awareness should not be built upon fear alone. It should be built upon knowledge, observation, curiosity, communication, and responsible decision-making. These are skills that children can continue applying throughout their lives as technology continues to evolve.

Why Stories Can Teach Better Than Lectures

Throughout history, stories have always been one of the most effective ways to teach values, wisdom, and life lessons. Long before classrooms, textbooks, or digital learning platforms existed, knowledge was passed from one generation to another through stories that people could remember, relate to, and share. While technology has changed dramatically, the way children learn has remained surprisingly consistent. They still remember characters long after they forget instructions. They remember emotions more easily than statistics. They remember meaningful experiences more than lengthy explanations.

This understanding became one of the foundations behind ScamAlert Junior™. Rather than producing another educational handbook filled with warnings and technical terminology, I wanted to create characters that children could genuinely connect with. Characters like Lukas, Leo, Lynn, Turbo, Johan, Lina, and Atuk Hassan each represent different personalities, perspectives, and life experiences. Through their adventures, mistakes, discussions, and teamwork, children are encouraged to observe carefully, ask questions, verify information, and think before acting.

Storytelling transforms learning into an enjoyable experience rather than a compulsory lesson. Instead of telling children what they should or should not do, stories allow them to explore situations alongside familiar characters, developing their own understanding through observation and discussion. When learning becomes emotionally engaging, the lessons often remain with children far beyond the final page of a book.

Building More Than Just a Comic

Many people who first hear about ScamAlert Junior™ naturally assume it is simply another children's comic book. While storytelling remains an important part of the project, the comic itself represents only one component of a much larger educational vision. From the beginning, my objective was never limited to publishing a series of books. I wanted to create an educational intellectual property that could continue supporting children across different learning environments for many years to come.

Behind every official character sits a comprehensive Character Asset Library that defines visual identity, personality, behaviour, educational purpose, communication style, expressions, poses, costumes, colours, and commercial guidelines. This ensures consistency regardless of whether the characters appear in books, classroom activities, animations, mobile applications, educational games, public awareness campaigns, or licensed merchandise. Every future adaptation remains aligned with the same educational philosophy and values.

Beyond the characters themselves, the ecosystem is designed to expand into activity books, teacher resources, parent guides, workshops, digital learning materials, exhibitions, community programmes, and future educational technologies. Each component shares the same mission: helping children become thoughtful, responsible, and confident digital citizens through engaging and practical learning experiences.

Building an educational intellectual property requires thinking beyond today's publication. It requires creating a foundation that remains relevant as new technologies, new challenges, and new generations emerge.

Looking Towards the Future

Artificial intelligence will continue advancing. Digital platforms will become even more sophisticated. Online scams will undoubtedly evolve in ways we cannot yet fully predict. While technology changes rapidly, the qualities that protect people often remain timeless. Critical thinking, empathy, responsibility, curiosity, integrity, and good judgement have always been valuable, regardless of the tools people use.

This is ultimately what ScamAlert Junior™ hopes to contribute. The project is not about creating fear of technology or encouraging children to avoid digital innovation. On the contrary, it is about helping young learners embrace technology with confidence while understanding the importance of thinking before acting, verifying information before believing it, and seeking guidance whenever uncertainty arises.

I also believe protecting children online should never be the responsibility of schools alone. Parents, teachers, communities, government agencies, technology companies, and industry leaders all have an important role to play in shaping the next generation of responsible digital citizens. Education becomes most effective when these groups work together towards a common purpose.

ScamAlert Junior™ was created with that long-term vision in mind. It is more than a comic, more than a collection of characters, and more than an educational campaign. It is a commitment to helping children build the confidence, judgement, and values they will need not only to recognise scams, but to navigate an increasingly digital world with wisdom, responsibility, and hope.

At a PDX2026 speaker briefing last year, a manufacturing CEO told me his company had just rolled out an AI forecasting tool that nobody on the floor was using. The tool wasn’t broken. Nobody had told the planning team which decision it was supposed to change. Six months and a licence fee later, the spreadsheets were still running the floor, and the AI dashboard sat open in a browser tab nobody clicked.

I hear a version of this story at almost every PDX prep call. The technology works. The leadership around it doesn’t move fast enough to point it at anything.

Three Things I Keep Seeing

The tool arrives before the decision does

Someone in IT or ops champions a good tool. It gets bought, piloted, even praised in a town hall. But nobody has decided what will change because of it — which report stops being manually built, which meeting gets shorter, which approval gets skipped. Without that, the tool becomes a second system running next to the old one, not a replacement for it.

Nobody owns the follow-through

A pilot has a project owner. Adoption rarely does. Once the vendor demo is over and the case study photo is taken, the person accountable for whether staff actually change their daily habits is often nobody in particular — which means, in practice, nobody.

Middle management absorbs a leadership problem

When adoption stalls, the story that gets told is usually “our people resisted change.” In my experience it’s rarely resistance. It’s that middle managers were handed a new tool and the same old targets, with no time carved out to actually redesign how the work gets done. They didn’t reject the technology. Nobody gave them room to use it.

A Test Before Your Next AI Pilot

Before signing off on another tool, I ask leadership teams three questions. If they can’t answer all three in one sentence each, the pilot is not ready to launch:

• What specific decision or task does this replace, not just support?
• Who is personally accountable for adoption twelve weeks after go-live?
• What will we stop doing to make room for this?

If the answer to the third question is “nothing”, you’ve just bought a second job for your team, not a productivity gain.

FAQ

Will AI actually take my team’s jobs?

Rarely in one clean step. What I see far more often is a role quietly becoming unnecessary over 12–18 months because leadership never redesigned the workflow around the new tool — the job doesn’t disappear so much as the company falls behind competitors who did the redesign.

What should a leader do differently this quarter?

Pick one AI tool already sitting half-used in your organisation and answer the three-question test above for it. Fix the adoption gap before buying anything new.

Is this really a leadership problem, not an IT problem?

If your IT team can point to a tool that’s live but nobody outside IT can point to a decision it changed, it’s a leadership problem wearing an IT costume.

The Short Version

The real risk was never that AI replaces people. It’s that leaders who can’t make a fast, specific decision about how work should change get quietly outpaced by leaders who can — using the exact same tools.

Running PDX means I get a year-on-year read on what Malaysian business leaders are actually worried about, not what a survey says they should be worried about. Between PDX2025 and PDX2026, the conversations in the delegate lounge changed in a way I didn’t expect.

Three Signals From the Delegate Floor

Signal 1: Fewer people ask “what is AI”

At PDX2025, a good third of conversations were still explaining basic concepts. At PDX2026, almost nobody asked that. The question had shifted to “who else in my industry has already deployed this, and what did it cost them to get it wrong?”

Signal 2: Vendors are being asked harder questions

Exhibition-floor conversations got sharper. Procurement teams showed up with checklists instead of curiosity — asking about integration with legacy ERP systems, not just feature lists. That’s a sign the buying committee has matured past the pilot-project stage.

Signal 3: The window to catch up is visibly shrinking

A supply-chain director told me flatly that two of his competitors had already renegotiated supplier contracts around real-time data sharing. His company hadn’t started. He wasn’t worried about being behind — he was worried about being unable to catch up before contracts renewed.

Where the Smart Companies Are Actually Positioning

The organisations that stood out to me this year weren’t the ones with the biggest AI budget. They were the ones who could describe, specifically, which of their existing workflows would be redesigned in the next two quarters — and who owned that redesign. Everyone else was still in “exploring options” mode, which is a polite way of saying nothing has actually changed yet.

A Question Worth Sitting With

If a competitor called your best customer tomorrow and said “we can already do that, in real time, at lower cost” — would your team know within the hour, or find out at contract renewal?

Where This Goes Next

This is exactly the gap we built PDX2026 around: not another round of AI explainers, but a room where the people already three steps ahead sit next to the people who need to move. If you want to see where Malaysia’s next phase of digital transformation is actually heading, that’s the conversation happening on the PDX floor, not in a webinar.

A few years ago, an OPERiON client — a mid-sized distributor — asked us to help fix a warehouse system their internal team had spent eight months building. It didn’t talk to their accounting software, couldn’t handle their busiest month of the year, and had already cost more than three off-the-shelf platforms combined. The build itself wasn’t incompetent. Nobody on the team had simply been given time to look outside the building before starting.

The Situation

Their internal IT lead was smart and had built useful tools before. But he was solving the problem with the only reference points he had: what the company had done in the past, and what he personally already knew how to build. Three competitors, we later found out, were already running a widely-used regional platform for the exact same workflow — at a fraction of the cost and time.

The Insight

Internal teams aren’t under-skilled. They’re under-exposed. A good engineer who has only ever seen one company’s way of solving a problem will build a solution shaped by that one company’s history, not by what the wider industry has already learned the hard way. That’s not a competence gap. It’s a visibility gap, and no amount of internal effort closes it, because the information simply isn’t inside the building.

What Changed

We didn’t replace their team. We changed the first step: before building anything, spend two weeks mapping what already exists in the market and who in their own supplier or partner network had solved something adjacent. That single habit — look outward before building inward — turned their next three projects from eight-month builds into six-week integrations.

Why This Keeps Happening

Vendor dependency gets a bad reputation, so companies overcorrect into “we’ll build it ourselves to stay independent.” But independence built on outdated information isn’t independence — it’s isolation with extra steps. The companies actually winning right now aren’t the most self-reliant. They’re the ones with the widest, fastest-moving network of outside insight feeding into decisions made inside.

A Question for Your Next Project

Before your team writes a single line of code or signs off on a build, can anyone in the room name two ways competitors or peers have already solved an adjacent problem? If not, you’re not being independent. You’re building blind.

Artificial intelligence is not reducing the importance of humans—it is redefining the value humans are expected to create.

Technology Has Entered a New Era

For almost two decades, I have worked in software development, digital transformation, and technology consulting. During most of that time, technical expertise was one of the strongest competitive advantages a professional could possess. The more programming languages you mastered, the more systems you built, and the more technical problems you solved, the more valuable you became to an organisation. Today, that equation is changing rapidly. Artificial intelligence is transforming the way software is written, analysed, tested, and maintained. Tasks that once demanded years of experience can now be accelerated within minutes using AI-assisted development tools. This is not a temporary trend or another technology cycle. It represents a structural shift in how knowledge work is performed. While many discussions continue to focus on whether AI will replace jobs, I believe the more important question is whether professionals are prepared to redefine the value they bring. Technology is evolving faster than many careers, and those who continue relying only on traditional technical skills may soon discover that technical execution alone is no longer enough.

AI Is Replacing Tasks Before It Replaces Professions

There is a common misconception that artificial intelligence will suddenly replace entire professions. In reality, AI is replacing individual tasks long before it replaces complete roles. Software developers can now generate code, automate documentation, identify programming errors, create user interfaces, and even suggest software architecture within minutes. Accountants can automate reconciliations. Designers can generate visual concepts almost instantly. Lawyers can summarise contracts with remarkable speed. These capabilities do not eliminate professionals overnight, but they significantly reduce the time required to complete routine work. As a result, organisations begin asking a different question. Instead of evaluating employees based on how efficiently they complete repetitive tasks, they increasingly evaluate them based on how well they solve business problems, make decisions, communicate across teams, and improve organisational performance. The value of execution is gradually shifting towards the value of thinking. Those who recognise this transition early will position themselves for future growth, while those who continue competing only on technical execution may find themselves competing directly against AI.

Technical Skills Will Remain Important—but They Are No Longer Enough

Some people interpret discussions about AI as suggesting that technical knowledge is becoming irrelevant. I disagree completely. Programming, engineering, cybersecurity, software architecture, and systems integration remain essential disciplines. However, technical capability is becoming the starting point rather than the destination. Future technology professionals must also understand business operations, organisational behaviour, customer expectations, process optimisation, and strategic objectives. Throughout my career, I have discovered that many software projects fail not because programmers cannot write code, but because business requirements are misunderstood, communication breaks down, or the organisation has never clearly defined the problem it wants to solve. AI may now generate thousands of lines of functional code, but it still depends on humans to ask the right questions, define meaningful outcomes, and evaluate whether the proposed solution actually creates business value. Technical knowledge remains valuable, but business understanding increasingly determines professional relevance.

The Professionals Who Thrive Will Become Translators

One observation has remained remarkably consistent throughout my experience working with clients from different industries. The individuals who create the greatest impact are rarely those with the deepest technical expertise alone. Instead, they are the people capable of translating between business and technology. They understand the language of executives while also appreciating the realities faced by programmers, engineers, and operational teams. They know how to convert a strategic objective into system requirements, and they know how to explain technical limitations in business language that decision-makers understand. Artificial intelligence will only increase the importance of this role. As AI becomes capable of generating technical output, organisations will need more professionals who can provide context, exercise judgement, resolve ambiguity, and align multiple stakeholders towards a common objective. The future belongs not only to builders, but to translators who connect ideas, people, systems, and execution.

Organisations Must Redesign Work, Not Just Buy AI

Many organisations are currently investing heavily in artificial intelligence platforms, hoping that productivity will improve automatically. Unfortunately, technology alone rarely transforms an organisation. I have seen projects where sophisticated systems were successfully deployed, yet employees continued using spreadsheets because workflows were never redesigned. Managers still approved work manually because responsibilities remained unclear. Communication problems persisted because the organisation focused on purchasing technology instead of changing behaviour. Artificial intelligence should never be viewed as an additional tool layered on top of existing inefficiencies. Instead, leaders must rethink how decisions are made, how information flows, and how responsibilities should evolve. AI changes the way work is organised, not merely the software employees use. Without leadership, ownership, communication, and redesigned processes, even the most advanced AI solution will struggle to create sustainable value.

Leadership Will Become More Valuable Than Technical Perfection

One of the biggest changes brought by artificial intelligence is the growing importance of leadership. Technical professionals who aspire to remain valuable must develop capabilities that AI cannot easily replicate. These include critical thinking, ethical judgement, creativity, emotional intelligence, negotiation, stakeholder management, adaptability, and strategic decision-making. Likewise, business leaders must develop sufficient technological understanding to make informed strategic decisions without needing to become programmers themselves. The strongest organisations of the future will not necessarily employ the most technically gifted individuals. They will build teams capable of combining business insight, technical capability, leadership, and continuous learning. In the AI era, leadership is no longer reserved for people with formal management titles. Every professional is increasingly expected to contribute ideas, challenge assumptions, coordinate across departments, and help organisations adapt to continuous change.

Dream It. Execute It. Ground It.

This philosophy has guided my work for many years, long before generative AI became part of everyday business conversations. Dreaming is about recognising opportunities that others have not yet seen. Execution is the discipline required to transform those ideas into practical workflows, systems, and measurable outcomes. Grounding is ensuring that innovation genuinely improves the lives of employees, customers, and organisations instead of becoming another technology experiment with little lasting impact. Artificial intelligence is giving organisations unprecedented capabilities, but capability without execution creates little value. Likewise, execution without grounding often produces systems that look impressive yet fail to solve meaningful problems. Sustainable innovation requires all three elements working together. Technology should serve people, support organisations, and strengthen long-term competitiveness rather than simply demonstrating technical sophistication.

The Real Question Every Professional Should Ask

Perhaps the most important question facing professionals today is not whether AI will replace them. A more meaningful question is whether they are developing capabilities that remain valuable even when AI becomes significantly more capable. If artificial intelligence can perform half of today’s technical tasks tomorrow, what unique contribution will you continue making? Will you become someone who simply executes instructions, or someone who frames problems, guides decisions, builds alignment, and creates lasting organisational value? Throughout history, every major technological revolution has rewarded those willing to evolve alongside it. The AI era will be no different. Traditional technical expertise will remain important, but the professionals who combine technology with strategic thinking, business understanding, communication, leadership, and disciplined execution will become the people organisations rely on most. In the years ahead, human value will be measured less by what we can do manually, and more by how effectively we help others navigate change.

I built my first automation system in 2008 — a customer-relationship tool I called Autobot CRM, inspired by watching Iron Man and wondering if a small business could have its own version of Jarvis. There was no “AI workflow” category back then. There was just a simple realisation: the software mattered less than the sequence of steps it was automating.

The Lesson That Still Holds

Autobot CRM wasn’t powerful because of clever code. It was useful because I’d mapped, in painful manual detail, exactly which follow-up happened after which customer action, and in what order. The automation just executed a workflow that was already clear. Companies rushing to bolt AI onto a messy, undocumented process today are making the same mistake I’d have made if I’d automated a workflow I hadn’t actually understood first.

Two Kinds of Companies in the AI Economy

Companies with a workflow to plug AI into

These organisations can describe, step by step, how a task currently moves from trigger to completion, including who touches it and why. When they adopt an AI tool, it slots into a known gap and the result is immediately measurable, because the “before” state was already documented.

Companies hoping AI will create the workflow for them

These organisations buy the tool first and hope structure emerges afterward. It rarely does. The AI ends up automating confusion faster, surfacing more inconsistent outputs at higher speed, which is a worse position than the manual mess they started with.

How OPERiON Builds Around This

Every system we design leans on independent, microservice architecture on purpose — not as a technical preference, but so that a client’s workflow can keep evolving without the whole system needing to be rebuilt each time a piece changes. Fragile, tightly-coupled systems are exactly where AI adoption stalls, because nobody can safely change one part without breaking three others.

A Practical Starting Point

Before evaluating any AI vendor, write down — on one page — the current manual steps of the process you want to improve. If you can’t fit it on one page, that’s the actual project. The AI tool is the easy part that comes after.

As AI makes software development faster, software architecture becomes more important—not less.

Everyone Is Talking About AI Writing Code. Few Are Talking About What Happens Five Years Later.

Artificial intelligence has transformed software development at an extraordinary pace. Today, developers can generate code, build websites, create mobile applications, design user interfaces, and even produce technical documentation within minutes. Tasks that once required days of programming effort can now be completed through carefully written prompts and AI-assisted development tools. This technological progress is remarkable, and I believe every technology professional should embrace it. However, while AI has dramatically reduced the time required to build software, it has also created a new misconception. Many people now assume that if software can be built faster, then software development itself has become easier. My experience over more than nineteen years tells me otherwise. Building software has indeed become faster. Building software that remains maintainable, scalable, secure, and valuable over many years is an entirely different challenge. That challenge has always been called software architecture, and in the AI era, it has become more important than ever before.

Building Software Is No Longer the Difficult Part

For many years, software projects were constrained by development speed. Businesses waited months for programmers to complete interfaces, databases, reports, and workflow modules. Today, AI has changed that equation completely. Prototypes can be created within hours. Landing pages can be generated within minutes. Developers can solve programming errors with unprecedented speed. Even non-technical users are beginning to create applications using AI-assisted platforms. This democratisation of software development is exciting because it lowers the barrier to innovation. More entrepreneurs can validate ideas, more organisations can experiment, and more people can participate in digital transformation. However, creating a working application should never be confused with creating a sustainable software platform. Speed solves the problem of building version one. It does not automatically solve the challenges of maintaining version fifty. The true complexity of software begins after deployment, not before it.

Architecture Determines Whether Software Can Grow

Every organisation changes. Customers evolve. Regulations are updated. Business models expand. New technologies emerge. As these changes occur, software must also evolve. This is where architecture becomes the foundation of long-term success. A well-designed architecture allows systems to scale without constant rebuilding. It enables modules to be upgraded independently, integrations to be added safely, and new business requirements to be implemented without affecting the entire platform. Poor architecture produces the opposite effect. Small changes create unexpected problems. New features become increasingly expensive. Technical debt accumulates. Eventually, organisations reach a point where replacing the system appears easier than maintaining it. The problem is rarely the programming language or the framework. More often, it is the architectural decisions made at the beginning of the project, when speed was prioritised over sustainability.

AI Understands Code. Architecture Requires Judgement.

Artificial intelligence has become remarkably capable of generating technical solutions. It can recommend database structures, optimise algorithms, suggest APIs, and write clean code based on detailed prompts. These capabilities significantly improve developer productivity. Yet software architecture extends beyond writing code. Architecture requires understanding business strategy, organisational workflows, operational risks, user behaviour, scalability requirements, security considerations, governance, and long-term maintenance. These decisions often involve balancing multiple priorities that cannot be resolved by technical optimisation alone. An architect must ask questions such as: How will this system evolve over the next five years? Which modules should remain independent? How should future integrations be managed? What happens if business priorities change unexpectedly? These questions require judgement, experience, and business understanding. AI can provide recommendations, but humans remain responsible for making architectural decisions that determine the future of an organisation’s technology.

The Most Expensive Software Mistakes Are Usually Invisible at the Beginning

One of the most dangerous characteristics of poor software architecture is that it often appears successful during the early stages of a project. The application launches. Users log in successfully. Reports are generated correctly. Management feels confident because the project has been delivered on time. The real problems emerge months or even years later. New business requirements become difficult to implement. Performance begins to decline as transaction volumes increase. Integrating external platforms requires significant redevelopment. Every enhancement introduces unexpected bugs because components are tightly connected. Technical teams spend more time maintaining old code than creating new value. These issues are rarely caused by poor programmers. They are usually the consequence of architectural decisions that failed to anticipate future organisational growth. By the time these problems become visible, correcting them is often significantly more expensive than building the system correctly from the beginning.

Software Architecture Must Begin with Business Architecture

Throughout my career, I have learned that successful software projects rarely begin with discussions about technology. They begin with conversations about the business itself. How does the organisation create value? Which workflows generate competitive advantage? Which information is most critical for decision-making? Where are operational bottlenecks occurring? Technology should support these answers rather than dictate them. Before writing a single line of code, organisations should first understand how work flows across departments, how responsibilities are assigned, and how customers experience the business. Software architecture should therefore reflect business architecture. When technology follows business strategy, systems remain aligned with organisational objectives even as technology continues evolving. When technology is designed independently from business reality, organisations often find themselves adapting their operations to accommodate software instead of allowing software to support the business.

AI Is Changing the Role of Software Professionals

The AI era is transforming what it means to be a software professional. Future developers will spend less time writing repetitive code and more time solving business problems. Software architects will increasingly evaluate AI-generated solutions rather than producing every technical component manually. Project managers will coordinate intelligent automation instead of supervising routine development tasks. Business analysts will become even more important because defining the right problem is now more valuable than generating another solution. Professionals who combine technical expertise with communication, critical thinking, business understanding, and architectural judgement will become indispensable. Those who focus only on code generation may discover that AI performs many of those activities faster and at lower cost. The future belongs to professionals who can bridge business strategy and technology implementation while ensuring systems remain maintainable long after the excitement of deployment has faded.

Dream It. Execute It. Ground It.

Artificial intelligence has given us extraordinary new capabilities, but technology alone has never guaranteed lasting success. Dreaming allows organisations to imagine new possibilities and innovate beyond traditional limitations. Execution transforms those ideas into working systems that improve productivity and create measurable value. Grounding ensures those systems remain practical, maintainable, scalable, and aligned with the realities of business growth. Software architecture represents this final step. It is the discipline that turns short-term innovation into long-term organisational capability. As AI continues changing how software is built, organisations should remember that technology may accelerate development, but architecture determines sustainability. The companies that succeed over the coming decade will not simply build software faster. They will build systems that continue serving their organisations long after today’s technologies have evolved into tomorrow’s history.

Executive Reflection

Before beginning your next software or AI project, ask yourself:

• Are we designing software, or are we designing a long-term business capability?
• Will this architecture still support our organisation five years from now?
• Does our technology reflect the way our business actually operates?
• Are we prioritising speed at the expense of sustainability?
• If AI can generate code in minutes, where will our long-term competitive advantage come from?

Artificial intelligence has changed how software is built.

It has not changed the importance of designing systems that organisations can trust, maintain, and grow with.

That is why software architecture remains one of the most valuable disciplines in the AI era.

Organising the first PDX conference, I made hundreds of decisions personally — which vendor, which stage layout, which speaker slot. By PDX2026, my job had changed almost entirely. I was no longer making most of those decisions. I was designing the system that let other people make them well, without calling me first.

Decision-Maker vs System Architect

A decision-maker is the person everyone waits on. A system architect is the person whose absence doesn’t stop anything, because the structure already tells people how to decide. Most leaders I meet are still operating as the first, even as their organisation has grown far past the size where that scales.

What a decision-maker optimises for

Being right, quickly, on the specific thing in front of them. It feels responsive. It also means every important choice funnels through one person’s calendar.

What a system architect optimises for

Designing the conditions — the information flow, the escalation rules, the shared context — so that a good decision is the default outcome even when the architect isn’t in the room. It feels slower to set up. It scales without you.

The PDX Test

The clearest sign PDX had become a system rather than a one-man decision engine: during the 2026 event itself, I was mostly moving between stages, not fielding operational questions. The team had the structure to handle what came up. That wasn’t luck. It was eighteen months of deliberately building the structure instead of just making faster decisions.

FAQ

Does this mean leaders shouldn’t make decisions anymore?

No — it means reserving your personal decision-making for the handful of choices that genuinely need it, and designing everything else so your team doesn’t need to ask.

Where should a leader start?

Pick the single decision your team asks you for most often. Instead of answering it again, write down the rule you used to answer it, and hand the rule to the team. That's the first brick of the system.

The best digital tool I’ve ever built won’t stop a single scam on its own. What stops a scam is a grandparent pausing for three seconds before clicking a link, or a teenager remembering to ask “why is this stranger asking me for a one-time password?” That’s not a technology outcome. It’s a thinking habit — and it’s the exact same gap I see inside companies that have spent heavily on digital transformation and still can’t explain what changed.

Two Kinds of “Digital”

Writing Scam-Proof and building the ScamAlert Junior comics taught me something I now see everywhere in corporate transformation projects too: giving someone a tool doesn’t give them the instinct to use it well. You can install the best anti-fraud software in Malaysia on every device in a household, and it won’t matter if nobody in that household has learned to pause before trusting an urgent message. The software was never the missing piece. The habit of questioning was.

Companies make the identical mistake with digital transformation budgets. They buy the platform. They skip building the habit of questioning how work should actually flow through it. Six months later, the platform is “live” and nothing about how people actually work has changed, because the organisation never learned to think differently — it just learned to click a new button in roughly the old way.

What “Thinking Differently” Actually Looks Like

In the scam-awareness talks I give to schools and community groups, the turning point is never the moment I show a slide about phishing techniques. It’s the moment someone in the room says, out loud, “wait, I did exactly that last week.” That’s a mindset shift, and it happens through story and reflection, not through installing anything.

Inside an organisation, the equivalent moment is a manager saying “wait, we’ve been approving this the same way for six years and nobody has asked why.” If your digital transformation programme has never produced that sentence out loud in a meeting, technology has been installed, but thinking hasn’t changed — and the transformation, whatever the dashboard says, hasn’t actually happened yet.

Where to Look First

Before your next platform purchase, sit in on the process you’re trying to fix and count how many times someone says “that’s just how we’ve always done it.” That sentence, not the software gap, is what you’re actually transforming.

Artificial intelligence is not simply changing the tools we use. It is forcing organisations to rethink how work is organised, decisions are made, and value is created.

Technology Is Moving Faster Than Most Organisations Can Adapt

Over the past two decades, organisations have invested billions of dollars in enterprise software, cloud platforms, automation, and, more recently, artificial intelligence. Yet despite this rapid advancement, many businesses continue to struggle with the same operational challenges they faced years ago. Meetings remain unnecessarily long, approval processes are slow, information is scattered across departments, and employees still spend valuable time performing manual tasks that technology should have eliminated long ago. This disconnect highlights an important reality. Digital transformation is no longer constrained by technology. Today’s tools are more capable than ever before. Instead, the limiting factor has become the organisation itself. The greatest challenge is no longer finding better software but redesigning how people collaborate, make decisions, share information, and execute work. Organisations that continue treating digital transformation as an IT project will increasingly find themselves falling behind competitors who understand that transformation begins with organisational redesign rather than technology acquisition.

Technology Alone Does Not Change the Way an Organisation Works

One of the biggest misconceptions surrounding digital transformation is the belief that implementing a new system automatically changes organisational behaviour. In reality, software only provides capability. People determine whether that capability creates value. I have seen organisations invest heavily in ERP platforms, CRM systems, workflow automation, AI assistants, and sophisticated dashboards, only to discover months later that employees still rely on spreadsheets, manual approvals, email chains, and disconnected processes. The technology functions exactly as intended, but daily operations remain largely unchanged. This happens because digital transformation is often approached as a technology deployment instead of an organisational redesign exercise. Installing new software without redefining responsibilities, communication channels, performance measurements, and decision-making processes simply digitises existing inefficiencies. Technology becomes an additional layer rather than a catalyst for meaningful improvement.

Artificial Intelligence Is Redefining Organisational Structures

Artificial intelligence is accelerating a transformation that extends far beyond automation. It is changing how organisations should be structured. Traditional organisations were designed around clearly defined departments, hierarchical approvals, and specialised job functions. AI is making these boundaries increasingly fluid. Employees now have access to tools that allow them to analyse information, create content, automate routine tasks, and solve problems that previously required multiple departments. As a result, organisations must rethink reporting structures, role definitions, decision authority, and collaboration models. The future organisation will rely less on rigid departmental silos and more on cross-functional teams capable of responding quickly to changing business needs. This shift is not about removing people. It is about enabling people to contribute at a higher level while allowing technology to handle repetitive execution. Organisational design must evolve alongside technological capability.

Leaders Must Shift from Managing Work to Designing Systems

Leadership itself is undergoing a significant transformation. For many years, effective managers were expected to supervise work, monitor performance, approve decisions, and solve operational problems. In the AI era, these responsibilities increasingly shift towards designing systems that allow good decisions to happen consistently without constant managerial intervention. Leaders must become architects of organisational capability rather than supervisors of daily activity. They must establish clear workflows, define accountability, simplify communication, and ensure information reaches the right people at the right time. Artificial intelligence can assist with analysis and automation, but it cannot replace thoughtful organisational design. Sustainable transformation depends on leaders who understand both business strategy and operational execution, creating an environment where technology supports people instead of forcing people to adapt to poorly designed systems.

Communication Is Becoming the Most Valuable Organisational Capability

Throughout my career in software development and digital transformation, I have observed that many projects do not fail because of poor technology. They fail because communication breaks down between business leaders, technical teams, operational users, and external stakeholders. Executives often describe business objectives while developers interpret technical requirements, yet somewhere between those conversations the original problem becomes distorted. Artificial intelligence does not eliminate this challenge. In many cases, it amplifies it. AI systems depend heavily on accurate context, clear objectives, and disciplined implementation. The organisations that succeed will therefore invest as much in improving communication as they do in purchasing technology. Employees who can translate business challenges into practical implementation strategies will become increasingly valuable because they bridge the gap between strategic vision and operational reality.

Organisational Agility Will Become the New Competitive Advantage

In the past, organisations often competed through economies of scale, production efficiency, or geographical reach. Today, competitive advantage is increasingly determined by organisational agility. How quickly can leadership recognise change? How rapidly can teams redesign workflows? How efficiently can information move across departments? How confidently can employees adopt new technologies? Artificial intelligence provides faster access to information, but organisations still require people capable of interpreting that information, making informed decisions, and executing consistently. Companies that redesign themselves around adaptability rather than bureaucracy will respond more effectively to market changes, customer expectations, and technological disruption. Agility is no longer simply an operational characteristic. It is becoming a strategic capability that determines long-term competitiveness.

Digital Transformation Requires Courage Before Technology

Every successful transformation I have witnessed began with leadership making difficult decisions rather than purchasing new software. Leaders chose to challenge long-standing assumptions, redesign familiar workflows, redefine responsibilities, and encourage employees to embrace new ways of working. These decisions often created discomfort because organisational redesign requires people to leave familiar routines behind. Technology implementation is usually the easiest phase of transformation. Changing behaviours, aligning stakeholders, and maintaining momentum require significantly greater discipline. Organisations must therefore recognise that transformation is fundamentally a leadership responsibility. Technology provides new possibilities, but courage, communication, and execution determine whether those possibilities become sustainable business outcomes. The future belongs to organisations willing to redesign themselves before competitors force them to do so.

Dream It. Execute It. Ground It.

Every meaningful transformation begins with a vision of what an organisation could become. Dreaming allows leaders to imagine a future beyond today’s limitations. Execution transforms that vision into redesigned workflows, improved communication, stronger leadership, and measurable operational improvements. Grounding ensures that transformation remains practical, sustainable, and aligned with the realities of employees, customers, and long-term organisational success. Artificial intelligence will continue evolving at remarkable speed, but technology alone will never determine which organisations succeed. Those that thrive will be the ones willing to redesign how they work, rethink how they lead, and continuously adapt how they create value. Digital transformation has therefore become much more than a technology initiative. It has become an organisational discipline that connects people, leadership, systems, and innovation into a sustainable competitive advantage.

Executive Reflection

Before launching your next digital transformation initiative, consider these questions:

• If every employee had access to AI tomorrow, would your organisation still operate the same way?
• Which workflows exist today simply because “that is how we have always done it”?
• Are your organisational structures designed for hierarchy, or for speed and collaboration?
• Does technology support your people, or have your people adapted to inefficient technology?
• If you could redesign your organisation from scratch today, what would you do differently?

The organisations that lead the next decade will not necessarily own the most advanced technology. They will be the organisations with the courage to redesign themselves before change forces them to.

Everyone who has organised a large event will tell you the idea is the easy part. Turning “Penang should have its own digitalisation conference” into two days at Setia SPICE Convention Centre with government, MNCs and industry leaders in the same room meant running straight into the same execution failures I now see inside almost every organisation I work with.

Three Failures That Almost Sank PDX

1. Everyone agreed on the goal, nobody agreed on the trigger

Early on, three teams all believed “get sponsors confirmed” was someone else’s next move. Nobody was wrong about the goal. Nobody had been told exactly what event should trigger their part of the work. The fix wasn’t a pep talk about ownership — it was a one-page document naming, for every workstream, the single event that started it.

2. Knowledge lived in one person’s head

For the first PDX, sponsor relationships existed mostly in my own memory and inbox. The moment I was unreachable for two days, decisions stalled, not because the team lacked judgement, but because they lacked the context I hadn’t written down anywhere. We now document context, not just tasks — the “why” behind a relationship or a commitment, not just the “what.”

3. Feedback arrived too late to matter

In year one, we found out what delegates actually wanted from post-event surveys — useful for next year, useless for the event already over. Now we build in short feedback checkpoints during planning, not just after the event, so a bad assumption gets caught in week three instead of month eleven.

The Pattern Behind All Three

None of these were knowledge problems. Every team involved knew, in the abstract, what needed to happen. What was missing was the specific trigger, the written-down context, and the fast feedback loop that turns knowing into doing. That gap — not a lack of smart people or good intentions — is what I’d call the real execution gap.

FAQ

Isn’t this just a project management problem?

Partly — but project management tools don’t fix it if the underlying triggers and context were never defined. The tool organises the gap; it doesn’t close it.

What's the fastest way to check if my team has this problem?

Ask three people on the same project to describe, unprompted, what specifically triggers their next task. If you get three different answers, you've found the gap.

Scammers adopted AI voice cloning and deepfake video call scams faster than most Malaysian banks updated their customer fraud warnings. I’ve tracked this gap closely while researching Scam-Proof, and it isn’t a story about criminals having better technology. It’s a story about who moves fast and who moves slow — and that exact gap shows up inside ordinary companies too, just with less dramatic headlines.

Fast Side, Slow Side

A scam network can test a new script, drop the ones that don’t convert, and scale the ones that do, all within days. A bank updating a customer warning message often needs sign-off from legal, compliance, and brand — a process measured in months. Neither side lacks intelligence. One side has removed the friction between noticing something and acting on it. The other hasn’t.

I see the identical pattern inside companies evaluating AI tools. A competitor tests, fails fast, adjusts, and ships. The slower organisation is still circulating the seventh draft of a risk-assessment memo for a pilot with no customer data in it yet. The technology gap between them is usually small. The decision-speed gap is enormous, and it compounds every quarter.

What Speed Actually Costs You If You Skip It

To be clear, this isn’t an argument for recklessness — a bank should absolutely check its fraud messaging carefully. It’s an argument for shrinking the distance between “we noticed a problem” and “we did something proportionate about it” from months to weeks. Every extra month of deliberation is a month a faster-moving competitor, or a faster-moving scammer, gets to operate unopposed in the same window.

Three Questions That Reveal Your Real Speed

• How long ago did your organisation last change a customer-facing process because of something you noticed last month, not last year?
• Can anyone below senior leadership approve a small, reversible experiment without three layers of sign-off?
• When something goes visibly wrong, does the fix ship in days, or does it wait for the next quarterly planning cycle?

If those answers are uncomfortable, the risk you’re carrying was never really about AI. It was about how long your organisation takes to notice and move — and in both fraud prevention and digital transformation, that number is the only one that actually predicts who gets hurt.