Standards or Chaos

1. Standards or Chaos Doug Higby

2. What is a standard? • Something established by authority, custom, or general consent as a model or example

3. What kind of IT standards exist in our diverse organization? • Authority • Website policy • Customs (de facto) • doc files (changing) • General Consent • Unicode, USFM

4. Types of Standards Standard procedures Interoperability standards Hardware Operating System Software

5. Often standards are field-driven

6. The Benefits of Standards Compelling reasons to adopt a defined standard or model Modified by Heidi Rosendall from original Powerpoint created by Doug Higby Adapted from The Benefits of Standard IT Governance Frameworksby George Spafford of Datamation

7. Benefit 1. The Wheel Exists • Many people want to find their own way, unaware that a standard solution already exists. • Time is a precious commodity. • OK, so creating databases is fun, but is it a wise use of time when someone else has already done it?

8. Benefit 2. Structure Standards provide a structure that we can follow, enabling us to know what is expected and to work more efficiently.

9. Benefit 3. Best Practices Best Practices are the result of people following imperfect standards. In this way, the standard evolves. The level of experience reflected in a best practice standard can not be matched by any single individual’s efforts. Good documentation usually follows.

10. Benefit 4. Knowledge Sharing • Standards foster the sharing of ideas. • The wider the usage of a standard, the more cross-fertilization that takes place. • FLEx, now on Google groups for wider participation, WeSay now publishing dictionaries online

11. Benefit 5. Auditable Standards help to measure progress. We are all somebody’s personnel resource. Following standards helps keep us accountable, and helps supervisors ensure progress and quality.

12. Benefit 6. Specialization (added) The more people have to figure out about a process on their own, the less productive they are. Following well-thought-out standards frees people to focus on their own specialized task.

13. Standards = Leadership Adam was watching while Eve ate the forbidden fruit. Were he to have helped her to apply the Standard, we could have avoided this whole mess called sin. In the same way, our own uncertainty can prevent us from providing leadership even when our knowledge is sufficient.

14. Users want Standards! • Users often find multiple options confusing. They don’t want a list of anti-virus programs to choose from. The want the “best” antivirus. • They look to the following sources: • Local IT people • JAARS • Domain consultants • Successful colleagues

15. Users often resist standards Users can feel that standards limit their freedom. Provide GOOD standards and make the benefits well known. Don’t be heavy-handed. Users may feel unwilling or unable to comply with the standard. Again – BENEFITS, but also proper training, encouragement, and consequences.

16. Ingredients for Standard-setting • Global thinking • Our solution could apply on a larger scale. • Team spirit • Others could benefit from what we’re doing • Confidence • We’re certain we have a good system • Determination • We won’t quit when we fail or are criticized. • Optimism • We will focus on the benefits.

17. Examples USFM – Unified Standard Format Marking OXES – MDF – Multi-Dictionary Formatting LIFT – Unicode Paratext Checking before Consultant Checking

18. The 5 Phases of Standard-setting Research Develop Experiment Promote Support

19. Case #1 Toshiba in Nigeria Group

20. Case #2 Heidi’s Typesetting Process

21. Case #3 Keyman

22. Case #4 PNG Phonology Statements

23. What standards do you want to see? What can you do about it?