2 added 325 characters in body
source | link

When I was a beginner many years ago, there was a situation when I understood something, the PM understood it, but the rest of the team did not. My explanations were not very useful. The discussions only closed temporarily until they opened again on the same topic.

I was initially confused by the approach of the PM, but I eventually understood it and adopted it. It was very helpful throughout the years.

The Method

Do not explain.

Let them present a solution. Then ask a question. Let them answer. Ask them another question. Let them answer. Continue until they understand that their solution is flawed.

Repeat until no more flawed solutions exist.

If a good solution is found, adopt it. If no other solution can be generated by the team, suggest a solution. Receive questions. Provide answers.

In the end, everybody will have to be happy - even if some egos might get hurt a little.


Clarification: All the procedure above happens during EXACTLY one meeting, not trial and error throughout the life of the project.

Worst case: a follow up meeting may be necessary, if something needs to be actually tested in the real world.


Gradually, they will come to understand that you understand things better and faster, and they will eventually come to trust you and let you talk first - what you actually want.

When I was a beginner many years ago, there was a situation when I understood something, the PM understood it, but the rest of the team did not. My explanations were not very useful. The discussions only closed temporarily until they opened again on the same topic.

I was initially confused by the approach of the PM, but I eventually understood it and adopted it. It was very helpful throughout the years.

The Method

Do not explain.

Let them present a solution. Then ask a question. Let them answer. Ask them another question. Let them answer. Continue until they understand that their solution is flawed.

Repeat until no more flawed solutions exist.

If a good solution is found, adopt it. If no other solution can be generated by the team, suggest a solution. Receive questions. Provide answers.

In the end, everybody will have to be happy - even if some egos might get hurt a little.

When I was a beginner many years ago, there was a situation when I understood something, the PM understood it, but the rest of the team did not. My explanations were not very useful. The discussions only closed temporarily until they opened again on the same topic.

I was initially confused by the approach of the PM, but I eventually understood it and adopted it. It was very helpful throughout the years.

The Method

Do not explain.

Let them present a solution. Then ask a question. Let them answer. Ask them another question. Let them answer. Continue until they understand that their solution is flawed.

Repeat until no more flawed solutions exist.

If a good solution is found, adopt it. If no other solution can be generated by the team, suggest a solution. Receive questions. Provide answers.

In the end, everybody will have to be happy - even if some egos might get hurt a little.


Clarification: All the procedure above happens during EXACTLY one meeting, not trial and error throughout the life of the project.

Worst case: a follow up meeting may be necessary, if something needs to be actually tested in the real world.


Gradually, they will come to understand that you understand things better and faster, and they will eventually come to trust you and let you talk first - what you actually want.

1
source | link

When I was a beginner many years ago, there was a situation when I understood something, the PM understood it, but the rest of the team did not. My explanations were not very useful. The discussions only closed temporarily until they opened again on the same topic.

I was initially confused by the approach of the PM, but I eventually understood it and adopted it. It was very helpful throughout the years.

The Method

Do not explain.

Let them present a solution. Then ask a question. Let them answer. Ask them another question. Let them answer. Continue until they understand that their solution is flawed.

Repeat until no more flawed solutions exist.

If a good solution is found, adopt it. If no other solution can be generated by the team, suggest a solution. Receive questions. Provide answers.

In the end, everybody will have to be happy - even if some egos might get hurt a little.