#NowListening هشتاد - سریال عصر وحشت در اوکلاهاما قسمت اول؛ شهر خاموش from ChannelB پادکست فارسی on @CastBox_FM https://castbox.fm/episode/هشتاد---سریال-عصر-وحشت-در-اوکلاهاما-قسمت-اول؛-شهر-خاموش-id2356600-id473677836?utm_source=twitter

Trick #1: Create a safe space
A successful retrospective meeting requires safety first and foremost.

Trick #2: Make it a ritual
Consistency is crucial to productivity.

Trick #3: Amplify the good
Retrospectives are inherently meant for finding ways to improve your work.

Trick #4: Choose your scrum master wisely
This job takes someone empathetic and impartial, with the skills to:
Remain objective
Identify learning opportunities.
Clarify insights.
Ask questions.
Summarize

Trick #5: Create clear actions
This point deserves to stand alone because unclear actions are perhaps the biggest sticking point in retrospective meetings

Trick #6: Keep the format consistent
As well as making it a habit, try to formalize the overall format of your retrospective meeting.

Trick #7: Keep everything else fresh
Retrospectives should never be boring.

Trick #8: Create a feedback loop
I’ve seen great leaders invest a lot of time and money into feedback training, and for good reason

Trick #9: Record everything
When you don’t, it’s easy to forget or lose track of the topics and actions covered in each retrospective meeting

Trick #10: Get to the root cause
In order to improve, you need to find the right solutions to problems.

Trick #11: Don’t jump to a decision
Experts say smart decisions result from two types of cognitive processes: intuitive and rational.

Trick #12: Don’t force it
Ultimately, the key to take away from these tricks is to make the retrospective meeting your own


https://nira.com/retrospective-meeting/

*Does Shopify have a strong writing culture to help people communicate without meetings?*

Yes, we try to make async decisions as much as we can. We do this in a few ways:

One of our mantras is “Do things, tell people.” You’ll see this plastered on our walls if you come to Shopify’s office.

We built an operating system called GSD (get shit done). This internal tool emphasizes frequent written updates, which are much easier to digest than constant meetings.

If there’s a need to go back and forth on an issue, then a meeting may be called. But that’s the thing:

*__A meeting is a bug that some other process didn’t work out.__*

When an ad hoc meeting happens, we try to understand why written exchanges didn't work to make improvements.

https://creatoreconomy.so/i/131565886/how-shopify-rages-against-meetings