Last Update
22 October 2003
11 September 2001
/2003 PCD Awards
PCD Solutions Category
SUBMISSION FORM
PCD Solutions are intrinsic or embedded and exclusively focused on the business performance outcome in measurable ways. For example, a PCD Outcome that replaces the interface of an enterprise application such that (a) the frequency of data entry errors is reduced; (b) the frequency of incomplete information entered into the system is reduced; (c) the speed with which data is entered is substantially increased; and (d) the need for any form of learning in advance of doing is eliminated is Performance Centered.
(Please replace italicized text with content specific to your entry.)
Entry Title
|
Enter here
|
Submitted by:
|
Enter organization name here
|
Contact Name:
|
Enter here
|
Phone:
|
Enter here
|
E-mail:
|
Enter here
|
Address:
|
Enter here
Enter here
|
Logo:
|
Please us a small graphic file
|
|
|
Purpose:
|
Insert a brief overview description of your PCD Solution and the business performance issue it is meant to address.
|
|
|
Solution:
|
Provide a detailed description of the overall design and/or specific components. Explain how the system supports business and user performance. For example, does it reduce the amount of business knowledge performers require before they can perform the function and, if so, how does it do this? Include any supporting graphics, screen shots, animation, or the like here so that we can see the supporting material. If online access is restricted, provide six (6) user IDs and passwords. You may assume that the judges will be using IE5.x or above to view your entry. Be sure to note any plug-ins required and the details for obtaining them if not automatically provided. Your Solution information - including the samples provided - should focus on PCD attributes, including (but not necessarily restricted to):
 Supports performers through best practice processes. Establishes, or aids in establishing, goals. Minimizes terminology translation or interpretation. Provides access to supporting and learning resources. Focuses on task(s), processes, and the natural flow of work. Reduces or eliminates the need for training/learning. Supports performance FIRST, and learning only as a secondary consequence of doing. Stretches the PCD paradigm. |
|
|
Further details (optional):
|
Use this section to provide further details and specifics of how the solution reflects certain PCD attributes. Elaborate on one or more of the attributes if there is clear evidence to support claims (studies, measurements, well-documented anecdotes, etc.).
|
|
1. Supports performers through best practice processes.
|
|
Synthesizes best practice behavior from multiple outstanding performers and incorporates best business practices or desired business practices that are not currently in place (as identified by business management). Automates when possible and appropriate. Stimulates performers through language, sequencing and other cues that prompt or enable what to do when (based on stored data, information, and performer input). Creates deliverables using best practice form, content, language and style.
|
|
2. Establishes, or aids in establishing, goals.
|
|
Includes explicit functions, elements, or components for the performer to select appropriate goals, presents relevant goals to the performer based on stored data/information or based on how performers have selected from among goals appropriate to the context, or re-directs performers toward only the most appropriate goals for the context. Describes goal outcomes and delineates conditions, considerations, and/or criteria for selecting a goal.
Helps performers establish what they can do, want to do, or where to go, based on stored data/information.
|
|
3. Minimizes terminology translation or interpretation.
|
|
Uses commonly understood terminology and descriptors rather than technically correct but obscure language that requires deep understanding of the domain or an unreasonable memory burden. If the performer interacts with others (customers, suppliers, work groups), the system facilitates use of language familiar to all, and which does not require them to interpret unfamiliar jargon.
Minimizes cognitive burden associated with interpreting terms of the content domain or software interface.
Calls a duck a duck.
|
|
4. Provides access to supporting and learning resources.
|
|
Integrates and makes visible support resources to further explain, illustrate or provide examples/non-examples about information, goals, outcomes, data, terminology, graphics, etc. that appear on the primary display. Support resources might include things like explanations, tips, examples, counterexamples, demonstrations, advice, walk-throughs (e.g. step-by-step explanation graphs, illustrations, procedures, processes, etc.), procedural steps, process diagrams, intelligent agents, system messages (aka error messages, dialogues), and exposing underlying logic.
These resources may be layered to accommodate performer diversity and/or to support the natural flow of work (i.e., resources are in support of criterion #5).
Support resources are represented in their most powerful form to achieve understanding, learning or task performance (e.g. a voice-narrated demonstration is more powerful than a procedural list when explaining a system interaction task; visual task models are more powerful than text descriptions; grids/tables are more powerful than text in paragraphs Support resources are not merely collections of reference material made available to the performer, but explicitly support or enable the other PCD criteria.). For example, support resources may appear in the interface to help the performer establish a goal or move the performer through the proper flow of work.
|
|
5. Focuses on task(s), processes, and the natural flow of work.
|
|
Uses task models and/or sequencing to facilitate best practice work performance by performers. Performers need not have internalized the task model and sequencing in advance to successfully perform the work. Data input, retrieval and manipulation are presented within the task context rather than as the primary focus of the system or as items that the performer is burdened with identifying or retrieving once the task context is identified. That is, the system can not require that the task model, data transformation, and navigation sequences be in the performer's head in advance with data-entry the only real goal of the system.
Task sequencing is more than simply navigating through various data screens. Task language, goals, and related resources are incorporated into the work-flows.
Reflects and/or accommodates the way work naturally occurs, thus supporting other PCD criteria (e.g., presents relevant data and tools to accomplish a goal at the proper point in the workflow). Does not merely instruct the performer of which sequence to navigate, but facilitates proper navigation. Passively constrains the performer to a flow or process in cases of high risk, or re-directs / suggests best alternatives when risk is low. Generates deliverables automatically (e.g. file notes, communications, purchase orders, etc.).
|
|
6. Reduces or eliminates the need for training/learning.
|
|
Even if the design basis of the solution is learning or reference, its PCD characteristics should reduce or eliminate the need for training/learning in advance of performing the supported task. Visual representations of quantities, actions, components, and physical affects/dynamics can instantly communicate vital information that enables task completion without the need for lengthy explanations. The use of metaphor, task sequencing, redirection, passive constraint, and embedded workflow can ensure speedy and accurate task completion without deliberation, hesitation, or extensive conceptual activity.
Reducing or eliminating training means that the flow of work/process, the information essential to getting the task done, and the specific human factors of the performer are orchestrated such that all three are optimal and overlap. Maximum results are attained with minimal cognitive effort because proper sequencing of events is facilitated, human preferences are anticipated or accommodated, and support for decisions presents itself immediately. The maximum amount of complexity of the task enabling tool is eliminated, leaving the performer free to synthesize business or organizational issues necessary to complete the task. If learning is at all necessary, it occurs as a secondary consequence of performing the task.
|
|
7. Supports performance FIRST, and learning only as a secondary consequence of doing.
|
|
The three essential elements of performance are process flow, human factors/diversity, and pertinent information/knowledge. All three elements are considered and optimized in the interaction domain of the work if performance is truly supported. If process steps are left to the performer to discover, then performance is not supported. If translation or calculations that could otherwise be accommodated by the interface are left to the performer, then performance is not supported. If the performer has to break the task context to obtain information vital to the task by clicking, navigating, or scrolling, then performance is not supported. If the performer population is visually oriented and learns kinesthetically, then a user interface that is primarily static and textual does not support performance.
Your solution's characteristics should exhibit that process flow/workflow is reflected and supported in the solution, that the human factors of performer personas are consistently represented, and that essential data, information, and knowledge are present. All three elements should work synergistically to ensure performance with minimal learning, cognitive burden, assistance, etc. Any learning elements of the solution must be essentially passive, meaning that learning takes place as a secondary consequence of doing. For example, performance-centered solutions are often inferred from visual representations of complex business rules. The task is completed first by observing graphical representations, and over time an explicit understanding of rules is developed.
|
|
8. Stretches the PCD/EPSS paradigm.
|
|
By its forward-looking, anticipatory nature, this criterion defies concrete description. In essence, the judges wish to be pleasantly surprised by clever design or application of performance-centered design principles in novel domains. For instance…
It achieves profound, focused results with elegance, meaning that a great deal is accomplished by a performer who expends little effort and encounters minimal cognitive challenges as goals are established and accomplished. (Example: Completing a total sales transaction in one or two clicks.)
It is self-contained, with high levels of integration of all elements required for successful work performance by very experienced through very inexperienced personnel. Appropriate constructs come to performer, regardless of competence / level of experience, without the performer having to make context- and experience-specific choices.
Changes dynamically to accommodate changes in business climate, organizational knowledge and strategy, and wisdom with a minimum of programmer intervention. At the very least, it does not have to wait for the next release to respond to and accommodate business dynamics.
Continuously captures and incorporates task structuring, knowledge, data, tools and communications. Represents each element in its most powerful form; e.g., highly visual, relationships are clear, language is natural.
Incorporates powerful, clever metaphors that enable many concepts, procedures, steps, and pieces of information to be assimilated and applied to the goal immediately and without confusion. Anticipates and accommodates changing requirements of performers and business.
Surprises the performer with its richness, representation and power. Is always self-revealing, regardless of how sophisticated the tasks it supports. Makes life very easy for performers.
By its forward-looking, anticipatory nature, this criterion defies concrete description. In essence, the judges wish to be pleasantly surprised by clever design or application of performance-centered design principles in novel domains. For instance…
It achieves profound, focused results with elegance, meaning that a great deal is accomplished by a performer who expends little effort and encounters minimal cognitive challenges as goals are established and accomplished. (Example: Completing a total sales transaction in one or two clicks.)
It is self-contained, with high levels of integration of all elements required for successful work performance by very experienced through very inexperienced personnel. Appropriate constructs come to performer, regardless of competence / level of experience, without the performer having to make context- and experience-specific choices.
Changes dynamically to accommodate changes in business climate, organizational knowledge and strategy, and wisdom with a minimum of programmer intervention. At the very least, it does not have to wait for the next release to respond to and accommodate business dynamics.
Continuously captures and incorporates task structuring, knowledge, data, tools and communications. Represents each element in its most powerful form; e.g., highly visual, relationships are clear, language is natural.
Incorporates powerful, clever metaphors that enable many concepts, procedures, steps, and pieces of information to be assimilated and applied to the goal immediately and without confusion. Anticipates and accommodates changing requirements of performers and business.
Surprises the performer with its richness, representation and power. Is always self-revealing, regardless of how sophisticated the tasks it supports. Makes life very easy for performers.
|
|
|
Prior State:
|
Insert a description of the processes and/or system(s) that were previously used to perform the function that your software now supports. If a system was used to perform this function, please consider including a screen shot of it.
|
|
|
User Profile:
|
Insert a profile of typical users; their skills, education level, job experience and business knowledge. Did this profile change as a result of implementing the PCD Solution? If so, please explain how.
|
|
|
Results:
|
Insert a summary of any performance improvement data you may have collected. For example, this might include information about reductions in errors, training time, or the time it takes to perform specific tasks.
|
Other Evidence:
|
Describe anything else that contributes to your submission being an exceptional and/or innovative PCD Solution entry.
|
|
|
NOTES AND REMINDERS
|
|
Fees:
|
Please enclose your non-refundable US $350 entry fee in the form of a check made out to EPSScentral LLC, or organize payment through PayPal (www.paypal.com).
Should your entry win an award, you are responsible for all additional costs associated with attending the conference, awards presentation, and demonstration session at Online Learning 2003 in Los Angeles.
|
|
|
Permission to Publish
|
Entering the competition constitutes permission to publish your submission on the web. Please signify your understanding and acceptance of this requirement by signing the publication release form.
|
|
|
Submission details:
|
Please provide:
6 copies of your HTML submission using the above template 6 copies of any supporting media to provide judges with a live experience (URL, CD, Video, DVD). If you are providing a secure link, please provide 6 (six) logins and passwords. Your non-refundable check for $350.00 made out to EPSScentral LLC, or the equivalent transaction completed via PayPal. Your signed permission form (see below). Send to:
2003 PCD Awards
c/o EPSScentral LLC
6909 Pacific Lane
Annandale, VA 22003-5936
All materials must be postmarked by July 15, 2003. If paying via PayPal, transaction must be complete by July 15, 2003.
|
Information:
|
Contact Gary Dickelman at:
703-622-9747
gdickelman@epsscentral.com
|
Permission to publish:
Please print this section, sign, date, and include the hard copy with your submission.
|
PUBLICATION RELEASE FORM
Please print, sign, date, and mail the release form with your entry.
Entry Title:
Submitted by:
Contact Name:
Phone:
E-mail:
Address:
I hereby grant permission to the 2003 PCD Awards administrators and sponsors to publish my entry in whole or in part, in electronic or print media, with attribution. Publication purposes include sharing news of the competition's results and providing inspirational models of innovative performance-centered designs to further interest in, and development of, the field of Performance-Centered Design.
Signed: _______________________________________
Date: __________________
|
|
|