Tag: Self Improvement

The Hidden Trap Destroying IoT Platforms: 3 Silent Mistakes Founders Don’t See Until It’s Too Late

Many IoT platforms began their journey with strong foundations. They had capable engineering teams, promising technology, and even early customer traction. In the early stages, everything appeared to be moving in the right direction.

Yet over time, many of these platforms quietly stalled. Some remained small niche products. Others slowly faded from the market.

The collapse rarely happened suddenly. It emerged gradually, almost invisibly.

From observing the evolution of many IoT platforms over the years, three recurring patterns often appear. These are what I refer to as the three silent killers of IoT platforms.

1. The “Nice Platform” Problem

The first and most common challenge is what I call the “Nice Platform” problem.

Technically, everything works as expected. Sensors transmit data. Dashboards display attractive charts. Connectivity is stable. Demonstrations during presentations look impressive.

Customers often respond with comments like, “This is very interesting.”

But the real question is much deeper than whether the technology works.

Is the platform essential to the customer’s operations?

Many IoT platforms unintentionally position themselves as helpful tools rather than critical systems. They focus heavily on features such as:

• dashboards
• device connectivity
• data visualisation

These capabilities are useful. They demonstrate the power of connected systems.

But organisations rarely allocate long-term budgets for visualisation tools alone.

Businesses invest in solutions that directly influence outcomes. What they are truly paying for are measurable results such as:

• reducing equipment downtime
• preventing operational accidents
• lowering energy consumption
• avoiding regulatory penalties
• increasing workforce productivity

When a platform is tightly connected to these outcomes, it becomes embedded in the customer’s daily operations. It becomes part of their operational backbone.

But when the platform only provides visibility without directly influencing decisions or actions, it remains optional.

And optional systems are the first to disappear when budgets tighten.

This explains why the most successful IoT deployments focus on mission-critical problems. Examples include:

• predictive maintenance in industrial environments
• fleet safety monitoring for logistics operations
• cold chain compliance for pharmaceutical distribution
• energy optimisation for large buildings

These systems cannot simply be turned off without significant operational consequences.

That is the difference between interesting technology and essential infrastructure.

2. The Customisation Trap

The second silent killer appears much later in the journey, often after the platform begins acquiring its first paying customers.

Early adopters frequently request modifications. They ask for specific dashboards, specialised workflows, or integrations with legacy enterprise systems.

At the beginning, these requests appear reasonable.

A startup needs revenue. The team wants to satisfy its customers. Agreeing to customise the platform seems like a practical decision.

However, a hidden risk gradually emerges.

Over time, the platform begins to fragment.

Instead of maintaining a single scalable product, the engineering team finds itself supporting multiple customer-specific versions:

• one version tailored for customer A
• another variation for customer B
• a different configuration for customer C

The product gradually shifts from a platform to a collection of bespoke solutions.

Engineering resources originally intended to improve the core platform are redirected to meet project-specific requirements.

At this stage, the business begins to resemble a consulting company rather than a product company.

The consequences are predictable:

• development cycles slow down
• engineering teams become stretched
• product direction becomes unclear
• operating margins shrink

Scaling becomes increasingly difficult because each new customer introduces new complexity.

Many IoT startups unintentionally move into this trap. They begin with a platform vision but gradually become project delivery organisations.

The strongest platform companies remain disciplined about this boundary.

They continuously ask a simple but critical question:

Is this a reusable product feature or a one-off project request?

If the capability cannot benefit many customers across different industries, it may not belong in the core platform.

Maintaining this discipline is difficult in the early stages when revenue pressure is high. Yet it is often the difference between building a scalable platform and building a services business.

3. The Ecosystem Illusion

The third silent killer relates to ecosystem development.

Many platform founders assume that once the platform is launched, developers and partners will naturally begin building solutions on top of it.

The belief is simple: build the platform first, and the ecosystem will follow.

In practice, ecosystems rarely grow automatically.

Developers and partners choose platforms based on several practical considerations:

• the size and activity of the ecosystem
• the availability of development tools and documentation
• the potential economic opportunity

The economic factor is frequently underestimated.

Developers invest their time where they can build sustainable businesses. If there is no clear revenue path, most will quickly move to other platforms.

This is one of the key reasons large ecosystems expanded rapidly. Platforms such as:

Amazon Web Services
Shopify
Salesforce
Apple

created strong developer communities by building clear economic incentives.

Developers could launch products, attract customers, and generate revenue through these platforms.

In many IoT platforms, the ecosystem layer is incomplete. APIs and SDKs are available, but the economic model is unclear.

For an ecosystem to grow meaningfully, partners must clearly understand:

• how they can generate revenue
• how easy it is to build solutions on the platform
• how large the addressable market is

Without these signals, the ecosystem remains limited.

Developers may experiment with the platform, but long-term commitment rarely materialises.

Why These Killers Are Difficult to Detect

One of the most dangerous aspects of these challenges is their subtle nature.

None of them produces immediate crises.

The company may still:

• secure new pilot projects
• receive industry recognition
• release new product features
• attract positive feedback from users

From the outside, everything appears healthy.

But internally, warning signs slowly emerge. Growth begins to plateau. Profit margins tighten. The product roadmap becomes fragmented.

Eventually, the platform struggles to reach the scale necessary to compete globally.

This pattern explains why many IoT platforms remain respectable but small companies rather than evolving into global infrastructure providers.

The difference between the two often lies not in technological capability but in strategic discipline.

For IoT platforms to achieve long term impact, they must move beyond attractive dashboards and connectivity features. They must anchor themselves in mission-critical outcomes, protect the integrity of their core product, and build ecosystems where partners can thrive economically.

Only then can a platform move from being an interesting technology to becoming part of the digital infrastructure that organisations truly depend on.

These lessons continue to shape how many leaders in connected systems approach platform strategy today, especially as IoT, AI, and edge computing converge to redefine how digital infrastructure is built and secured.

Building IoT Alone Is the Biggest Mistake Most Companies Still Make

A reflection on growth, loneliness, and choosing not to build alone

There are moments when I catch myself repeating the same message, again and again, to different audiences.

Students. Founders. Engineers. Startup teams.

And every time, I pause for a second and ask myself quietly, Why does this still matter so much to me?

Then I remember the early days. The long pauses after unanswered emails. The feeling of being technically right, yet institutionally invisible. The realisation that effort alone does not always translate into progress.

That is usually when I say it out loud.

No company grows far on its own.

This piece is not about theory. It is about what I have seen, lived, and learned over the years while working with companies, policymakers, universities, and ecosystems. It is about why industry associations, when done properly, remain one of the most human ways to grow a sector.

The invisible ceiling of going solo

When you run a company, especially in a regulated or emerging sector, the limits show up sooner than expected.

You feel it when policies are unclear or outdated.
You feel it when rules were written without input from those actually building things.
You feel it when feedback channels exist, but nothing seems to move.

I have watched capable founders hit this ceiling repeatedly.

They write thoughtful letters.
They request meetings.
They try to explain context.

Silence.

Am I wrong? they wonder.
Or am I just too small to be heard?

Most of the time, it is the second.

Public institutions are structured to listen at scale. They are not designed to interpret dozens of fragmented voices. They need consolidation. They need synthesis. They need representation that speaks for more than one balance sheet.

This is where industry associations (like MyIoTA) quietly do their most important work.

A collective voice changes the tone of the conversation

An association does not shout louder. It speaks more clearly.

It gathers input from members with different sizes, strengths, and constraints. It filters emotion from facts. It frames issues in ways that policymakers can engage with responsibly.

Instead of saying, “This is my problem,” the message becomes, “This is what the industry is experiencing.”

That shift matters.

I have seen discussions move from defensive to constructive simply because the message came from an association rather than an individual company.

Not because the idea changed, but because the context did.

Business does not scale on capability alone

Let us talk about the part founders understand best.

Business.

In technology fields like IoT, no single organisation holds all the pieces. One is strong in devices. Another in platforms. Another in deployment. Another in funding and compliance.

Yet customers and tenders often expect a complete answer.

This gap creates frustration.

Small companies feel locked out.
Large companies feel stretched thin.

Associations create the space where these gaps can close naturally.

They do not force partnerships. They simply bring people into the same orbit often enough for trust to form.

I have seen partnerships start from casual chats at association events. No pitch decks. No contracts. Just shared pain points and curiosity.

Months later, those same people show up together in proposals.

That is how ecosystems grow. Quietly. Organically.

Partnerships are built long before tenders appear

One thing I often remind younger founders is this.

You cannot rush trust.

Consortia that work are rarely formed under pressure. They are formed over time, through repeated interactions, shared learning, and mutual respect.

Associations make this possible by creating continuity. You see the same faces. You observe who contributes. You learn who listens.

By the time an opportunity arrives, relationships already exist. There is no scrambling. No forced alignment.

Just readiness.

The underestimated value of presence

Some benefits of associations look small on paper.

Discounted exhibition rates.
Shared booths.
Collective branding.

But for growing companies, these matters are more than they appear.

Beyond cost savings, associations provide presence. They place members in rooms where conversations shape direction, not just execution.

Closed-door briefings. Industry dialogues. Stakeholder meetings.

Being present does not guarantee opportunity. But absence almost guarantees irrelevance.

Associations as connectors, not owners

One role I deeply respect is that of associations, which connect worlds that often struggle to meet.

Industry and universities.
Students and practitioners.
Researchers and real problems.

Universities need access to industry for research, surveys, and placements. Companies need talent that understands reality, not just textbooks.

Associations act as the bridge.

They lower the friction. They create trust. They shorten the distance between ideas and application.

Over time, students gain exposure. Companies gain insight. Research gains relevance.

Everyone benefits, without ownership being forced on anyone.

Leadership defines credibility

This part is uncomfortable, but necessary.

Associations are only as strong as the people leading them.

Titles do not build trust. Actions do.

Members quickly sense whether leaders are serving the sector or just their own organisations. Engagement follows honesty.

Through my work with the Malaysia IoT Association, I have learned that leadership in associations is not about visibility alone.

It is about consistency. Listening. Following through.

When leaders treat the role as stewardship, not status, members respond.

Sustainability without losing soul

Associations need money to function. That is reality.

Membership fees, events, and partnerships all play a role. The challenge is remembering why the association exists in the first place.

The moment it behaves like a profit-first entity, trust erodes.

Members are not customers. They are contributors.

They stay not because of perks, but because they feel movement. They see effort. They feel represented.

What I wish more founders realised earlier

I often hear this sentence.

“I will join when I am ready.”

Usually, that means bigger. More stable. Less busy.

But associations are not emergency services. They are growth environments.

They work best when you grow alongside them, not when you only show up during difficulty.

A few grounded thoughts if you are thinking of joining

Let me leave you with some practical reflections.

Join with curiosity, not expectation.
Participation creates value faster than observation.

Contribute before you ask.
Ecosystems reward generosity in strange but real ways.

Pay attention to leadership.
Active leaders signal healthy associations.

Think long term.
Relationships compound quietly over time.

Remember the purpose.
Associations exist to lift industries, not egos.

We were never meant to build alone

Every time I reflect on this topic, I come back to the same conclusion.

Growth is easier when shared.
Progress is faster when voices unite.
Resilience is stronger when support exists.

We like to celebrate lone heroes. But industries are built by communities.

If you have been part of an association, whether it helped you or disappointed you, I would genuinely like to hear your story. Share your experience in the comments. That is where better ecosystems begin.

From Classrooms to Critical Operations: The Truth About Favoriot’s Enterprise Role

They Thought Favoriot Was Just for Students.

I Let That Misunderstanding Linger for Too Long.

I need to admit something first.

This one is on me.

For years, people have come up to me and asked a question that always makes me pause.

“Dr Mazlan, is Favoriot only an education platform?”

Every time I hear that, I smile politely. I explain. I clarify. I move on.

But deep inside, I talk to myself.

How did we let this idea stick for so long?
Why didn’t we tell the story better?

Let me do this properly here. Slowly. Honestly. From the heart.

Because Favoriot was never born as an academic toy. It was never designed to live only inside labs, classrooms, or final-year projects. Favoriot was built as an enterprise IoT platform for real deployments, real operations, real risks, and real consequences.

Education came later. And it came for a reason.

Favoriot Was Built for the Real World First

When we started Favoriot, the vision was very clear.

Factories. Warehouses. Farms. Buildings. Cities.
Sensors are sending data every second.
Dashboards that people depend on, not admire.
Alerts that wake someone up at 3 a.m. because something is wrong.

That was the intention.

An enterprise IoT platform is not glamorous. It is not flashy. It does not impress with demos alone. It needs to survive power outages, unstable networks, noisy data, and human mistakes.

That is the world Favoriot was designed for.

Air quality monitoring, indoor and outdoor.
Gas detection in agriculture and manufacturing.
Cold chain and warehouse monitoring.
Energy usage. Environmental sensing. Operational visibility.

These are not student exercises. These are systems people rely on to protect assets, livelihoods, and, at times, lives.

And yes, many of these implementations cannot be publicly shared. Clients trust us with their data and their operations. Confidentiality is part of doing real work.

Ironically, that silence made people assume nothing was happening.

Maybe that’s where the misunderstanding started.

The Real Problem Was Never the Platform

Here is the uncomfortable truth.

The biggest challenge in IoT is not platforms.
It is not sensors.
It is not cloud infrastructure.

It is people.

Or more specifically, the lack of people who truly know how to build an IoT solution end-to-end.

Back in 2017, we offered a free plan. We thought adoption would be instant.

It wasn’t.

People signed up.
Then they stopped.
Nothing moved.

And I remember thinking, “Why is no one using it?“

The answer hurt a little.

They didn’t know how.

They knew dashboards from presentations.
They knew buzzwords from conferences.
They knew how to connect one sensor, sometimes.

But building a full solution?
Designing data flows?
Handling failures?
Understanding why data behaves badly in the real world?

That knowledge gap was huge.

From 2017 to 2022, I saw it everywhere. Universities. Startups. Even some companies. Everyone wanted IoT. Very few knew how to build it properly.

Why We Walked into Education

So we made a decision.

Not a pivot. Not a retreat. A foundation.

If people cannot build IoT solutions, no platform will ever matter.

I remember asking myself:
Do we complain about the talent gap, or do we help close it?

That is when we started working closely with educators. Training lecturers. Creating step-by-step tutorials. Supporting students not to pass subjects, but to understand systems.

That is why Favoriot content online often looks educational.

Not because we are an education-only platform.
But because education was the missing piece in the ecosystem.

We were not selling theory. We were teaching how to connect sensors, send data, manage devices, handle failures, and make sense of messy reality.

Education was not the destination. It was the on-ramp.

Two Worlds. One Platform.

Here is what many people missed.

While all this educational work was happening in public, Favoriot was quietly working with industry in parallel.

Two tracks. Same platform.

On one side, students and lecturers are learning how to build.
On the other, enterprises deploying systems that run daily operations.

The platform did not change.
The expectations did.

Students learn to make things work.
Enterprises demand that things not break.

That dual role was never a conflict. It was a strength.

Education feeds industry.
Industry validates education.

Yet we did not tell that story clearly enough. And for that, I take responsibility.

The Irony of Global Adoption

Here is another irony that few people realise.

Favoriot users come from all over the world. When someone subscribes, they build whatever they want.

We do not always know what devices they connect.
We do not always know what systems they deploy.
We only see data flowing.

Some of the most interesting use cases are completely invisible to us.

And that is exactly how a real platform works.

No hand-holding. No spotlight. Just infrastructure doing its job.

But again, silence creates assumptions.

If people don’t see it, they think it doesn’t exist.

This Is Not Just About Favoriot

This reflection is not only about correcting a misunderstanding.

It is about how we, as a country and as a community, think about capability.

We love importing solutions.
We love buying finished systems.
We rarely invest in learning how they are built.

Then we wonder why we depend on outsiders for everything.

IoT is not magic. It is engineering. It is discipline. It is patience. It is experience.

Platforms like Favoriot matter only when people know how to use them properly.

That is why education and enterprise must never be separated.

What I Wish People Would See

I wish people would stop asking whether Favoriot is for education or industry.

It has always been both.

Education builds builders.
Industry needs builders.

One without the other collapses.

Sometimes I ask myself:
If we had focused only on selling enterprise solutions, would the ecosystem be stronger today?

Honestly? No.

Without talent, platforms die quietly.

A Personal Reflection

I have spent my life in technology. Telecom. IoT. Smart systems. Startups.

The pattern is always the same.

People rush to buy tools.
Very few invest in learning how to use them well.

Favoriot’s story is a reminder to me, too.

Technology without understanding is decoration.
Understanding without real deployment is a fantasy.

We need both.

My Message to Educators

Do not treat IoT platforms as demo tools.

Treat them as environments where students learn responsibility.

Teach failure.
Teach troubleshooting.
Teach why things break.

That is how builders are formed.

My Message to Industry

Do not dismiss platforms you see in universities.

Those environments are where your future engineers are learning.

Support them. Challenge them. Hire them.

You will thank yourself later.

My Message to Policymakers and Leaders

If you want digital capability, stop funding only deployments.

Fund learning.
Fund training.
Fund local platforms and ecosystems.

Ownership starts with understanding.

And Finally, My Message to You

If you are reading this and you once thought Favoriot was “just for education”, I hope this piece helped.

If you already knew the bigger picture, help me tell the story better.

Because platforms do not build ecosystems.
People do.

And ecosystems take time, patience, and honesty.

I’m still learning that myself.

What about you?

Have you seen similar misunderstandings in your work or industry?
Drop your thoughts in the comments. I read them all.

AI Is Everywhere Today, But the Real Power Still Comes From Somewhere Else

There are moments when I sit back after a lecture, pack my bag, and feel a strange mix of pride and worry.

Pride because I have seen how far technology has come.

Worry because I know how easily we forget the foundations.

That Friday lecture on the relevance of IoT and the rise of AI stayed with me long after I left the room. Not because the topic was new. I have lived with IoT for more than a decade. It stayed with me because of the silence that follows whenever I ask a simple question.

Where does your data actually come from?

Everyone lights up when we talk about AI. Eyes widen. Phones come out. Someone mentions ChatGPT. Someone else talks about image generation, voice cloning, videos that look real enough to fool our parents and sometimes ourselves.

Then I bring up sensors.

And the room goes quiet.

I Have Seen This Story Before

I thought to myself, This feels familiar.

Back in 2014, when we published the national IoT roadmap, the words “Internet of Things” sounded foreign to many. We talked about low-powered networks, sensors, connected devices, and data that flows quietly in the background. At that time, most people were still trying to understand what IoT even meant.

Later came the Fourth Industrial Revolution hype. AI, blockchain, cloud, analytics. Big words. Big slides. Big expectations.

Then COVID arrived and forced everyone online. Suddenly, digitising forms was no longer optional. Meetings went virtual. Systems moved to the cloud. People realised something uncomfortable.

We were talking about advanced technologies, but many organisations were still doing basics by hand.

We wanted intelligence without instrumentation.

The Quiet Truth About AI

Here is the uncomfortable truth that does not trend well on social media.

AI without data is just hope.

AI without sensor data is mostly guessing.

Most of the “intelligent” things people want today depend on time-based data from the physical world. Energy usage. Temperature. Vibration. Traffic flow. Air quality. Machine health. Human movement.

All of these begin with IoT.

When someone says they want predictive insights, I gently ask, How long have you been collecting data?

When they say they want anomaly detection, I ask, Do you know what normal looks like for your system?

These are not trick questions. They are reminders.

AI does not magically appear. It grows from data that has been quietly collected, cleaned, and understood over time.

Dashboards Make Us Feel Safe

I have seen countless dashboards.

Beautiful charts. Moving lines. Big screens in control rooms. Red, amber, green indicators blinking politely.

And yet, I always ask myself, What decision changed because of this screen?

Dashboards tell us what has already happened. That is useful, but limited. It is like driving while looking only in the rearview mirror.

What people really want is to know why something is happening. Or what might happen next. Or what they should do about it.

That is where analytics, machine learning, and edge intelligence come in.

But none of that works if the data is poor, sparse, or misunderstood.

The Rise of Edge Thinking

One part of the lecture that excited me was the discussion of edge intelligence.

I remember thinking, This is where things finally feel grounded.

Not every decision needs to travel to the cloud and back. Cameras detecting unusual behaviour. Machines sense abnormal vibration. Safety systems reacting in milliseconds.

These decisions must happen close to where the data is created.

That requires discipline in how we design systems. What runs on the device. What runs centrally. What gets escalated to humans.

Technology is not just about speed. It is about trust.

Why IoT Feels Invisible Now

IoT has become so normal that people barely talk about it anymore. It works quietly. Sensors sit on walls, poles, machines, and vehicles. Data flows without fanfare.

AI, on the other hand, talks loudly. It writes. It draws. It speaks. It performs.

So attention shifts.

But I keep reminding myself, and my students, that the loudest technology is not always the most important one.

AI sits atop IoT, not beside it.

Universities Are Catching Up, and That Gives Me Hope

One of the most encouraging things I see today is how universities are changing.

Students are no longer just learning theory. They are building devices. Choosing protocols. Sending data into platforms. Visualising it. Asking questions. Experimenting with machine learning.

When students understand the full journey of data, from sensor to insight, something clicks.

They stop chasing shiny features.

They start thinking like builders.

A Subtle Lesson From the Field

Over the years, working closely with real deployments, I have learned something simple.

Systems fail not because of a lack of intelligence, but because of a lack of patience.

AI needs time. IoT needs consistency. Data needs care.

Platforms that respect this reality are the ones that last. I have always believed that an IoT platform should quietly support learning, experimentation, and growth without demanding attention. It should help teams move from visibility to understanding, and later to confidence.

That philosophy has shaped how we build things at Favoriot. Not chasing headlines, but supporting people who want to do the hard work properly.

Advice I Keep Repeating to Myself

As I reflect on that lecture, I find myself repeating a few reminders.

Do not rush AI before you understand your data.

Do not replace thinking with automation too early.

Do not trust dashboards that cannot explain themselves.

Do not ignore sensors just because they are quiet.

Most importantly, do not forget that technology exists to help humans make better decisions, not to impress them.

Progress is not about who adopts AI first.

It is about who builds understanding that lasts.

If this reflection resonates with you, share your thoughts. I would love to hear how you are balancing IoT and AI in your own work, and what lessons you are learning along the way.

Why Becoming a Producer Nation Still Keeps Me Awake at Night

There was a moment some time ago when I paused in the middle of a talk and looked around the room. Not because I forgot my slides. Not because I lost my train of thought.

But because something heavier crossed my mind.

I was surrounded by capable people. Young engineers. Curious technologists. Lecturers who cared. Students who wanted to build something meaningful.

And a question whispered quietly in my head.

What kind of future are we actually preparing them for?

That question refuses to leave me. It follows me into meetings, classrooms, and late-night reflections. It comes back whenever I see another imported system being installed, another local prototype ignored, another talented graduate settling for work that barely scratches their potential.

This is not about blaming anyone.
This is about being honest with ourselves.

The comfort trap we rarely talk about

Let me say this plainly.

Being a consumer nation feels safe.

You buy what already works.
You rely on someone else’s research.
You avoid the pain of early failure.

There is no embarrassment in using technology built elsewhere. We all do it. I do it too. The problem begins when using becomes the end of the story.

When a country only consumes, it slowly forgets how to create.

Companies no longer need deep technical teams.
Jobs no longer demand strong problem solvers.
Graduates are hired, but not challenged.

And when skills are not demanded, they are not rewarded.

I have watched this cycle quietly repeat itself.

Low demand for advanced skills leads to low salaries.
Low salaries keep household income stuck.
And national ambition stays trapped in speeches instead of results.

I often ask myself, what is the point of producing bright graduates if the economy only needs users?

What changes when a nation chooses to build

A producer nation changes the conversation entirely.

Instead of asking, “What can we buy faster?”
It asks, “What can we build better?”

The moment local companies start developing their own products, something shifts inside the system.

Skills suddenly matter.
Experience becomes valuable.
Talent is no longer replaceable overnight.

Companies compete for people who can design, test, deploy, and maintain real systems. Salaries rise not because someone demands it, but because value is being created on the ground.

This is how strong economies grow. Quietly. Patiently. Through capability, not dependency.

I remind myself often that a producer nation is built by people who are willing to be uncomfortable first.

The painful truth about local innovation

Here is where the story becomes uncomfortable.

Most local startups do not fail because their ideas are bad.
They fail because nobody buys from them early enough.

There is a fragile phase every builder faces.
The search for the first ten customers.

Without those early believers, there is no runway. No learning loop. No chance to improve.

And this is where I sometimes feel uneasy.

We encourage innovation.
We fund research.
We celebrate prototypes.

Yet when it is time to adopt, trust disappears.

I catch myself thinking: why do we support people in building, but hesitate to stand beside them when they are ready?

Without local adoption, many promising efforts fade away. Not loudly. Quietly. One by one.

Universities are not broken. Expectations are.

For years, I have heard the same complaint repeated.

“Universities are not producing commercial products.”

That statement misses the point.

Universities were never meant to be factories.
They are meant to be places where thinking goes deep.

They excel at long-term exploration.
They are strong at building early prototypes.
They train minds, not sales pipelines.

The problem starts when we expect universities to sprint like startups.

I often tell myself, you do not ask a marathon runner to win a 100-meter dash.

When companies bring real, long-term problems to universities, something powerful happens. Research becomes grounded. Students work on issues that matter. And ideas mature with purpose.

The missing bridge between lab and market

There is a wide gap between a working prototype and a product that survives in the field.

Many people underestimate this gap.

A system that works in a lab has not yet faced real users, harsh environments, unreliable networks, or unexpected behaviour. This is where companies must step in.

Universities build understanding.
Companies build resilience.

When they work separately, both struggle.
When they move together, progress accelerates.

This bridge was not built overnight. It takes patience, shared goals, and trust.

Why the first believer matters most

Every global success begins at home.

Before the world trusts you, someone local must.

That is why early adopters matter so much. Especially large organisations and government bodies.

Being the first customer is not charity.
It is leadership.

It gives builders confidence.
It creates reference stories.
It signals belief.

Belief, more than marketing, opens doors beyond borders.

Why I chose to build instead of complain

At some point, reflection was not enough.

I asked myself a harder question.

If I believe in building local capability, what am I personally doing to make it happen?

That question led me to Favoriot.

Favoriot was never about flashy dashboards.
It was about enabling builders.

A place where students move beyond demos.
Where startups test ideas without fear.
Where organisations grow solutions they understand and own.

I wanted a platform that supports responsibility, not just visibility.

A quiet piece of advice I return to often

Do not wait for perfect systems.
Do not wait for perfect policies.
Build anyway.

To students
Choose projects that solve real problems.

To universities
Work with companies that think beyond short grants.

To companies
Invest in local capability, even when it feels slower.

To decision-makers
Adopt local solutions early, not after they succeed elsewhere.

My invitation to you

If you believe our future depends on building, not just buying.
If you believe talent deserves meaningful challenges.
If you believe local solutions deserve real trust.

Then take one step.

Support a local product.
Adopt a local system.
Encourage someone who is trying.

And if you are looking for a place to start building, experimenting, and growing with confidence, explore Favoriot.

Not as software.
But as a choice.

I would love to hear your thoughts.
Are we ready to move from comfort to courage?

Crafting Impactful Final Year Projects: A Guide

I’ve sat on many evaluation panels over the years.

Different universities. Different rooms. Different faces.

But strangely, the pattern is always familiar.

Students walk in carrying posters, prototypes, sometimes with wires still exposed, sometimes with boxes made from recycled lab scraps. They look nervous. Excited. Hopeful. Tired.

And almost every presentation begins the same way.

“This project is about…”
“The objective of this project is…”

I sit back in my chair and quietly think to myself, Ah… here we go again.

Because at that moment, something important is missing.

The Moment Evaluators Lean In or Tune Out

When I evaluate a Final Year Project, I’m not hunting for perfection. I’m not expecting commercial-grade products. I’m not counting how polished the slides are.

I’m listening for one thing.

Do you understand why you built this?

Many students rush straight into objectives, features, and functions. But they forget to set the stage. They forget to frame my mind.

Without a background.
Without a problem that feels real.
Without a pain point that matters.

And when that happens, evaluators start asking questions not because the project is weak, but because the story is unclear.

Help me care first, I always think. Then help me understand.

Start With Pain, Not Purpose

The strongest projects I’ve seen don’t start with what was built.

They start with what hurts.

A system that fails silently.
A manual process that wastes hours.
A safety issue nobody notices until it’s too late.
A data gap nobody talks about.

When students explain the background clearly, something shifts. The room wakes up. The evaluator’s brain starts connecting dots.

Only after that does the objective make sense.

Because now, the solution has a reason to exist.

Scope Is Not a Weakness

Another thing I notice again and again.

Projects that look “complete,” but aren’t honest about their limits.

Students are afraid to admit constraints. Limited time. Limited budget. Limited access to hardware. Limited skills.

But here’s the truth.

A clear scope shows maturity.

When you explain what you chose not to build and why, you’re telling me you understand trade-offs. You understand reality. You’re not pretending.

That impresses evaluators more than pretending everything is done.

The Story of Struggle Matters More Than the Result

Some of the most memorable presentations weren’t the ones that worked perfectly.

They were the ones where students said:

“We tried this. It failed.”
“So we changed this.”
“It broke again.”
“Here’s why we finally chose this approach.”

That tells me you didn’t just follow a tutorial. You wrestled with the problem. You learned where things break.

And that’s exactly what real engineers, builders, and problem solvers do.

Architecture Is Not Just a Diagram

I’ve lost count of how many times I’ve seen architecture diagrams that don’t reflect reality.

Devices sending data to nowhere.
Networks are magically working.
Platforms floating without context.

When I ask, “Where does the data go next?”
Silence.

Architecture is not an artwork. It’s a thinking tool.

If you can’t explain how data moves from device to network, from network to platform, from platform to application, then you don’t fully own your system yet.

This is where supervisors play a big role. And this is where students must slow down and really understand what they are drawing.

Prototypes Don’t Need to Look Pretty

Some students apologise for their mock-ups.

“Sorry, sir, this is just a box.”
“Sorry, sir, we used old parts.”

I always smile.

Because that’s not what I’m judging.

What excites me is when students act out real scenarios. When they simulate how users interact. When they demonstrate behaviour, not just hardware.

I still remember sitting inside a car to experience a student-built parking system. That wasn’t about polish. That was about empathy.

The Question That Makes Everyone Nervous

Then comes the part that always makes students laugh nervously.

“So… who would buy this?”

Suddenly, the room gets quiet.

Many students talk about the cost of components. Few talk about customers. Fewer talk about value.

I’m not expecting a full business plan. I’m testing awareness.

Do you understand that solutions exist to be used?
Do you know who benefits from what you built?

Because a project that solves a real problem for a real group of people already has more value than one that only looks good on demo day.

When Systems Break, Thinking Is Revealed

The most important questions often come at the end.

“What happens if the system fails?”
“How do you troubleshoot this?”
“What would you check first?”

These answers reveal everything.

They show whether learning happened.
They show whether the student truly built the system or just assembled it.

In team projects, I watch carefully. Everyone should understand their role. Everyone should be able to support each other. Silence from team members tells its own story.

Forty Years of Change, One Pattern That Remains

I’ve watched student projects evolve from the 1980s until today.

Better tools. Better access. Better exposure.

Yet one problem remains.

Projects restart from zero every year.

Limited budgets force repetition. The same sensors. The same ideas. The same level of impact.

Imagine if universities treated projects as living systems.

One cohort builds the base.
The next improves it.
Another adds data analysis.
Another adds intelligence.

That’s how meaningful systems grow.

Especially in IoT, where data collected over time becomes more valuable than the device itself.

My Advice to Students and Educators

If you’re a student, remember this.

Your project is not judged by perfection.
It’s judged by understanding.
Clarity.
Honesty.
Growth.

Tell the story of your problem.
Explain your decisions.
Show your struggles.
Own your limits.

If you’re an educator or supervisor, help students see beyond grades.

Teach continuity.
Teach systems thinking.
Teach them to build on each other’s work.

Because the real world doesn’t reset every semester.

And the most important lesson a Final Year Project can teach is not how to build something that works.

It’s how to think when things don’t.

The Moment the Smart City Dashboards Stopped Impressing Me

There was a time when I was impressed by command centres.

Rows of screens.
Maps glowing in neon colours.
Charts are moving in real time.
Operators are pointing at dashboards like air traffic controllers.

It looked powerful.
It looked serious.
It looked… convincing.

But one day, standing quietly at the back of the room, I caught myself thinking something uncomfortable.

If one screen goes dark, who notices?
If the data contradicts another system, who decides?
If something breaks at 2 a.m., who actually understands what is happening?

That was the moment the screens stopped impressing me.

Because cities are not run by visuals.
Cities are run by clarity.

And clarity does not come from dashboards alone.

How Cities Slowly Accumulate Silos Without Realising It

Most local councils chose not to fragment.

Fragmentation happened to them.

Projects arrived one by one.
Budgets were approved year by year.
Each initiative solved a real problem at the time.

Flood monitoring came first.
Then air quality.
Then lakes.
Then traffic.
Then parking.

Each project was justified.
Each vendor delivered.
Each system worked.

Individually.

What nobody planned for was the moment when all these systems would need to speak to each other.

So the command centre slowly became a collection of disconnected truths.

Each dashboard told its own story.
None of them told the whole truth.

When a Dashboard Is Mistaken for a Platform

I often hear this sentence.

“Yes, we already have a smart city platform.”

Then I look closer.

What I see is usually a visual layer.
A presentation surface.
A beautifully designed window.

But behind it, there is no device management.
No rule engine.
No action triggers.
No real-time orchestration.

Just data being shown.

And showing data is not the same as running a city.

A true platform does not just display.
It listens.
It reacts.
It remembers.
It connects.

Two Types of Data That Rarely Shake Hands

Cities live in two data worlds.

The first world is structured, administrative, and familiar.

Assets.
Licences.
Collections.
Population data.
Facilities.

This data is critical. It reveals the city’s shape. It is refreshed periodically and often lives inside systems branded as urban observatories.

The second world is restless.

Sensor data.
Live streams.
Alarms.
Failures.
Spikes.
Drops.

This is IoT data.
It does not wait politely.
It arrives when it wants.
It demands attention.

The mistake happens when we treat both worlds as if they behave the same way.

They do not.

GIS and Digital Twins Without Real-Time Truth

Many councils have strong GIS platforms.

Layers upon layers of insight.
Maps that tell stories about people, land, and risk.

Some go even further with digital twins.
Virtual representations of buildings, roads, and infrastructure.

I admire these efforts.

But without live sensor input, these systems are frozen in time.

They show structure.
Not behaviour.

A city is not just where things are.
It is how things change.

Without IoT data, even the most beautiful digital twin is only a photograph, not a mirror.

Why an Integrated IoT Platform Is Not Optional Anymore

At some point, cities reach a tipping point.

They stop asking for new dashboards.
They start asking better questions.

Why did flooding worsen after that traffic upgrade?
Why does air quality dip only in specific zones?
Why do alarms trigger too late?

These questions cannot be answered inside silos.

They require correlation.

This is where an integrated IoT platform matters.

Not to replace everything.
But to connect everything.

A layer where data from rivers, rain, air, traffic, parking, and buildings can coexist.
A place where patterns emerge.
A place where decisions are supported, not guessed.

This is the role of IoT middleware.
This is where platforms like FAVORIOT were designed to sit.

The Fantasy of One Platform to Rule Them All

Every city dreams of simplicity.
Every vendor dreams of being central.

The idea of one master platform controlling everything is seductive.

But reality is less romantic.

Platforms are built with different goals.
Vendors protect their niches.
Legacy systems do not disappear quietly.

Trying to force everything into one system usually creates resistance, delays, and disappointment.

Cities do not need domination.
They need coordination.

The Quiet Risk Nobody Likes to Talk About

There is a dangerous sentence I hear too often.

“We don’t mind. Let the vendor manage everything.”

It sounds efficient.
It sounds hands-off.

Until the day the council asks for raw data.
Or integration rights.
Or historical access.

And discovers they cannot.

No API.
No export.
No control.

That is vendor lock-in.
And by then, it is too late to complain.

A smart city without data ownership is not smart.
It is dependent.

Procurement Is the Real Smart City Strategy

Smart cities are not won in control rooms.

They are won in procurement documents.

When councils specify openness.
When they demand interoperability.
When they insist on owning their data.

That is when cities protect their future.

Technology can always be upgraded.
Contracts are harder to undo.

Integration Is an Act of Maturity

I no longer believe in replacing everything.

I believe in respecting what already works.
Connecting what matters.
Opening what was once closed.

Legacy platforms should remain.
Specialised systems should continue.
But data must flow.

Sometimes that means managing two or three core platforms instead of one.

That is not failure.
That is realism.

Why I Keep Writing About This

I am not chasing trends.
I am chasing calm.

Calm operators.
Calm decision-makers.
Calm cities that respond instead of react.

When systems are integrated, nights are quieter.
When data is shared, trust grows.
When platforms cooperate, leaders sleep better.

If you are building a smart city, pause before asking for another screen.

Ask instead:
Can this system talk?
Can it share?
Can it last?

If this reflection sounds familiar, I would love to hear from you.

What have you seen in your city?
Where did silos slow you down?
What worked when integration finally happened?

Drop your thoughts in the comments.
Let us learn from each other and build cities that truly understand themselves.

When the Dashboard Goes Quiet, That’s When IoT Gets Real

There is a moment in every IoT journey that nobody prepares you for.

It does not happen during Demo Day.
It does not happen when the dashboard looks clean and colourful.
It does not happen when everyone claps after a presentation.

It happens much later.

Usually at night.
Usually, when you are already tired.
Usually, when someone sends you a short message that feels far heavier than it looks.

“Why is there no data?”

I have seen this moment too many times.

With students working on their final-year projects.
With startup founders handling their first paying customer.
With engineers running systems inside real buildings.
With councils operating services that citizens quietly rely on every day.

And every single time, something changes inside the person responsible.

I remember thinking, this is the exact point where IoT stops being exciting and starts being serious.

This piece comes from years of deployments, troubleshooting sessions, and long conversations after systems went silent. Not theory. Not slides. Just reality.

The Comforting Lie After Deployment

There is a lie many of us tell ourselves.

“The device is configured.”
“The data is visible.”
“The dashboard is live.”
“So… we’re done.”

No, we are not.

IoT is not a setup task. It is a living system. It depends on networks, power, firmware, environments, and people. The moment you walk away thinking the job is finished is the moment problems start lining up quietly.

I caught myself smiling too early more than once.

Dashboards give confidence. Continuity demands discipline.

One shows you data.
The other earns trust.

Start Calm, Not Defensive

When data disappears, panic is natural.

The first instinct is often to blame the IoT platform.

But here is a simple rule that has saved me countless hours.

If the platform were really down, everything would stop.

All devices.
All data streams.
All dashboards.

Platforms do fail, but when they do, they fail loudly.

So if only one device goes quiet, or just a few sensors disappear, the problem is almost always somewhere else.

I tell myself this every time. Breathe first. Then diagnose.

Troubleshooting is not about pointing fingers. It is about narrowing the truth.

Connectivity Breaks More Systems Than Code

Most IoT failures are not complicated.

They are forgotten changes.

One common story involves Wi Fi.

Sensors work perfectly for months.
Data flows.
Everyone forgets they exist.

Then suddenly, silence.

What happened?

Someone changed the network name.
Or updated the password.
Or replaced an access point.

No announcement. No warning.

The IT team did their job. The sensors were simply not in their mind.

Machines never forget. People do.

The same thing happens with cellular networks. Coverage shifts. Base stations go down. Buildings block signals. Sometimes there is simply no other tower to talk to.

Connectivity is fragile. Always question it early.

Power Is Never a Small Detail

If there is one lesson I wish every IoT builder would take seriously, it is this.

Power decides everything.

Battery-powered devices do not fail dramatically. They fade away quietly.

Solar-powered systems look perfect on paper until cloudy days stretch longer than expected.

I have seen devices placed outdoors with confidence in solar charging, only to stop transmitting because the battery never recovered.

I remember asking myself, “Why didn’t we check the battery level?”

Every remote device must report its own energy health.

Battery level matters.
Charging status matters.
Energy trends matter.

If you do not watch power, it will surprise you at the worst time.

Hardware Lives in the Real World

We love talking about cloud systems and apps.

But IoT lives outside.

Rain falls.
Heat builds up.
Humidity creeps in.
Lightning strikes.

Boards short circuit. Connectors loosen. Devices age.

Sometimes the device is simply broken.

No amount of dashboards can fix damaged hardware.

Software forgives. Physics never does.

This is why placement, casing, grounding, and environmental awareness matter far more than people think.

Firmware Can Help or Hurt You

Firmware sits quietly in the background until it does not.

Change it carelessly, and devices disappear.
Never change it, and vulnerabilities grow.

Remote systems need over-the-air updates, but that alone is not enough.

You need to know which device runs which version.
You need a way to recover when updates fail.
You need discipline.

Without that, scaling feels stressful instead of rewarding.

You Must See Both Sides Clearly

Serious IoT work demands a wider view.

You cannot focus only on software.
You cannot focus only on hardware.

You need to understand how the app, device, network, and power behave.

And more importantly, how they fail together.

That is why platforms matter. Not because of charts, but because they help you see the whole chain when things stop working.

A good platform does not just show data. It helps you ask the right questions when data disappears.

The Shift Nobody Warns You About

There is a quiet transition every IoT builder goes through.

At first, dashboards excite you.
Later, inconsistency frustrates you.
Eventually, responsibility humbles you.

The moment someone depends on your system, everything changes.

You stop chasing features.
You start chasing stability.
You stop admiring charts.
You start valuing calm silence.

I once realised that boring systems are often the best ones.

Because boring usually means reliable.

Why This Matters Now

As more devices enter buildings, cities, farms, factories, and public services, silence becomes dangerous.

No data is not just a technical trouble.
It is broken trust.

People stop believing.
Teams lose confidence.
Organisations lose sleep.

Trust takes years to build and seconds to lose.

That is why learning IoT must go beyond dashboards. We need to talk openly about failure, continuity, and responsibility.

A Quiet Invitation

If you are a student, do not rush past problems. Sit with them. They are shaping how dependable you will become.

If you are a developer, stop asking only what features to add. Start asking what can quietly fail.

If you are an organisation, invest in people and systems that understand the whole picture, not just the surface.

And if you have already felt that heavy moment when the dashboard went quiet, you are not alone.

That moment means you care.

Share your story.

When was the first time your system stopped sending data?
What did that moment teach you?

Write it in the comments.

Why Universities Need a Real IoT Lab, Not Just Another Embedded Lab

I still remember a meeting with a group of lecturers, where I asked a simple question.

“Why do we really need an IoT Lab in universities?”

I paused for a moment.
Because deep down, I already knew the answer.

Most universities already have something they proudly call an IoT lab. Rows of ESP32 boards. Arduino kits. LEDs are blinking happily. LCD screens displaying temperature values. Students smile because something lights up.

And yet, something feels incomplete.

This is not IoT. This is just the beginning.

This blog is not meant to criticise universities. I have spent years inside them. I was once a lecturer designing syllabuses, labs, and assessments. This comes from care. From concern. From watching students graduate with confidence in embedded programming but struggle the moment systems become real, connected, and dependent upon.

This reflection is based on a recent lecture I delivered on the need to establish a proper IoT Lab in universities, one that reflects how systems are actually built, deployed, and trusted today.

Embedded Systems Taught Us How to Build Devices

Let me be very clear.

Embedded systems are important. They are foundational.

Students need to learn how to program microcontrollers. They need to understand sensors, actuators, interrupts, memory, and power consumption. All of that matters.

An embedded system is usually a standalone device. It senses something. It controls something. It logs data into local storage.

There is nothing wrong with that.

In fact, embedded systems are still used today in places with no connectivity. Remote areas. Harsh environments. Offline conditions.

But here is the problem.

Once the data is captured, someone has to physically go to the site, connect a laptop, download the data, return with it, and process it manually.

I have seen this happen too many times.

Two technicians. One vehicle. Hours of work. Just to retrieve data that could have been transmitted automatically.

I always ask myself… why are we still doing this in 2026?

Connectivity Changes Everything

The moment a device is connected to the internet, everything changes.

Data no longer waits for humans to come and collect it.
It flows.
It moves.
It becomes alive.

This is the moment embedded systems evolve into the Internet of Things.

Now we can monitor systems remotely.
Now we can detect failures early.
Now we can see battery levels dropping before devices die silently.
Now we can act before complaints arrive.

And yet, most university labs stop just before this moment.

Students are taught how to blink LEDs, but not how to send data reliably.
They learn how to display values, but not how to secure data in transit.
They build devices, but not systems.

And systems are what the real world depends on.

A Real IoT Lab Must Teach Technology Layers

IoT is not a single skill. It is a stack.

In my lecture, I stressed that a proper IoT Lab must expose students to multiple technology layers, not in theory, but through hands-on work.

Layer 1: Hardware and Firmware

This is where universities are already strong.

Sensors. Controllers. Actuators. Firmware logic. Power management.

Students should continue learning this well.

But they must also understand that this is just one layer.

Layer 2: Connectivity and Protocols

This is where gaps start to appear.

Students must learn how data travels.

Wi-Fi. Cellular. LPWAN.
Bluetooth. ZigBee. RFID.
MQTT. CoAP. REST. HTTP.
LoRa. NB-IoT. Sigfox.

Not as a list to memorise.
But as choices with consequences.

Which protocol suits low power?
Which network works for long range?
What happens when connectivity drops?

Without this understanding, troubleshooting becomes guesswork.

Layer 3: Platform and Middleware

This is the heart of IoT.

Devices do not talk directly to dashboards. They talk to platforms.

An IoT platform manages devices.
Authenticates them.
Stores data.
Provides APIs.
Handles scale.

This is where students should learn about device identities, data ingestion, databases, and analytics pipelines.

This is also where they start to understand why platforms like FAVORIOT exist in the first place.

Not to replace learning.
But to enable it.

Layer 4: Analytics and Visualisation

Dashboards are not the end goal.

They are the beginning of understanding.

Students should learn how data evolves from descriptive charts to deeper insights.
They should see patterns.
Spot anomalies.
Ask better questions.

This prepares them for real projects, not demos.

Security Must Exist Across All Layers

Security cannot be an afterthought.

Devices must be authenticated.
Data must be encrypted.
Platforms must be protected.
Applications must be hardened.

Most labs barely touch this.

And yet, this is where real systems fail.

When Systems Break, Knowledge Is Tested

I often tell students this.

The real test of IoT knowledge is not when everything works.

It is when something breaks.

Data stops arriving.
Dashboards go blank.
Alerts do not trigger.

At that moment, students panic if they only know how to code LEDs.

But students who understand layers start asking better questions.

Is it the device?
Is it the network?
Is it the platform?
Is it the visualisation?

This is the mindset a real IoT Lab must build.

Research, AI, and the Future of IoT Labs

Universities are not just about projects. They are about research.

To do meaningful research, students need data. Lots of it. Clean data. Continuous data.

IoT Labs enable this.

Once data flows reliably, students can apply machine learning.
They can explore pattern recognition.
They can experiment with predictive models.

Today, this also means understanding edge AI.

Inference running on devices.
Decisions made locally.
Latency reduced.
Systems are becoming smarter as they operate.

This is where IoT Labs naturally evolve into AIoT Labs.

And this is where universities must go.

This Is a Call to Universities, Lecturers, and Policymakers

If we want graduates who can build real systems, not just academic projects, we must change how we teach IoT.

IoT Labs must move beyond embedded programming.
They must teach architecture, trade-offs, and responsibility.
They must reflect how systems are deployed outside campus walls.

I believe universities can do this.
I believe lecturers want this.
I believe students deserve this.

But it requires intention.

It requires investment.
It requires collaboration with the industry.
It requires courage to redesign labs that have been unchanged for years.

If you are a lecturer, start asking what your lab is missing.
If you are a dean, ask whether your graduates can troubleshoot real systems.
If you are a policymaker, ask whether our talent pipeline matches national ambitions.

And if you are a student reading this, ask yourself one question.

Am I learning how to build a device… or how to build a system people can trust?

I would love to hear your thoughts, experiences, and struggles in building or teaching IoT.
Drop a comment. Let’s talk.

Smart Cities in Malaysia – Between Beautiful Documents and Real Implementation

There is a kind of silence I remember very clearly.

Not the silence of an empty room.
But the silence appears when too many slides are shown, too many big words are used, and too few honest questions are asked.

I was sitting in yet another Smart City presentation. Everyone was talking about master plans, KPIs, ISO standards, indicators, and rankings. The slides looked polished. The diagrams were neat. The language sounded confident.

Yet inside, a quiet question kept repeating.

Who will take care of this after the launch?
Who will wake up when the system fails?
Who will face the public when citizens are angry?

Those questions rarely appear on slides.

And that, for me, is where the real Smart City problem in Malaysia begins.

Why We Talk About Smart Cities at All

Smart Cities are not about technology.

They are about people.

They are about parents stuck in traffic every morning.
Children breathe unhealthy air.
Small business owners suffer when flash floods arrive without warning.

I often say this, and I truly believe it.

The final goal of a Smart City is very simple.

People can live healthier lives.
People can live happier lives.
Cities can run without constant chaos.

That’s it.

Not rankings.
Not awards.
Not plaques on office walls.

Yet somewhere along the way, we lost that simplicity.

When Everyone Wants to Be “Smart”

Today, almost everyone wants the Smart City label. Some go further and call themselves “AI Cities”.

I usually smile when I hear that.

Which AI?
Where is the intelligence?
Or is it just a new signboard?

Many systems branded as AI are simply basic automation. This is not a technology problem. It is a misunderstanding.

What troubles me more is this.

Some cities work quietly, building systems that actually function, yet receive no recognition because they never submitted an application. Others receive recognition early simply because they know how to fill out forms.

That’s when we learn a hard truth.

Recognition does not always reflect maturity.

From 30,000 Feet to 3 Feet

To be fair, Malaysia does have a solid Smart City framework.

On paper, it makes sense.

At 30,000 feet, there is the national master plan.
At 3,000 feet, there are state-level blueprints.
At ground level, around 3 feet, there should be detailed action plans for local councils.

Everything looks structured.

But in reality, many councils are stuck somewhere in between.

Some are still writing plans.
Some are experimenting with pilot projects.
Very few are running systems consistently, day after day.

Not because they don’t care.
Not because they are lazy.

But because something fundamental is missing.

Delivery structure.

Command Centres That Feel Empty

I have visited many command centres.

The name sounds powerful. Command centre. It feels important.

But once inside, the scene is often the same.

CCTV screens.
Live video feeds.
A few officers are watching.

That’s all.

I quietly ask myself.

Where is the data integration?
Where is the analysis?
Where are the decisions driven by this data?

A command centre should be the brain of the city.

Not just its eyes.

Imagine traffic data, air quality, noise levels, parking systems, citizen complaints, legacy databases, all connected and analysed together.

First, we know what has happened.
Then, we understand why it happened.
Next, we anticipate what might happen.
Finally, we know what action to take.

This is where technology truly matters. Not to impress, but to guide decisions.

The Challenges We Rarely Admit

Since around 2015, I have seen the same issues repeat.

Budget That Is Never Enough

Local councils are not money-making machines.

They rely on limited revenue sources. Assessment taxes. Parking fees. Licenses.

With limited funds, choices become limited too.

Projects that generate revenue or reduce costs often get priority. Long-term social impact projects struggle to survive.

Risk-heavy concession models usually favour large companies with deep pockets. Smaller local players, often full of ideas and energy, get pushed aside.

Sometimes I ask myself quietly.

Do we really want local ecosystems to grow?
Or are we just choosing the easiest path?

Projects Without Guardians

This one hurts the most.

Many Smart City projects are launched with excitement. Press conferences. Posters. Promotional videos.

A year later, the system is silent.

No maintenance.
No monitoring.
No clear ownership.

The project becomes a white elephant.

Not because the technology failed.
But because no one was assigned to take care of it.

Skills Gap Is Real

Smart Cities demand new skills.

Data management.
IT infrastructure.
Commercial thinking.
Long-term contract handling.

Many council officers come from strong urban planning backgrounds. They are good at what they do.

But we cannot expect them to suddenly manage complex digital systems without proper support.

This is not an individual failure. It is a structural one.

Fragmented Governance

For solution providers, one simple question often becomes complicated.

Who should we speak to?

Without a clear focal point, discussions lose direction. Time is wasted. Trust slowly fades.

One Answer I Strongly Believe In

If there is one thing that matters most, it is not technology.

It is a Delivery Unit.

A dedicated team.
Given authority.
Given responsibility.
Given continuity.

This unit becomes the caretaker of the entire Smart City lifecycle.

From strategy.
To execution.
To daily operations.
For long-term maintenance.

When this unit exists, everything changes.

Communication becomes clear.
Ownership becomes visible.
Projects do not get abandoned.
Citizens start feeling real benefits.

Smart City stops being a document.
It becomes a service.

Why I Still Have Hope

I am not writing this out of frustration.

I am writing because I still believe.

I believe our local councils are capable.
I believe our local talent is strong.
I believe technology is just a tool, not the answer.

What we need is the courage to admit weaknesses and the wisdom to build the right structure.

Smart City is not a race.
It is a responsibility.

If we want public trust, we must start taking care of what we build.

And it begins with one honest question.

Who will make sure this city still works tomorrow morning?

If this piece made you pause and think, I would love to hear your thoughts.
Leave a comment. Let’s talk.