I Prefer Working in “Lowercase P product teams"

When speaking, sometimes all you need to communicate properly is tell the listener if a word you are using is a proper noun or not. If you don’t, they may misunderstand you.

One example of this method I use often is “lowercase p, product” to denote a team that makes digital products, not a team of Product Managers. Here’s two versions of a phrase that could have very different meetings to a non-product manager audience:

“The Product Team revised its roadmap.”

“The product team revised its roadmap.”

The first could mean only the Product Managers worked on the roadmap, which is not how cross-functional integrated teams should work. All job families within the product team should create the roadmap together.

The second version is what you intended, but verbally sounds the same.

This is where “lowercase P, product” is handy to share your true intent with the listener.

Try this instead:

“The lower-case P product team revised its roadmap.”

It’s a small thing, but can go a long way in sharing your true intent and not causing confusion, or worst case, a need for damage control.

Leaders Leave Meetings Last

I loved this reminder from Kyle at audacious.blog to hang around at the end of each meeting in case someone has a question for just you:

Today, even though I’m only a quick keyboard shortcut away from instantly exiting any Zoom call, I still try to be the last one to leave. Once we say our goodbyes, I hang on for ten more seconds as the group filters out. Most of the time I’m left looking at me. Sometimes though, someone else waits around too. Then, given this serendipitous opportunity to bring up that gnawing question, they ask if I have another minute, and I say sure.

Jargon vs. Shared Language

Corporate jargon isn't inherently bad, it's a shared language that increases speed and accuracy of communication. The jargon is bad when it bastardizes a word for another word that confuses people or is BS.

When you have a simpler word to choose, use that. There is no need to complicate things unnecessarily. Unnecessary jargon is like a virus; a couple of folks you hear use a phrase, and others adopt it quickly, until folks say it without even realizing what has happened. Think to yourself if there’s a simpler way to state your point (e.g., “tee up a conversation” versus “start a conversation”).

Making software is complex and difficult. Jargon that is shared language to explain a complicated concept can be efficient, as long it is shared language among the audience, and it serves its purpose. If not, it's unhelpful jargon.