1. Decide where it starts.
2. Decide where it ends.
3. Be clear about its objectives.
4. Be clear WHY you are defining it.
5. Be clear HOW users will access the definition, and the level of detail they need.
6. Know where the process fits within the overall management system.
7. Ensure that the people who will be using the process description are competent – or train them.
8. Describe tasks in verb – noun format.
9. Identify logical stages within a process (if relevant) to make the description more readable.
10. (Unless you are defining a process at a high level…) Clarify who is RESPONSIBLE for each task, and who else is INVOLVED (“RACI”).

TEN COMMON MISCONCEPTIONS ABOUT BUSINESS PROCESSES

ANOTHER TEN MISCONCEPTIONS ABOUT BUSINESS PROCESSES

TEN REASONS WHY PROCESS MAPPING / MANAGEMENT IS OF VALUE

TEN POINTS TO REMEMBER WHEN DEFINING A PROCESS

TEN MISTAKES TO AVOID WHEN DEFINING A PROCESS

TEN OBJECTIVES WHEN CREATING A PROCESS DESCRIPTION

Ian Leaver of independent analyst Forward Look explains "user-centric process management"software.

TEN FEATURES TO CONSIDER FOR PROCESS MAPPING / MANAGEMENT SYSTEM SOFTWARE

PROCESS MANAGEMENT GLOSSARY