A global staffing organization was six weeks away from scheduled UAT on a five-year ERP transformation. The Onboarding team had provided the required preparation information six months earlier, but the work had not been completed. Project reporting did not reflect the actual state of readiness, and there was a risk that the Onboarding pillar would be blamed for a failure it had warned about.

The implementation supported complex staffing processes, including resource onboarding, assignments, billing, payroll, accounts receivable, and accounts payable. A failure in these processes could have prevented the business from operating effectively after go-live.

Kasandra identified the gap, escalated it to leadership, and worked with SMEs to validate the risk. Leadership initially found the situation very difficult to believe, so she continued escalating the issue until the evidence was confirmed.

She then helped mobilize a recovery effort that paused all other project work for two weeks. The ERP PMO, business teams, Onboarding, consultants, and SMEs worked together to complete four weeks of preparation before UAT began. Kasandra led daily coordination, clarified ownership, addressed communication breakdowns, and maintained focus through intense time pressure.

• UAT began as scheduled.

• The ERP program went live on schedule.

• The Onboarding workstream generated fewer than 300 tickets compared with thousands in other areas.

• The next phase included clearer boundaries for consulting-partner ownership and accountability.

When reporting and execution reality diverge, leadership needs someone who can identify and validate the risk, make it credible, mobilize action, and protect the outcome.

Three weeks before a $4.5M ERP Finance upgrade began, the organization lost its Finance decision-makers and subject-matter experts, including leadership at the CFO level. At the same time, a state-mandated audit expanded scrutiny across colleges and universities.

The program could not be delayed. Contractors and interim resources were brought in, but decision authority and available skills changed from week to week. The organization was operating under significant fear and uncertainty while additional executive initiatives were added to the delivery environment.

Kasandra created a single source of truth for program status, decisions, risks, documentation, and communications. The information was kept current through the prior workday, giving executives and stakeholders a reliable view of what was happening.

She established flexible governance and resource practices that adapted as personnel changed. She maintained decision-ready executive reporting, coordinated across business and technology teams, and kept the core ERP Finance program focused despite additional scope and leadership turnover.

• The $4.5M ERP Finance program remained on track.

• The program achieved a successful go-live.

• Frequent audits, sometimes initiated with only four hours’ notice, received perfect to near-perfect results.

• Delivery continuity was maintained through significant leadership turnover and resource instability.

In a crisis, reliable visibility and adaptable governance are not administrative conveniences. They are the infrastructure that allows an organization to keep operating.

At the beginning of an ERP HCM upgrade, consultants were taking up to two weeks to become fully productive. At approximately $250 per hour, the organization was absorbing substantial paid time while consultants waited for access, equipment, email, scheduling, and other onboarding requirements.

Consultants were also prohibited from using organizational equipment and email. The restriction appeared to be a policy requirement, but the organization had never investigated the underlying reason.

Kasandra worked with Legal and Information Security to investigate the restriction. The analysis showed that the policy was based on a decades-old misinterpretation of contract language.

She helped secure a policy change that enabled consultants to receive organizational email accounts and equipment. She then worked with multiple ERP workstreams to create a standardized onboarding process, workflow, checklist, governance model, and reporting structure.

The process included reporting across 60 data points and was first used for approximately 12 HCM consultants. Responsibility later expanded to all consultants across the HCM and Finance programs and then the whole organization.

• Saved $630K on an $8.5M ERP program.

• Onboarded 90 consultants.

• Reduced onboarding time from two weeks to four hours.

• Removed policy and access barriers.

• Created a required system standard.

• Converted the solution into an automated process for broad enterprise use.

Hidden process friction becomes expensive when nobody owns the problem. The right intervention can convert waste into a scalable operating capability.

A firewall implementation was approximately one year behind schedule and facing resistance from influential faculty and other stakeholders. The IT project team was also frustrated because the previous project-management approach bypassed the chain of command and assigned work directly to individuals without regard to workload or functional accountability.

Kasandra was not initially a firewall subject-matter expert, but she needed to create a credible schedule and establish a path forward.

She met with the leaders of resistant stakeholder groups to understand and address their concerns. During the transition, she reset expectations with the IT delivery team, clarified roles, and committed to assigning work through functional managers who understood staff capacity and competing priorities.

She partnered with DataComm to identify a meaningful workload-based progress measure and used it to build a realistic schedule. She then prepared the Technical Advisory Group by identifying its concerns in advance and presenting clear responses and mitigation actions.

Kasandra maintained focus on the implementation, used the appropriate leadership channels, and continued working the delivery plan.

• Secured unanimous Technical Advisory Group approval to proceed.

• Rebuilt trust between the project manager and IT delivery team.

• Established a credible schedule and accountable work model.

• Completed the firewall implementation in three months.

• Accommodated student work schedules without losing delivery momentum.

Technical expertise matters, but difficult projects also require stakeholder intelligence, chain-of-command discipline, trust repair, and the ability to lead without relying on authority.

A university system needed leadership across nine complex initiatives involving multiple institutions, limited shared resources, consultants, vendors, and several hundred stakeholders. Some projects had reached an execution impasse despite experienced project-management teams.

Kasandra created and implemented a PMO with practical governance, templates, lifecycle controls, policies, reporting, risk management, training, and mentoring. She presented weekly decision-ready updates to executive leadership, including the CFO and CIO, and negotiated resource conflicts across four universities.

• Managed a $10M portfolio.

• Coordinated nine complex initiatives simultaneously for up to 35,000 end users.

• Built PMO capabilities supporting more than 100 concurrent projects.

• Improved executive visibility into decisions, dependencies, risks, ownership, and delivery status.

• Helped restore stalled projects and create a repeatable management system.

A PMO should not exist to produce more reports. It should help executives see reality, make decisions, prioritize the work when needed, and move the portfolio forward.