What does ownership mean in organizations where everyone, everywhere is expected to step up? Well, it depends on seniority. Ownership for executives looks like buy-in. For cross-functional collaborators, it's about advocacy. For content contributors and direct reports, it's concrete, meaningful ownership of the development and production processes. Specific to this last point, I want to stress that our job is not to be a quality-control gatekeeper — at least not during ideation. As my friend [Behzod Sirjani](https://behzod.com/?ref=content-technologist.com) said about his time running research at orgs like Facebook and Slack, "Our job is not to be product police; it's to build a practice of learning." With organizational design, I like to think about it as building a practice of collective writing. We start by: - [[Define expectations when setting up editorial processes]] - [[Healthy feedback cultures draw on grounded rationale]] - [[Content success depends on crossfunctional advocacy]]