If you are writing code, you can produce data or "pieces" of information without blocking your main program:

This paper discusses the CAP theorem, which states that it is impossible for a distributed system to simultaneously guarantee consistency, availability, and partition tolerance. The paper also introduces the concept of eventual consistency, which is often used in asynchronous systems.

Depending on your context, here is how you might "produce a piece" of work asynchronically: 1. In Software (Code)

How do you actually function ? It is not simply "send an email instead of calling." That is a tactic. Asynchronicity is a philosophy. It rests on four pillars: