My approach leverages the power of the CSDM model for ownership and accountability. Allowing you to scale to any team, dept, line of business into Enterprise Knowledge Management. while minimizing knowledge mgmt overhead.
The idea is that all items in the CSDM framework have ownership. It does not matter where in the stack the CI is. Because all CI's roll up to a "Managed by", "Owned by" or even a Support Group for ticket routing. It does not matter if the CI is operational or not. This approach works for my organization, but you can choose what field to use for your knowledge workflow. Out of the box you can associate knowledge articles to Configuration Items and Service Catalog items. All of which are owned in one way or another.
You can design you workflow to use knowledge templates in order to minimize manual work for knowledge mgmt.
Additionally, you need to decide what field in the CI record to use ("Managed by", "Owned by" or even a Support Group) in order to trigger workflow notification and review accountability\ownership.
Below is a high level of this in action.
