| Date | Name | Role | Version | Comments |
|---|---|---|---|---|
| @January 23, 2023 | John Doe | Founder | 0.1 | Initial draft |
<aside> <img src="/icons/help-alternate_gray.svg" alt="/icons/help-alternate_gray.svg" width="40px" /> What is a process document?
A process guide is a step-by-step manual that outlines how to carry out a specific task in your company. It might detail precisely how to move a certain piece of your data from legacy servers to the cloud, for instance. It could be presented as a rule, a guide, or a flowchart. It may be found in your organization's business strategy, guidebook for new hires, company handbook, or cloud-based standard operating procedures.
Documenting the entire process of completing a task is known as “process documentation.” In a perfect world, it would occur immediately. Employees record each action they take as they complete a task. Regular process reviews and ongoing process documentation allow staff and managers to understand what works and what doesn't, benefiting everyone.
</aside>
<aside> <img src="/icons/light-bulb_gray.svg" alt="/icons/light-bulb_gray.svg" width="40px" /> Why do you need this document?
To begin documenting a process, you must first identify it and give it a clear name and objective.
Document the starting and ending points of the process. Identify what triggers the process to begin and how you can determine when it is complete. For example, the process might start when you realize that your app's home screen looks outdated and end when the updated version has been sent to all customers.
What is the expected outcome of the process? This could be something like "The finalized app is released to end users" or "The software update is pushed to all registered users without any issues."
Take note of the necessary materials and equipment needed to complete the process. This may range from simple assembly lines and robotic assistants to complex legacy servers, private clouds, and multiple platforms.
While it's helpful to brainstorm how a process might work, it's even better to perform the entire process from start to finish. For instance, you could walk through the entire sales funnel to ensure that no elements were omitted during the mock-up phase. It's important to keep in mind that if a button isn't included in the wireframe, engineering won't build it!
List the individuals responsible for completing the process. This typically includes only those who perform the task, but you may also note who the decision makers are for that process.