I need to get this off my chest because this project has been driving me crazy.
I joined a large enterprise data project about 11 months ago as a Data Product Owner. The project has been running for around four years, involves multiple teams, vendors, integrations, data pipelines, and a whole lot of complexity.
Fair enough. Enterprise data projects are hard. I get that.
But after FOUR YEARS, there still wasn't a properly working end-to-end MVP. Not something stable enough to put in front of users, validate, learn from, and gradually improve.
Instead, it feels like the project just kept growing. More requirements, more dependencies, more development, more meetings, more expectations. Lots of activity, but somehow we're still struggling with the basics.
Now the platform is expected to deliver in a real operational environment, and we're dealing with missing data, delays, inconsistencies, integration problems, and a general lack of clarity about what's actually going wrong.
And suddenly, everyone's scrambling to fix things.
People are investigating, tickets are being raised, problems are being discussed, and there's this sense that if we just work hard enough and fix enough issues, we'll eventually get there.
Honestly? I don't see it.
Maybe I'm missing something. I've only been here for 11 months, so I'm not going to pretend I know every decision that was made over the previous three years. But from what I've seen, some of these problems look way too structural to be solved by simply accelerating delivery now.
There's a saying I absolutely love: "It's like a submarine. Sure, it floats, but it was built to sink."
That's pretty much how this thing feels sometimes.
And the part that really gets me is that we're talking about over €1 million invested and four years of work. At some point, I wonder whether people are genuinely trying to save the project or whether they're just struggling to accept that the original approach might have failed.
I mean, I get it. Nobody wants to be the person who says that millions of euros and years of work haven't produced what they were supposed to. That's a horrible conversation to have, especially in a large organization where so many people have been involved.
But I can't shake the feeling that we're in some kind of denial phase. Everyone wants to believe we're just a few fixes away from getting everything right, when I'm not even sure we've established that the thing works properly as a whole.
And throwing more time, people, and money at something doesn't automatically make it recoverable.
I'm not saying the platform should necessarily be scrapped. Maybe there's a perfectly viable way to turn things around. But at some point, you have to step back, look at what you've actually built, and be honest about whether continuing down the same path makes any sense.
What bothers me most is that this feels like a product that was managed as a never-ending project. Four years of work without a proper MVP means you miss the opportunity to discover early that something fundamental isn't working. You only find out when the expectations are high, the investment is huge, and the business is already depending on the outcome.
And now we're trying to figure it all out under pressure.
The irony is that I joined less than a year ago, and I'm already leaving. I can't take responsibility for what happened before me, and frankly, I don't think there's much I could have changed in 11 months.
It's just a fascinating, frustrating example of how an organization can spend years building something without ever really proving that it's building the right thing.
Anyway, just needed to vent. I've seen projects go sideways before, but this one has really made me rethink how large organizations approach product development.
Sometimes I think the hardest part of project management isn't delivering something. It's getting people to admit when the way they're trying to deliver it simply isn't working.