Monday Morning Meeting #54
We’re giving Filament Fridays a new look! If you want to come work at Filament this Friday, you’re welcome to join us. We’ll ask that you share a challenge you’re working on and offer a bit of help to others who might appreciate a hand. RSVP here.
TOOLS WE USE
We use “experiments” in nearly every Filament meeting. In this post, we share our methodology and a few of the new worksheets we’ve designed.
NEW ON OUR BOOKSHELF
We’ve been embracing silence more and more in our meetings — especially during the times we’re asking people to think about new ideas. Here’s why you should add more to your meetings:
When we present common knowledge, others reinforce it via social approval. Nods, supportive glances, and smiles are common reactions received when we present information that others share. Unique knowledge, on the other hand, can challenge conventional ideas, which can rock the boat leading to social disapproval. Attendees often hold back in meetings, waiting to hear what others say and what their boss might say out of fear of being perceived as difficult, out of touch, or off the mark. Silence can be a solution to this problem, allowing space for unique knowledge and novel ideas to emerge.
Does your team have a set of simple “rules” for how you work together? You might find some inspiration (at least from a simplicity standpoint) from Chuck Jones’ Nine Rules for Road Runner Cartoons. My favorite:
Rule #5: The Road Runner must stay on the road — otherwise, logically, he would not be called Road Runner.
Stuck? Maybe you need some help from a 4-year-old.
In an insightful post, the folks at Dropbox share several product-building lessons. Here’s the one that sticks with me: “Evaluate” instead of “validate” your hypotheses:
We have the bad habit of saying we’re going to “validate” things. “We’re going to validate if customers do x” or “let’s validate if that’s true.” The challenge in being able to appropriately gauge our hypotheses and assumptions is that we need to be okay with being wrong (yeah, that whole celebrate failure thing). Constantly saying “validate” sets an expectation for validation or accepting a hypothesis as true and, worse, implies that “invalidating” is the opposite of making progress. So by simply saying “evaluate” instead of “validate” you can help your team adopt the learning mindset necessary for developing products in a way that leads to impact. Plus, “evaluate” is the correct term for studies and experiments. Science!
Such a great sentiment: Make it Anyway!
Finally, we’ll share our Change Advocacy Team (ChAT) model next week. Until then, just remember that every idea needs a sponsor.
“If all you did was just looked for things to appreciate, you would live a joyously spectacular life.” ― Esther Abraham Hicks
“You can’t lose either the past or the future; how could you lose what you don’t have?” — Marcus Aurelius
“Learn the rules like a pro, so you can break them like an artist.” — Pablo Picasso
“There is no time for cut-and-dried monotony. There is time for work. And time for love. That leaves no other time.” — Coco Chanel
If you’d like to subscribe to the Monday Morning Meeting or check out older issues, you can do so here.