diff --git a/src/ebooks/why-your-cms-will-fail/chapters/chapter-1.md b/src/ebooks/why-your-cms-will-fail/chapters/chapter-1.md
new file mode 100644
index 0000000..45967a4
--- /dev/null
+++ b/src/ebooks/why-your-cms-will-fail/chapters/chapter-1.md
@@ -0,0 +1,11 @@
+---
+title: Introduction
+image: "chapter-1.png"
+image-alt: "your alt text here"
+layout: chapter
+---
+
+There is a lot on the line when rolling out a new CMS. It powers your website, which is your primary marketing tool. Getting it right is important, and yet so many get it wrong. Many CMS projects end up delayed and over budget. And then after a few years, the situation can deteriorate to the point where the organization tries again with a shiny new CMS that promises to solve all of its problems, and the cycle begins anew. 
+
+How do you stop this from happening? Here are the top reasons your CMS project might fail and ways to mitigate them.
+
diff --git a/src/ebooks/why-your-cms-will-fail/chapters/chapter-2.md b/src/ebooks/why-your-cms-will-fail/chapters/chapter-2.md
new file mode 100644
index 0000000..4f13197
--- /dev/null
+++ b/src/ebooks/why-your-cms-will-fail/chapters/chapter-2.md
@@ -0,0 +1,11 @@
+---
+title: 'A lack of stakeholder involvement'
+layout: chapter
+---
+
+
+You’ve set aside the budget and signed the contracts, but did you remember to budget enough time for your people to contribute? The first few months of a CMS project require dedicated time from everyone involved. This phase is called project discovery.
+
+Your people probably already have a full plate. Unless they are already highly invested in the project's outcome, they won’t be keen to carve out valuable time to contribute. Before the project starts, set proper expectations and give your people some space to breathe so they can temporarily shift their priorities. What you don’t want is your agency partner trying to schedule meetings with stakeholders that have no availability, causing frustration and delays.
+
+**Takeaway:** Set the expectations and give your people plenty of time to participate in the project, especially the months following project kickoff.
diff --git a/src/ebooks/why-your-cms-will-fail/chapters/chapter-3.md b/src/ebooks/why-your-cms-will-fail/chapters/chapter-3.md
new file mode 100644
index 0000000..0f2b9f1
--- /dev/null
+++ b/src/ebooks/why-your-cms-will-fail/chapters/chapter-3.md
@@ -0,0 +1,16 @@
+---
+title: 'Not consulting the people who use the website most'
+layout: chapter
+---
+
+
+This problem comes in two flavors, and projects can have both.
+
+- The primary audience—actual end users—was not asked what they needed or what actions they performed when using the website. Do they even want a website at all?
+- Those responsible for creating, editing, and managing the site content were not asked what features and options would best support their workflows and facilitate communication with their audience.
+
+Higher-ups with authority and control of the budget are almost never left out of the meetings that decide on website features, but they aren’t using the CMS every day. They aren’t fielding support requests and questions from your primary audience. As a result, they often have an unrealistic or skewed picture of what the website needs.
+
+This can lead to disillusionment after launch, as most people who use the CMS find it unhelpful. What was supposed to make content management easier ends up being another roadblock.
+
+**Takeaway:** Include ALL stakeholders when starting a web project to avoid exacerbating an existing problem.
diff --git a/src/ebooks/why-your-cms-will-fail/chapters/chapter-4.md b/src/ebooks/why-your-cms-will-fail/chapters/chapter-4.md
new file mode 100644
index 0000000..cb0db9a
--- /dev/null
+++ b/src/ebooks/why-your-cms-will-fail/chapters/chapter-4.md
@@ -0,0 +1,11 @@
+---
+title: 'User needs are neglected'
+layout: chapter
+---
+
+
+CMS projects are often driven by the need to update outdated technology. This is obviously important. There are security and performance concerns and a desire to access new features.
+
+However, these concerns can overshadow the actual purpose of a site, which is to help its audience do whatever the audience needs to do. You can have a CMS with all the bells and whistles your heart desires, but if those bells and whistles make noises that no one cares about or pays attention to, your project will fail.
+
+**Takeaway:** Keep the real purpose of your project front and center, whether it's helping the business continue making money or aiding the state government in getting information to its citizens efficiently.
diff --git a/src/ebooks/why-your-cms-will-fail/chapters/chapter-5.md b/src/ebooks/why-your-cms-will-fail/chapters/chapter-5.md
new file mode 100644
index 0000000..afe55de
--- /dev/null
+++ b/src/ebooks/why-your-cms-will-fail/chapters/chapter-5.md
@@ -0,0 +1,11 @@
+---
+title: 'The project has an unrealistic timeline'
+layout: chapter
+---
+
+
+Timelines are often driven by budgets or edicts from higher-ups who do not understand the project’s needs.
+
+If timelines are bogus, this leads to broken promises and unmatched expectations, leading to a breakdown in trust and communication. Your CMS project might never launch; if it does, it might be held together by duct tape and bubblegum.
+
+**Takeaway:** Ensure plenty of time for discovery to develop a realistic scope based on business and user needs.
diff --git a/src/ebooks/why-your-cms-will-fail/chapters/chapter-6.md b/src/ebooks/why-your-cms-will-fail/chapters/chapter-6.md
new file mode 100644
index 0000000..981579e
--- /dev/null
+++ b/src/ebooks/why-your-cms-will-fail/chapters/chapter-6.md
@@ -0,0 +1,11 @@
+---
+title: 'Not knowing how to use the system'
+layout: chapter
+---
+
+
+You can do everything right, and your project can still derail after launch. If your authors and editors don’t know how to use the new CMS, it doesn’t matter if the project was delivered on time and under budget.
+
+Authors and editors must understand how the new CMS meets the needs they communicated earlier in the project. They’re also the ones who will be best at identifying bugs that need to be fixed and confusing language that needs clarification.
+
+**Takeaway:** Make time for training, answering questions, and receiving ongoing feedback.
diff --git a/src/ebooks/why-your-cms-will-fail/chapters/chapter-7.md b/src/ebooks/why-your-cms-will-fail/chapters/chapter-7.md
new file mode 100644
index 0000000..c929360
--- /dev/null
+++ b/src/ebooks/why-your-cms-will-fail/chapters/chapter-7.md
@@ -0,0 +1,11 @@
+---
+title: 'Thinking the project is “done”'
+layout: chapter
+---
+
+
+A CMS project is never done. It is only closer to meeting your goals than it was previously. Not everything can be completed before launch. There are always bugs and new feature requests. Don’t forget about ongoing maintenance to keep all of the software up to date.
+
+If you present the new CMS as a finished product, as if you were delivering a pizza, then people will be frustrated and upset. A large portion of your people will think they got the wrong pizza or they were overcharged, and they won’t be wrong. Remember to set proper expectations and timelines and communicate them clearly. For example, “This feature won’t make it in before launch, but we plan on having it completed before the end of the quarter.”
+
+**Takeaway:** Set proper expectations and communicate timelines with ALL stakeholders.
diff --git a/src/ebooks/why-your-cms-will-fail/chapters/chapter-8.md b/src/ebooks/why-your-cms-will-fail/chapters/chapter-8.md
new file mode 100644
index 0000000..d066783
--- /dev/null
+++ b/src/ebooks/why-your-cms-will-fail/chapters/chapter-8.md
@@ -0,0 +1,11 @@
+---
+title: 'Too much complexity'
+layout: chapter
+---
+
+
+This happens when you throw in everything, including the kitchen sink. Marketing needs infinitely flexible landing pages. Check. Each product team needs different designs for their promos. Check. Editors want rigid workflows and permissions, so nothing gets by without their approval. Check. The CEO wants the logo bigger and to spin when someone hovers over it. Check.
+
+When you give everyone everything they want, sometimes you end up with a Frankenstein monster of a website that becomes too complicated. Were these really problems that needed solving? And if so, were these really the solutions for those problems?
+
+**Takeaway:** Dive deep into every request to arrive at the true need. Often, what people think they need is not what they actually need.
diff --git a/src/ebooks/why-your-cms-will-fail/chapters/chapter-9.md b/src/ebooks/why-your-cms-will-fail/chapters/chapter-9.md
new file mode 100644
index 0000000..ac8f43a
--- /dev/null
+++ b/src/ebooks/why-your-cms-will-fail/chapters/chapter-9.md
@@ -0,0 +1,11 @@
+---
+title: 'Hiring the wrong agency partner'
+layout: chapter
+---
+
+
+The right agency partner will help you avoid all of the above pitfalls. They will be open and honest about timelines and budgets and do their best to discover your actual problems that need to be solved. They will push back when needed and not just tickle your ears with half-truths. They will guide you through the tough decisions.
+
+The right agency partner will also have experts in the CMS you are implementing with a proven track record. If the CMS is open-source, the agency should contribute to the code and be well-regarded in the community.
+
+**Takeaway:** Don’t hire based on price alone. That’s letting budgetary concerns be the main driver of your project, setting it up for failure. The cheapest agencies will often cost you much more in the long run.
diff --git a/src/ebooks/why-your-cms-will-fail/cover.md b/src/ebooks/why-your-cms-will-fail/cover.md
new file mode 100644
index 0000000..cdab5c1
--- /dev/null
+++ b/src/ebooks/why-your-cms-will-fail/cover.md
@@ -0,0 +1,7 @@
+---
+layout: cover
+slug: "why-your-cms-will-fail"
+title: "Why Your CMS Project Will Fail"
+---
+
+Eight reasons why your new CMS might fail to live up to its promises and how to overcome them.
\ No newline at end of file
diff --git a/src/ebooks/why-your-cms-will-fail/images/chapter-1.png b/src/ebooks/why-your-cms-will-fail/images/chapter-1.png
new file mode 100644
index 0000000..c86b4c2
Binary files /dev/null and b/src/ebooks/why-your-cms-will-fail/images/chapter-1.png differ
diff --git a/src/ebooks/why-your-cms-will-fail/index.html b/src/ebooks/why-your-cms-will-fail/index.html
new file mode 100644
index 0000000..49f52bf
--- /dev/null
+++ b/src/ebooks/why-your-cms-will-fail/index.html
@@ -0,0 +1,8 @@
+---
+title: "Why Your CMS Project Will Fail"
+layout: layout
+---
+
+{% include 'chapter.liquid' %}
+
+{% include 'pagination.liquid' %}
diff --git a/src/ebooks/why-your-cms-will-fail/table-of-contents.md b/src/ebooks/why-your-cms-will-fail/table-of-contents.md
new file mode 100644
index 0000000..75dfc1b
--- /dev/null
+++ b/src/ebooks/why-your-cms-will-fail/table-of-contents.md
@@ -0,0 +1,11 @@
+---
+title: "Table of Contents"
+layout: table-of-contents
+pagination:
+  data: collections.booksWithChapters
+  size: 1
+  alias: "bookWithChapters"
+  filter: "{{ page.filePathStem.split('/')[2] }}"
+---
+
+{% include "table-of-contents.liquid" %}
\ No newline at end of file