I am not sure where this belongs exactly so I just chose ISO9000 forum.
I am in need of clarification. When I worked for Lockheed Martin, I was taught that a procedure was something that was in your hand as a "checklist" during the manufacturing process (in this example of making a cable).
Now I am told that a procedure is a process that does not have to be in front of you (like getting in a car and starting it would be following a "procedure").
I look at it like this... if you follow a procedure without any "checklist" in front of you is TRAINING. And then when you follow a procedure with the documentation in front of you is a "procedure".
Welcome to The Cove, ISObuster! I'm sure you'll find lots of people here willing to help you out and provide their opinions to your questions.
Okay, definition time...that means I need my handy-dandy ISO 9000:2000....
specified way to carry out an activity or a process
NOTE 1 Procedures can be documented or not.
NOTE 2 When a procedure is documented, the term "written procedure" or "documented procedure" is frequently used. The document that contains a procedure can be called a "procedure document".
Clear as mud?
Document designations vary from company to company. What your former company called a procedure, mine would call a work instruction.
Procedures where I work are a higher form of documentation...less detailed...more process-based (i.e., paperwork trails, responsibilities, accountability, process-flow, etc.).
Work Instructions are more detailed, task-specific....kind of like a checklist.
It sounds as if your current company does have documentation. It may not necessarily be in front of you (it doesn't always need to be there!) and they happen to use different language than your former company.
Don't let the differences in documentation designations get the best of you, ISObuster!