Turning scattered project management into an operating system

Organization / Context

SB Comm, Inc.

Challenge

SB Comm needed a consistent home for existing and new projects as it moved away from Motion. The transition had to connect project records with the team's existing Zoho workflows and daily coordination, so a software change could become part of the way the company operated.

My Role

I worked inside SB Comm's leadership team and owned the company priority to replace Motion with Zoho Projects for existing and new projects. My responsibilities spanned transition planning, operational coordination, and follow-through on project and process issues with the team.

What I Changed

• Led the Motion-to-Zoho Projects transition as a company priority reviewed through the leadership meeting cadence.
• Preserved Motion task records through spreadsheet exports, saved them in Drive, and linked the records to company and project context.
• Worked with the team on project setup and the connection between project information, operational follow-up, and billing workflows.
• Helped surface and address practical adoption issues, including access to project links and the handling of labor information in finance workflows.

Results / Evidence

• Motion task records were preserved and linked to the company's project context rather than discarded during the transition.
• Later operations and finance records show Zoho Projects in active use for project access and labor-billing workflows.
• Project-system issues had a recurring place for review and assigned follow-up across leadership, operations, and finance.

Timeframe

Documented work: October 2025–March 2026.

Tools / Frameworks

• Zoho Projects
• Zoho CRM
• Motion
• Google Drive
• Project-process documentation

Work performed in a prior leadership role before the formation of Martin Operational Strategy.