49. Service vs. Documentation vs. Support

The paradox is:

• Build a service that doesn’t require documentation.
• Create documentation that doesn’t require support.

Prevent your user from falling down this staircase.

The cost increases as the user falls.

Frustration does too.