Q Before we get into this week's discussion thread, I want to set some context and parameters of what is expected of you as this discussion progresses. Don't worry about coming up with every detail for the items below. Part of the purpose of these discussions is to see problems, identify what they are, and some of the whys as to the root cause. Your fellow discussion group members can help with the causes and how to remedy them. One part of this discussion is to comment on how to fix these issues from other student's posts or to propose alternative reasons, i.e., digging deeper into the problem. It is my belief that this back and forth is a large part of the learning in the class. Also, and I can't emphasize this point enough, not everyone needs to post a problem. If you are really good at digging into problems and asking follow-up questions and/or offering solutions, just doing that for this week's assignment is perfectly fine. I think that having a handful of really deep and well discussed posts is better than a more diluted discussion where there are too many "problem" posts that are not well dissected. In this week's lecture, we learned about the critical path and the theory of constraints at the resulting bottlenecks. With that in mind think of a recent service encounter and • Describe the service • What was the bottleneck? • What was the cause of the bottleneck (speed of service, information transfer issues, etc.)? • What could be done to remedy the issue? • Other observations