Early on in the conference there was a panel of "experts" discussing the debating the topic of "There's only us" even though we tend to falling back to blaming "them". Much of the debate centered around trust, and some members of the panel were purposely playing devil's advocate to trust--which for me sharpened the reason of what the purpose of trust is in delivering software. I took all of the chaos from the panel discussion and tried to distill it here. It still feels like it is lacking in some dimensions, but here's a first draft.
The purpose of trust is to increase productivity of the whole.
Individual productivity can thrive in an environment without trust, but doesn't necessarily benefit the whole.
Tension can rise as individual productivity begins to level out during attempts to gain trust.
Trust needs conflict in order to grow.
Conflict slows down productivity.
Interesting relationship in that conflict fights against the purpose of trust, even though trust needs conflict in order to grow.
Conflict is resolved through the combination of courage and collaboration.
Resolving conflict builds trust.
Avoiding conflict weakens trust.
Avoiding conflict ties back to fear -- or lack of courage.
Attempting to resolve conflict without collaboration never really resolves conflict. It shatters it into smaller pieces and scatters them all around.
No comments:
Post a Comment