The Case of the Poorly Written Manual John Howard was shaking his head as he left the meeting with his boss, Joe French. Joe was right; the new technical manual was simply not up to the company's standards. Yes, he had told Joe that there were three new people in the test group, but that was no excuse. The three apparently were simply not capable writers; they might be capable product engineers, but their writing was terrible. John called the training department and asked for Susan Harris. Could Susan schedule his three new employees in her next technical writing course? 1. What are John's assumptions in making this decision? 2. Is this an appropriate approach to solving his problem?

John's assumptions in making this decision are that the three new product engineers are not capable writers and that their writing is terrible. John also believes that the only way the technical manual can be brought up to company standards is by offering a course in technical writing.

This is not an appropriate strategy for resolving the issue, as decisions should never be made based solely on assumptions, such as the fact that the product engineers in question are new hires and therefore unable to write. This is further explained below.

What is a decision?

Generally, a decision or conclusion was arrived at after careful deliberation.

In conclusion, When John was making this choice, he made a number of assumptions, one of which was that the three new product engineers are not competent writers and that their writing is horrible. John is also of the opinion that the only way the firm's technical handbook can be brought up to the standards of the corporation is by providing students with the opportunity to take a course in technical writing.

Because choices should never be made entirely based on assumptions, such as the fact that the product engineers in question are new employees and hence unable to write, this is not a suitable technique for fixing the problem. Decisions should never be made solely based on assumptions.