How Network Management Turned Me Into a Project Manager: Victor Omoti's Journery
When I started working as a Network Manager, I understood the role in fairly straightforward terms: keeping weather stations operational, ensuring data is flowing, and supporting field teams to carry out installations and maintenance effectively. Four years into this role, I now see it as something much broader, something that sits at the intersection of people, systems, and processes, and naturally evolves into project management work, whether or not that is the formal title.
My work has placed me between multiple groups within the organization. On one side are the field teams responsible for installing and maintaining weather stations. On another are the IT teams developing the systems that support operations. Then there is management, which needs visibility into performance, risks, and strategic priorities. Beyond the organization itself are clients, partners, suppliers, and stakeholders, each with their own expectations and objectives.
Over time, this has drawn me into the design and improvement of workflows that connect these different parts. One area where this becomes very real is in weather station maintenance operations. A technician completing a task in the field is not just finishing a job, it is an event that needs to be reflected across multiple systems. It should update asset inventories, trigger reporting systems, and be visible on dashboards used for decision-making. Ensuring that this flow works seamlessly requires thinking beyond individual tasks and focusing instead on how systems communicate with each other.
This is where my involvement has grown, especially in supporting how maintenance applications are designed for field technicians and how these tools connect to broader systems such as reporting platforms, asset tracking, and operational dashboards. What I have learned through this process is that effective systems are not defined only by their technical architecture, but by how well they match the real working patterns of the people using them. The challenge is always in bridging that space between design and reality.
A similar experience has come through working on QA/QC processes. In a distributed network, data quality cannot depend entirely on manual review. It needs to be supported by systems that can detect issues early, trigger alerts, and ensure that the right people receive the right information at the right time. Over time, I have been involved in shaping workflows that embed this logic directly into operations. Instead of QA/QC being a separate step, it becomes part of the system itself, continuously running in the background, ensuring reliability and consistency.
Beyond system design, there is also a strong logistics and coordination dimension to the role. Managing a network that spans multiple countries means following equipment from procurement, through shipment and customs, to final delivery and installation in the field. Each stage depends on the other, and visibility across the entire chain becomes essential. This experience has strengthened my understanding of end-to-end project coordination and the importance of ensuring that information flows as effectively as physical equipment.
Another important dimension has been working with clients and partners. These interactions have shown me that every collaboration begins with understanding. Different organizations come with different needs, constraints, and expectations, and the first step is always to listen and understand what they are really trying to achieve. From there, it becomes possible to identify where there is alignment and how systems or solutions can be shaped to meet shared goals. Some of the most effective outcomes have come from this kind of mutual understanding rather than predefined solutions.
Looking at all of this together, I have come to realize that much of my work naturally aligns with project management, even when it is not formally labeled that way. It involves coordinating across teams, shaping workflows, supporting system development, managing deployments, and ensuring that different components of the organization work together effectively. It is less about a title and more about a function bringing clarity, structure, and coordination to complex, interconnected work.
What started as a focus on managing a network has become a deeper understanding of how systems are built and sustained. It has shown me that the most effective work happens when people, processes, and tools are aligned in a way that reflects real-world operations. In that space between design and execution, project management naturally emerges as the work of making everything fit together.
