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.

A Letter to My Future Self

Dear Mazlan,

As you sit in your grand office atop the towering Favoriot Building, overlooking a city that once seemed like a distant dream, I hope you take a moment to pause.

Yes, you’ve made it.

The name “Favoriot” shines not just on that magnificent skyscraper but across 25 countries, each with its own bustling branch, and the crown jewel—IoT Campus—where the next generation of innovators walks the halls, inspired by a journey that started long before the world knew your name.

But Mazlan, I’m writing this to remind you: don’t forget where it all began.

Remember that tiny office in IOI Business Park—not exactly glamorous, was it? Small desks crammed into a space barely big enough to contain our ambitions, let alone our team. The whiteboard stained with faded markers, the flickering fluorescent lights, and the cheap coffee that fueled countless late nights. It wasn’t luxury, but it was ours.

Remember the struggles during COVID-19—those dark days when uncertainty knocked louder than opportunity. The world paused, but you couldn’t. The team—our team—sacrificed so much. They showed up, not just physically but with heart, even when fear lingered in every breath. There were days when morale dipped, cash flow threatened to suffocate us, and hope felt like a fragile thread. But we clung to it.

Do you recall the pain of landing our first customer? How many times did we pitch—a hundred? A thousand? Rejections stacked higher than the proposals we printed. Investors smiled politely, nodding through presentations, only to pass us by. They didn’t believe in Favoriot. But we did.

Remember the feeling after every rejection? That hollow ache in your chest, the self-doubt whispering, “Maybe they’re right.” But you didn’t let it win. You went back to the drawing board, reworked the slides, tweaked the demos, and pitched again. Not because you were fearless—you were terrified. But because giving up was never an option.

Now, as you sit surrounded by accolades, global partnerships, and a team that’s grown beyond your wildest dreams, stay humble.

Never forget the people who stood by you when Favoriot was nothing more than an idea scribbled on paper. The team who accepted cut salaries during Covid, who believed in the vision even when the bank account said otherwise. The friends who listened to your endless rants about IoT, investors, and cash flow. The mentors who gave advice for free because they believed in you more than you believed in yourself.

Success has a way of making the past feel distant, almost like it happened to someone else. Don’t let it.

Walk the halls of IoT Campus and remember that it’s built on the sweat, tears, and sacrifices of people who dared to dream with you. Visit the small office at IOI Business Park whenever you can. Stand there. Let the memories wash over you—not to romanticize the struggle but to honor it.

And when you speak to young entrepreneurs, don’t just tell them about the success. Tell them about the sleepless nights, the empty bank accounts, the rejections, the fear. That’s where the real story lives.

Be proud, Mazlan. But more importantly, be grateful.

With all my heart,

Your Past Self

(Back when Favoriot was just a name, not an empire)

5 Lessons I Learned About Writing (The Hard Way)

When I started writing, I was like an overexcited kid given the keys to a candy store—brimming with enthusiasm but absolutely clueless about what I was doing. I devoured every piece of writing advice I could find, hoping to fast-track my journey to becoming a better writer.

Some tips helped, sure, but a lot of it? Pure noise.

Looking back, I realize I could’ve saved myself from much frustration if I had learned these lessons sooner. But that’s the beauty of growth—you stumble, fall, and eventually figure things out.

I discovered five hard-earned lessons through trial and error and a fair share of facepalms.

1. Write Often, But Fix Your Mistakes

When I first dipped my toes into the writing world, I kept hearing this mantra: “Just write as much as you can. Quantity over quality.” So, I did precisely that. I wrote. A lot. Blog posts, social media updates, random thoughts jotted in the middle of the night—you name it.

But here’s the catch: I wasn’t getting any better.

“Why isn’t this working? I’m writing so much, but nothing feels right.”

One day, curiosity (or maybe self-torture) made me reread my older pieces. I cringed. I mean, really cringed. My sentences felt awkward, and my ideas scattered like puzzle pieces from different boxes. That’s when the lightbulb flickered on. Writing isn’t just about pouring words onto a page; it’s about learning from those words.

Now, I treat writing like a conversation with my past self. I write, but I also pause, reread, and reflect. I ask, “What was I trying to say here? Could I say it better?” Mistakes? Oh, they’re inevitable. But fixing them? That’s where growth lives.

2. Read What Interests You, Not Just to Impress Others

There was a phase when I believed that I needed to read everything under the sun to be a great writer. Self-help books I didn’t care for? Check. Academic articles that felt like decoding alien scripts? Double-check.

But guess what? None of it stuck.

“Am I even absorbing any of this? Or just pretending to?”

I was reading to tick boxes, not to learn. I’d skim through articles, drop a “Great piece!” comment, and move on—thinking I was building connections. Spoiler alert: I wasn’t.

Eventually, I realized that meaningful reading comes from genuine curiosity. Now, I read what sparks my interest. Whether it’s a thought-provoking essay, an IoT case study, or even a quirky poem, I take my time. I underline sentences, jot down notes, and let the words marinate.

Reading this way doesn’t just fill my brain; it fuels my writing.

3. Comment Like You Mean It

Ah, the “comment-for-engagement” strategy. Been there, done that.

In the early days, I thought leaving many comments would make me visible. So, I plastered generic lines like, “Nice post!” or “Interesting thoughts!” across articles.

But here’s the thing—writers can smell insincerity from a mile away.

“Why isn’t anyone responding to my comments? Aren’t I engaging enough?”

One day, I received a heartfelt comment on one of my posts. It wasn’t long, but it was thoughtful. The reader shared how my words resonated with their experience. That comment? It stayed with me.

I realized genuine connections aren’t built on autopilot responses. Now, when I comment, I pause. “Did something in the article make me think differently? Did it remind me of a personal story?” I share that. Authenticity might not flood your notifications, but it builds lasting bridges.

4. Don’t Play the Follow-for-Follow Game

Ah, the seductive trap of the “follow-for-follow” game. In my eagerness to grow my audience, I followed anyone and everyone, thinking they’d return the favour. For a while, it worked. My follower count climbed, but my engagement? Crickets.

“Why do I have so many followers but no real interactions?”

I had an audience, but not a community.

One day, it hit me: “Why am I following people whose work doesn’t inspire me? Why am I chasing numbers instead of connections?”

So, I hit the reset button. I started following writers whose words I genuinely enjoyed and whose thoughts challenged me. The growth became slower, but it felt real. When someone follows me today, I know it’s because they value my voice, not because of an unspoken social contract.

5. Write When You Have Something to Say

“Write every day, no matter what.”

I took that advice to heart. Even on days when inspiration was as dry as the Sahara, I forced myself to write. The result? Words that felt forced, soulless, and frankly, forgettable.

“Why does my writing feel empty even though I’m consistent?”

Then I had an epiphany: Writing isn’t just about writing. It’s about sharing—sharing an idea, a lesson, or a story that matters—even if it’s just for you.

Now, I write when something stirs within me. It could be a fleeting thought, a conversation, or an article that sparked an idea. Writing from that place? It flows. It feels alive. And more often than not, it resonates with readers.

Final Thoughts

Writing isn’t a race. It’s a journey filled with detours, pit stops, and occasional breakdowns.

I’ve stumbled, cringed at my past mistakes, and learned lessons the hard way, but each misstep has shaped my growth.

If you’re starting your writing journey, here’s my two cents: Don’t chase perfection. “Chase authenticity.” Write, reflect, connect genuinely, and let your voice evolve.

After all, the most powerful stories aren’t the ones polished to perfection—they’re the ones that come from the heart.

A Usual Day in My Life: From Dawn to Dusk

I often reflect on what my usual day looks like—not one where everything is extraordinary, but one that feels fulfilling and balanced and leaves me content as I drift off to sleep. Here’s a glimpse into my day, from dawn to dusk.

5:00 AM – The Quiet Hour

My day starts before the sun peeks over the horizon. No alarm is needed—my internal clock knows when it’s time. There’s something special about these early hours. The house is still, the world outside is hushed, and it’s just me, my thoughts, and the gentle whisper of dawn.

I sit on the prayer mat at Surau nearby, grounding myself with Subuh. It’s a moment of reflection, gratitude, and connection. After prayers, I take a few quiet minutes, no phone or emails, just pure stillness.

6:00 AM – Morning Rituals

I ease into the morning with light stretches, sometimes a brisk walk if the weather allows, or simple exercises at home. It’s not about intensity but about shaking off sleep and clearly welcoming the day.

Breakfast follows—a simple, healthy meal. Maybe oats, eggs, and, of course, a cup of tea. That first sip feels like a handshake with the day, setting the tone for what’s ahead.

7:00 AM – Diving into Work

Before emails flood and meetings take over, I carve out sacred writing time. My mind feels sharpest now. I open my laptop, fingers poised over the keyboard, and let the words flow—whether it’s a blog on IoT or entrepreneurship.

Writing is more than sharing ideas; it’s a conversation with myself. Sometimes, I start with a question like, “Why do people give up on writing?” and soon find myself deep in thought, discovering new perspectives.

9:00 AM – The IoT Hustle Begins

Now, it’s full-throttle Favoriot mode. I have meetings with the team, brainstorming sessions, and partner calls—a mix of strategic discussions and problem-solving. Some days, I present IoT solutions to clients, explaining how we can transform smart agriculture or address energy challenges.

I enjoy watching ideas evolve into tangible impacts. Not every meeting is a revelation, but each is a step forward.

12:30 PM – The Midday Pause

Lunch is more than a meal; it’s a mental reset. Sometimes with the team, sharing stories beyond work, or alone with a plate of nasi campur, lost in thought or scrolling through Medium for inspiration.

A brief walk post-lunch helps shake off sluggishness and recharges my focus.

2:00 PM – The Afternoon Grind

Afternoons are for deep work. Strategic planning or preparing presentations —tasks that need full attention. I tackle emails too, managing the endless flow without letting it overwhelm me.

Inspiration can strike anytime. A quirky TikTok idea, an analogy for an article—I jot them down quickly because ideas are fleeting, like mischievous cats.

5:00 PM – Wrapping Up

I review my day before logging off. What did I achieve? What could’ve gone better? There is no formal checklist, just a mental debrief. Planning tomorrow’s priorities helps me mentally clock out, knowing everything’s noted.

A deep breath signals the day’s end, a small ritual before stepping away from work.

6:30 PM – Family & Personal Time

Evenings are for family. We share stories, laugh, watch shows, or simply enjoy each other’s company. These moments remind me of the bigger picture.

I remember the days when I might strum my guitar, revisit old Bee Gees tunes, and let the music reconnect me with simpler times. But unfortunately, there’s no more guitar with me.

9:00 PM – The Wind Down

Before bed, I read—an article, a book, or just a reflection on the day. I try to avoid screens, but curiosity sometimes wins, leading me down YouTube rabbit holes of obscure tech facts.

I jot down lingering thoughts—fragments, ideas, and reflections.

10:00 PM – Lights Out

Lying in bed, I flip through the day’s snapshots in my mind: the laughter, the challenges, the small victories. I whisper a prayer of gratitude, close my eyes, and let sleep take over, ready to greet another day.

And that’s my usual day—not perfect, but perfectly mine.