-
Psychological safety vs producive stress. How not to go #toxic.
Psychological safety vs producive stress is a conflict of interest. People usually think that much “safety” can lead to laziness ? Don’t rest on your laurels as they say ? On the other stress and some level of danger motivates us to harder work. Workplaces need a certain level of pressure to move forward. Deadlines, feedback, and responsibility all matter. But pressure is not the same as panic, and motivation is not the same as fear. The real challenge is to create an environment where people feel safe enough to speak honestly, while still being stretched enough to grow (or just get exploited and run down the mill?). Safety leads…
-
What Jack Oneill teaches us about efficiency
What Jack Oneill teaches us about efficiency, underneath his sarcasm, is ruthlessly practical. Listening to Jack You can easily figure out the most important things to do simple… efficient… are : Jacks worldview reminds us that intelligence isn’t just about knowing, it is rather wisdom anyway, but more so it is about acting clearly in the face of confusion. In a world rewarding complexity, that kind of simplicity is both rebellious and profound. Colonel (later General) Jack O’Neill ( two Ls) from Stargate SG‑1 is remembered for his sarcasm and not liking scientists. Beneat dry humor lies, a surprisingly deep, wisdom rooted in simplicity, straight talk, and cutting through noise…
-
Losada coefficient at life and work
The Losada coefficient at life and work is pretty much the same theory. Also known as Losada ratio or critical positivity ratio. Proposes a fixed ration between positive and negative interactions / emotions. Supposedly distinguishes positive from negative individuals or teams.We should have proportionally MORE POSITIVE INTERACTIONS so in the long run we will be happy.Originated in 2005 paper by psychologists Barbara Fredrickson and Marcial Losada, who calculated a threshold of ~2.9:1 and upper? limit around 11.6:1 Losada ratio in coportate In highly skilled IT software development teams ( or any other team for that matter) this balance shows up in code reviews, stand‑ups, meetings, emails, design discussions and production…
-
Do not be a hero – 3 pros and some tradeoffs
Do not be a hero. Why ? . Ever seen that one guy doing midnight fixes, hot releases after hours and then gets praised in front of everyone making You look bad ? When features are delivered on time and on target the team is considered heroes. We all love rewards and recognition but heroism might become … Heroes give up work / life balance. As the ancient wisdom teaches us “no good deed goes unpunished”. Whenever there is a new crisis or a target to achieve is set, yesterday’s heroes are quickly forgotten. Long hours eventually might lead to burnout, anxiety and/or even depression. What “Don’t Be a Hero”…
-
Informed captain decision making in team
Informed captain decision making in team is another idea, from netlifx, to make everything in a company better, decentralized and so on and so forth. Fater, better harder stronger 😉 The generic idea is about “empowering teams and individuals” but here are the key points about this concept. Short story : Informed captain listens to everyone than is trusted to take the best decision to move forward. Informed Captain Responsibilities The captain owns the team’s mission, mandate, and metrics, and has full decision-making authority within their scope. Decision-Making Process Decisions are not made by consensus or committee votes. The captain has the final say after considering different viewpoints. Kinda like…
