I like the spirit of this blog post, and I believe strongly in trying to get devs to stake in to product ownership (understanding product use, asks, &c) is a huge advantage, something small companies tend to have exceedingly better competencies at.<p>Shadowing sessions are great. I've never seen workshops nor internal podcasts, but I have my doubt that this will provide authentic connection, or generate real stake in. But we should try things, so good luck.<p>Overall though I don't feel like most companies are willing to change themselves. Trying to reshape developers seems besides the point. It's your organization that needs to change. Merely throwing more obligations & responsibility on your in the trench forces is not where real wins come from. What incentivizes engineers to step away from the code, from smashing tickets, & to wade into your product organization & it's myriad power structures & less obvious mechanisms? What new power or capabilities will the engineer receive? What is going to make them feel more empowered or better? I love the general idea here, but frankly, it's with many good reasons that most engineers would rather be heads down, not dealing with customers having issues (many of which will invariably be beyond their power to adddress) and corporate power structures (which will keep them from addressing what they might).