In the preceding section, I showed how to use work and conversation patterns as a basis for design. In this last section I discuss principles for building these patterns into the system. What does it mean to “put work patterns into the system”? To what degree should it be done? How should it be done?

As my example I shall use the data entry parts of the data entry (registrering) process classified as control style in Section II.2.2.2. Here I noted that the PGP-system is in control in this part of the work process and guides the worker through a fixed standardized sequence of operations:

In addition, it automatically provides the next card of the same batch, and the first card of the next batch when the last of the previous batch is finished and the batch tallies. If it does not tally, it enters the completing subview. The system supervises the user's work, and directs the worker's attention to and from the screen by means of error messages like

a type of control which was consciously introduced by the developers: they wanted to “stop a phase where you work with the card, and initiate a phase where you work with the screen”.

I have already classified this standardization of work as a “frozen” variant structure.