Since we're developers who work with teams who don't write code, we strive to balance our communication between verbose and easy-to-understand for non-technical users. It might make for a lengthy email to a seemingly simple question, but we always try to provide a little more information than you needed to hopefully answer that next inevitable question you hadn't asked yet.
Fortunately, that works out pretty well for documentation. We've generated easy-to-read API specifications, information architecture, user manuals, workflow and content publishing diagrams, editorial guidelines, and best practice presentations to help keep teams on track and paying attention to the right details.
This documentation can also accompany an onsite workshop where we'll walk through an application, content management system (CMS), or other workflow systems where your team is sure to get the training they'll need to work effectively.