Get Practical Playscript Writing Procedure Manuals That People Can Use 3rd Edition Robert Burnett free all chapters
Get Practical Playscript Writing Procedure Manuals That People Can Use 3rd Edition Robert Burnett free all chapters
com
https://ebookfinal.com/download/practical-playscript-
writing-procedure-manuals-that-people-can-use-3rd-edition-
robert-burnett/
OR CLICK BUTTON
DOWNLOAD EBOOK
https://ebookfinal.com/download/writing-and-designing-manuals-and-
warnings-4e-4th-edition-robinson/
ebookfinal.com
https://ebookfinal.com/download/from-conflict-to-cooperation-labour-
market-reforms-that-can-work-in-nepal-1st-edition-robert-kyloh/
ebookfinal.com
https://ebookfinal.com/download/practice-notes-county-court-procedure-
practice-notes-3rd-edition-gerlis/
ebookfinal.com
https://ebookfinal.com/download/how-lis-professionals-can-use-
alerting-services-1st-edition-ina-fourie-auth/
ebookfinal.com
Legal Writing 3rd Edition Lisa Webley
https://ebookfinal.com/download/legal-writing-3rd-edition-lisa-webley/
ebookfinal.com
https://ebookfinal.com/download/extreme-cuisine-the-weird-and-
wonderful-foods-that-people-eat-freeman/
ebookfinal.com
https://ebookfinal.com/download/helping-people-to-give-up-smoking-can-
be-easy-1st-edition-fabio-lugoboni/
ebookfinal.com
https://ebookfinal.com/download/college-writing-a-personal-approach-
to-academic-writing-3rd-edition-toby-fulwiler/
ebookfinal.com
https://ebookfinal.com/download/safe-use-of-chemicals-a-practical-
guide-1st-edition-t-s-s-dikshith/
ebookfinal.com
Practical Playscript
Writing procedure manuals that people can use
ALSO BY ROBERT BARNETT
Practical Playscript
Robert Barnett
www.RBAinformationdesign.com.au
ISBN 978-0-9586384-3-2
Contents
Acknowledgments ix
v
Chapter 1 The Role of Procedure Manuals 1
Why have a procedure manual? 2
Functions of a manual 5
vii
Practical Playscript
viii
Practical Playscript
Acknowledgments
M
ost books on management include ideas and principles gathered
by the author from predecessors and restructured to suit the ix
author’s aims. This book is no exception.
The primary acknowledgment goes to Leslie H. Matthies whose books,
The New Playscript Procedure and Documents To Manage By, have been my
primary inspiration in writing procedure manuals. I have drawn heavily
on his work and have endeavoured to keep the Playscript format as close as
possible to his original concepts.
I have also drawn much inspiration from Clyde Jackson’s book Verbal
Information Systems and from numerous other writers whose works are
mentioned in the footnotes and in Appendix 1.
I would also like to thank the many people who have contributed
positive comments about the earlier editions. This encouraged me to retain
the same format and writing style, while reducing the page size in keeping
with our other publications.
Most of all I would like to thank my wife Patricia for her never-ending
support and patience, and for her tireless efforts at rekeying all my old
course notes.
Robert Barnett
Practical Playscript
x
Chapter 1
The Role of Procedure Manuals
It has been said that ‘behind every business activity there lies a piece of paper’
and, even with today’s emphasis on computers, this adage is still true. In addition 1
to such practical office work tools as forms, reports, correspondence and memos,
there is a vast range of other administrative paper—much of it essential—but
much of it superfluous.
This book deals with documentation that comes under the general heading
of procedure manuals. Although it is primarily concerned with procedures, we
need to consider all manuals briefly because other material is often included in
procedure manuals, either through ignorance or because the writer cannot think
of anywhere else to put it. Administrative documentation covers a wide range of
subject matter such as:
Policy statements Organisation charts
Job/position specifications Standards
Lists of authorities Appointment announcements
Departmental functions lists Memos
Circular letters Temporary announcements
Form-filling instructions Forms catalogues
In addition to general administrative paper, we have a whole range of
computer systems documentation.
You need to write and structure each type of documentation to suit the
particular needs of its users, so you need to think carefully about what you are
including in each manual. Only some of this material comes under the general
category of procedures.
Practical Playscript
1 Jackson, Clyde (1974) Verbal Information Systems, Association for Systems Management, Cleveland Ohio.
Chapter 1 • The Role of Procedure Manuals
computer through us, they have seen us almost as the ‘high priests’. And, generally we love
every moment of it. Let’s quit putting ourselves and them on. The computer is a machine.
That’s all. Granted, it is complex and sophisticated, but it is still a machine. It can only do
what people tell it to.”
However, the extent to which you should include this type of material in
a user’s procedure manual is debatable. It has been my experience that many
computer people think of their work in terms of projects or programming products
rather than overall efficiency of the organisation. But general office workers don’t
necessarily think in terms of systems or projects unless the content of those
systems coincides with the content of their day-to-day work. This can happen,
but it is wrong to assume that it is always the case. The structure of a computer
system tends to be machine-oriented and it is rare for the human component of
the system to follow the same form.
Keith London2 described this with a matrix based on the Blake Management
Grid as shown in Figure 1.1.
2 London, Keith (1976) The People Side of Systems, McGraw Hill Book Company (UK).
Practical Playscript
Operatives
4 The operatives are at the opposite end of the scale to management. They
certainly need to have a broad understanding of what management expects of
them, but their primary interest is in the fine detail. They want to know:
‘How do I do my job?’
‘What happens next?’
‘What do I do with this paper when it lands on my desk?’
‘How do I make these calculations?’
‘How do I evaluate this application?’
‘What do I enter into this computer?’
‘Where do I send this piece of paper?’
‘Do I have the authority to make a decision on this problem or should I refer it to my
supervisor?’
Clyde Jackson3 said that:
“the impact of a procedure manual is either:
(1) To help solve operational and management problems, or:
(2) To help create operational and management problems.”
If you don’t write with the users in mind, then the manuals will create their
own additional problems.
3 Jackson, Clyde (1974) Verbal Information Systems, Association for Systems Management, Cleveland Ohio.
Chapter 1 • The Role of Procedure Manuals
Functions of a manual
In the next chapter we’ll be looking at the types of material included in
manuals. But first we need to consider in more detail why we need manuals.
Clyde Jackson lists six important functions of manuals. While it would
be possible to add even more to his list, I believe that his descriptions are
comprehensive enough to be quoted without further comment.
“INSTRUCTION. A manual instructs people in all levels of the company.
• It teaches line personnel facts about their jobs, as well as providing step-by-step
instructions about performing their jobs.
• It provides supervisory personnel with the knowledge required to manage the
productivity of their people.
• It gives management a concise overview, plus the details of operations, depending on
how thoroughly management reads the manual.
5
• It provides a training guide for new personnel.
REFERENCE. No one can remember everything about a system or a particular function
within the system. The manual is a valuable reference containing detailed information
about a system.
• It is a source for solutions to non-routine problems. If a person can find the answer in a
manual, he saves his superior’s time, and he is more independent.
• It refreshes a person’s knowledge of his job when he reviews the manual periodically.
• It provides authoritative answers to operational questions.
REVIEW. A manual allows a review of operations. Putting operations down on paper
allows several levels of criticism.
• It allows overall criticism, to see if the overall operation accomplishes its objectives.
• It allows a more efficient sequencing of activities or assignments of personnel if needed.
• It asks the question, “Is this the best way to do it?” of every function.
CONTROL. A manual, when well developed, has important control functions on several
levels.
• It allows supervisory personnel to assign and evaluate their people more effectively.
Practical Playscript
• It gives control departments such as auditing, quality, safety, etc., the information they
need to perform their functions.
• It enables management to more intelligently allocate resources and set objectives.
STANDARDS. A manual is important for establishing and enforcing work standards.
• Where required, it will help see that the same job is done the same way each time.
• It defines the acceptable level of performance and instructs the personnel in the method
to achieve it.
• It serves as an objective basis of evaluating either an individual’s or a department’s
performance by stating the criteria for measurement in advance of the evaluation. The
“evaluator” and the “evaluatee” will both benefit by knowing the ground rules.
DOCUMENTATION. Stated simply, a manual is a record of how a particular company
does a certain function. It is a record of what they do. While this statement is a gross
oversimplification, it accurately describes the documentation function of a manual.”
6
Chapter 2
Content of Procedure Manuals
In the first chapter I covered the range of material that people include in
procedure manuals. We can now break this down into specific categories and this 7
will help us to arrive at the optimum structure.
Corporate policy
This is one of the most difficult areas to define because it varies greatly from
one organisation to another. I’m not getting embroiled in the argument about
whether or not such a policy should exist. Writers such as Tom Peters1 and Robert
Townsend2 have strong words against it, while others sing its praises. My point in
this chapter is simply to define what we mean by corporate policy statements as a
component of manuals. To begin, here is what various writers have said.
Stephen Page3 defines policy as “a predetermined course of action established as a
guide toward accepted business strategies and objectives.”
George Terry4 defines policy as “a basic guide to action. It prescribes the overall
boundaries within which activities are to take place and hence reveals broad management intentions
or forecasts broad courses of managerial action likely to take place under certain conditions. …
Knowing the policies of an enterprise provides the main framework around which all actions are
based. Policies furnish the background for an understanding of why things are done as they are.”
System objectives/narrative
If your procedures are part of a computer system, you will usually need a
general description or narrative for the benefit of people who need an overview.
The narrative usually describes such features as:
• the concepts behind the system
• descriptions of the way in which each subsystem operates
• descriptions of the functions and workings of each computer program
• description of each report produced.
5 Matthies, Leslie H. (1982) Documents to Manage By, Office Publications Inc., Stamford.
Chapter 2 • Content of Procedure Manuals
I have seen many computer systems where this was the only user document.
It was left to the individual managers and operatives to work out how to put it into
action. This doesn’t help productivity. Good system documentation should go way
beyond the electronic aspects and deal with the people side of systems.
2. Functions
The Forms Management Department will specify the design of all printed forms used
throughout the company, in order to achieve:
2.1 Systems compatibility and efficiency in use
2.2 Economy in ordering and procurement
2.3 Prevention of redundant forms.
Accordingly, all requests for new or revised forms/screen layouts will require the
approval of the Forms Management Department.
3. Responsibilities
Procedure/task objectives
This is similar to system objectives but broken down to the individual task
level. It can be helpful for staff to understand the objectives or reasons behind each
particular task, together with any organisational policy that specifically refers to
that item. These may be just very brief comments, or in the case of very important
matters, they could run into a number of pages.
Some writers object to any form of policy statement being included in a
procedure, but over the years I have come across many people doing jobs and not
having any idea why they were doing it. These people just go about their jobs as
a matter of daily routine and without any real enthusiasm for the task. I’m a great
believer that workers need to be really involved in their jobs. The more they are
personally motivated, the happier they will be.
Procedure
Throughout this book I will be using the definition of procedure given by
Leslie Matthies6 to distinguish it from a task outline.
“It is a write-up that reflects the system. It is a document that spells out clearly how an
activity flow proceeds from one work group to the next, down through the system channel
from start to finish.”
It is a step-by-step instruction concentrating on the flow of work between
people. The main emphasis is on what is done rather than the how to. It may
10 include the how to but usually not in the same detail as a tack outline.
The procedure’s emphasis is on teamwork telling all the team members how
their work fits into the overall process—or how the work proceeds from step to
step. Where you need a great amount of fine detail, you would cross-reference it to
a task outline. Figure 2.2 shows a typical Playscript procedure.
Task outline
This tells how to perform a certain task. It covers all the step-by-step detail,
usually leaving nothing out, and covering every alternative and optional course of
action. It describes the method of doing the job with the how to do it having
the greatest emphasis rather than what is done. You could call it a one-person
procedure. Figure 2.3 shows a typical task outline.
The task outline should be so comprehensive and straight forward that a new
person can follow it with little or no outside help. The intent of the task outline is to
give an employee all the information they need to perform the task.
Remember, if you can explain a task to someone in person, you should be
able to explain it in writing.
6 Matthies, Leslie H. (1977) The New Playscript Procedure, Office Publications Inc., Stamford.
Chapter 2 • Content of Procedure Manuals
how to fill it in. My experience is that while possibly being of use in a system
description, or as part of the form’s History File, it is usually a waste of time in
user documentation. Such a specification should be unnecessary if the form is well
designed and the procedures and task outlines are well written.
Supplementary data
This would include lists of codes, glossaries, error messages, etc. These are
often vital parts of a computer system that must be made known to the user.
-----------------------------
Practical Playscript
If not arrange allocation of new Keyword (see Task Outline No TRM 001).
3. EXAMINE the numeric keyword index to find out if special file subdivisions are
used.
If so DETERMINE category.
Note: If the subject doesn’t fit into an existing subdivision and it appears necessary
to open a new group, check with the manager of the department concerned before
allocating.
4. ALLOCATE next available file number.
5. SELECT appropriate descriptors(see Task Outline No TRM 002).
6. ENTER details onto “Index Maintenance” form (No. 765).
7. DETERMINE the file retention periods for the record type in accordance with the
needs of the user department.
8. ENTER “Active” file retention period on “Record Location Maintenance” form (No.
12 767).
-----------------------
readers are advised to evaluate any criticism in the light of his later findings.
Its main thrust is to cull policy and general descriptive material leaving
behind the step-by-step detail of how to carry out the procedure. Having culled
this material, Matthies further breaks down the content into two separate types of
documents, ‘Procedures’ and ‘Task Outlines’.
An overview of Playscript
I have been writing procedures for over forty years and have seen and tried
a great variety of systems. Some of them have been complete failures while others
have been reasonably successful.
When I was introduced to Playscript, we found problems with the way it
was being used and tried various ways to get around them. Later, we discovered
that we had not been given the full story. Matthies covered many of the problems
we encountered and it became clear that our criticisms were not justified. It was
we who were wrong; we weren’t using Playscript as intended to be used. Part of
this came about because Leslie Matthies’ book was written primarily to “sell” the
method, rather than to explain the fine detail of how it worked.
• We didn’t differentiate policy from step-by-step detail.
• We didn’t make provision for complex decision-making instructions.
• We tried to write everything the same way when we should have used
different methods for different types of material.
14 The following five guidelines are what I use to produce effective user
manuals.
1. Write up any procedural and system policy or objectives in narrative or
Outline format.
2. Use Playscript Procedures to describe the overall workflow procedures
for every system and subsystem within the organisation. These explain
what is done.
3. Write detailed task outlines using the Playscript format where there is a
need for fine step-by-step detail for an individual employee. These explain
how to carry out each task.
4. Incorporate brief task-oriented policy and objectives at the top of task
outlines wherever there is a need for the individual to know them. These
explain why the task is being carried out.
5. Write up system descriptions and similar documentation as captioned
narratives.
It helps management
It is a great advantage to management whenever there is any dispute about the
way to do something. Management time is usually scarce and managers appreciate
having a procedural system that enables them to quickly locate troublesome
areas.
15
Playscript simplifies writing
While using a standard format such as this places restrictions on writers,
it is so simple that anyone who can write in plain language can use it effec
tively, and professional writers are not necessary. It helps to force writers to use
simple language. While the best results are going to come about if the writers
are professional analysts, I have had a great deal of success in training staff
to write their own Playscript procedures and task outlines. Leslie Matthies found
that most people learned to write clearly after only 5 or 6 hours of training and
practice. In my own consulting work, I have had similar results with procedure
writers being able to produce clear and logical procedures after only a few short
review sessions.
It forces brevity
Experience shows that any writer using Playscript automatically shortens the
statements and cuts out excessive description. The direct nature of the language,
using action verbs, brings this about.
18
Chapter 3
Rules of Structure
If you intend to use Playscript, or are already using it, I recommend that
you read Leslie Matthies’ books Documents To Manage By and The New Playsript 19
Procedure for a useful and entertaining background to the method.
However, I have written this book as a training tool and have structured the
content in a straight through sequence, starting at the top of a procedure and
working down through the body with its various components and physical layout.
The basic rules of simple procedures are covered first with the more complex
subroutines dealt with in more detail later.
… If you try to modify a proven, effective technique, all you’re doing is improving
backwards. Fifteen years of research has developed a format that works. Another twelve
years of application in organizations of every type has convinced us that this is THE
format.”
Page title
People call procedures by an incredibly wide variety of names. One of the
more common names that I have encountered—and one that Matthies also
mentions—is ‘Standard Practice Instruction’. On the other hand, some organi
sations use the word ‘procedure’ when they aren’t procedures at all.
We are talking specifically about ‘procedures’ here, so why not use the word?
It makes sense and everyone will know what it means.
The subject
Every procedure should state the subject. This is the key to indexing the
procedures and, although brief, should state clearly what the procedure deals with.
If you are indexing them using a keyword system then you will need to carefully
select every word in the subject. You will also need to make sure that no two
procedures in the organisation use the same subject.
If you are producing an index using an automatic indexing program such as
that in Microsoft Word® or Adobe InDesign®, then you will be able to add additional
hidden index words. If so, I suggest using the approach that I use when developing
an alphabetic index for a book such as this. Read through the procedure and ask
Chapter 3 • Rules of Structure
what people would look up in the index if they were searching for the procedure.
Remember that people don’t all think alike and will not necessarily look for the
same words that you would use. The subject should reappear at the top of each
separate procedure sheet. The matter of multiple pages is covered in more detail
under Page number.
Procedure
Section Subsection Section No.
Procedure No.
Procedure No.
21
Subject Date
Procedure number
Like its counterpart, the form number, this is one of those controversial
aspects of procedures. Yet, I have found that most people have little real basis for
Practical Playscript
their opinions. The way in which you number the procedures will depend on the
size and type of organisation for which they’re written and especially the number
of different types of manuals in use.
Some organisations number their procedures by department or section, but
procedures reflect business functions that can cross over departmental bound
aries. Categorising your procedures by department or section may be breaking
them down artificially and often to no advantage.
Another method is to categorise them by systems project. Now, we might
think that since procedures are system-based that this is the way to go, but
experience shows that, in the long term, this method doesn’t work either. System
project groupings are usually chosen arbitrarily to reflect the work being carried
out at a specific period of time. On the other hand, the systems staff may have
chosen them because that particular group of procedures was all that they could
handle at any one time with the staff available. The development staff usually think
of tasks that have to be done to make the computer system work.
Added to both these problems is the matter of change. As soon as there is a
change to a system, or a regrouping of departments or sections, the old boundaries
may cease to exist and the total numbering system may have to change.
The solution is to categorise procedures by business function. In many cases
such functions will coincide with departmental boundaries and computer systems,
but I want to stress that this may be just coincidence. As many people have found
when they tried to number procedures by department or system, just because
22 function coincides with department or system at the time it is introduced, it is no
guarantee that it will continue into the future. I suggest that it should be corporate
policy that manuals are to be structured by function, unless there is a strong case
for doing otherwise in your organisation.
As for the numbering of the manuals, there are many approaches. Some
procedures analysts suggest that the best method is to number sequentially from
“1” with a good alphabetic index. This is the same approach recommended by
most professional forms analysts for form numbering. It definitely works with
forms, but they are not like procedures. The practical use and reading process is
different. A form may be a part of the overall business system, but it is generally
used in isolation. Users often have to read a procedure in conjunction with related
procedures so that they can understand the whole system. The procedure is a
reference document, not a one-at-a-time resource.
My preference is to follow a system such as that given by Jean d’Agenais &
John Curruthers1. From my experience it is more appropriate to large organi
sations. It breaks manuals up by business function rather than computer system or
department. Although d’Agenais & Curruthers don’t suggest it, I would give each
type of manual a two (or three) character alphabetic code starting at “AA” and
working sequentially to “ZZ”. Note that the codes themselves have no functional
1 d’Agenais, Jean & Carruthers, John (1985) Creating Effective Manuals, South-Western Publishing Company,
Cincinnati Ohio.
Chapter 3 • Rules of Structure
significance—they are solely for identification and indexing. You would then break
each Manual down into “Section”, “Subsection” and “Subject”, each with a two-digit
code separated by spaces or dashes. The introductory pages would normally be in
Section 00. For example, you could classify the procedure for applying for annual
leave in the Human Resources Manual (Code HR) as HR-02-05-01:
SECTION 02 Leave
SUBSECTION 05 Annual
SUBJECT 01 Application
Following the same pattern, the document giving an overview of the
company’s Annual Leave policy could be HR-02-05-00:
This construction allows for greater flexibility for the user. Related proce
dures are close to one another and save the user looking up indexes when the
whole function is being studied.
Page number
A well-planned Playscript procedure will usually have a maximum of about 25
work statements. This means that the average procedure could go on the front and
back of a single sheet of paper. Some people claim that short procedures don’t need
page numbers. However, if you are using word processing software it is usually an
advantage to automatically number the pages. You may also find that it is helpful
to have the subject and page number on every page so that they don’t get mixed up
in reproduction and filing. However, don’t number the pages continuously for the
whole manual. Start each procedure at page 1. 23
Procedure layout
Playscript is written like a play and each step has four main ingredients:
1. action by (person performing the action)
2. logical step sequence number
3. action word (verb)
4. action performed
A normal Playscript page is laid out in columns as shown in Figure 3.2. Since
Playscript was devised, the introduction of International Standard paper sizes (e.g.
A4) and the use of computers for word processing has changed the way procedures
can be laid out. While it is possible to use a fixed pitch typeface such as Courier,
you would be more likely to use proportionally spaced type such as Times New
Roman. The amount of space you use will depend on the typeface and size you
have chosen. For space reasons in this book, the following example uses 8 point
New Century Schoolbook. On a full-size page, I would increase this to 10 point,
or 11 point if using Times New Roman (since it is a smaller typeface) and vary the
column width accordingly.
Practical Playscript
The margins you leave will depend on your binding mechanism and the
method you use for production. If you are using a typewriter or similar mechanical
device, you will probably need at least 25 mm (1 inch) at the bottom for a gripper.
If using a laser printer, you could reduce this. Figure 3.3 shows a suggested spacing
for each column. Note that the inch measurement only approximates the metric
measurement.
Column headings
Some people prefer the column headings to be over the centre of the columns.
My preference is to align them to the left as this is an easier typing action and may
also provide for greater reading clarity. This is another of those points that should
not be a major issue.
The white space around each Action by title clearly shows where the person
“comes on and off the stage” and how each action fits with the activities of other
people in the workflow.
Only the first word of the person’s work position needs a capital initial letter
unless it is an official position title. In this case, each word would normally be
capitalised.
If you have a long title that must be written in full, then use two lines. You
could align the second line to the right or left, although the left takes less typing
activity. Alternatively, you could indent the second line a few spaces. Figure 3.4
shows three examples of the same step showing how it would appear. Note that the
last example has the Action performed starting on the same line as the second line
of Action by. If you are using a typewriter, this will probably be easier, but takes up
more space. My preference is for the first version.
Plant and
Facilities Engineer 5. INDICATE on the form when preliminary action
25
will be taken to investigate the matter.
‘Step’ column
The step number is the logical sequence of the steps in time order and always
starts at 1 at the beginning of every procedure. The numbers would often be right
aligned so that where the number of steps reaches 10 or more, all numbers will be
aligned for neatness. Step sequence is covered later in the chapter.
occur and that the Secretary’s step, being a ‘trigger’ action, should be the start of
a separate procedure. In fact, in a longer procedure, there would be a total break
here and a new procedure started. In this case it is only short, but the Secretary
needs to be able to pick up the flow easily at the point where it starts again, and I
have found underlining ideal for achieving this.
You can also use highlighting and underlining for branching activities and
alternative paths. This is covered in detail in Chapter 4.
-----------------
Purchaser 5. GIVE the Purchase Order number to the vendor and ask
that the number be shown on the invoice.
6. INSTRUCT vendor to send the Invoice to the Association,
marked ‘Attention Treasurer’.
Vendor 7. SHOW the Order Number on the Invoice and send it to
the Association as requested.
ON RECEIPT OF INVOICE
Association 8. CHECK with purchaser to make sure that items have
Secretary been received and note this on the Invoice.
26 -----------------
Highlighting verbs
Even before using Playscript, I found it very profitable to start each step of a
procedure with a verb and to highlight it.
In one company, we wrote the verb in a separate column but I found this
to be a waste of space and it makes reading unnatural. It is better to keep the
verb in the sentence context, maybe highlighting it in bold type. With modern
word processing systems this is an easy operation. You could use capital letters or
underlining in addition to bold type, or as an alternative to it. I have found this
approach advantageous for the following reasons:
1. Outline
The bold verbs provide an instant outline of the task outline or procedure.
2. Fast location
They help the reader go to a specific point in a procedure without the need to
read through from the start.
3. Memory assistance
They can assist a user who is working directly from the procedural text to carry
out a task. They assist the user to find the next step in the procedure once they
come back to it after completing the preceding step.
Chapter 3 • Rules of Structure
Verb tense
The verb is always in the present tense and may be in either the second or
third person. In the example in Figure 3.6, it is in the second person, which is my
preference since it is an instruction, but it is not wrong to use the third person.
For example: 2nd person 3rd person
SORT or SORTS
DELIVER or DELIVERS
SIGN or SIGNS
The third person may be better for straight through reading, but the second
person is more direct as an instruction.
This system relies on every sentence beginning with a verb—something
that isn’t always practical. For example, a step may begin with timing or other
information that shows when it is to commence. Figure 3.6 shows part of a
procedure using this approach. But note that the layout isn’t compatible with
normal Playscript.
2.
Form 683, entering department designation.
DELIVER to time clerks.
27
Time Clerk 3. DISTRIBUTE time cards to all personnel.
Employee (all) 4. PREPARE time cards as instructed in procedure 02-04-
04, Daily Time Tickets.
5. SIGN time card at start of each day, writing department
number in parentheses after signature.
-----------------
A way around this is to turn the timing instruction into a subheading so that
the actual steps do begin with a verb immediately after the step number as shown
in Figure 3.7.
Figure 3.8 Step 2 combines two actions in one step (‘examine’ and ‘note’)
Figure 3.10 contains two totally separate actions included together as if they
happen at the same time. Figure 3.11 is a better arrangement.
Supervisor -----------------
4. ASK Department Head for approval. Tell the employee
that the official leave will be granted by personnel and that
a note will be sent to that effect.
Supervisor -----------------
4. ASK Department Head for approval.
5. TELL the employee that the official leave will be granted
by personnel and that a note will be sent to that effect.
Sequence of steps
To determine the sequence of steps, think in terms of time. A procedure is a
series of activities being carried out by people in a logical sequence. Except where
there is a branching activity and two things are happening at the one time, the
steps take place in strict time sequence—one after the other.
Practical Playscript
As Matthies2 says:
“…some people write their procedures as though this logical time sequence didn’t exist.”
For example, if an employee is applying for leave, the steps could occur as
follows:
This is the sequence in which the steps occur, so unless there are exceptions
this is the sequence in which the procedure will be written. Branching activities
and alternative paths are dealt with in Chapter 4.
The main work sequence follows the action, not the piece of paper. The
following is a summary of the process. Chapter 7 covers it in more detail and
explains how to identify the work channels.
Mail Clerk 1. OPEN mail bag and empty onto sorting table.
2 Matthies, Leslie H. (1977) The New Playscript Procedure, Office Publications Inc., Stamford.
Chapter 3 • Rules of Structure
Delay
27. REPORT to the Claims Controller on the assessment
of the damage.
Claims Controller 28. COMPLETE claim form.
29. send completed claim form to insurer.
3 Matthies, Leslie H. (1977) The New Playscript Procedure, Office Publications Inc., Stamford.
Practical Playscript
Inclusion of functions/policy
I agree very much with Leslie Matthies when he says that you should keep
matters such as departmental functions and systems separate. But I have found
a few occasions when it was helpful for the user to read a brief description of
the task’s function first. Statements of timing can be included under separate
subheadings. This is covered in more detail in Chapter 5.
These are the most difficult parts of any procedure and Playscript is no excep
tion. Subroutines occur whenever there is a decision-making point in a procedure. 33
In some cases there can even be decision-making points within a subroutine.
There are no firm rules for handling them, as you need to deal with each
procedure on its merits. The following principles provide guidelines for subroutines
of different complexities. As I’ve mentioned in earlier chapters, in this edition of
Practical Playscript I’ve added additional material based on more recent research
in human communication. The technique is based on the extensive success that has
been achieved through the use of questionnaires in the design of business forms.
It occurred to me that there is little difference between a numbered sequence of
questions in a form and a series of steps in a procedure. Both involve step-by-step
progress with action at each step. The advantage of the approach is that it simplifies
complex decision making routines using questions with “Yes”/“No” answers and
routing to relevant steps. The approach is explained in more detail later in the
chapter.
Provided at least one of the two channels can be included in a single step,
indent the side channel using the same step number, but with lower case alpha
suffixes to indicate the substeps.
Figures 4.1 and 4.2 show two possible ways of handling the same side
channel.
Note that the second example highlights the alternative payments more
effectively and draws the cashier’s attention to the fact that there are two different
actions.
After the side channel is completed, the procedure returns to the normal
position and numbering sequence.
Applicant -----------------
5. HAND payment and completed Application Form to the
Cashier.
Cashier 6. EXAMINE Application Form to verify amount to be paid
and, if paying with currency, enter amount into cash
register.
6a. If paying by cheque, EXAMINE “Stop List” to
determine whether cheques are acceptable from this
applicant.
34 6b. If cheques are not acceptable, TELL applicant to go to
the enquiry counter.
7. RECORD receipt on Application Form butt and return it
to the Applicant.
Purchaser -----------------
5. GIVE the Purchase Order number to the vendor and ask
that the number be shown on the Invoice.
if paying by cash
5a. OBTAIN the signature of the person receiving the
cash plus the word ‘PAID’ on the Invoice.
If credit purchase
5b. INSTRUCT the vendor to send the Invoice to the
Company marked ‘Attention Accounts’.
Vendor 5c. SHOW the order number on the Invoice and send it to
the company as requested.
Accountant 6. on receipt of invoice 35
check with purchaser to make sure that items have
been received and note this on the invoice.
Account -----------------
Executive
7. SEND documents to Cover Note Clerk.
8. if invoice set has been produced
8a. ENTER Invoice Number in the Cover Note Control
Register.
8b. DELETE the entry from the Invoice Set Pending List.
8c. REMOVE photocopy of draft invoice from file and
destroy it.
9. if invoice set has not been produced
9a. ENTER Cover Note details in the Cover Note Control
Register.
9b. RECORD the Invoice in the Invoice Set Pending List.
9c. FILE photocopy of draft invoice in the Invoice Pending
File.
10. PREPARE Cover Expiry Record (Form No. 45) in
duplicate.
11. FILE original of the Cover Expiry Record in the Register
36 Box in expiry date sequence.
Records -----------------
Controller
4. SORT documents by subject.
5. EXTRACT appropriate Keyword File from cabinet and
place documents in strict date order with latest date on
top.
5a. If there is no Keyword File in existence for the subject,
switch to subroutine
go to Procedure 09-08-13.
6. RETURN the Keyword File immediately to the cabinet
and process the next set of documents as outlined above.
Cashier -----------------
37
10. CIRCULATE cash receipts to Account Managers.
Manager 11. RETRIEVE appropriate record from file.
11a. if renewal of policy
handling problem 9a. If the item cannot be identified from the description
exception given on the order, refer the matter to the Technical
Supervisor.
The same article called attention to the fact that the “penny”
papers of England were really two-cent papers. The Sun’s price had
been announced as “one penny” on the earliest numbers, but on
October 8, when it was a little more than a month old, the legend
was changed to read “Price one cent.”
From the Collection of Charles Burnham
The Sun ran its first serial in the third month of its existence.
This was “The Life of Davy Crockett,” dictated or authorized by the
frontiersman himself. It must have been a relief to the readers to get
away from the usual dull reprint from foreign papers that had been
filling the Sun’s first page. In those days the first pages were always
the dullest, but Crockett’s lively stories about bear-hunts enlivened
the Sun.
Other celebrities were often mentioned. Aaron Burr, now old and
feeble, was writing his memoirs. Martin Van Buren had taken
lodgings at the City Hotel. The Siamese Twins were arrested in the
South for beating a man. “Mr. Clay arrived in town last evening and
attended the new opera.” This was “Fra Diavolo,” in which Mr. and
Mrs. Wood sang at the Park Theatre. “It is said that Dom Pedro has
dared his brother Miguel to single combat, which has been refused.”
A week later the Sun gloated over the fact that Pedro—Pedro I of
Brazil, who was invading Portugal on behalf of his daughter, Maria da
Gloria—had routed the usurper Miguel’s army.
On December 5, 1833, the Sun printed the longest news piece it
had ever put in type—the message of President Jackson to the
Congress. This took up three of the four pages, and crowded out
nearly all the advertising.
On December 17, in the fourth month of its life, the Sun
announced that it had procured “a machine press, on which one
thousand impressions can be taken in an hour. The daily circulation
is now nearly FOUR THOUSAND.” It was a happy Christmas for Day
and Wisner. The Sun surely was shining!
The paper retained its original size and shape during the whole
of 1834, and rarely printed more than four pages. As it grew older, it
printed more and more local items and developed greater interest in
local affairs. The first page was taken up with advertising and
reprint. A State election might have taken place the day before, but
on page 1 the Sun worshippers looked for a bit of fiction or history.
What were the fortunes of William L. Marcy as compared to a two-
column thriller, “The Idiot’s Revenge,” or “Captain Chicken and
Gentle Sophia”?
The head-lines were all small, and most of them italics. Here are
samples:
INGRATITUDE OF A CAT.
PERSONALITY OF NAPOLEON.
WONDERFUL ANTICS OF FLEAS.
BROUGHT TO IT BY RUM.
The news paragraphs were sometimes models of condensation:
The Sun, although read largely by Jacksonians, did not take the
side of any political party. It favoured national and State economy
and city cleanliness. It dismissed the New York Legislature of 1834
thus:
Nothing more. If the readers wanted more they could fly to the
ample bosoms of the sixpennies; but apparently they were satisfied,
for in April of 1834 the Sun’s circulation reached eight thousand, and
Colonel Webb, of the Courier and Enquirer, was bemoaning the
success of “penny trash.” The Sun replied to him by saying that the
public had been “imposed upon by ten-dollar trash long enough.”
The Journal of Commerce also slanged the Sun, which promptly
announced that the Journal was conducted by “a company of rich,
aristocratical men,” and that it would take sides with any party to
gain a subscriber.
The influence of Partner Wisner, the Abolitionist, was evident in
many pages of the Sun. On June 23, 1834, it printed a piece about
Martin Palmer, who was “pelted down with stones in Wall Street on
suspicion of being a runaway slave,” and paid its respects to
Boudinot, a Southerner in New York who was reputed to be a tracker
of runaways. It was he who had set the crowd after the black:
During the anti-abolition riots of that year the Sun took a firm
stand against the disturbers, although there is little doubt that many
of them were its own readers.
The paper made a vigorous little crusade against the evils of the
Bridewell in City Hall Park, where dozens of wretches suffered in the
filth of the debtors’ prison. The Sun was a live wire when the cholera
re-appeared, and it put to rout the sixpenny papers which tried to
make out that the disease was not cholera, but “summer complaint.”
Incidentally, the advertising columns of that day, in nearly all the
papers were filled with patent “cholera cures.”
The Sun had an eye for urban refinement, too, and begged the
aldermen to see to it that pigs were prevented from roaming in City
Hall Park. In the matter of silver forks, then a novelty, it was more
conservative, as the following paragraph, printed in November, 1834,
would indicate:
EXTREME NICETY—The author of the “Book of Etiquette,”
recently printed in London, says: “Silver forks are now
common at every respectable table, and for my part I cannot
see how it is possible to eat a dinner comfortably without
them.” The booby ought to be compelled to cut his beefsteak
with a piece of old barrel-hoop on a wooden trencher.
On the following day the True Sun title was entirely missing, and
its absence was explained in an editorial article as follows:
A day later (June 24, 1835) the Sun declared that in establishing
the True Sun “Short, who is one of the printers of the Messenger,
actually purloined the composition of his reading matter”; and it
printed a letter from William Burnett, publisher of the Weekly
Messenger, to support its charge of larceny.
On June 28, six days after the True Sun’s first appearance, the
Sun announced the failure of the pretender. The True Sun’s
proprietors, it said, “have concluded to abandon their piratical
course.”
Another True Sun was issued by Benjamin H. Day in 1840, two
years after he sold the Sun to Moses Y. Beach. A third True Sun,
established by former employees of the Sun on March 20, 1843, ran
for more than a year. A daily called the Citizen and True Sun, started
in 1845, had a short life.
When a contemporary did not fail the Sun poked fun at it:
A few weeks later, when Attree, who had left the Transcript to
write “horribles” for the Courier, was terribly beaten in the street,
the Sun denounced the assault and tried to expose the assailants.
In February, 1835, a few days after the indictment of the
partners, Mr. Wisner was challenged to a duel by a quack dentist
whose medicines the Sun had exposed. The Sun announced
editorially that Wisner accepted the challenge, and that, having the
choice of weapons, he chose syringes charged with the dentist’s own
medicine, the distance five paces. No duel!
It would seem that the Sun owners sought a challenge from the
fiery James Watson Webb of the mahogany pistol, for they made
many a dig at his sixpenny paper. Here is a sample:
T HE man whom Day met at the murder trial in White Plains was
Richard Adams Locke, a reporter who was destined to kick up
more dust than perhaps any other man of his profession. As he comes
on the stage, we must let his predecessor, George W. Wisner, pass into
the wings.
Locke was nine years older than Poe, who at this time had most of
his fame ahead of him. Poe was quick to recognize the quality of
Locke’s writings; indeed, the poet saw, perhaps more clearly than
others of that period, that America was full of good writers—a fact of
which the general public was neglectful. This was Poe’s tribute to
Locke’s literary gift:
LATELY MADE
BY SIR JOHN HERSCHEL, LL.D., F.R.S., &c.
After solemnly dwelling on the awe which mortal man must feel
upon peering into the secrets of the sky, the article declared that Sir
John “paused several hours before he commenced his observations,
that he might prepare his own mind for discoveries which he knew
would fill the minds of myriads of his fellow men with astonishment.” It
continued:
And well might he pause! From the hour the first human
pair opened their eyes to the glories of the blue firmament
above them, there has been no accession to human knowledge
at all comparable in sublime interest to that which he has been
the honored agent in supplying. Well might he pause! He was
about to become the sole depository of wondrous secrets which
had been hid from the eyes of all men that had lived since the
birth of time.
It cannot be said that the whole town buzzed with excitement that
day. Perhaps this first instalment was a bit over the heads of most
readers; it was so technical, so foreign. But in Nassau and Ann Streets,
wherever two newspapermen were gathered together, there was
buzzing enough. What was coming next? Why hadn’t they thought to
subscribe to the Edinburgh Journal of Science, with its wonderful
supplement?
Nearly four columns of the revelations appeared on the following
day—August 26, 1835. This time the reading public came trooping into
camp, for the Sun’s reprint of the Journal of Science supplement got
beyond the stage of preliminaries and predictions, and began to tell of
what was to be seen on the moon. Scientists and newspapermen
appreciated the detailed description of the mammoth telescope and the
work of placing it, but the public, like a child, wanted the moon—and
got it. Let us plunge in at about the point where the public plunged:
So, at last, the people of earth knew something concrete about the
live things of the moon. Goats with beards were there, and every New
Yorker knew goats, for they fed upon the rocky hills of Harlem. And the
moon had birds, too:
At this point clouds intervened, and the Herschel party had to call it
a day. But it had been a big day, and nobody who read the Sun
wondered that the astronomers tossed off “congratulatory bumpers of
the best ‘East India particular,’ and named this place of wonders the
Valley of the Unicorn.” So ended the Sun story of August 26, but an
editorial paragraph assured the patrons of the paper that on the
morrow there would be a treat even richer.
What did the other papers say? In the language of a later and less
elegant period, most of them ate it up—some eagerly, some grudgingly,
some a bit dubiously, but they ate it, either in crumbs or in hunks. The
Daily Advertiser declared: