Ts. Lukas J. Tan

Sometimes, we spend years searching for the right answer, only to discover that the answer was never meant to be created. It was meant to reveal itself when the mission became clear.

When people see the PDX mascot in the future, they may simply see an octopus. Some may think it looks friendly. Others may think it represents technology or artificial intelligence. Few will know that behind this little character lies years of conversations, hundreds of meetings, thousands of kilometres travelled, and one simple question that has shaped everything we do: How do we help businesses transform successfully in the digital era?

The story of our mascot did not begin with a design brief. It began with a problem. And like many meaningful discoveries, it appeared only after we stopped searching for it. Looking back today, I realise the octopus was never just a mascot. It became a reflection of what PDX had quietly evolved into—a platform built not around technology, but around people, collaboration, and a connected ecosystem. This is the story behind why an octopus became the face of PDX.

1. Seeing the Problem Beyond Technology

Long before PDX was established, I spent years meeting business owners across different industries. Every meeting sounded familiar. Companies wanted to digitalise. They wanted to embrace AI, automate operations, improve productivity, and remain competitive. Yet despite the growing number of software solutions, government initiatives, grants, and technology providers available in Malaysia, many businesses were still unsure where to begin. The challenge was never a lack of technology. Instead, it was a lack of clarity and coordination. Business owners struggled to translate operational challenges into digital requirements. Technology companies spoke in technical language that many business leaders found difficult to understand. Universities were producing graduates, but employers still complained about talent shortages. Funding opportunities existed, yet many businesses were unaware of them or lacked the confidence to apply. Every stakeholder was working hard within their own area of expertise, but they were rarely connected. The more conversations I had, the more convinced I became that Malaysia did not need another technology exhibition. What we truly needed was an ecosystem where every stakeholder could understand one another, collaborate, and move in the same direction.

2. PDX Was Never Meant to Be Just Another Event

That belief became the foundation of Penang Digitalisation and AI Conference & Exhibition (PDX). From the very beginning, my vision was never to organise the biggest conference or exhibition. Events last for a few days, but ecosystems continue growing long after the exhibition halls become empty. Every decision we made was driven by one question: “How do we create meaningful connections?” We wanted business owners to meet solution providers who genuinely understood their challenges. We wanted universities to hear directly from industries about future workforce requirements. We wanted government agencies to engage businesses beyond policy announcements. We wanted investors to discover innovation before it became mainstream. We wanted students to experience the opportunities waiting for them in the digital economy. Slowly, year after year, more organisations joined the journey. Government agencies, multinational corporations, startups, educational institutions, technology providers, investors, and industry associations all became part of something much larger than a conference. Without realising it, PDX was no longer just an annual event. It was becoming a living ecosystem where different communities could finally come together with a shared purpose.

3. Searching for a Mascot That Didn't Exist

As PDX matured, our team began discussing something many established organisations eventually consider—a mascot. It sounded simple at first. We organised brainstorming sessions, explored different concepts, and experimented with various designs. We sketched futuristic robots, AI-inspired characters, digital avatars, and technology icons. We even tried incorporating Penang's iconic blue, white, and yellow colours into the design. Every concept looked professional. Every illustration was creative. Yet every time we reviewed the proposals, something felt incomplete. None of them represented who we really were. Looking back today, I understand why. We were trying to create an identity before we had fully understood our own story. A mascot is not simply a marketing tool. It should represent a mission, a culture, and a belief that people can immediately recognise. At that stage, we were searching for a character. What we truly needed was a symbol that reflected the ecosystem we had spent years building. The answer could not be found in a design studio because it had not yet revealed itself in our journey.

4. The Conversation That Changed Everything

The breakthrough came in the most unexpected place—not during a branding workshop, but during a yacht networking session organised before PDX2026. There were no keynote speeches, presentation slides, or sales pitches. Instead, everyone simply shared their stories. Around the table were business strategists, AI educators, cybersecurity experts, software developers, infrastructure providers, investors, government representatives, university leaders, and entrepreneurs. Each person spoke passionately about the role they played in helping businesses succeed. As I listened carefully, I stopped seeing individual organisations. I began seeing an interconnected ecosystem. Every participant represented a different capability, yet none could create meaningful digital transformation alone. Strategy required execution. Technology required talent. Talent required education. Innovation required investment. Infrastructure enabled everything else. Government created the environment for progress. One conversation naturally connected to another, and another after that. It was one of those rare moments where the entire vision of PDX became visible—not on a presentation screen, but through the people sitting around the table.

5. The Moment I Looked at the Octopus Differently

As the evening continued, my eyes rested on a small orange octopus sitting quietly on the yacht. Until that moment, it had simply been a decorative toy. Then something unexpected happened. I no longer saw a toy—I saw the ecosystem sitting right in front of me. The brain represented strategy and leadership, providing direction for transformation. Every tentacle represented a specialised capability, from AI and cybersecurity to software development, cloud infrastructure, automation, and digital consulting. The nervous system reminded me of education and talent development, ensuring knowledge reached every part of the ecosystem. The flow of nutrients throughout the octopus symbolised funding and investment, sustaining innovation and growth. Each arm could perform independently, yet every movement remained coordinated because they were connected to the same central purpose. Suddenly everything made sense. We had spent two years searching for a mascot when, in reality, our ecosystem had quietly created one for us. The octopus was not chosen because it looked memorable. It was chosen because it perfectly represented what PDX had become.

6. The Real Meaning Behind the PDX Octopus

Today, the octopus represents far more than branding. It symbolises intelligence, adaptability, collaboration, and resilience—qualities that every organisation needs in an AI-driven economy. More importantly, it reminds us that successful digital transformation is never achieved by one company alone. No software provider can transform an organisation without leadership commitment. No consultant can succeed without technology partners. No AI solution creates value without skilled people. No innovation scales without investment, infrastructure, and policy support. Every stakeholder matters. Every contribution matters. The role of PDX has never been to become the centre of attention. Instead, our mission is to become the platform that connects every stakeholder so they can create greater value together. When businesses stop viewing digital transformation as a technology purchase and start seeing it as an ecosystem, their chances of success increase dramatically. That philosophy is what the octopus now represents.

7. A Mascot That Will Continue to Grow With the Ecosystem

People have asked me what the PDX octopus will look like in the years ahead. My honest answer is that I don't know—and that uncertainty excites me. Perhaps it will evolve into different characters. Perhaps it will inspire educational programmes for students. Perhaps it will become recognised across Malaysia as a symbol of collaboration in the digital economy. Whatever form it takes, one thing will never change. It will always represent the belief that transformation happens when people work together rather than apart. Every exhibitor, every speaker, every student, every policymaker, every investor, and every entrepreneur who joins PDX becomes another connection within this ecosystem. The mascot will continue growing because the community behind it continues growing. Its story is still being written, and every new partnership adds another chapter to that story.

8. Building the Next Chapter Together

When I reflect on the journey of PDX, I realise that the greatest achievement was never organising a successful event or introducing a mascot. The greatest achievement has been bringing together people who genuinely believe Malaysia can build a stronger, smarter, and more connected digital future. The octopus simply reminds us of that responsibility. As AI reshapes industries and digital transformation accelerates, businesses can no longer afford to navigate the journey alone. They need a clear roadmap, trusted partners, practical strategies, and an ecosystem that supports long-term growth. That has always been the mission of PDX, and it continues to be my personal mission as well.

Your Digital Transformation Journey Starts With the Right Roadmap

If your organisation is exploring digital transformation, AI adoption, automation, or long-term technology strategy, don't start by asking “What software should we buy?” Start by asking “What roadmap do we need?”

Technology is only one part of the equation. Success comes from aligning leadership, people, processes, funding, talent, and the right implementation partners into a single, practical strategy.

If you are ready to build a digital roadmap tailored to your organisation, I would be delighted to have that conversation.

Let's build your digital future—together.

Lukas J. Tan
Digital Transformation Strategist | AI Advisor | Founder, PDX
Digital Roadmap Consulting • AI Strategy • Ecosystem Development

This case study is based on an actual digital transformation project undertaken during the COVID-19 Movement Control Order (MCO). To protect the confidentiality of the client, the company's identity and certain operational details have been anonymised. However, the business challenges, transformation approach and outcomes presented in this article accurately reflect the project.

Case Background

Industry: Retail Business
Business Size: 20 retail branches across Malaysia
Workforce: Approximately 200 employees
Project Type: Enterprise Digital Transformation & Business Process Redesign

The client is an established retail business operating approximately 20 branches with a workforce of around 200 employees. As the organisation expanded, managing information across multiple branches became increasingly difficult. Critical business operations still relied heavily on Microsoft Excel and manual processes, resulting in inconsistent data, duplicated work, limited visibility and weak permission control. Although the company had already invested nearly a year developing a custom business system, the project had reached a point where continuous modifications were creating more operational issues than solutions.

This article shares how we approached the project—not by fixing the software first, but by redesigning the organisation behind it. It also explains why I believe Digital Transformation must always come before Artificial Intelligence, because AI is only as good as the business processes and data that support it.

The Wake-Up Call During MCO

The COVID-19 pandemic changed the way businesses operated almost overnight. During the Movement Control Order (MCO), many companies suddenly realised that the systems and processes they had relied on for years were no longer sufficient. One particular client approached us during this challenging period with a problem that, on the surface, sounded very familiar. They were still managing critical business operations using Microsoft Excel. As the company expanded, multiple employees were editing the same files, data was constantly being overwritten, and management had no confidence that the reports they were looking at were accurate. More importantly, there was no proper permission control. Anyone with access could modify information, whether intentionally or accidentally. The management team knew they needed to digitalise, but what they believed they needed was simply a software system. What they actually needed was something much bigger.

A Year Spent Building, But Not Progressing

For various reasons, the company eventually engaged another software developer instead of working with us. Over the next twelve months, the system went through countless revisions. Every few weeks there was another meeting, another change request, another bug to fix, and another feature to modify. Unfortunately, the project slowly entered a cycle that many business owners know all too well. Every time one problem was solved, another appeared somewhere else. New features could not be introduced because the development team was constantly repairing existing functions. Users became frustrated because familiar processes kept changing, while management began losing confidence in the project altogether. After nearly a year of investment, both financially and emotionally, they were still nowhere close to having the stable business system they had originally envisioned. That was when they returned and asked if we could help.

I Didn't Start by Looking at Their System

When I first met the management team again, they expected me to review the software, analyse the database, or identify the technical problems that had accumulated over the previous year. Instead, I did something that surprised everyone in the room. I barely looked at the system at all. After nearly twenty years of building enterprise software, I have learned that software is rarely the real problem. A poorly performing system is often nothing more than a reflection of a poorly structured organisation. If the business itself lacks clarity, no amount of programming can compensate for that confusion. Rather than spending days trying to understand thousands of lines of source code or documenting every existing screen, I decided to start from the very top. Before discussing technology, I wanted to understand the business.

The First Question Was About People, Not Technology

The very first document I asked the CEO to show me was not a system manual or a workflow diagram. It was the organisation chart. I wanted to understand how the company was structured before understanding how the software had been designed. Looking at the organisation chart, I asked three simple questions for every department. How many people work here? Does this department generate revenue, or is it a support function? What is its primary responsibility? These questions may sound basic, but they immediately exposed issues that had never been discussed during software development. Several departments had overlapping responsibilities. Some approval processes existed simply because they had always existed. Certain teams were overloaded while others had unclear ownership. Before redesigning technology, we first needed to redesign organisational clarity.

Understanding the Business Before Designing the System

Once the organisational structure became clear, I asked the management team to explain something even more important. I didn't ask how every individual screen should work, nor did I request every operational detail. Instead, I asked them to walk me through the complete customer journey. How does a customer first hear about your business? What happens after they make an enquiry? How are quotations prepared? How are orders confirmed? What happens during production, delivery, invoicing and after-sales support? By understanding the entire business lifecycle, we could identify how information should naturally flow throughout the organisation. Only after understanding the business model did we begin discussing software. Technology should always support business operations, never dictate them.

Digital Transformation Is Not About Digitising Existing Problems

One of the biggest misconceptions surrounding digital transformation is that businesses believe success comes from converting manual paperwork into digital forms. In reality, that approach simply transforms inefficient manual processes into inefficient digital processes. If an organisation has unnecessary approvals, duplicated work, poor communication between departments and inconsistent ownership, software will only make those weaknesses more visible. Digital transformation is not about replicating yesterday's workflow on a computer. It is about questioning every process, eliminating unnecessary steps, simplifying communication and redesigning how the organisation operates. Only then should technology be introduced to automate and support those newly designed processes. Software should never preserve inefficiency; it should eliminate it.

Building a Business System Instead of Just Another Software Application

One aspect of this project that I truly appreciated was the trust given to our team. After we completed our analysis and proposed a new operational framework, the client allowed us to redesign the system based on business objectives instead of individual preferences. They did not interfere with every button, every screen or every workflow. Instead, they judged us based on one simple expectation: when the system is delivered, it must work. It must be intuitive for employees to use, easy for new staff to learn, and capable of providing management with accurate, real-time information. Every department would have its own permission controls, ensuring that employees only accessed information relevant to their responsibilities. Data would move seamlessly from one department to another without repeated manual entry, while every enquiry, customer case and business transaction could be monitored through dedicated operational dashboards. The goal was never to create beautiful software. The goal was to create a business that operated more effectively.

The Real Transformation Happened Inside the Organisation

When the project was completed, the biggest success was not the software itself. The greatest transformation occurred within the organisation. Departments began communicating more effectively because everyone was following the same workflow. Information no longer disappeared inside spreadsheets stored on individual computers. Management gained complete visibility into every stage of the business instead of relying on fragmented reports prepared manually by different teams. Employees spent less time searching for information and more time serving customers. Permission control reduced unnecessary risks, while structured processes improved accountability across the organisation. The company did not simply receive a new system. They gained an entirely new way of operating, where decisions were based on reliable information rather than assumptions.

Before Artificial Intelligence Comes Digital Transformation

Today, almost every boardroom conversation revolves around Artificial Intelligence. Organisations are eager to adopt AI assistants, intelligent automation and predictive analytics. Yet one important question is often overlooked: is the organisation actually ready for AI? Artificial Intelligence does not magically fix poor business processes, inconsistent data or fragmented operations. AI simply consumes whatever data an organisation provides. If the underlying data is incomplete, duplicated or inaccurate, AI will only produce faster and more convincing mistakes.

This is why I often remind business leaders that Digital Transformation is not an optional step before AI—it is the foundation upon which every successful AI initiative is built.

Digital Transformation creates structured business processes. Structured business processes generate reliable and consistent data. Reliable data empowers trustworthy Artificial Intelligence. Skip the first two steps, and AI simply becomes another expensive technology layered on top of organisational chaos.

Many organisations today are rushing to purchase AI tools before asking whether their own operations are ready. They hope AI will solve problems that actually originated from years of inconsistent processes, disconnected systems and poor operational governance. Unfortunately, AI cannot create operational discipline. It can only amplify whatever already exists. If your business operates with clarity, AI accelerates performance. If your business operates in confusion, AI accelerates confusion.

That is why I always tell business leaders during my keynote presentations that AI is not the starting point of transformation. Digital Transformation is.

A Leadership Lesson Beyond Technology

Looking back, this project reinforced something I have believed throughout my career. Technology has never been the hardest part of Digital Transformation. People often assume software development is about coding, databases and programming languages. In reality, the most difficult challenge is helping organisations rethink the way they operate.

Every company already has a workflow. Every company already has departments. Every company already has reporting structures. The question is whether those structures are still suitable for today's business environment.

Digital Transformation is not an IT initiative. It is a leadership initiative. It requires management to rethink responsibilities, decision-making, accountability and information flow before technology can truly deliver value. When leaders embrace this mindset, software becomes an enabler instead of a burden.

A Message to Business Leaders

If your organisation is constantly modifying its system but never seems to make real progress, perhaps the problem isn't your software vendor. If your employees continue relying on spreadsheets despite having an expensive system, perhaps the issue isn't user adoption. If every department keeps asking for new features while management still cannot obtain accurate information, perhaps the real challenge lies much deeper than technology.

Before introducing AI into your organisation, ask yourself a simple question: is your digital foundation strong enough to support it?

AI is only as intelligent as the data it receives. Data is only as reliable as the processes that generate it. And those processes are only as effective as the leadership that designs them. If the foundation is weak, AI will only make poor decisions faster. If the foundation is strong, AI becomes one of the most powerful business accelerators your organisation will ever adopt.

Over the past two decades, I have worked with organisations not just to build software, but to redesign how businesses operate. Sometimes that means stepping into projects that others could not complete. Sometimes it means rebuilding the architecture from the ground up. Much like an intensive care unit (ICU), our role is to stabilise critical digital transformation projects before they fail completely, allowing organisations to recover, modernise and prepare for the future.

If your organisation is facing endless software revisions, disconnected systems, poor data quality, weak permission controls or operational processes that no longer scale with your business, let's have a conversation. Whether through executive advisory, Digital Transformation consulting or one of my keynote sessions, my mission remains the same: to help organisations build the right digital foundation today, so they are truly ready for the AI-powered future tomorrow.

After using AI intensively over the past few weeks, I realised something interesting. My way of working has completely changed.

In the past, I spent almost the entire day operating my computer—writing, editing, checking, and executing every task myself. Today, my computer is running multiple AI agents at the same time. One is writing, another is researching, another is designing, while another is analysing data. My role is no longer to do everything manually.

Instead, I wait for the first draft. I review it, make adjustments, approve it, and let AI continue improving. My value has shifted from execution to judgment. The keyboard is no longer where I spend most of my time—my thinking is.

What the Waiting Moments Became

What surprised me most was what happened during those waiting moments. Instead of rushing to the next task, I found myself picking up a book, enjoying a coffee, or simply thinking about bigger ideas. It feels like a break, but in reality, it’s becoming some of my most productive time.

The Better Question

People often ask me whether AI will take away our jobs. I think a better question is this: When AI gives us back time, what will we do with it? Will we spend it scrolling through social media, or will we invest it in learning, reading, thinking, and becoming better leaders?

For me, that’s the real promise of AI. It isn’t replacing people—it is giving us the opportunity to focus on the things that only people can do: think deeply, make better decisions, and create a greater impact.

How has AI changed the way you spend your time? Has it made you busier, or has it given you back time to learn and think? I’d love to hear your experience in the comments.

Over the past two weeks, one of the biggest lessons I learned wasn’t about AI itself. It was about myself. For most of my career, I’ve been someone who is very detail-oriented. I like to understand every process, every implementation, and every small step before moving forward. That mindset has helped me build businesses over the years.

But recently, I found myself working differently. Instead of spending hours thinking about every detail, I began focusing on the outcome I wanted to achieve. I realised that AI is often capable of handling the detailed execution faster, more consistently, and sometimes even better than I could. It challenged a habit that I had built over many years.

Details Still Matter — But Who Handles Them Changes

This doesn’t mean details are no longer important. Details still matter. The difference is who should spend more time on them. As leaders, perhaps our greatest value is no longer doing every detail ourselves, but ensuring the direction is correct, the objectives are clear, and the instructions are precise. AI can help execute, but it still depends on us to define the destination.

Leadership Is About the Right Work, Not the Most Work

It reminded me that leadership has never been about doing the most work. Leadership is about helping people—or now, even AI—do the right work. The clearer our thinking, the better the execution becomes. I’ve started spending more time asking “What problem are we trying to solve?” rather than “How do I complete every individual task?”

I’m still learning every day, and I’m sure my thinking will continue to evolve. But this has probably been my biggest personal takeaway so far. AI isn’t replacing our thinking. It is pushing us to think at a higher level, focusing more on strategy, judgment, and leadership than ever before.

I’d love to hear your experience too. Has AI changed the way you work, lead, or make decisions? What’s the biggest mindset shift you’ve experienced? Let’s learn from one another, because I believe we’re all still discovering what leadership looks like in the AI era.

People often ask me why I started the Penang Digitalisation & AI Conference & Exhibition (PDX). Some assume it was because I wanted to organise a conference or create another technology event. The truth is much deeper than that. PDX was never about organising an event—it was about solving a problem that I had observed for many years.

Throughout my journey with OPERiON, I had the opportunity to work with organisations across different industries. I realised that government agencies, businesses, technology providers, universities and talented individuals were all working towards the same goal of driving innovation and economic growth. However, they were often working independently, with limited opportunities to connect, collaborate and create meaningful impact together.

I came to believe that digital transformation is not simply about adopting new technologies. It is about bringing people together, redesigning the way organisations operate, and building stronger partnerships across the entire ecosystem. Technology is only an enabler. Real transformation happens when people share knowledge, trust one another and work towards a common vision.

The Future Belongs to Ecosystems, Not Individuals

As artificial intelligence continues to reshape every industry, the importance of collaboration has become even greater. No single organisation can prepare for the future alone. Governments need industry. Businesses need technology partners. Universities need closer connections with employers. Students need opportunities to learn from real-world experiences. The future belongs to ecosystems, not individuals.

That belief became the foundation of PDX. My vision was to create a platform where government, industry leaders, technology providers, universities, startups and future talent could come together under one roof. A place where ideas become collaborations, collaborations become opportunities, and opportunities become lasting impact for our communities and economy.

Every Obstacle Became Part of the Journey

The journey has not been easy. Building an ecosystem is far more challenging than building a company. There have been countless challenges, financial pressures, setbacks and moments of uncertainty. Yet every obstacle has reinforced one important lesson: if the mission is meaningful and benefits others, every challenge becomes part of the journey rather than the reason to stop.

Today, PDX represents much more than an annual conference and exhibition. It is a growing movement to accelerate digital transformation, encourage responsible AI adoption, develop future-ready talent and strengthen collaboration between the public and private sectors. It is a platform designed to help organisations learn, connect and move forward together.

Looking Ahead

Looking ahead, my vision extends far beyond the next event. I hope to see PDX become a leading AI and digital ecosystem that starts in Penang and creates impact across Malaysia and the region. Through initiatives such as AI Hackathons, leadership forums, talent development programmes and industry collaborations, we can build a stronger future together. If you share this vision, I warmly invite you to join us on this journey by following PDX2027, participating as an exhibitor, partner or delegate, and becoming part of an ecosystem that believes innovation grows stronger when we build it together.

Think Bold. Build Together. Transform the Future.

Follow PDX

🌐 Website: penangdigitalisation.com

📢 Follow the PDX social media channels for the latest updates on exhibitions, conferences, partnerships, AI programmes and exhibitor opportunities.

We look forward to welcoming you to the PDX ecosystem.

By Ts. Lukas J. Tan

For the past two decades, businesses have invested heavily in Search Engine Optimisation (SEO). We optimised keywords, built backlinks, improved page speed, and published articles to rank higher on Google. Those strategies are still important, but while building my own AI workforce recently, I realised something that completely changed my perspective. The next generation of websites won’t compete only for search rankings—they’ll compete to be understood by AI.

One unexpected lesson came from something developers have quietly used for years: Markdown (.md). I wasn’t trying to learn Markdown. I discovered it while building AI-powered systems with Claude. At first, I wondered why almost every document was stored as a Markdown file instead of Microsoft Word or plain text. Then it clicked. Markdown isn’t just a writing format; it’s a structured way of organising knowledge. AI doesn’t care about beautiful layouts or animations. It understands hierarchy, relationships, context, and clearly organised information. The better your knowledge is structured, the easier it is for AI to understand your business.

This made me rethink how we build websites. Traditionally, we start by designing pages—Home, About Us, Services, Contact. Today, I believe we should start by designing knowledge. Most websites, especially traditional CMS platforms, were built primarily for humans to read and search engines to crawl. They can absolutely be made AI-friendly, but many organisations still organise content page by page rather than as a connected body of knowledge. With AI-assisted development, I now find myself creating structured knowledge first, then letting AI generate the website, proposals, profiles, and other business assets from that single source. The website becomes one output—not the starting point.

From SEO to GEO and AEO

I believe we are entering the next phase of digital transformation. In the past, we optimised for SEO. Today, conversations are shifting toward Generative Engine Optimisation (GEO), Answer Engine Optimisation (AEO), and other AI-focused approaches. Whatever terminology eventually becomes the standard, the direction is clear: organisations need websites that communicate expertise in a way AI systems can understand, not just pages that look attractive to people.

One Knowledge Base, Every Output

The organisations that adapt early will gain a significant competitive advantage. Imagine maintaining one trusted knowledge base that powers your website, LinkedIn articles, keynote profiles, proposals, sales materials, training content, and even your internal AI workforce. Instead of rewriting the same information across different platforms, AI understands your knowledge once and helps you publish it consistently everywhere. That changes not only how we build websites, but how we manage knowledge across an entire organisation.

I am still researching and learning in this space, but one thing is becoming increasingly clear. The last 20 years were about building beautiful websites. The next 20 years may be about building websites that AI can understand. The question is no longer, “Does your website rank on Google?” The better question is, “Can AI understand your business well enough to recommend it?” Those who begin restructuring their websites into AI-ready knowledge platforms today may be the ones who remain visible, trusted, and discoverable in tomorrow’s AI-first world.

People often ask me what framework I use or which technology I recommend. The truth is, I have never been someone who learns technology by memorising names or following trends. I learn by solving real business problems. Many years ago, I built a UI component system that made my projects more consistent and easier to maintain. Years later, someone looked at my code and said, “This is basically Bootstrap.” I smiled because, at the time, I had never even thought about Bootstrap. I wasn't trying to use a framework — I was simply trying to solve a problem.

The same thing happened again around 2009. As my projects became larger, I realised I needed a better way to control code quality. I designed my own PHP project structure so developers could only access the folders they were supposed to access. Business logic, presentation, and data were separated to make maintenance easier and reduce mistakes. Years later, I discovered that what I had built followed the same philosophy as the Model-View-Presenter (MVP) pattern. I didn't set out to implement MVP. I was simply designing a better way to build software.

The Problem Comes First, the Name Comes Later

Looking back, I realised this has always been my approach. I rarely start with a technology or a framework. I start with the problem. Once I understand the problem deeply, I build the architecture that solves it. Sometimes the industry already has a name for it. Sometimes it becomes a recognised design pattern. Either way, the name has never been the goal. The solution has always been the goal.

Why the Database Comes First

If there is one area I have always believed deserves the most attention, it is the database. Frameworks change. Programming languages evolve. AI models improve every few months. Cloud platforms come and go. But your data remains. A poorly designed database will create problems for years, no matter how modern the technology stack is. A well-designed database, on the other hand, allows applications, frameworks, and even entire platforms to evolve without disrupting the business. To me, the database is not just another component — it is the foundation of the organisation's digital assets.

That is why, throughout my career, I have invested more time in database architecture than in chasing the latest technology trends. Naming standards, relationships, primary keys, audit trails, migrations, scalability, and future-proof design are not glamorous topics, but they are the reason software survives. If people remember me for one thing, I hope it is this: build the database right, and everything else becomes easier.

If your organisation is facing challenges in database architecture, system design, digital transformation, or AI-ready application architecture, I would be glad to have a conversation. The right database design doesn't just solve today's problems — it creates the foundation for the next decade of growth.

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.