How to Use 'Explain Me' for Work Tasks: Step-by-Step Breakdown
The 'Explain Me' tool helps you understand a topic when you need not just a definition, but a comprehensible explanation tailored to a specific preparation level. In this article, we will explore how to apply it to a work process using a fictional scenario: an employee receives a task that needs to be passed to a colleague or a newcomer. You will learn how to formulate a request, check the result, and understand where the tool may err. We will not promise that the explanation will always be perfect, but we will show how to make it useful.
Open tool: Topic explainer ↗What the Tool Actually Does
"Explain Me" is a text tool that accepts two fields: "Your text or idea" and "Audience or experience level". Upon output, you receive one explanation in the chosen language, including an example and a short comprehension check. This is not a chat or an editor: you fill out the form, press the button, and the result appears in a separate panel. It can be copied or downloaded as a plain text TXT file.
The tool cannot work with documents, does not perform batch processing, and does not automatically save results. It is not suitable for generating images, audio, or video - it is purely a text task. If you need to explain a process that consists of steps, it is better to describe it immediately in the first field. The more specific the input, the more useful the output.
Important to remember: the model may err, and queue and availability may change. Therefore, the result is worth checking, especially if it concerns work instructions, where an error can lead to a failure.
In the "Your text or idea" field: "Vacation approval process in a department: an employee submits an application, the manager checks the schedule, HR enters the data." In the "Audience" field: "New employee without experience." Result: a step-by-step explanation with an example and a comprehension question.
How to Prepare Input Data
The first field accepts up to 8000 characters, the second up to 1000 characters. This is enough to describe a process or idea. You do not need to write code or insert large tables: the tool works with plain text. It is better to break the description into logical blocks: what happens, who is involved, what constraints exist.
In the second field, specify the audience as precisely as possible. "Beginner" is too general. "Intern seeing this process for the first time" or "Experienced employee, but from another department" will give a more appropriate level of detail. If the audience is not specified, the explanation may turn out to be either too simple or overloaded.
Do not add irrelevant details to the request. The tool does not analyze your files and does not search for information on the Internet. It relies only on what you wrote. Therefore, if there is an important exception in the process, it is better to mention it right away.
Poor request: "Make an explanation." Good request: "Explain the weekly report process: data collection from CRM, error checking, sending to the manager. Audience - an employee who has never worked with CRM before."
Practical Scenario: Passing a Task to a Colleague
Imagine a fictional situation: you are going on vacation and must pass a colleague a task of preparing a monthly report. The colleague has a general idea, but does not know the details. You open "Explain Me" and describe the process: which data to take, where to check, who to send it to. In the audience field, you indicate "a colleague familiar with reports, but not with this specific one." The tool outputs an explanation with steps and an example.
The received text can be used as a draft instruction. It does not replace the official regulation, but helps quickly structure thoughts. Check that all steps are present, there are no missing exceptions. If something is omitted, add it to the original request and generate again.
Such an approach saves time on composing an explanation from scratch. But remember: the tool does not know your internal rules unless you describe them. It cannot check if the process corresponds to reality. Responsibility for accuracy remains with you.
Request: "Task transfer: monthly report. Steps: extract data from CRM for the month, reconcile with expense table, fill template, send for review to the manager before the 5th. Audience: a colleague familiar with reports, but not with this process." Result: an explanation with an example and a question "What step should be performed before sending the report to the manager?"
How to Check the Result
After generation, read the explanation in full. Make sure it corresponds to your audience: are there too complex terms or, conversely, unnecessary simplifications. Check if there is an example and a comprehension check. If the comprehension check is formulated vaguely, this may be a sign that the request was not specific enough.
Compare the explanation with your original description. Are all key steps reflected? Are there added details that you did not indicate? The model may guess, so it is important to filter out fictional facts. If the explanation contains steps unfamiliar to you, do not use them without verification.
The comprehension check is not a test with a grade, but a question that helps ensure the reader grasped the essence. You can use it as the basis for a short survey or self-check. If the question seems inappropriate, reformulate the request and try again.
After generation you see a question: "Which step should be performed before sending the report to the manager?" This is useful if you are passing a task. But if the question is unrelated, it means the request lacked context.
Limitations and Typical Errors
The tool does not work with files, does not export to DOCX or PDF, and does not save history. It is not suitable for tasks where you need to compare several variants or edit already generated text. If you need to edit an explanation, you will have to copy it into another editor.
Do not use "Explain Me" for financial, medical, or legal consultations. It can give a general explanation, but it does not replace a specialist. In such topics, it is better to limit yourself to educational purposes and not rely on the result as a guide to action.
Another error - too long or vague request. If you write 8000 characters of unstructured text, the result may be superficial. Better to break the topic into parts and generate explanations separately. Also, do not expect the tool to remember previous requests: each time it starts with a clean slate.
A user enters: "Explain everything about work." The result will be general. If you enter: "Explain how to approve a purchase of office supplies: application, budget check, approval by the manager. Audience - a new employee," the explanation will be specific.
How to Adapt the Explanation to Different Levels
The same process can be explained differently. For a beginner, simple steps and minimum terms are important. For an experienced employee, focus on exceptions and nuances. By changing the "Audience or experience level" field, you get different versions. This is convenient if you need to prepare materials for different groups.
For example, for an intern the explanation will contain more explanations and examples. For a manager - a brief description with key control points. Do not be afraid to generate several variants and choose the best one. It will not take much time, as each request is processed separately.
If you are not sure which level to choose, start with the simplest. Then complicate the request, adding details. Thus you will understand which option is better suited for your task. The main thing is not to overload the input data with unnecessary information.
For a beginner: "Explain how to fill out a vacation request: enter the system, select dates, send to the manager." For a manager: "Describe the vacation approval process from the point of view of control: schedule check, approval, HR notification."
"Explain Me" is a useful tool for quickly creating comprehensible explanations based on your source data. It does not replace an expert and does not guarantee error-free output, but helps structure information and adapt it to the audience. Use it for work processes, training, and task transfer, but always check the result. Remember the limitations: text only, no files and no automatic saving. If you follow the described steps, you will be able to receive practical explanations that will save time and help colleagues understand the task faster.
Open tool: Topic explainer ↗Interface translations are machine-assisted and may need refinement.