In my last post, we talked about how to get started with your insight solution deployment and the importance of establishing an enterprise-wide center of expertise for Advanced Enterprise Search. This, along with our other best practices, aims to prevent you from making common mistakes in your deployment that could delay the return on your investment.
The next thing to be aware of during your deployment is the “Requirements Peacock” (pictured below). Let me explain. Too many people consider their insight solution deployment as just a technology project. Yes, technology is definitely a very important piece, but there are certainly more elements to be addressed in order to increase the success of the project.
Here’s where the “Requirements Peacock” comes in. Requirements come in all sizes and colors, but they all need to be captured, documented and prioritized. If you don’t take the time to gather those requirements, don’t expect them to simply be mentioned by anyone, ever. They will come out when you least expect them, derailing the project and greatly handicapping the value created by the solution.
It’s a best practice to capture, document and review all those requirements with stakeholders early in the project to help determine the deployment activities. In some cases, capturing those requirements can be a standalone project from which a deployment project will be derived.
Have you managed your requirements for your insight solution deployment, or did they end up managing you?
We have another best practice post in this series to share, but in the meantime, let us know what else you’d like to hear aboutthat may aid in your insight solution deployment.