A selection of cross-functional technology initiatives I’ve led across technical operations, site reliability engineering, documentation, change management, automation, and enterprise portfolio work. Details are generalized to protect confidential systems and processes.
Program & Operational Buildout
Building a 24/6 Live Operations Capability
The Challenge
As the technology portfolio expanded, production support needed a scalable operating model capable of coordinating incidents, escalations, communications, and technical response across approximately 28 SaaS products.
My Role
Led the development and operation of a 24/6 Live Operations capability spanning Incident Management, Site Reliability Engineering, Technical Writing, and partner technology teams.
Project Management Approach
- Defined operational scope, ownership, and escalation paths.
- Coordinated work across onshore and offshore teams.
- Established incident response and communication processes.
- Developed runbooks, playbooks, and operational documentation.
- Managed dependencies across Engineering, QA, Infrastructure, vendors, and business teams.
- Established recurring operational and corrective-action reviews.
- Tracked performance and identified opportunities for continuous improvement.
Building and Scaling a Technical Writing Function
The Challenge
Technical documentation needed a consistent operating model, publishing platform, standards, workflows, and ownership structure capable of supporting a growing technology organization.
My Role
Built and led the Technical Writing function, establishing the people, processes, standards, tooling, and delivery model required to support engineering and operational teams.
Project Management Approach
- Defined the documentation operating model and delivery workflow.
- Implemented a documentation-as-code publishing environment.
- Established templates, style standards, and review processes.
- Coordinated priorities with Product, Engineering, Operations, and business stakeholders.
- Managed work through sprint-based planning and delivery.
- Established recurring maintenance and publication tracking.
Outcome
Created a repeatable documentation program capable of supporting technical teams across a broad SaaS portfolio rather than relying on ad hoc documentation requests.
Process & Change Management
Redesigning Production Change Management
The Challenge
Production deployments were creating unpredictable incident spikes and increasing operational risk across the technology organization.
My Role
Led operational improvements to the production change process, working across Engineering, SRE, QA, and technology leadership.
Project Management Approach
- Analyzed recurring incident patterns and deployment-related risks.
- Introduced formal go/no-go review gates.
- Strengthened release-readiness and rollback planning.
- Participated in Change Advisory Board governance.
- Identified QA, access, and dependency requirements before major changes.
- Used incident outcomes to drive iterative process improvement.
Transforming Documentation Delivery
The Challenge
Documentation delivery needed to keep pace with engineering and operational requirements across a distributed technical writing team.
My Role
Led the redesign of documentation workflows, standards, tooling, and delivery practices.
Project Management Approach
- Mapped the existing documentation workflow and delivery constraints.
- Standardized templates and content-development processes.
- Introduced AI-assisted authoring using GitHub Copilot and Writer.com.
- Coordinated adoption across a distributed team.
- Tracked documentation work through sprint boards.
- Introduced automated publication and maintenance tracking.
Risk & Dependency Management
Enterprise Dependency Mapping
The Challenge
Two major third-party outages demonstrated that the organization did not have complete visibility into which internal systems depended on external platforms.
My Role
Initiated an effort to identify and map dependencies across the technology environment so downstream impact could be understood before the next major external outage.
Project Management Approach
- Identified stakeholders and system owners across technology teams.
- Collected dependency information from multiple functions.
- Mapped upstream and downstream system relationships.
- Identified ownership and dependency gaps.
- Connected technical dependencies to operational impact.
- Used findings to improve outage readiness and risk visibility.
Outcome
Shifted dependency management from discovering downstream impact during an outage toward identifying critical relationships proactively.
Managing Cross-Functional Vendor Risk
The Challenge
Vendor-side changes and outages could affect internal workflows even when no internal deployment had occurred, creating both technical and coordination risk.
My Role
Coordinated investigation and response across internal teams when third-party services affected production systems, ensuring the correct dependency was identified and the appropriate teams were engaged.
Project Management Approach
- Coordinated technical stakeholders across internal teams.
- Tracked external dependencies affecting delivery and reliability.
- Escalated vendor-related risks when business impact increased.
- Connected incident findings back to dependency and readiness planning.
- Improved visibility into risks outside direct organizational control.
Outcome
Improved the organization’s ability to distinguish vendor-side failures from internal issues and incorporate external dependencies into operational planning.
Automation & Continuous Improvement
Automating Documentation Status Tracking
The Challenge
Publication and maintenance status was being tracked manually from sprint-board tasks, creating repetitive administrative work.
My Role
Identified the manual workflow as an automation opportunity and implemented a Power Automate solution to collect and organize the information automatically.
Project Management Approach
- Mapped the existing manual process.
- Identified the sprint board as the system of record.
- Defined the information required for publication and maintenance tracking.
- Implemented the automated workflow.
- Integrated the output into the team’s ongoing operating process.
Outcome
Reduced manual administrative work and created a repeatable method for tracking publication status and upcoming documentation maintenance.
Improving Operational Visibility and Response
The Challenge
Reliable incident response depended on identifying production issues quickly and giving responders enough visibility to understand where failures were occurring.
My Role
Led operational improvements around observability, alerting, incident processes, and recurring review of production issues.
Project Management Approach
- Established monitoring baselines and dashboards in New Relic.
- Improved alerting and escalation practices.
- Used recurring incident patterns to prioritize corrective work.
- Coordinated improvements across SRE and partner Engineering teams.
- Tracked operational performance through incident metrics.

