When One Role Covers Three Very Different Tools
I joined a small San Francisco-based tech startup at what I can only describe as organized chaos. The CEO was constantly generating new ideas, pivoting priorities, and spinning up initiatives faster than the team could document them. My job was straightforward on paper: keep the project management tools running, maintain internal documentation, and make sure stakeholders always had what they needed. In practice, it was three jobs in one.
The core asks were clear enough. Create and update project schedules in Excel, convert Visio diagrams into PDFs for stakeholder distribution, and maintain the company wiki with all internal documents and resources. Each task was manageable on its own. Together, under constant deadline pressure, they added up quickly.
Where Excel Project Schedules Get Complicated Fast
I started with the Excel project schedules. I know Excel reasonably well — formulas, conditional formatting, basic pivot tables. But the startup's project tracking needs were more layered than I expected. Multiple teams, overlapping timelines, dependencies that shifted week to week. Every time I updated one schedule, something downstream needed to change too.
I spent a significant amount of time trying to build a clean, scalable tracking system. The problem was not my Excel skills — it was that the structure itself needed to be designed thoughtfully from the ground up, with logic that could handle rapid changes without breaking. What I had built worked, but it was fragile. One team lead changing a milestone would throw off three other sheets.
Visio Diagrams and the PDF Conversion Problem
The Visio side was a different kind of challenge. The startup used Visio for process flow diagrams — system architecture, onboarding workflows, product decision trees. My job was to keep these updated and convert them into clean PDFs for stakeholders who did not have Visio installed.
The conversions themselves were not complicated, but the diagrams were. Some had outdated labels, overlapping shapes, and inconsistent formatting carried over from multiple contributors. Sending a messy diagram as a PDF to an external stakeholder was not an option. I cleaned what I could, but some of the more complex process diagrams needed a more experienced eye to restructure properly.
Keeping the Wiki Accurate When Everything Changes Daily
The company wiki was its own beast. It served as the single source of truth for internal documentation — policies, processes, tool guides, team contacts, project briefs. The problem was that no one had been maintaining it consistently before I came in. Pages were outdated, some were duplicated, and others referenced tools the company no longer used.
Organizing and rewriting wiki content while simultaneously managing live project schedules and Visio exports was stretching my bandwidth. Something had to give.
Bringing in the Right Support
After a few weeks of juggling all three workstreams alone, I reached out to Helion360. I explained the situation — the Excel scheduling system that needed a more robust structure, the process flow diagrams that needed to be cleaned up before PDF conversion, and the wiki overhaul that was falling behind. Their team understood the problem immediately and took over the parts that were creating the most friction.
Helion360 rebuilt the Excel-based project tracking structure with cleaner logic and cross-sheet dependencies that actually held up under frequent updates. They also redesigned several of the Visio process flow diagrams, making them consistent, properly labeled, and export-ready. That alone saved hours of back-and-forth with stakeholders.
What the Startup Actually Needed
Looking back, what the startup needed was not just someone to run tools — it needed someone to design systems that could scale with the pace of the company. The Excel schedules, the process diagrams, the wiki — all three needed to be built with intention, not just maintained reactively.
Once Helion360 delivered the restructured schedules and cleaned-up diagrams, the wiki maintenance became far more manageable. I could focus on keeping content current rather than trying to fix foundational issues on the fly. The data flow the CEO wanted finally felt smooth.
If you are in a similar situation — managing documentation, project schedules, or process diagrams for a fast-moving team and finding the workload harder to control than expected — Helion360 is worth reaching out to. They stepped in at the right moment and delivered exactly what the role needed.