[throw82473751]

Eerm sorry, either misunderstanding something, but the first point sounds like totally incompetent POing and classical overengineering (though here we have the PO wanting to show off, to overengineer is the engineer's job please!!) even before the realization that the CEO just wanted to share an idea?

I mean a simple "let hires watch a video about our product" is just about saving some repetitive time... who asked for a "video onboarding solution"? And let the full tech team work on that for two weeks, jeeez! Be happy noone else noticed that wasted time and fired you?

A motivated PO could do this on his own if he has a little bit knowledge and the right tools in his spare hours (at least ours could)...should be good enough just for new hires. Or maybe better delegate that to some marketing guy that maybe even already has video material and who is done within half a day??

[reidalert]

Yep, guilty as charged and I look back on this experience and see a lot of things that could have been done differently. To clarify, the video idea was about new users of the product not internal hires, so the production quality would need to be higher. These days I'd probably whip up a Retool-style intro video using Loom + Wistia in a day or so.

[ownagefool]

I'm more suprised that a PM can up and change what a dev team is working on with such frivolity, especially one whos so green. Typically I'd rather get a commitment from a developer or development team, and expect them to ask why this random thing trumps what is being displaced.