Practice what you want to say before a meeting

A five-minute pre-meeting rehearsal

1. Decide what the listener needs

Complete one sentence:

After I speak, they should understand ________.

Then note any fact that must not disappear: a number, condition, exception, uncertainty or deadline.

2. Record one ordinary take

Speak naturally. Do not restart every time you hesitate. The point is to hear what your current explanation actually sounds like, not produce a polished demo.

3. Listen for one thing

Choose one question:

• Did the main point arrive early enough?
• Was the important condition easy to hear?
• Did I make the next action clear?
• Did I bury the recommendation under background detail?

One question is usually more useful than judging your entire voice at once.

4. Change one thing

Move the point earlier. Separate two ideas. State the request explicitly. Keep the wording mostly intact so you can hear what the change did.

5. Record a second take

Compare the two attempts. Do not assume Take B wins because it came second. If the first version is clearer or more natural, keep it.

6. Use new words

Now explain the same point without repeating the exact sentence. This is the useful final check: can the structure survive when the wording changes?

What this rehearsal is for

Use it before a project update, stakeholder explanation, technical handoff, recommendation, difficult question or other short work conversation.

It is not a substitute for preparing the facts. A confident delivery cannot repair a wrong number, missing condition or unclear decision.

Ptichi is being built as a private desktop practice instrument for this loop: Take A, listen, one change, Take B, compare, transfer. While the public app is still in development, the exercise above works with any recorder.