All Posts

A detailed guide to implementing Workday HCM and Financials from scratch in a new organization — covering all 8 phases from project initiation through go-live, plus the six Workday modules every team needs to know.

A comprehensive breakdown of every phase involved in migrating from Workday to SAP — from requirements gathering to go-live — with timelines, key risks, and critical success factors.

How I led 22 concurrent security projects across a 6-building life sciences campus — delivering access control, CCTV, alarm, and GSOC integrations on time with zero audit findings.

There's a conversation that happens in every engineering organization, usually on a Monday morning. Someone pulls up a slide deck. Someone else pastes numbers from a spreadsheet. A third person is on Slack frantically DMing pod leads for updates they haven't gotten yet. Forty-five minutes later, leadership has a vague sense of where things stand — and six engineers have lost the best focus hours of their week to a meeting that could have been an automated summary sent at 9 AM

Digital transformation isn’t just about adopting new tools—it’s about rethinking how core business functions operate. One of the most impactful transformations organizations undertake today is implementing an integrated ERP system like Workday. In this post, I’ll walk through a realistic project scenario of a Workday ERP implementation, along with the stakeholder management strategies that drive success. Project Context - A mid-sized global services company decides to replace

As a project manager, there’s a moment that hits harder than missed deadlines or scope creep. It’s when you realize that the detailed project plan you carefully created… hasn’t actually been read by anyone. You spent hours structuring timelines, mapping dependencies, identifying risks, and documenting everything clearly. But execution tells a different story. People are working on the wrong tasks, stakeholders are asking basic questions, and priorities seem completely misalig

In the fast-paced world of IT project management, unrealistic deadlines are less of an exception and more of a recurring challenge. Whether driven by market pressure, stakeholder expectations, or competitive urgency, compressed timelines can put even the most experienced project managers in a difficult position. The real skill lies not in avoiding these situations—but in managing them effectively without compromising outcomes or team well-being. Why Unrealistic Deadlines Happ

The situation was critical: a healthcare data migration project, three months overdue, budget nearly exhausted, and stakeholder confidence at an all-time low. As the newly appointed project manager, I had six weeks to turn it around. This is the framework I used to rescue the project and deliver results that exceeded expectations. The Challenge The project scope involved migrating patient data processing systems from legacy infrastructure to a modern cloud-based architecture.

he Case: The Never-Ending Data Pipeline Six months into a critical data migration project, I was building pipelines to move patient data from legacy SQL servers to Snowflake. Everything was on track until week three, when stakeholders started changing requirements weekly. First, they wanted real-time data instead of batch loads. The next week, they needed additional data fields we hadn’t scoped. Week after that, the entire data retention policy changed. Sound familiar? The Pr

“Build us an AI solution to understand our customers better.” That was the entire project brief. No data requirements, no model specifications, no definition of “better,” no success metrics. Just a mandate from the C-suite who’d read one too many articles about ChatGPT and wanted their own “AI thing.” I was assigned as the project lead for what would become a four-month AI product development initiative, but on day one, I didn’t know if we were building a chatbot, a recommend

It was a Tuesday morning sprint planning when our VP of Product walked into the room unannounced. “I need you to add real-time chat to our e-commerce platform. Competitors have it, customers are asking for it, and I promised the board we’d have it by quarter end.” My team had spent three months building a new checkout flow that would reduce cart abandonment by an estimated 18%. We were two weeks from launch. The VP wanted us to pivot immediately to build live chat — a feature