diff --git a/content-production-plan.md b/content-production-plan.md
index 10f8c19..8adaa7d 100644
--- a/content-production-plan.md
+++ b/content-production-plan.md
@@ -1,37 +1,12 @@
 ## Blog Post
-* Research - writer
-* Write - writer
-* Review - subject expert of writer's choosing
-* Revise - writer
-* Approve - subject expert
-* Publish to CMS - writer
+* For technical posts, get at least one person's review for clarity and accuracy. As the original author, it's your call as to when you feel it's ready to be published.
+* For political posts, be sure to notify everyone in the coop so they have time to weigh in on it. Sometimes it makes more sense for political posts to be published from one's own personal website,rather than Agaric's.
 
 ## Case Study
-* Research - writer
-* Write - writer
-* Review - subject expert of writer's choosing
-* Revise - writer
-* Approve - subject expert
-* Publish to CMS - writer
+* Be sure to notify everyone in the coop so they have time to review. Ultimately though, it's the original author's choice as to when it's ready to be published.
 
 ## Event
-* Write - writer
-* Review - subject expert of writer's choosing (can be skipped if time is pressing)
-* Revise - writer (can be skipped if time is pressing)
-* Approve - subject expert (can be skipped if time is pressing)
-* Publish to CMS - writer
-
-## Initiative
-* Research - writer
-* Write - writer
-* Review - subject expert of writer's choosing, client
-* Revise - writer
-* Approve - subject expert
-* Publish to CMS - writer
+* Ideally have one other person review the event for accuracy and clarity, but it's most important that event announcements get made on time.
 
 ## Profile
-* Write - writer
-* Review - subject expert of writer's choosing
-* Revise - writer
-* Approve - subject expert
-* Publish to CMS - writer
\ No newline at end of file
+* We are experts on ourselves! That said, it's good to have someone else read it to share an outsider's perspective.
\ No newline at end of file