Explore

rewqrewq

Use this root cause reasoning (RCR) template to identify and communicate the fundamental reason behind tough problems. Once you understand the problem and root cause, propose a solution and share with your team to gather their questions and sentiment. Inspired by

Zoom’s decision-making ritual⁠

⁠

Clear example data

⁠

Problem

What is the problem that needs to be solved, and why?

Root Cause

What is the fundamental reason there is a problem?

Discovery methods

Discovery methods

⁠

Solution

What is the proposed solution?

Owner:

Who is the directly responsible individual for implementing the solution?

Done reading?

⁠

Q&A: Topics for discussion

⁠

Add a topic

⁠

Idea

Author

Upvote

Notes

Do we have budget for swag?

Can we open the thumb wresting tournament with magic?

How do we incentivize people to come to a virtual event?

There are no rows in this table

⁠

Pulse: How do you feel about the RCR?

⁠

Add your sentiment

⁠

Toggle to show everyone's sentiment (

3

⁠

submitted with average sentiment of

4

⁠

)

Sentiment

Who

Reflection

Ship it! It’s a huge improvement and I think will really benefit power users and new makers alike. My only concern is it sometimes shows up when I don’t want it, but I think we’re balancing that fairly well on the whole.

Really enjoying this feature overall! It’s made room for some delightful visual updates like transparency over cover photos. 👏 Discoverability of certain features is the main concern I’ve had and where I imagine some roadblocks for users.

I feel good about this change overall. The main question I have is around how do we mitigate the pain around moving the cheese. There was an initial shock for me, but I very quickly came around. So I feel we just need to figure out how to manage the migration.

There are no rows in this table

⁠

Table