More Posts
Does your state have staffing ratio laws?
Water bottle recommendations? 😅
20 * 0 = 0

Hogwarts Houses? Go!
Additional Posts in Tech
Has anyone heard of Kuba Pay?
I'm graduation in the spring and looking at working at the following companies (I have current offers from three of them), which would you pick, salary aside as they are all similar and revealing. I'm hoping to work in a silicon related area.
Ampere Computing LLC Oregon
Qualcomm California
AMD California
Apple California
Nvidia California
Hoping to have some WLB but challenging projects
New to Fishbowl?
unlock all discussions on Fishbowl.
There's only a conflict there if you define "accountability" as blame. For example, being accountable as in accepting fault and "never doing it again", even though that basically assumes that it is possible to eliminate mistakes. The blameless idea is that trying to focus on fault and pointing a finger at someone or some team to "be accountable" doesn't help, but rather that determining the root causes, coming up with action items to fix flaws uncovered by the issue, and overall learning how to prevent similar issues in the future *is* being accountable.
Simple in my opinion. The financial and career incentives need to revolve around the collective team and not specific people. For example, if my team is not able to increase registration by 10%, I don’t care why. The entire team failed. Basically the team is always blamed, and the team needs to find a solution.
Bowl Leader
One approach I've read about is a three strike rule follow by a week or two timeout from code check-ins. A sort of mini PIP directed at actual improvement (unlike the HR ritual). Not sure of the phrasing nuances for making this feel safe, but seems reasonable.
It sounds like the real thing here is individual vs group responsibility. I think serious and reliable 1:1s really help get that individual responsibility across, even if it's just as PART of the group.