寻求建议,而非许可 (2015)
Ask for Advice, Not Permission (2015)

原始链接: https://boz.com/articles/advice-not-permission

与他人合作时,避免寻求许可而不是建议。 而不是问“我可以做某事吗?” 考虑说“你对我的 X 计划有什么建议?” 通过寻求建议,您可以表达尊重,而不将责任强加给他人,并鼓励开放的沟通。 寻求许可通常会导致个人感觉有义务提供支持或对结果承担责任,这可能会导致不信任和浪费精力。 此外,请求许可有时会操纵信息以达到预期的结果,从而导致同事之间的不信任。 相反,寻求建议可以鼓励合作、促进问责制并允许同事提出建设性的批评。 此外,由于个人对项目成功/失败的投入感,它还可以提高贡献者的参与度。 总的来说,寻求建议来建立关系、吸引团队并有效地做出明智的决策。

在团队中,如果任务最终不成功,请求完成任务的许可可能会让其他人失败。 当团队成员操纵局势导致项目失败时,就会发生这种情况。 例如,团队成员可能会在项目早期向几位高级同事寻求反馈和设计审查,并收到积极的回应。 然而,随着项目接近完成,同样的前辈们对小细节变得挑剔,坚持对组件进行重大修改,甚至完全重写。 尽管一些组织提倡彻底的设计审查,但这种做法通常需要在项目开始实施后对其进行完全投入。 团队成员应该遵守商定的计划,而不是通过批评或破坏同事的努力来损害他们的利益。 应在项目的适当阶段提供反馈,而不是在项目失败时将其用作指责他人的工具。 此外,提供建设性的反馈,而不是简单地说“不”,有助于维持关系并鼓励学习机会。 为了避免不必要的延迟和冗余,团队成员可以选择在进行更大规模的更改之前实施小的实验性更改。 最后,团队成员应协作解决冲突或分歧,避免玩弄政治或背后中伤同事以实现个人目标。
相关文章

原文

One of the most common anti-patterns I see that can create conflict in an otherwise collaborative environment is people asking for permission instead of advice. This is such an insidious practice that it not only sounds reasonable, it actually sounds like the right thing to do: “Hey, I was thinking about doing X, would you be on board with that?”

The problem with permission is that you are implicitly asking someone else to take some responsibility for your decision. You aren’t inviting them to participate in its success — permission is hardly seen as a value adding behavior — but if it goes wrong you might end up involving them in the failure: “Hey, I asked that team and they said it was fine.”

As a consequence, someone being asked for permission will feel a burden to do some diligence and may be resentful of it. That may mean second guessing work that has already been done to ensure they are supportive which is likely a waste of time. In the best case, they will ultimately agree but this process will nonetheless feel disrespectful and appear to demonstrate a lack of trust to the team asking permission. In the worst case, they will decline to give their permission which is not just a matter of rejection but also of loss given all the thought that had already been put into the issue before bringing it to them. Worse still, if your goal is permission you’ll have a strong instinct to present information in a way that favors the outcome you want which can come across as dishonest and further undermine trust. All around, this is a bad situation that breeds antagonism.

Advice, on the other hand, is easy. “Hey, I was thinking about doing X, what advice would you give me on that?” In this instance you are showing a lot of respect to the person you are asking but not saddling them with responsibility because the decision is still on you. Your obvious goal with this approach is to do the best you can, so they are going to trust you aren’t hiding any gritty details and therefore aren’t going to waste time second guessing your premises. They are going to feel comfortable giving you all their honest feedback knowing the responsibility lies with you, and your ego will remain intact because you invited the criticism on yourself directly.

Asking for advice is also a much better way to create advocates for your approach as those who have contributed their ideas will feel some personal ownership over the result much more than if they were just another approval in a long chain. It gives them a personal stake in the resulting success or failure.

The world is full of gatekeepers who think they have veto rights. Don’t believe them. If you need them to invest time or resources then they deserve to have a say, otherwise the responsibility remains with you to decide how to proceed and to suffer the consequences or reap the rewards, as the case may be.

Pitbull got it right: “Ask for money, get advice. Ask for advice, get money twice.”

联系我们 contact @ memedata.com