HELP!

I went and flowed an either/or decision (see attached) and my Boss did not like the way I did it. Is there a better way of flowing an either/or decision?

Thanks,
Doug

Doug,

Is there a piece missing? If not, where do I start in this flow chart? Some boxes only have arrows going into the box, not out of, so I think I see the confusion. I think I can help if you tell me where to start.

Here's a shot - The one problem with your flow chart was the 2 yes arrows coming out of a decision box.

I agree.

Where does it start?

Cindy

Doug,

Is there a piece missing? If not, where do I start in this flow chart? Some boxes only have arrows going into the box, not out of, so I think I see the confusion. I think I can help if you tell me where to start.

I would tend to agree Laura. It appears that you begin with the first decision, and most folks say you don't begin a flowchart with a decision. However, if the point is just to show the either/or decision point, I have no problem with it.

I agree with Laura's rendition as well. But I would suggest, for simplification, that you just eliminate the 'OR' loop completely. Just use the first decision diamond only: If it is "standard" you go one way, and if it is "special" you go the other. If you have both special and standard, then both 'directions' apply. I would not be confused by that.

I modified your flow. Maybe it will give you a different perspective.
Glenn

I modified your flow. Maybe it will give you a different perspective.
Glenn

Glenn,

This is an excellent fix. Simple and easy to follow

Greg B

HELP!

I went and flowed an either/or decision (see attached) and my Boss did not like the way I did it. Is there a better way of flowing an either/or decision?

Thanks,
Doug

Doug

The answer is Yes. But even better to avoid decisions if possible - or at least the diamonds with 2 (or even worse 3) alternative routes out. There are a number of potential problems with what I call "words in the boxes" type flowcharts, which can go all over the page and end up getting folk lost. But if you do use this format, I know that some folk apply conventions such as:
1. only 2 routes out (I think that your example could be confusing even deciding which route to take)
2. down = "normal" route, side = exception (other folk make it "Yes" is down, "No" is to the side).

We find that you can often build a "decision" into the text and make it a normal task. So if someone reads "If Special Tooling required, make a copy of the PO", and they know there isn't a Special on this order, they just go on to the next step.

I have defined entire quality systems without a decision anywhere to be seen - or at least without diamonds! It can be done, and what is more to the point the end result is far clearer to a reader.

Wow! Thanks for the suggestions - everyone! Sorry if I did not provide more of the flow, I just wanted ideas about how to deal with Either / Or Decisions.

Rob: Originally I did not have the second decision block, but my Boss said that the flow did not properly show how to process orders that had both types of product, so I added it to show that both processes are performed in conjunction with the other when an order contains both Standard Tools and Special Tools, which are our product types. But Of Course he did not like the two yes decisions coming from the OR decision either!

Peter: Interesting concept about flowcharting without decisions and your example I have used when generating a process control plan. However, to process Information and/or Documentation, or just showing interactions between Leadership, People, and Information Systems I tend to try and capture the primary decisions that affect those interactions.

Thanks Again Everyone!

Doug

I thought all three modifications posted were good suggestions, but I think my eyeballs like the fixer's best.