THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
rodwelch@pacbell.net


S U M M A R Y


DIARY: May 27, 2002 10:22 AM Monday; Rod Welch

Ron Pinder requests permission to use SDS records for article.

1...Summary/Objective
2...User Centered Design Seminar on Software Design Requirements


..............
Click here to comment!

CONTACTS 
0201 - Maskery & Associates                                                                                                                                           O-00000805 0604
020101 - Mr. Ron Pinder                                                                                                                                                   O-00000805 0604

SUBJECTS
Pinder, Ron Article Seminar Author Speaker Requests Permission to Use
Requests Permission to Use SDS Record on Tom Landauer's Book That it
POIMS SDS Record Attractive Marketing Materials Government Agencies A
Article Seminar Author Speaker Requests Permission to Use SDS Record
Permission to Use SDS Record on Tom Landauer's Book That it is Hard f
Seminar Speaker Requests Permission to Use SDS Record on Tom Landauer
IP Intellectual Property SDS Com Metrics POIMS
IP Welch Interests Protected Jack Wants to Work on SDS Has Ideas for
Permission to Use Welch Writing on Internet
Usefulness Utopia SDS Makes Everything Available When Needed Typical
Request Permission to Use SDS Record Content for Article and Seminar

2813 -
2813 -    ..
2814 - Summary/Objective
2815 -
281501 - Follow up ref SDS 21 0000, ref SDS 20 0000.
281502 -
281503 - Received ref DRT 1 0001 from Ron Pinder asking for permission to use
281504 - information from SDS records on the Internet.
281506 -  ..
281507 - Research on Ron Pinder shows there is a company in Ottowa, Canada...
281508 -
281509 -
281510 -                   Maskery & Associates
281511 -
281512 -                      http://www.maskery.ca/
281513 -
281514 -
281515 - ...with a Contact page that lists Ron Pinder, which is also shown in
281516 - Ron's letter today, so this may be where Ron works.
281517 -
281518 -     http://www.maskery.ca/contact.html
281519 - ..
281520 - Ron says in his letter today...
281521 -
281522 -     Found your site doing research on Tom Landauer's book, "The
281523 -     Trouble with Computers". Very much like the way you think.
281524 -     ref DRT 1 0001
281525 -
281526 -     With your permission, I would like to use a few lines you've
281527 -     written in an article and talk for an upcoming conference,
281528 -     properly referenced, ref DRT 1 L45M, of course...
281529 -
281530 -          http://www.foruse.com/2002
281532 -      ..
281533 -     Talk abstract:
281534 -
281535 -          http://www.foruse.com/2002/program.htm#t32
281536 -     ..
281537 -     Point of the talk is that designers focus on usability too
281538 -     much and don't measure or manage for usefulness (ultimate customer
281539 -     value), or clearly bring it into the design process. ref DRT 1
281540 -     T46H
281542 -  ..
281543 - Ron cites a section from the record on 950710 that reviews Tom
281544 - Landauer's book "The Trouble with Computers," ref SDS 7 0585, and then
281545 - comments further that...
281546 -
281547 -     In over 10 years as a practitioner and manager of 'User Centered
281548 -     Design' in a large corporation we have always walked a fine line
281549 -     between 'a solution looking for a problem' and genuine customer
281550 -     value.  It all starts with requirements.  Garbage in garbage out.
281551 -     If there is no true customer value - as in usefulness - captured
281552 -     in the requirements, a useless product or service will almost
281553 -     certainly result, except perhaps by chance.  The communication of
281554 -     requirements is poor at best - and for many of the reasons you
281555 -     describe in 'Communications Metrics'. ref DRT 1 267K
281557 -  ..
281558 - Ron's reference to Com Metrics suggests he has investigated POIMS and
281559 - Com Metrics beyond the record on 950710, although he does not cite any
281560 - further specific references indicating what he may have reviewed.
281561 -
281562 -     Would be interesting to get a list of "reasons" Ron identified in
281563 -     Com Metrics that caught his attention in relation to his work and
281564 -     objectives. Perhaps this will be set out in the article or
281565 -     Powerpoint presentation for the seminar he mentions.
281566 -
281567 -     "Requirements" for technology that augments intelligence are
281568 -     particularly difficult, as opposed to requirements for a lawnmower
281569 -     computer or software program that explain observable activity,
281570 -     because the character of intelligence is hidden from the mind's
281571 -     eye, as explained in the record on 010924. ref SDS 15 NK4J and in
281572 -     more detail later in the same record. ref SDS 15 QN7M  POIMS makes
281573 -     the same point. ref OF 1 MQ6J
281575 -  ..
281576 - Recognition that "usefulenss" is the ultimte arbiter of market
281577 - success, and that product/service "requirements" are critical to
281578 - developing useful technology shows promise of progress, and supports
281579 - recent discussions with Gary about SDS on 010522. ref SDS 22
281580 - 0001
281581 - ..
281582 - Ron continues...
281583 -
281584 -     I hope you are comfortable with us referencing bits of your
281585 -     material and work from your site. ref DRT 1 379L
281586 -
281587 -      1.  Would be helpful to get a listing of specifically what SDS
281588 -          records and/or Welch publications are used and for what
281589 -          purpose....
281590 -
281591 -              http://www.welchco.com/00601.HTM#4460
281593 -           ..
281594 -      2.  Welch work product should be distinguished from Landauer's
281595 -          work, so that Landauer gets full credit and attribution, as
281596 -          shown in the record on 950710, ref SDS 7 0001, which Ron
281597 -          cites in his letter today. ref SDS 0 BQ6H
281598 -          ..
281599 -      3.  SDS work product applying User Centered Design is shown
281600 -          in the record on...
281601 -
281602 -             Empathic design................ 940508, ref SDS 5 6930
281603 -                "      "    ................ 990527, ref SDS 10 6633
281604 -             Human Centered Design.......... 940510, ref SDS 6 3850
281605 -             User Centered Design........... 950710, ref SDS 7 6403
281606 -             UCD applied for project led
281607 -             by Doug Engelbart at SRI....... 001017, ref SDS 12 1575
281609 -  ..
281610 - Ron concludes...
281611 -
281612 -     Do feel free to contact me if you have any questions or concerns.
281613 -     ref DRT 1 484Q
281615 -  ..
281616 - Submitted ref DIT 1 0001 to Ron with copy to Amy Dillon, and linked
281617 - to this record with instructions on using Welch material that
281618 - properly attributes Landauer.  Sent a copy to Tom for reference.
281619 -
281620 -
281621 -
281622 -
281623 -
281624 -
281625 -
2817 -

SUBJECTS
User Centered Design Seminar Talk on Developing Success Metrics that

2903 -
290401 -  ..
290402 - User Centered Design Seminar on Software Design Requirements
290403 -
290404 - Research on the Internet produced an outline for a talk (probably
290405 - Powerpoint-type thing) delivered by the president of Maskery &
290406 - Associates, Helen Maskery, Ph.D. dated 020117. ref OF 4 0001
290407 -
290408 - Ron Pinder is listed as a contributor, along with Amy Dillon,
290409 - ref OF 4 489F, who received a copy of the letter Ron sent today,
290410 - ref DRT 1 00W2, asking for permission to use information from SDS
290411 - records for another presentation, per above. ref SDS 0 0001
290413 -  ..
290414 - This seems like an excellent sales presentation on steps developers
290415 - can take to create software that will be succesful in the market place
290416 - based on user centered design, which Ron mentions in his letter today.
290417 - ref SDS 0 BQ6H
290418 -
290419 - "Success metrics" are mentioned in the presentation, ref OF 4 T95L,
290420 - but thankfully there is not a lot of essoteric mathematics to wade
290421 - through.  Some mathematical analysis, however, might strengthen the
290422 - argument.
290424 -      ..
290425 -     Example of Palm Pilot for success metrics is unclear. ref OF 4
290426 -     Z64I
290428 -  ..
290429 - The presentation explains Palm Pilot delivered anytime, anywhere
290430 - information. ref OF 4 PF9F and ref OF 4 MD5J
290431 -
290432 -     There is no discussion of information overload that requires
290433 -     anytime, anywhere intelligence for converting information into
290434 -     useful knowledge for saving time and money.
290436 -  ..
290437 - The presentation does a good job explaining the challenge of
290438 - delivering added value to customers without requiring people to
290439 - increase skills.
290441 -  ..
290442 - Suppose, however, the aim is to improve underlying skills to think,
290443 - remember and communicate.  How would this presentation help people
290444 - recognize added value of alphabet technology and improving that
290445 - methodology?
290447 -  ..
290448 - Meetings are identified throughout the presentation as a resource for
290449 - applying User Centered Design, for example....
290450 -
290451 -
290452 -    1.  When you're in a development team meeting, everyone can think
290453 -        of ways in which that success metric will help them,
290454 -        ref OF 4 5F4H
290456 -         ..
290457 -        By suggesting product attributes, ref OF 4 LH9M
290459 -         ..
290460 -        By suggesting how to verify the product, ref OF 4 9I4G
290462 -         ..
290463 -        By thinking of alternative way to meet the objective,
290464 -        ref OF 4 AI4K
290466 -         ..
290467 -    2.  What you think the value proposition is? The other project
290468 -        boundaries (schedule, project cost, product cost, etc Done
290469 -        through meetings, one-on-one work sessions, brainstorming
290470 -        sessions, sub-teams, ref OF 4 0P6F
290472 -         ..
290473 -    3.  Develop a view of the "end-to-end process" associated with the
290474 -        product. Frequent project team meetings to ask the questions:,
290475 -        ref OF 4 KQ6O
290476 -
290477 -           Will this "concept" deliver to the success metrics?
290478 -
290479 -           Does it stay within all the other project boundaries?
290481 -         ..
290482 -        Hold meeting with key decision-makers to get OK to proceed to
290483 -        Phase 3 - Build, ref OF 4 QT4I
290485 -  ..
290486 - What does User Centered Design say to do about planning these
290487 - meetings, capturing organizational memory and adding intelligence to
290488 - create intellectual capital in order to make meetings productive?
290489 -
290490 -     For example, on 921021 Frank at JPL in Pasadena, CA advised that
290491 -     team members should hold a lot of meetings to manage NASA projects
290492 -     for sending people to the moon, probes to Mars, and more recently
290493 -     to the International Space Station (ISS); but when asked about
290494 -     managing information developed from the meetings, there are no
290495 -     procedures. ref SDS 2 A252
290497 -      ..
290498 -     This led to a disaster when the Challenger exploded in 1986.
290499 -     ref SDS 2 4499
290501 -      ..
290502 -     Later on 940114 a founder of PMI observed in an article that
290503 -     meetings suffer the poorest productivity of almost any human
290504 -     activity, next to calls and email, yet are indispensible,
290505 -     ref SDS 4 2290, as implied by Maskery's presentation.
290507 -      ..
290508 -     Last year new evidence indicates communication problems in 1986
290509 -     continue on the ISS project, reported on 011006. ref SDS 16 O99K
290511 -      ..
290512 -     Since meetings are important to UCD, how can this method be
290513 -     strengthened by Communication Metrics to add value to customers
290514 -     based on success metrics methodology?
290515 -
290516 -
290517 -
290518 -
290519 -
290520 -
290521 -
290522 -
290523 -
290524 -
290525 -
290526 -
290527 -
290528 -
290529 -
290530 -
290531 -
290532 -
290533 -
290534 -
Distribution. . . . See "CONTACTS"