Continuous Delivery, as I see most organizations looking at it, reeks of failure demand.  Blinders are being put on to why problems are occurring and, instead of addressing those problems, people in authority say 'We need Continuous Delivery....'  and so teams run off to choose their continuous delivery tool.  Too many organizations are running to Chef / Puppet / Ansible / Salt / etc without reflecting on what is jacked up internally.

If your products are of low quality, what value is there in delivering more horrible stuff faster?

If your environment is overly and accidentally complex, how successful do you think you will be in automating that complexity?

Is your critical application split across a large number of teams, so coordinating even the simplest change is an exercise in frustration and huge risk?

Do you know how the work works in your organization?  Can you picture how it could work?  Is that even possible?

Don't get me wrong, continuous delivery may help you go faster. Continuous Delivery is an amazing learning tool.  The majority of the organizations I have seen simply aren't ready for it though.  They need to start by simplifying what they are doing, slowing down, stop doing so much of the wrong thing - even if you are doing the wrong thing fast.

Consider a customer - they have a need that you can fill.  How can you find what that need is? Continuous Delivery is about the desire to learn faster - do you know what you want to learn?  If you don't know what you want to learn, how does Continuous Delivery help you?  What is really stopping you from learning that?  I'm guessing it isn't a tool.