diff --git a/content/posts/2013-03-26-i-am-here-for-an-argument.md b/content/posts/2013-03-26-i-am-here-for-an-argument.md
new file mode 100644
index 0000000..ffd8eab
--- /dev/null
+++ b/content/posts/2013-03-26-i-am-here-for-an-argument.md
@@ -0,0 +1,37 @@
+---
+title: "I'm here for an argument"
+kind: article
+created_at: 2013-03-26
+tags:
+  - why
+  - leadership
+  - inspiration
+---
+
+When people make a request or proposal I often see them present their request and arguments using the following structure:
+
+1. Make a request
+2. Give a plethora of arguments why that request is a good idea.
+
+An example:
+
+* I want to go to the zoo!
+* Because I want to see animal
+* Because I want to spend time with you
+* Because it has been a long time
+
+Here I think, meh, the zoo. And then I read some arguments that may or may not change my opinion on actually going to the zoo or not.
+
+You start with the _what_ and then continue on to the _why_, but I've already lost interest.
+
+Consider this request:
+
+* I want to spend time with you and see animals.
+* It has been a long time since we went to the zoo
+* Let's go to the zoo!
+
+Here you start with me agreeing on spending time together and it becomes easier for me to accept your request to go to the zoo. I'm not blinded by your request.
+
+You start with the _why_ and then continue to the _what_.
+
+In addition to this article, please watch [Simon Sinek's TED Talk](http://www.ted.com/talks/simon_sinek_how_great_leaders_inspire_action.html) [18m05] How great leaders inspire action.
\ No newline at end of file