There is a very simple kind of training that I call “counting.” What it originally sets out to solve is not a lack of knowledge, but a more common problem: having a lot in your head, yet being unable to say clearly what you are actually asking; hearing someone say a lot, yet being unable to grasp the main point.

The method is simple: before you open your mouth, first count what you want to say into 1, 2, 3.

This is not meant to make people talk like machines. It is about giving thinking a minimal skeleton when information is in chaos. What it trains is not eloquence, but ordering, choosing, and confirming.

First count your words out

One of the most basic moves is this: before you are ready to speak, limit yourself to only one to three points, and explain each point in just one or two sentences.

For example, instead of saying “this thing has a lot of problems, the progress feels off, no one is aligned, and the plan probably needs to change,” you can first organize it into:

  1. The goal has not yet been unanimously confirmed;
  2. There is a key assumption in the current plan that has not been verified;
  3. If the verification cannot be completed this week, the follow-up schedule will need to be adjusted.

These three sentences do not necessarily provide the answer yet, but they let the other person know: these are the three questions we are discussing. Only then is it worth discussing the background, evidence, and actions.

The numbers themselves are just labels. For someone under a heavy information load, one or two points are enough; for a collaborator who already knows the context, you can make three to five points. Beyond that, it is usually not suitable to rely on speaking alone — you should write it down.

Listen, restate, answer

“Counting” training eventually forms a complete loop.

  1. Listen: from the other person’s messy narrative, first sort out the 1, 2, 3 points they may be trying to make.
  2. Restate: say it back in your own words, and confirm “whether the key points I understood are correct.”
  3. Answer: respond only to the questions that have been confirmed, and expand as much as possible following the 1, 2, 3 structure.

This step looks slow, but in practice it is often faster. A great deal of communication cost does not come from having no opinions, but from everyone assuming they are answering the same question when in fact they are answering different things.

You can practice with an everyday scenario. Someone says, “There’s too much going on lately, the project isn’t moving forward.” Do not rush to give advice; restate first:

I hear three things going on: first, the number of tasks exceeds the time you can put in; second, the priorities have not been set yet; third, some blockers need help from others. Which one do you want to solve first?

As long as this step is confirmed, the discussion that follows will turn from emotional complaining into actionable questions.

How numbers grow into frameworks

Being able to list 1, 2, 3 does not yet mean your thinking is clear. The next step is to prepare some frameworks for common problems that you can quickly call up in your mind.

Quickly syncing on a problem

When you need to sync an anomaly, a risk, or a blocker, you can organize it in this order:

  1. Phenomenon: what happened, and how does it differ from expectations?
  2. Background: why does this matter need attention right now?
  3. Cause: what are the known causes, the unknown parts, and the evidence, respectively?
  4. Progress: what has already been done, and what is the next step?
  5. Help needed: who needs to make what decision by what time?

Planning or phase reporting

Planning should not start from a project checklist. You can first ask:

  1. Current state: what are the verifiable facts?
  2. Goal: what do you want to change, and how will you judge that it has been achieved?
  3. Challenge: what is the key problem standing in the way of the goal?
  4. Path: what options are there, and why choose this one?
  5. Rhythm: what are the next step, the milestones, and the review points, respectively?

Research or analysis

A piece of research can first be compressed into three layers:

  1. Question: what do you want to figure out this time, and what is the scope?
  2. Cases: what are the two or three typical situations you observed?
  3. Judgment: what do they collectively suggest, and what is the recommended next step?

These frameworks are not meant to make you fill in templates to write long texts, but to train you — when information has not yet fully taken shape — to first know which slot is missing.

Count along the timeline

Counting is not only for a single conversation; it can also be used for review.

When a project ends, a period of study ends, a trip ends, or even a quarter ends, you can ask: what were the three most important things over this past period? Why did they happen? If you could do it over again, which judgment would be most worth changing?

Summarizing the past is usually easier than predicting the future; but the better next step often grows out of such a summary. In the long run, life and work are both made up of many timelines of different lengths: a week, a project, a career phase of several years. Reviewing regularly is not meant to manage every minute, but to avoid only discovering — after things have ended — that they have been drifting for a long time.

Counting to the end is knowing yourself

In the end, this training lands on a more personal and more difficult question: how do you stand outside yourself and look at yourself?

You can try making a list for yourself that no one else needs to see:

  1. What do I really want to accomplish, and what do I clearly not want to do?
  2. What kind of person do I hope to become in work, relationships, and life?
  3. Which of my judgments are facts, and which are only emotions, biases, or temporary fears?
  4. In the feedback others give me, which parts are worth accepting, and which parts are only their own perspective?
  5. Can I accept my own strengths, limitations, and unresolved problems?

Shortcomings and strengths are often the same trait showing up in different environments. Knowing yourself does not mean reshaping yourself into some standard answer; what matters more is seeing your situation clearly and seeing your choices clearly, doing your best within what you can bear, and then calmly facing the parts that are not under your control.

When you find that you cannot think anything through, it is not necessarily because your knowledge or ability is lacking. It may simply be that the problem at hand is too hard, or the goal too distant. Do not rush to force a complete answer out of yourself; first find one thing you can start doing, count it into 1, 2, 3, and then slowly move forward.