decisions, procedures show the "how to's" for completing a task or process. Procedures are action oriented. They outline steps to take, and the order in which they need to be taken. They're often instructional, and they may be used in training and orientation. Well-written procedures are typically solid, precise, factual, short, and to the point. Many procedures seem "black and white," with clear steps and only one way of doing things: "Complete A, then B, then C." But sometimes you need to be less exact and allow room for personal judgment. When a procedure is too tight, it can cause confusion. Since life isn't always simple and clear-cut, some procedures need to allow subjectivity and individual choices. When Do You Need a Procedure? Not everything needs a procedure, so don't create procedures for basic tasks -- otherwise they'll be ignored. The number-one rule of procedure writing is to make sure there's a reason to create them: Perhaps people forget to take certain actions, perhaps they keep on getting things wrong, or perhaps tasks are so long and complex that people need a checklist if they're going to get things right. A written procedure is necessary only if the issue is important or if there will be a significant benefit from clarifying a process. Before you begin, ask yourself if people really need or want to know about something. In a company, it's typical for many things to get done without written procedures. There are "unwritten rules" and informal procedures. But