Introduction
After you’ve implemented the solution, your next step is to provide documentation for the customer. It’s important that you write documentation for its intended audience so that they understand the systems that you’ve built and deployed. Additionally, you’ll need to consider whether the audience is technical or if they’re end users.
As a functional consultant, you’re the person who knows the most about all aspects of the system. You know the reasons why the customer has asked for certain components and changes. You know the various considerations that were taken during solution creation, including the technical considerations. You’re one of the people who knows the most about the entire project. Accordingly, it makes sense that you should be the one who creates the documentation.
Make sure that you keep documentation top of mind and that you create it for every project that you do. Creating good documentation can be time-consuming, but it’s crucial for the long-term success of business applications. Having a small amount of accurate documentation is better than having a lot of documentations that’s inaccurate. A common challenge is to make sure that the documentation reflects the as-built details of the solution.
Several types of documentation are available that you should always estimate for in every project, including system documentation and user documentation.