Navigating IoT Projects: A Non-Techie’s Guide to Success

From the balanced view of Bianca Ionescu; our stellar PM.

In today’s era of digital transformation, the Internet of Things (IoT) stands as a powerful force, interconnecting devices and revolutionizing entire industries. As a project manager with limited technical expertise, I’ve had the privilege of overseeing a variety of IoT projects, encountering challenges and gleaning invaluable insights along the way. In this article, I’m excited to share my experiences and insights on navigating IoT projects from a non-technical standpoint.

About Me

My journey with Salt & Pepper spans 2.5 years of which 1.5 years have been particularly entwined with IoT projects. Sometimes, I think that these projects chose me, not the other way around because when I first encountered the term “IoT,” it might as well have been Martian to me (along with most other tech jargon). Yet here I am today, writing an article I hope will serve as a beacon for others embarking on similar journeys.Now, let’s shift the focus away from me and delve into the heart of the matter: the projects themselves.

About the Projects

• Web app based on a platform device that provides a variety of vital signs & biodata in a continuous and contactless manner
• Companion app for a wearable device that delivers holistic data to minimize the risks of long periods of uninterrupted screen use
• Companion app for a smart docking station that aims to create healthy smartphone habits
• Mobile companion app, which enables fast interaction with the Embr’s Wave® wristband that delivers precisely engineered cooling or warming waves for instant thermal relief and comfort. (read more about it here)

Timing is Everything

In IoT systems, the integration of software, hardware, and firmware components is intricate and interdependent. Even the slightest change to one component can reverberate across the entire system, requiring meticulous coordination to maintain compatibility and functionality. Amidst fixed-price projects, this coordination game reaches a whole new level.

In my journey, we at Salt and Pepper tackled the software component while hardware and firmware were handled on the client side. You might think it’s a breeze: start coding and everything magically falls into place. But, as we all know, reality rarely plays out like a fairy tale. Understanding this, I relied heavily on good old communication, coordination, and teamwork simple yet powerful tools to keep things transparent and make sure everyone was aligned in reaching the same goal.

Understanding Tools & Technologies

My tech knowledge was close to 0 back in the day. I often found myself scratching my head over unfamiliar jargon, tools, or technologies, and wrapping my head around risk management felt like a scary task. My lack of tech know-how made me doubt myself and my ability to navigate this world of projects.

But here’s the silver lining: over time, patterns emerged from the tech discussions, and I found myself connecting the dots. Moreover, I learned to lean on my team’s expertise, realizing I don’t need to navigate the labyrinth of IoT tools and technologies solo. The cumulative knowledge of the team and business acumen makes us confident to tackle new challenges together. I’ve also found myself becoming somewhat of an expert.

Communication is Key

Apparently it takes repeating something five times for it to truly sink in. Why? Because we often listen without truly absorbing information—a scenario exacerbated by assumptions. Countless times, we fall into assumption patterns when trying to solve a problem. We can’t fault our brain for how it’s hard wired but we can take a second before we indulge in old thinking patterns.

To counter this, I’ve tailored my communication to suit each audience and leveraged visual aids—Miro being a personal favorite—to enhance clarity. Additionally, I’ve learned never to mistake silence for comprehension,it never hurts to double check if it brings clarity. Let’s not adopt the “Silence is an answer too” mantra in our projects, okay? Unless we’re asking existential questions about our project plans, then silence might just mean we’ve confused everyone!

Agile, Kanban, Waterfall, or a Fusion?

IoT projects, with their intricate dependencies and evolving nature, pose a conundrum for traditional Agile methodologies. While I’m an ardent advocate of Agile, my experiences have prompted introspection:Does Agile truly align with the intricacies of IoT projects?

Among my listed projects, only one adhered strictly to Agile principles, while the others followed a hybrid Agile-Kanban approach. This adaptability, born from periodic reassessment and feedback solicitation, has proven pivotal. Gone are the days of blindly adhering to theoretical frameworks; instead, I prioritize adaptability, embracing change to drive project success.

I’ve learned to adapt and periodically check “the vibe”, instead of going on pilot mode. It’s important to be present in your project and admit when certain things are not working (theory and practice don’t always go hand in hand so mastering the art of adaptability is key).

Oh, and don’t forget to ask for feedback from your team or client! Sure, it’s a tip you’ve probably heard a million times before, but let’s face it: sometimes the classics are classics for a reason! As for me, it took a hot minute to embrace this approach—I was too busy trying to be the Agile poster child. But guess what? There’s no such thing as a perfect project, and thank goodness for that! Embrace the chaos, roll with the punches and lean into a problem solving mindset.

To sum up, handling IoT projects calls for a flexible, ever-evolving strategy that mixes tech smarts with clear communication, savvy planning, and a willingness to pivot when needed. Sure, it’s no walk in the park, but every bump in the road is a chance to learn and get better.