Overview
Proper documentation helps communicate designs to engineering and development teams. Different projects call for different types of documents and the scope of designer’s influence in development can vary.
Generally speaking, the more information that can be passed from design, the more effective and efficient the engineering.
Application Map
The Application Map provides a visual reference for user flows and helps engineering quickly grasp the architecture of a project. Although I try to compile one map of the entire product, it’s sometimes important to provide specific user flows that might be more complex to understand.
UX Development Guide
The UX Development Guide essentially becomes the Bible of a project. It is the ultimate reference for anything UX. The guide breaks down and provides written instruction on every detail of the user interface and user interaction. Each button will have detailed responses and all the invisible attributes of an interface manifest. As designs change and new or alternate functions are introduced, this document changes with it.
Database & API Architecture
For projects with complex data structures, I have experience detailing out the database and API endpoints required for an application.
Although not an engineer, these documents have proved extremely useful in guiding successful integration of backend servers developed independently of client applications.
