Category: Thought Leadership

Social Media, Business, and the Invisible War Every Founder Must Learn to Fight

Long before I became a founder, I was already experimenting with social media, not because it was fashionable, not because someone told me personal branding would become important, and not because I had a grand strategy written neatly inside a notebook, but because I could sense that these platforms were quietly changing the way people discovered ideas, trusted experts, followed companies, and made decisions.

It started with Twitter, then Facebook came along, followed by YouTube, LinkedIn, Instagram, and later TikTok and Threads, and with every new platform I joined, I found myself learning the same painful but useful lesson: every platform has its own behaviour, its own audience, its own rhythm, and its own strange way of rewarding or punishing your content.

There were no formal classes for me, no coach sitting beside me, no step-by-step manual that said, “Mazlan, this is exactly how you should build your voice online.” I learned the old-fashioned way by reading, testing, failing, adjusting, and trying again, which sounds noble now, but at that time, it was mostly trial and error with a lot of silent head-scratching in between.

When FAVORIOT started to grow, social media was no longer just a personal space where I shared thoughts, opinions, and reflections. It became part of the business itself, and suddenly I was not only speaking as Mazlan Abbas, the person, but also carrying the voice of FAVORIOT, the company, the brand, the team, and the mission we were trying to build.

That was when things became complicated.

I thought to myself, “So now I have to be myself, represent the company, educate the market, promote the product, build trust, and still sound human at the same time?”

Yes, apparently.

And I had to do all of that while running a startup.

When Social Media Starts Feeling Like a Battlefield

At one point, managing social media felt like being a soldier defending too many frontlines at the same time, because LinkedIn wanted professional insights, Facebook preferred a more personal tone, X rewarded sharp and quick comments, TikTok demanded visual storytelling, Threads wanted casual conversations, Instagram needed strong visuals, and YouTube required patience, planning, and a completely different level of commitment.

Every platform seemed to ask for something different, yet all of them demanded the same thing from me: time, attention, consistency, and energy.

The difficult part was not just posting. Anyone can post. The real challenge was knowing what to say, how to say it, where to say it, and which version of myself should be speaking.

For my personal account, people followed me because they wanted my thoughts, my stories, my experiences, and my reflections. They wanted to see the human side of the founder, not a walking advertisement. For the FAVORIOT account, the expectations were different because the company needed to sound clear, professional, relevant, and trustworthy to customers, partners, developers, investors, universities, and the wider IoT community.

That was where the first real problem appeared: mixed messaging.

The Fine Line Between Personal Voice and Company Voice

The line between a founder and the company can become blurry, especially in a startup where the founder’s face, voice, reputation, and personality are often tied closely to the brand, and while this can be powerful, it can also create confusion if we are not careful.

Whenever I posted too much business content on my personal account, engagement usually dropped because people did not follow me just to receive product updates. They followed me because they wanted perspective, stories, lessons, observations, and sometimes a little honesty about what it really feels like to build something from the ground up.

At the same time, if the company account became too personal, it risked weakening the professional image of the brand, because a company page must serve a different purpose. It must help customers understand what the company does, why it matters, how it solves problems, and why people should trust it.

This was not just a technical content issue. It was an identity issue.

Before pressing publish, I often had to ask myself, “Am I speaking as Mazlan, or am I speaking as FAVORIOT?”

That small question became very important, because personal branding and company branding may support each other, but they should not become the same thing. A personal account earns attention through authenticity, while a company account earns trust through clarity.

“Your personal account earns attention through authenticity. Your company account earns trust through clarity.”

It took me years to truly understand that, and even now, I still remind myself of it whenever I prepare content for different platforms.

The Hardest Battle Is Still Time

If anyone asks me what the biggest challenge is in managing social media as a founder, my answer is very simple: time.

Many people assume content creation means typing a few lines, adding a nice image, and clicking publish, but anyone who has done it seriously knows that one good post can involve research, choosing the right angle, writing the hook, shaping the message, checking the tone, preparing visuals, proofreading, deciding where to post, adjusting the format for each platform, and then monitoring the response after it goes live.

Now multiply that by several platforms.

Then multiply it again by two accounts, one personal and one company.

Then add meetings, proposals, customer follow-ups, speaking engagements, product discussions, investor conversations, staff matters, and the never-ending demands of running a startup.

That is when social media stops looking like a simple marketing activity and starts feeling like another full-time job quietly hiding inside your actual full-time job.

There were moments when I honestly felt like shutting everything down and focusing only on the “real work,” but each time that thought appeared, another thought answered it almost immediately.

“But this is part of the real work now.”

That is the reality for founders today, because social media is no longer optional if you want people to discover you, understand you, evaluate your credibility, and eventually trust you enough to have a serious conversation.

A startup can have a good product, a committed team, and a powerful vision, but if nobody sees it, hears about it, or understands it, the market may assume that nothing much is happening.

And that is dangerous.

Doing Everything Alone Can Drain You Quietly

For a long time, I handled most of the social media work by myself, which meant writing, editing, posting, choosing angles, creating variations, checking responses, replying to comments, and thinking about how to balance the personal voice with the company voice.

From the outside, people only see the final post, but they do not see the hesitation behind it, the drafts that never get published, the captions that are rewritten five times, the posts that are deleted because they do not feel right, or the late-night moment when you stare at the screen and wonder whether the message is useful or just noise.

Founders know this feeling very well.

We are not only building products. We are also building trust, visibility, confidence, and a story that the market can understand.

Many times, we do this with limited people, limited budget, limited time, and limited emotional energy, yet social media continues to demand freshness, consistency, and relevance as if we have a large content department hiding somewhere inside the company.

I thought to myself, “If people knew how much effort goes into one simple post, maybe they would forgive me for occasionally disappearing.”

But the market rarely forgives silence for too long.

If you disappear, people forget.

If you only appear when you want to sell, people resist.

If you post without direction, people get confused.

That is why founders need not only content, but also a system.

Then AI Changed the Way I Work

When AI tools like ChatGPT arrived, my content process changed in a major way, not because AI replaced my thinking or my voice, but because it helped me organise what I already had inside years of writing, speaking, presenting, and explaining.

Before AI, I wrote almost everything from scratch, and that meant every post felt like a new battle with a blank page. Now, I can start from existing material: old blog posts, keynote notes, training slides, customer questions, proposal ideas, or reflections from past experiences.

Over the years, I had written many articles on IoT World and my personal blog, and those articles were filled with experience, analysis, stories, opinions, and lessons that were still relevant. What I did not fully realise before was that all of that content was not old material. It was a content bank waiting to be reused.

A single blog article can now become several Threads posts, a polished LinkedIn article, a casual Facebook update, a short video script, a newsletter idea, or even a talking point for a presentation. The main idea remains the same, but the structure, tone, and length can be adjusted for each platform.

That saved me a lot of time.

More importantly, it reduced the pressure of always creating from zero.

I thought to myself, “Why should I keep starting from an empty page when I already have years of thoughts sitting quietly in my blog?”

That was a turning point.

AI gave me a better rhythm, but it did not remove my responsibility. I still had to decide what mattered, what should be published, what should be edited, what should be removed, and whether the final content sounded like me.

AI can help shape the clay, but the clay must still come from real experience.

“AI should not replace your voice. It should help your voice travel further.”

That is how I see it, because the danger is not in using AI, but in allowing AI to make us sound like everyone else.

Your Old Content May Be More Valuable Than You Think

Many founders underestimate the value of what they already have, because they assume content must always be new, fresh, and created from scratch, when in reality, some of the best content comes from old ideas explained in a clearer and more current way.

Old blog articles can become new social media posts.

Past presentation slides can become short educational content.

Customer questions can become articles.

Training notes can become carousels.

Proposal explanations can become LinkedIn posts.

Mistakes can become lessons.

Founder reflections can become trust-building stories.

Even a simple WhatsApp explanation to a customer can become the seed of a good post, because if one person asked that question, many others may be thinking about the same thing silently.

The key is to stop looking at content as a one-time activity.

Content should be treated like an asset.

You create it once, then reshape it, reuse it, update it, and distribute it in different ways depending on the platform and audience.

This is where AI becomes useful, because it can help turn raw material into different formats quickly, but the source must still be yours. Your voice, your judgement, your stories, and your understanding of the audience cannot be outsourced completely.

AI can help you move faster, but it should not make you disappear from your own content.

Lessons I Learned From Managing Personal and Business Accounts

After many years of managing both personal and company social media accounts, I have learned that clarity is more important than volume.

The first lesson is to separate the purpose of each account. Your personal account should carry your stories, reflections, opinions, values, and human experiences, while your company account should focus on customer problems, product value, use cases, industry education, credibility, and business outcomes.

The second lesson is to build a content bank before you need it. Do not wait until you are tired, busy, or under pressure before thinking about what to post, because that is when content becomes stressful. Save ideas continuously, collect useful questions, keep links to your old articles, and record your best explanations when they appear naturally.

The third lesson is to use AI as an assistant, not as a replacement. Let it help with structure, tone, rewriting, repurposing, and idea expansion, but never surrender your judgement, because AI may produce words, but only you know whether those words carry the right meaning for your audience.

The fourth lesson is to master one or two platforms first instead of trying to be everywhere at the same time. Many founders try to appear on every platform and end up weak on all of them, when they should first understand where their audience spends time and what kind of content works best there.

The fifth lesson is to respect the character of each platform. LinkedIn is suitable for professional insights and deeper reflections, Facebook allows a more personal touch, Threads feels more conversational, TikTok needs visual storytelling, and YouTube rewards those who can explain ideas with patience and consistency.

The sixth lesson is to measure what matters. Likes and views are pleasant, but meaningful comments, direct messages, serious enquiries, partnership discussions, speaking invitations, and sales leads are much better signals that your content is creating real value.

The seventh lesson is to accept that consistency matters more than perfection. A steady flow of useful and honest content is more powerful than one perfect post every few months, because people trust those who show up repeatedly with something worth saying.

Social Media Is a Marathon, Not a Firework Show

Social media is not a one-week campaign, a single viral post, or a magic trick that suddenly turns a quiet startup into a famous brand overnight. It is a long game of showing up, learning from your audience, improving your message, and staying visible without becoming a slave to the algorithm.

Some posts will perform well.

Some will disappear quietly.

Some will attract customers.

Some will attract critics.

Some will open doors you never expected.

Some will teach you what your audience truly cares about.

That is part of the process.

The founders who survive social media are not always the loudest or the most polished. Many times, they are the ones who know how to pace themselves, reuse their content wisely, protect their energy, stay clear about their message, and keep showing up even when the response is not immediate.

After all these years, I am still learning.

I am still experimenting.

I am still adjusting.

But now, with AI beside me, I no longer see social media as a monster waiting to eat my time. I see it as a set of channels that can carry my thoughts, my work, and FAVORIOT’s story to the people who need to hear it.

Not perfectly.

But consistently.

And for a founder, consistency is already a very big win.

So let me ask you this.

Are you managing your personal and business social media accounts on your own, or do you already have a team helping you? What has been your biggest challenge so far?

Share your experience in the comments.

Source based on the uploaded text.

Founder’s Weekend Notes – Why Entrepreneurs Work on Weekends and Stop Apologising for It

My Weekend Has No Off Button
Founder’s Weekend Notes

My Weekend Has No Off Button

And I have stopped apologising for it.

By Dr. Mazlan Abbas · Reflections on founders, focus, writing, and FAVORIOT
© Dr. Mazlan Abbas · Founder reflections · FAVORIOT · IoT · AIoT · Writing · Strategy

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.

The Day I Realised I Was Becoming a Human FAQ

There was a time when I actually felt proud every time someone asked me about Favoriot.

Each question felt like a small victory.

It meant people were noticing.
It meant the story was spreading.
It meant our work was reaching somewhere beyond our small team.

Someone would message me.

“What exactly is Favoriot?”
“Is it just a dashboard?”
“Can it connect to this device?”
“How is it different from AWS IoT or ThingsBoard?”
“Do you support AI?”
“Can students use it?”
“Is it for smart cities, or factories, or farms?”

And every time, I replied.

Patiently.

Sometimes through WhatsApp.
Sometimes through LinkedIn messages.
Sometimes through emails that arrived late at night.

Okay, Mazlan… this is good, I told myself.
It means people are interested.

So I kept answering.

Again.

And again.

And again.

Until one day, after probably the hundredth explanation, I suddenly paused.

I stared at my laptop.

Then I asked myself a question that hit me harder than I expected.

Wait… am I building a technology platform… or am I becoming a human FAQ?

That was the moment something clicked.

A small but powerful realisation.

This was not really about repeating answers.

It was about something deeper.

Energy.

Focus.

And scale.

Because if the story of Favoriot only lives inside my head, then every explanation will depend on me personally.

And that is not scalable.

That night, I realised something important.

When people keep asking the same question, it is not a problem.

It is a signal.

A signal that your story is not documented clearly enough.

A signal that your knowledge is trapped inside conversations.

A signal that your platform needs a voice that can speak even when you are asleep.

That was my first aha moment.

The Emotional Side of Repeating Yourself

Let me be honest.

There were moments when I felt tired.

Not angry.

Not irritated.

Just mentally drained.

Imagine explaining the same thing dozens of times.

Sometimes, even after giving a talk or presentation.

For example, after speaking at events like The Star Cybersecurity Summit, where I was invited to share thoughts about IoT systems, AI, and the future of connected technologies, people would still approach me afterwards and ask the exact same question.

“So… what exactly does Favoriot do?”

Part of me almost laughed.

Did I not just explain that on stage for half an hour?

Then another voice in my head replied.

Relax Mazlan. Every audience is new.

Every listener hears things differently.

Every person arrives with a different level of understanding.

Some are engineers.

Some are students.

Some are policymakers.

Some are just curious.

And none of them is wrong for asking.

That was my second realisation.

Repetition is not the enemy.

Confusion is.

If people keep asking the same question, it simply means the explanation has not reached them in a form they can digest.

And that responsibility sits on my shoulders.

The Turning Point

One evening, while replying to yet another email asking the familiar question, I suddenly stopped typing.

I leaned back in my chair.

Why am I answering this privately again?

Then another thought appeared.

Why not answer it publicly once… and let it help hundreds of people instead of one?

That thought changed everything.

Instead of seeing repeated questions as interruptions, I began seeing them as content ideas.

Every repeated question was actually a signal about what people wanted to understand.

If five people ask the same thing, it deserves an article.

If ten people misunderstand a feature, it deserves a tutorial.

If customers keep comparing Favoriot with other platforms, it deserves a structured explanation.

That was the moment I started writing more seriously on IoT World.

Not random thoughts.

Not marketing slogans.

But clear explanations.

What exactly is the Favoriot Insight Framework?

How Favoriot moves from raw data to meaningful decisions.

Why IoT is not just about dashboards.

How universities can build AIoT labs.

Why local councils struggle with smart city projects.

How system integrators can deploy IoT faster.

Each question became an article.

Each doubt became a story.

Each confusion became clarity.

And slowly, something magical happened.

Instead of repeating myself endlessly, I started sending links.

“You might want to read this article.”
“This explains the architecture clearly.”
“This post shows the use case.”

The conversation immediately became deeper.

People no longer start from zero.

They started with understanding.

Building Something Bigger Than Myself

But something else happened, too.

After publishing several articles, people began asking another question.

“Is there one place where we can read everything about Favoriot?”

I smiled when I heard that.

Alright, Mazlan… now the next step is obvious.

That was when the idea of a Favoriot Resources Page was born.

Not a marketing page.

Not a product brochure.

But a knowledge hub.

A place where people can explore the ecosystem properly.

A place where they can learn at their own pace.

On that page, anyone can now explore:

What Favoriot really is
Tutorials and technical guides
Real IoT project challenges
Case studies and architecture explanations
The Favoriot Insight Framework
AI and IoT integration concepts
Videos and learning materials

I wanted it to feel like a digital campus.

Because Favoriot is not just software.

It is an ecosystem.

And ecosystems require structure.

They require stories.

They require documentation.

Without those elements, people only see fragments.

With them, people see the full picture.

The Hidden Lesson for Founders

Many startups face this same challenge.

We assume people understand our product.

We assume our website is clear.

We assume our explanation is good enough.

Most of the time, it is not.

People are busy.

They skim.

They scan.

They make assumptions.

And sometimes those assumptions are completely wrong.

So when people keep asking the same question, the worst reaction is frustration.

The better reaction is curiosity.

Ask yourself:

Why is this still confusing?

Which part of my explanation is missing?

How can I make this easier to understand?

Repeated questions are feedback.

Free feedback.

Valuable feedback.

And if you listen carefully, they tell you exactly what your audience needs.

When the Story Finally Clicked

After writing consistently and building the Resource page, I noticed something interesting.

My explanations became sharper.

Writing forces you to think clearly.

When you write publicly, your ideas become structured.

And suddenly the narrative becomes easier to communicate.

People begin to see the bigger picture.

They understand that Favoriot is not just a tool.

It is a framework.

It is an ecosystem.

It is a learning platform.

It is an AIoT foundation.

Without structure, that sounds confusing.

With structure, it becomes powerful.

The Resource page helped me connect the dots.

From devices to cloud ingestion.

From data streams to analytics.

From rule engines to AI insights.

From dashboards to decision intelligence.

That clarity changed everything.

The Unexpected Reward

Today, people still ask questions.

Of course they do.

And I welcome them.

But the feeling is different now.

Instead of feeling drained, I feel grateful.

Because each question tells me that someone is curious.

Someone is exploring.

Someone wants to understand.

And now I have something meaningful to share.

Not just an answer.

A pathway.

When someone tells me,

“I read your Resource page, and now I understand what Favoriot is.”

That feels incredibly satisfying.

More satisfying than closing a sale.

Because understanding builds trust.

Trust builds relationships.

And relationships build ecosystems.

The Aha Moment

Looking back, I now see that the repeated questions were never the problem.

They were actually guiding me.

They were telling me exactly what needed to be documented.

Exactly what was needed was clarity.

Exactly what was needed was storytelling.

And once I finally organised all that knowledge into structured content, something powerful happened.

The pressure disappeared.

The message became scalable.

And the story of Favoriot could travel further than my own voice.

That was my real aha moment.

When people stop depending on your explanation and start learning from your ideas, you know something meaningful has been built.

Favoriot is not just about connecting devices.

It is about connecting understanding.

And that journey started with a simple realisation.

Sometimes, the most annoying repeated questions are actually the best teachers.

Now I am curious.

Have you ever experienced the same situation in your own journey?

People asking the same question again and again?

What did you do about it?

Did it frustrate you, or did it push you to build something better?

FAVORIOT Resources

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.