Menu

The Johari Window: A Guide for Leaders

The Johari Window: A Guide for Leaders by Sheril Mathews is a very helpful post for leaders about a model I wasn’t familiar with:

The Johari Window is a 2×2 matrix that captures how we communicate based on self-knowledge and how others see us. It’s a disclosure-feedback model of awareness based on principles of feedback and learning. It can be used for increasing levels of openness, self-awareness, and self-understanding. This makes the Johari Window a particularly relevant tool for leaders and managers.

Sheril goes on to explain the model in detail, and how to increase the size of the top left corner of the matrix, called “The Arena”:

This is the public space. It’s the part of ourselves—behaviors and feelings—that we’re aware of, and so are others. All information is known to all parties. We move freely within this space and it fosters open communication.

Johari Window

Why meeting overload happens, and what to do about it

Anne Helen Petersen brings some much-needed clarity to the meeting overload debate in The Root of Over-Meeting Culture. It’s worth reading this one in full because she takes her time to lay out the argument logically, but a few of things especially stood out to me.

When their team was fully in the office, managing probably felt straightforward. Most people managed by, well, looking and walking around. That was the heart of it. Now, figuring out what your team is doing, and how they feel about doing it, it’s a lot more work. So managers not only feel like they’re doing more work — and less productive themselves, as workers — but they also feel like they’re doing a worse job, and have less insight into what their reports are doing.

This is a good point that I don’t see talked about much. One of the reasons that RTO policies have become so prevalent is the lack of visibility that managers feel about the work their teams are doing. There are way better solutions to this problem than forcing a return to the office (regular async updates, clear priorities, etc.), but that seems to be the default approach to deal with what is essentially a communication problem, not a presence problem.

More talk about prioritization = more manager confidence (that their reports are doing the things that matter most) and more employee confidence (that they’re doing what they should be doing). It’s difficult to understate just how powerful this sort of clarity can be.

Related to the previous quote, +1 to this! No one on the team should be wondering if they’re working on the right things, and what they should be doing next. This is, in my opinion, the most important job of the 1:1 meeting, and why that meeting has to be (at least) weekly.

I have all the reservations about AI that other smart people do, but one of its real potentials is summarizing meetings in a way that makes people feel like they understood what happened and whether or not their input is needed after the fact without having to attend the actual meeting.

Another big +1 to this. Gong does this incredibly well by summarizing sales calls, pulling out action items, providing searchable transcripts and call insights, and more.

There are some pretty wild stats in the post about how meeting time has increased 252% since 2020. Some of that is necessary because of the shift to remote work, but not all of it. We somehow still view meetings as the default solution to figuring out what’s going on in an organization. I wrote Good / Bad Remote Worker before the pandemic, but I think this principle is more important than ever:

A good remote worker always thinks about collaboration through the lens of asynchronous communication. Remote work naturally creates great environments for deep, focused work, so it makes sense to optimize for asynchronous communication. This lets everyone get involved when it works best for them — and when they are ready to give something their full attention.

A bad remote worker tries to recreate an open office environment through too many meetings and other forms of synchronous communication. Meetings aren’t inherently bad. But unnecessary meetings and synchronous feedback sessions undermine one of the most significant benefits of remote work and should be used sparingly.

The Power Shift: Mastering Reverse Interviews and Interim Roles

This is a great hiring post on “reverse interviews”—or how to make interviews less one-sided and make sure you get the information you need to make a decision about a company. I like this question in particular:

Ask your direct manager for examples of promotions and attritions they have managed. Request stories about individuals they’ve managed in the past who have gone on to achieve significant success. Ask about the frequency of their meetings with direct reports, their perspective on their role in your work, their preferred communication styles, and their approach to staying informed. Also, clarify who makes which types of decisions.

How ✨ became the unofficial AI emoji

I’ve definitely seen this too! How ✨ became the unofficial AI emoji:

In the relatively short history of emoji, sparkles have been used to express excitement and magic, said Jane Solomon, the senior emoji lexicographer at the emoji reference site Emojipedia. Branding new AI products with the ✨ emoji suggests that these tools are exciting and magical, which might encourage more people to test out the technology. “It can seem like magic if you don’t understand how it works,” Solomon said.

How To Ship Fast

This is a highly opinionated piece (nothing wrong with that!) and I think there’s some nuance needed, but in general I like these principles from How To Ship Fast. This one is definitely a hot take, but in a dream world where everything is perfect I would agree:

Time spent on prioritization is the canary in the coal mine for not being close enough to your customers. The discrete task of prioritization should take almost no time. Only work on Important things. Sort those Important things into “Do now” and “Do next”. If you are only working on Important things, the order does not matter too much (and don’t spend time debating it). If what’s Important is not obvious you are not close enough to your customers.

Sales-First Storytelling

Great post by April Dunford on how marketing teams and sales teams need to tell different stories about a product:

Our goals in marketing are very different from our goals in a sales situation. Often in marketing, we are simply trying to capture an audience’s attention and get their permission to continue marketing to them. […] Sales, on the other hand, is generally dealing with the folks who have already raised their hand in some form and are in a purchase process. Our primary job in sales is to help guide prospects through the purchase process.

However, both approaches to storytelling need to come from the same positioning source:

Sales and marketing should use the same inputs for whatever storytelling structure they choose, and those inputs should come from our positioning. Both marketing and sales communicate the value that the product delivers that no other solutions can. Both have a common definition of what a good-fit prospect looks like. Both teams need to understand the alternative approaches, including the status quo and more direct short-list competitors. Our positioning defines the inputs for marketing and sales content—we ultimately need commonality across marketing and sales because our positioning defines where we win and why.

Building community out of strangers

I love Tracy Durnell’s blog—it’s been in my RSS reader for a long time. In Building community out of strangers she makes a case for personal sites to be more… personal.

I like hearing about the trials and triumphs of other normal people’s lives, seeing what goals they pursue and what they care about enough to write about. I gather book recommendations from others’ reviews, sample others’ taste in music, and delight in the daily wonders of others’ worlds: the cat luxuriating in a strip of sunshine, the stream in the dappled light of an open forest, the neat-looking conjunction of lines on the wall they passed on their morning walk. While social media emphasizes the show-off stuff—the vacation in Puerto Vallarta, the full kitchen remodel, the night out on the town—on blogs it still seems that people are sharing more than signalling. These small pleasures seem to be offered in a spirit of generosity—this is too beautiful not to share.

I love that perspective—and this is exactly why I follow so many personal blogs. And yet I’ve always been a little scared to go there on this site. I’m supposed to be a professional! This is work!

Well, I think that 20 years into doing this tech thing for a living it’s time to start sharing a bit more about all my interests, not just the product stuff. So I guess this is your fair warning that you might start to see more of that here!

PS. Tracy also updated her blog roll (remember those!?) and I am definitely going to add one here as well.

My $500M Mars Rover Mistake: A Failure Story

My work at Jeli so far has given me a new lens on “incidents”—both in the software world and beyond—that I didn’t have before. These “failures” are everywhere around us. But are they really failures? Or are they ways for us to learn more about the systems we work within, and how to improve them? I think it’s the latter, and My $500M Mars Rover Mistake by Chris Lewicki is another story that showcases that…

The core lesson I’ve drawn from my rover ordeal is best expressed in these words: Let your scars serve you; they are an invaluable learning experience and investment in your capability and resilience.

More

  1. 1
  2. ...
  3. 14
  4. 15
  5. 16
  6. 17
  7. 18
  8. ...
  9. 202