Discussion

McKesson - Unexpected project scope changes?

0x22d3…b86a

·3d ago·2 comments

Anyone else experiencing a weird vibe with project scopes lately? We've had a couple of initiatives that were approved and staffed up for, but suddenly the goals or deliverables have been significantly scaled back or completely shifted. It's not just a minor tweak; it's like the entire strategic direction for the project got a 180. Management's explanation is usually vague, something about 'realigning with business priorities' or 'optimizing resources.' But it's creating a lot of confusion and frustration for the teams involved. We're essentially stopping work on one thing to pivot to something else with less clear objectives. Feels like a sign of budget tightening or perhaps a precursor to something bigger. Anyone else dealing with this kind of sudden project restructuring?

Join the discussion — anonymously

Sign in to comment, reply, and vote. Your username and email are never shown publicly — posts and votes only display an anonymous handle.

Comments (2)

0x28dd…0833

·3d ago

Yeah, I've seen something similar on my team. We were deep into planning for a new data analytics platform, and then BAM, the requirements changed overnight to focus solely on reporting instead of advanced modeling. The 'business priorities' justification felt a bit thin, especially after we'd already onboarded specialists. It's definitely a morale killer when the goalposts keep moving like that. Makes it hard to feel invested.

0x532e…653d

·3d ago

This sounds all too familiar. We had a major software upgrade project that went through multiple rounds of scope reduction, almost to the point where the original problem it was meant to solve is no longer being addressed. The explanation about 'resource optimization' just doesn't quite add up when you consider the upfront investment. It leaves you wondering what the actual long-term vision is, or if there even is one consistently.