Basic Web Literacy

A practical reference for everyday use

Overview
This handbook presents the subject as a series of short, focused chapters. Each chapter introduces one
concept, outlines practical principles, provides an application exercise, and includes review questions
for independent study.

Topics
How the web works • Web browsers • URLs • Domain names • DNS overview • HTTP and HTTPS •
Web pages • Links • Search engines • Search queries • Source evaluation • Advertising • ...

Page 1
1. How the web works
How the web works can be approached effectively by using a simple and repeatable method. This
chapter introduces the purpose of how the web works, explains practical considerations, and provides a
short exercise for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about how the web works.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which how the web works matters. Describe the starting point, the
desired outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 2
2. Web browsers
Web browsers can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of web browsers, explains practical considerations, and provides a short
exercise for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about web browsers.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which web browsers matters. Describe the starting point, the desired
outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 3
3. URLs
URLs can be approached effectively by using a simple and repeatable method. This chapter introduces
the purpose of urls, explains practical considerations, and provides a short exercise for applying the
idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about urls.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which urls matters. Describe the starting point, the desired outcome, and
three possible actions. Compare the actions by effort, reliability, and ease of maintenance. Select one
and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 4
4. Domain names
Domain names can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of domain names, explains practical considerations, and provides a short
exercise for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about domain names.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which domain names matters. Describe the starting point, the desired
outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 5
5. DNS overview
DNS overview can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of dns overview, explains practical considerations, and provides a short exercise
for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about dns overview.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which dns overview matters. Describe the starting point, the desired
outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 6
6. HTTP and HTTPS
HTTP and HTTPS can be approached effectively by using a simple and repeatable method. This
chapter introduces the purpose of http and https, explains practical considerations, and provides a short
exercise for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about http and https.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which http and https matters. Describe the starting point, the desired
outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 7
7. Web pages
Web pages can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of web pages, explains practical considerations, and provides a short exercise
for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about web pages.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which web pages matters. Describe the starting point, the desired
outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 8
8. Links
Links can be approached effectively by using a simple and repeatable method. This chapter introduces
the purpose of links, explains practical considerations, and provides a short exercise for applying the
idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about links.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which links matters. Describe the starting point, the desired outcome, and
three possible actions. Compare the actions by effort, reliability, and ease of maintenance. Select one
and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 9
9. Search engines
Search engines can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of search engines, explains practical considerations, and provides a short
exercise for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about search engines.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which search engines matters. Describe the starting point, the desired
outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 10
10. Search queries
Search queries can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of search queries, explains practical considerations, and provides a short
exercise for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about search queries.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which search queries matters. Describe the starting point, the desired
outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 11
11. Source evaluation
Source evaluation can be approached effectively by using a simple and repeatable method. This
chapter introduces the purpose of source evaluation, explains practical considerations, and provides a
short exercise for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about source evaluation.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which source evaluation matters. Describe the starting point, the desired
outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 12
12. Advertising
Advertising can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of advertising, explains practical considerations, and provides a short exercise
for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about advertising.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which advertising matters. Describe the starting point, the desired
outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 13
13. Tracking
Tracking can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of tracking, explains practical considerations, and provides a short exercise for
applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about tracking.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which tracking matters. Describe the starting point, the desired outcome,
and three possible actions. Compare the actions by effort, reliability, and ease of maintenance. Select
one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 14
14. Cookies
Cookies can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of cookies, explains practical considerations, and provides a short exercise for
applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about cookies.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which cookies matters. Describe the starting point, the desired outcome,
and three possible actions. Compare the actions by effort, reliability, and ease of maintenance. Select
one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 15
15. Browser storage
Browser storage can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of browser storage, explains practical considerations, and provides a short
exercise for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about browser storage.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which browser storage matters. Describe the starting point, the desired
outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 16
16. Privacy controls
Privacy controls can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of privacy controls, explains practical considerations, and provides a short
exercise for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about privacy controls.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which privacy controls matters. Describe the starting point, the desired
outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 17
17. Downloads
Downloads can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of downloads, explains practical considerations, and provides a short exercise
for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about downloads.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which downloads matters. Describe the starting point, the desired
outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 18
18. File types
File types can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of file types, explains practical considerations, and provides a short exercise for
applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about file types.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which file types matters. Describe the starting point, the desired outcome,
and three possible actions. Compare the actions by effort, reliability, and ease of maintenance. Select
one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 19
19. Online forms
Online forms can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of online forms, explains practical considerations, and provides a short exercise
for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about online forms.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which online forms matters. Describe the starting point, the desired
outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 20
20. Account creation
Account creation can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of account creation, explains practical considerations, and provides a short
exercise for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about account creation.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which account creation matters. Describe the starting point, the desired
outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 21
21. Authentication
Authentication can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of authentication, explains practical considerations, and provides a short
exercise for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about authentication.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which authentication matters. Describe the starting point, the desired
outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 22
22. Phishing pages
Phishing pages can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of phishing pages, explains practical considerations, and provides a short
exercise for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about phishing pages.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which phishing pages matters. Describe the starting point, the desired
outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 23
23. Browser extensions
Browser extensions can be approached effectively by using a simple and repeatable method. This
chapter introduces the purpose of browser extensions, explains practical considerations, and provides a
short exercise for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about browser extensions.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which browser extensions matters. Describe the starting point, the
desired outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 24
24. Updates
Updates can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of updates, explains practical considerations, and provides a short exercise for
applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about updates.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which updates matters. Describe the starting point, the desired outcome,
and three possible actions. Compare the actions by effort, reliability, and ease of maintenance. Select
one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 25
25. Public computers
Public computers can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of public computers, explains practical considerations, and provides a short
exercise for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about public computers.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which public computers matters. Describe the starting point, the desired
outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 26
26. Mobile browsing
Mobile browsing can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of mobile browsing, explains practical considerations, and provides a short
exercise for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about mobile browsing.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which mobile browsing matters. Describe the starting point, the desired
outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 27
27. Accessibility
Accessibility can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of accessibility, explains practical considerations, and provides a short exercise
for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about accessibility.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which accessibility matters. Describe the starting point, the desired
outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 28
28. Troubleshooting
Troubleshooting can be approached effectively by using a simple and repeatable method. This chapter
introduces the purpose of troubleshooting, explains practical considerations, and provides a short
exercise for applying the idea in a realistic situation.

Practical principles

• Identify the specific outcome you want before making decisions about troubleshooting.

• Use a consistent process so that results can be compared and improved over time.

• Reduce unnecessary complexity when a simpler method provides the same useful result.

• Review the result and record important changes, especially when the process will be repeated.

Application exercise

Consider a normal situation in which troubleshooting matters. Describe the starting point, the desired
outcome, and three possible actions. Compare the actions by effort, reliability, and ease of
maintenance. Select one and define how you would verify that it produced the intended result.

Points to remember

A procedure is useful only when it can be understood and repeated. Avoid relying on assumptions that
have not been checked, changing several things at once, or adding complexity without a clear benefit.
Periodic review helps keep a system relevant as requirements change.

Review questions

Question Check

Is the intended outcome clearly defined? Yes / Review

Can the process be repeated consistently? Yes / Review

Is unnecessary complexity being avoided? Yes / Review

Can the final result be verified? Yes / Review

Page 29