Design a "no immediate criticism" rule for the first 10 minutes of any brainstorm — raw ideas die fast if judged before they mature.

Breathe ten times and find the point between your emotional and logical minds.

Imagine a safe place you always remember — invoke in crisis.

To open trust in a new team, share your failure first — others will open up.

Anonymously ask Edmondson's three questions to score your team's psychological safety.

Convert mutual critique into a two-way SBI meeting with 5-whys for root cause.

Set explicit working hours and broadcast them in your email signature.

Co-create a remote-team charter defining overlap hours, channels, and reply SLA.

Sign a civility pact with your team: no interrupting, no sarcasm, no replying angry.

Don't analyze a problem from your desk. Go where it happens and observe 30 minutes before suggesting a fix.

Log every task you do for a full week, then tag: delegable / non-delegable.

Go to the workplace, observe yourself, ask "why" 3 times, don't intervene.

Error defined as system problem not person — unlocks honest info without fear.

Give every employee the right to halt the process instantly upon spotting a defect, without waiting for manager approval.

Write with your team the basic rules of engagement (how we decide, how we disagree, when we're reachable) before the first real conflict.

Five anonymous questions each quarter surface problems nobody will voice aloud in a meeting.

Every two weeks, each member gives one peer specific feedback in a fixed format — no waiting for the annual review.

Measure with 7 questions whether your team feels safe to tell truths, ask questions, admit mistakes.

3 conditions for crucial conversations: high stakes, opposing opinions, strong emotion — use 7 skills to succeed.

Teams with high psychological safety perform 4x better. This exercise measures and raises it in your team.

A small "innocent" comment wounds an employee. Your job as leader: interrupt immediately, respectfully, without trial.

Write a speech or message declaring your commitment to a fail-safe environment.

Before any open forum, write the 10 hardest expected questions and answer them in writing — never improvise live.

Real change needs some tension, not zero — your role isn't removing all discomfort, but keeping it within a range that produces learning, not collapse.

There's no ready solution for adaptive problems — treat your next solution as a small learnable experiment, not a final plan that must succeed on the first try.

Design a monthly public ritual celebrating the best "smart failure" (a hypothesis tested fast and cheap, proven wrong) — not every failure deserves celebration.

Use a short immediate phrase ("pause — let's go back to that point") instead of silence now or a delayed confrontation after the meeting.

Use the format "I agree on X, but I see a risk in Y, and suggest Z" instead of silence or unstructured direct opposition.

Test your confidential reporting channel yourself (not just theoretically) — is it actually anonymous, and did it respond the last time it was used?

When teen gets a license, sign a written contract — reduces accidents 50% (CDC).

Ask the model to decompose the problem and show its reasoning before answering, raising accuracy on complex tasks.

Ask the model to "think out loud" step by step before the final answer, especially for logic and math problems.