Posts by Jade Rubick
In this episode, we delve into the concept of task forces and their crucial role in addressing organizational challenges.
It should be a valid option to identify that one role owns an area of responsibility, but delegates that responsibility to the other role.
A trick I learned in an executive presence class is to focus on connecting with your audience. They taught me to look around the audience, and look at a different person as I make each statement. To my surprise, that eliminated all my verbal tics!
I think one of the arts of implementing a strategy is knowing when to be fluid and adapt to incoming information and when to stay the course.
That back and forth may indicate that I haven't thought about things completely enough. Usually, the problem is that I haven't considered the bigger picture: how a particular change would affect the rest of the company.
Labs: Think of yourself as the team that dynamites the way through the mountains, not lays the roads.
Before you start the interview, copy and paste the questions you're asking to search for bias in the questions you're asking. I often find I'm gender coding in a way that might exclude women -- for example, in a recent interview I used two masculine-coded words: "active" and "force". Usually remo...
Many people fetishize straight communication and feedback but don't understand what it takes to actually build a culture where it is safe (for everyone) to do that.
The most valuable part of the definition of Tiny is this: "you can deliver it by the end of the day". One danger of Tiny Thursdays is that work can bleed into the next day or take several days longer. "Tiny == Today"!
Molly also shares her (provative, deliberate, rare!) approach to organizational design, executive team dynamics, and her experience giving a TED Talk on the topic of cliff jumping versus ladder climbing with your career.
I can't emphasize enough how meaningful this can be for people from other backgrounds -- their entire work experience has been workplaces ignoring their needs. When you make it easy for them to take their important holidays, that is very significant!
I’ve found that frustrating in the past. One hack I have sometimes found useful is to pretend there are multiple projects, and have the first project be more exploratory. You can estimate when that part will be done, and then he output of that project is the plan for future projects.
Moving teams is an expected, low-effort change. So what this means is that during the Collective meetings, there is a pattern of people recreating their teams, but the composition tends to not change as much as you might imagine.
We delve into the concept of "piles", and why it can be a useful tool for seeing how to optimize flow.
They don't think about what can go wrong. They don't plan for learning. They don't think through the contours of the project.
We cover a simple process change that is the most impactful way I've seen to prioritize reliability work.
Dependencies are one of the main decelerants for your org -- make someone responsible for taking care of the org structure.
The report transferred the responsibility for reliability to the teams that could do something about it. The reliability team then became the team that helped teams improve.
They come from a place where the individual is supposed to be tough, not where the environment is supposed to make it safe for people to be contrarian.