About Me

  • 10+ years of experience leading complex, cross-functional projects
  • Focus areas: higher-education enterprise platform integrations, process improvement, accessibility/compliance, and software deployment
  • Skilled at turning ambiguous problems into clear, actionable project plans
  • Strong track record aligning technical and non-technical stakeholders around shared goals
  • Known for clear communication, structured execution, and thoughtful risk management
  • Proven impact: reduced manual work, improved deployment speed and quality, and strengthened compliance across multiple initiatives

Project 1: Enterprise Platform Integration Projects

Role: Project Manager / Technical Integration Lead
Environment: SaaS, cross-departmental teams, external partners

Project Summary

I managed multiple enterprise integration projects related to higher education scheduling software and involving internal development teams, QA, operations, external clients, and third-party vendors. These projects supported mission-critical workflows and required careful coordination, documentation, and stakeholder communication.

Responsibilities

  • Managed full project lifecycle from intake, planning, and execution through deployment and closeout
  • Coordinated schedules, dependencies, and deliverables across multiple teams
  • Gathered, documented, and validated functional and technical requirements
  • Facilitated regular status meetings and communicated progress, risks, and next steps
  • Maintained project documentation and timelines using Jira and Confluence

Tools

  • Jira and Confluence
  • Bruno, an open source API client
  • Stakeholder workshops
  • Series25 documentation for 25Live API

Outcomes

  • Improved time-to-delivery for integrations while supporting hundreds of enterprise users
  • Improved coordination between technical and non-technical stakeholders, reducing uncertainty and miscommunication
  • Established repeatable integration processes that improved consistency across projects

Project 2: Process Improvement & Workflow Automation

Role: Project Manager
Focus: Operational efficiency and project tracking

Project Summary

I led efforts to identify and improve manual processes that were slowing project delivery and increasing administrative workload. The goal was to create more consistent, transparent, and efficient workflows without disrupting existing teams.

Responsibilities

  • Assessed current project and operational workflows to identify inefficiencies
  • Designed and implemented Jira-based workflow automation
  • Documented updated processes and created training materials
  • Supported teams during adoption and gathered feedback for continuous improvement

Tools

  • Jira and Confluence
  • Selenium
  • Series25 documentation for 25Live API

Outcomes

  • Reduced manual administrative work by approximately 350+ hours per year
  • Improved accuracy and consistency in project tracking and reporting
  • Increased team capacity to focus on higher-value project work

Project 3: Accessibility & Compliance Coordination

Roles: Project Manager / Accessibility Lead / Quality and Assurance Release Manager
Focus: Accessibility compliance and documentation

Project Summary

I coordinated accessibility and compliance initiatives to ensure digital products met required standards and supported inclusive access for all users. This work required close collaboration with technical teams and clear documentation for compliance purposes.

Responsibilities

  • Coordinated accessibility audits and remediation efforts across multiple applications
  • Managed VPAT documentation and compliance tracking
  • Worked with stakeholders to prioritize accessibility issues and schedule remediation work
  • Integrated accessibility considerations into project planning and delivery processes

Tools

  • Jira and Confluence
  • ada.org for ADA information
  • Axe platform for accessibility testing
  • w3c.org for WCAG information
  • NVDA / NV Access, a screenreader tool
  • JAWS, a screenreader tool
  • WAVE, a web accessibility tool
  • Accessibility audits

Outcomes

  • Successfully completed accessibility assessments and VPAT documentation
  • Reduced compliance risk by 33% and improved accessibility awareness across teams
  • Supported organizational compliance requirements through consistent documentation

Project 4: Stakeholder Communication & Change Support

Role: Project Manager
Focus: Communication, coordination, and adoption

Project Summary

I supported multiple departments through system and process changes by providing clear communication, structured planning, and ongoing support to ensure smooth transitions.

Responsibilities

  • Facilitated stakeholder meetings to gather requirements and align expectations
  • Developed project plans, timelines, and status updates for diverse audiences
  • Created documentation and training materials to support change adoption
  • Served as a liaison between technical teams and end users

Tools

  • Jira and Confluence
  • Salesforce
  • KnowledgeOwl, an enterprise-level wiki site

Outcomes

  • Improved stakeholder understanding and engagement during project changes
  • Reduced confusion and rework through clear communication and documentation
  • Maintained positive working relationships across departments with competing priorities

Project 5: Software Deployment Improvement

Roles: Project Manager, Quality and Assurance Release Manager
Focus: Reducing sprint engineering duration

Project Summary

I supported multiple departments through the reduction of sprint duration by providing clear communication, structured planning, and identifying resource allocation .

Responsibilities

  • Identified how further entrench our team in agile methodology
  • Developed project plans, workflows, and timelines that would leverage iterative changes
  • Collaborated with multiple teams to ensure that the expedited timeline could be supported
  • Served as a liaison between technical teams and end users

Tools

  • Jira and Confluence
  • Stakeholder workshops
  • Zoom

Outcomes

  • Improved the speed of software deployment of individual sprints from 6 weeks to 3 weeks
  • Reduced software bug regression by improving focused changes
  • Elevated end user satisfaction with better application experience and 20% fewer end user support requests