Comment by tegling

I'm thinking maybe this is rather to present an opportunity for the team to put forward their expectations, pain points and desires. Being 'vulnerable' for me in a workplace setting means perhaps admitting that I really don't appreciate people bikeshedding over items I'm submitting for review (rather than being actually constructive) or that I feel the git work flow don't attribute fairly (hiding my contributions). Maybe others feel the same and we could do something about it? And those were only on individualistic side. To evolve the team and team play I'd think this a good time to bring up that I'm actually hating responding to support inquiries and rather have Pete doing more of that. And that I think Sue is doing amazing work with Figma and I'd really like to learn from her. Wouldn't this type of 'vulnerable' make sense in a team?