Assigning the burden of proof to those who make the initial claim
Haebom
Asking a colleague who throws out too many ideas in meetings (I call them divergent thinkers) to take on the 'burden of proof' is a useful way to keep discussions productive and the project on track. These kinds of colleagues are essential for any team. But sometimes... they can go overboard—ideas spill out, but they can't take them back. If this kind of behavior keeps repeating, it's time for a conversation.
Understanding the concept of 'burden of proof':
In the legal field, the 'burden of proof' refers to the principle that the person making a claim must provide supporting evidence. For example, when someone presents a particular argument, they're expected to bring proof backing it up.
Applying this in business meetings:
When a coworker suggests a new feature or idea in a meeting, you give them the responsibility of proving why it's needed or beneficial. In other words, don't just toss out an idea—back it up with evidence and details to validate its necessity. (Bring data to support it!)
Concrete response strategies:
Suggest that the proposer try building their idea as a separate microservice or app. (You do it!) This lets us explore whether the idea is actually feasible, without messing with current work.
After it's built, we review how it turned out and decide if it's worth merging into the main project.
After it's built, we review how it turned out and decide if it's worth merging into the main project.
Following up with further questions:
You can ask questions like these to test whether the idea really needs to be implemented:
•
"What need does feature X meet that isn't already covered by module A or B?"
•
"Will the X feature actually deliver added value to users?"
•
"Has there been a real request for feature X? Or is it something to consider only if people start asking for it?"
This way, you can handle random change requests during meetings in a reasonable manner and steer the discussion effectively. By applying the burden of proof, every idea goes through careful review before becoming part of the project. This boosts meeting productivity and helps everyone stay focused on the real project goals.
Subscribe to 'haebom'
📚 Welcome to Haebom's archives.
---
I post articles related to IT 💻, economy 💰, and humanities 🎭.
If you are curious about my thoughts, perspectives or interests, please subscribe.
haebom@kakao.com
---
I post articles related to IT 💻, economy 💰, and humanities 🎭.
If you are curious about my thoughts, perspectives or interests, please subscribe.
haebom@kakao.com
4
Haebom
사실 이런 짤방이 있죠.
A
anonoymous
잘 읽고 있습니다. 감사합니다.
Haebom
이런 댓글이 큰 힘이 됩니다. 감사합니다.
고
고다녈
ㅎㅎ 발산형인재로서 첨언을 드리자면 이 아이디어를 던진다기보다 인싸이트를 던진다에 가깝습니다. 던진 인싸이트에 전체적인 공감이 있으면 디테일한건 함께 고민해보고자 던져요~ 물론 실제로 실행할 각오도 되어 있구요~문제는 어떤 아젠다의 회의에 던지냐인것 같습니다. 아무때나 그러면 피곤하죠 ㅎㅎ
See latest comments