diff --git a/Writerside/d.tree b/Writerside/d.tree
index ed21cfe..b436eac 100644
--- a/Writerside/d.tree
+++ b/Writerside/d.tree
@@ -31,6 +31,7 @@
         <toc-element topic="SOMe-unnamed-software.md"/>
     </toc-element>
     <toc-element topic="AI-Things.md">
+        <toc-element topic="Cutting-Corporate-Bullshit.md"/>
         <toc-element topic="Testing-Phi3.md"/>
         <toc-element topic="Text-based-adventure-with-gemini.md"/>
         <toc-element topic="Liar.md"/>
diff --git a/Writerside/topics/Cutting-Corporate-Bullshit.md b/Writerside/topics/Cutting-Corporate-Bullshit.md
new file mode 100644
index 0000000..bd67d84
--- /dev/null
+++ b/Writerside/topics/Cutting-Corporate-Bullshit.md
@@ -0,0 +1,56 @@
+# Cutting Corporate Bullshit from Corporate Documentation
+
+Corporate documentation is often plagued with jargon, redundancy, and unnecessary complexity. Here are some strategies to streamline and clarify your documents:
+
+## Identify and Eliminate Bullshit
+
+* **Jargon:**
+    * Replace complex terms with simpler language.
+    * Define technical terms for clarity.
+    * Avoid using multiple synonyms for the same concept.
+* **Redundancy:**
+    * Remove repeated information.
+    * Condense lengthy explanations.
+    * Eliminate unnecessary qualifiers (e.g., "very," "extremely").
+* **Passive Voice:**
+    * Convert passive voice to active voice for clarity and conciseness.
+    * Example: "The report was written by the team" becomes "The team wrote the report."
+* **Unnecessary Complexity:**
+    * Break down complex ideas into smaller, easier-to-understand points.
+    * Use bullet points or numbered lists to organize information.
+    * Avoid overly long sentences.
+
+## Focus on Clarity and Conciseness
+
+* **Write for Your Audience:**
+    * Tailor the language and level of detail to your reader's knowledge.
+    * Avoid assuming prior knowledge.
+* **Use Strong Verbs:**
+    * Replace weak verbs with stronger ones for impact.
+    * Example: "Use" instead of "utilize."
+* **Be Specific:**
+    * Provide concrete details and examples.
+    * Avoid vague or general statements.
+* **Proofread Carefully:**
+    * Eliminate typos, grammatical errors, and inconsistencies.
+
+## Practical Tips
+
+* **Read Your Document Aloud:**
+    * This helps identify awkward phrasing and unnecessary complexity.
+* **Use a Style Guide:**
+    * Consistent formatting and language improve readability.
+* **Seek Feedback:**
+    * Ask colleagues to review your document for clarity and conciseness.
+
+## Example: Before and After
+
+**Before:**
+> "The implementation of the new system will necessitate a comprehensive evaluation of existing processes to ensure optimal utilization of resources and alignment with strategic objectives."
+
+**After:**
+> "We'll need to assess current processes to make the new system work best and fit our goals."
+
+By following these guidelines, you can create clear, concise, and effective corporate documentation that is easy to understand and act upon.
+
+**Would you like to provide a specific example of corporate documentation you're working on? I can help you identify areas for improvement.**