- You are a carpenter, manufacturing windows and wooden door frames.
- Customers tend to shop around and ask price-quotations at many different competitors. Making price-calculations is a time consuming job.
- You decide to make a quotation-module on the internet: The customer answers the questions you would normally ask him, and gets his quotation a quickest possible way.
- Any frame will get a quotation! Square, rectangular, unequal shapes, with or without turning windows… As long as they are made of wood!
Basically the manufacturing process consists of:
- Making wooden profiles
- Making joints (a simple window is 4 profiles and 4 joints)
- Apply rotating- and locking mechanisms
What are the parameters you will have to question the customer upon?
How does the process to finally calculate the correct price look like?
Make a solid Process Structure Diagram.
To give you some idea about similar situations in real life, look at those two examples (that do not handle any situation!)
Example 1 (click on picture)
Triage – Decision trees: The pitfalls
Triage systems –and other decision trees– are commonly used to direct actions in a process.
Sometimes it is a simple sieve; in other cases it is a multi-dimensional ‘funneling system’ that leads the user through a series of questions to bring him to the one and only possible answer. Remember in biology lessons, the plant determination guide?
1. Ease of use
Many triage procedures are ‘written text’ and may be absolutely correct. However since our brain is much more powerful in visual handling than text handling, it would help to present the ‘decision making process’ in a visual manner.
The following example is based on a Dutch tax form.
||First the whole process was precisely and in detail designed, including all ‘what if scenarios’. This was brought into a PSD that was very much correct and complete, but also became quite difficult to read. Based on the insight now gained, de relevant decision points where transformed into understandable and unambiguous questions. Those question where presented in a visual manner to the final user.
In the design-state, the use of PSD can dramatically ease up the insight of the process; compare those two examples:
|A simple sieve in a flowchart….
||….the same sieve in PSD
2. Questions are unambiguous
“The patient can go to blood test” Yes – No
Does this mean “The patient is able go there?” or does it mean “we are ready to send the patient there”.
You might recieve different answers, depending the pespective the user is answering the question from! This should be prevented at all circumstances!
3. Questions are easy to understand
“Do you want to prevent to get no sugar with cream?”
Now what are you going to prevent exactly?
Sometimes it is difficult enough to ansewer the question… them why make a riddle from a question?
4. Structure of design
A good triage is full- ánd fool proof… so it should work at all circumstances. Things tend not to go wrong when everything is OK. A triage should also, no precisely work when things gó wrong, under pressure, when there is panic!
- What do I have to do if I can not answer one of the questions?
- What should I do if I made a wrong decision at any point?
- What should I do if the answer is neither A or B but an unexpected C?
- Is it possible to answer a specific question at this specific moment in the triage? (“If you do not like the product you may return it in an unopened package”)
To achieve a proven correct structure to the triage process, a PSD is a tremendously strong tool!
Case: Calculating Week Numbers
Depending on the year, the last week of the year is week number 52 or 53.
Figure out how to determine whether december 31 of a random year is week 52 or 53.
Describe this decision-making process in a PSD.