John Cutler Profile picture
Nov 22, 2019 8 tweets 3 min read Read on X
Some common loops #proddev #systems

1/7 Why does that team seem to always take on too much work?
2/7 Why does that shared resource seem to be perpetually under-staffed?
3/7 Why does the team keep slipping into planning big batches?
4/7 Why does a myopic focus on increasing velocity eventually hurt quality?
5/7 Why are the team’s stories never “good enough” ?
6/7 Why does my team hide things from me?
7/7 Well…you saw what happened when we tried to just hand them a problem, right?
BONUS (that wraps up lots of these)

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with John Cutler

John Cutler Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @johncutlefish

Apr 2, 2023
The “messy middle” problems is one of the biggest impediments to product success. Here’s what it looks like:

The strategy and vision is somewhat clear.

Teams have specific features they’re working on.

But there’s nothing in between.

Why does it matter? 1/n
High level visions and strategies are helpful, but they lack the specificity to guide teams.

Specific project-based roadmaps feel “actionable” but they are very fragile—they don’t inspire aligned autonomy.

You need a linking mechanism 2/n
Some teams use goal cascades

The problem is the classic MBO problem: goals get more specific & prescriptive as you move down the stack. And by definition they should be “time bound”.

They too are fragile and foster “figure out what you want to build AND THEN tack on goals” 3/n
Read 5 tweets
Mar 26, 2023
I was reading the transcript of a work presentation. Then I watched the presentation.

The transcript was filled with issues / logical fallacies / open questions.

While watching I noticed very few.

I think this is the root issue with presentation culture.
I noticed different parts of my brain firing in each context. When slides had lots of “stuff” it felt like a sense of “oh they’ve figured this out” even when the words did not match.

If you pay attention you can feel this happening.
The confident voice of the presenter made the “three focus areas” feel certain, clear, and logical.

In writing it felt incoherent.

I guess this is a point for “a compelling visual” but still it’s interesting.
Read 6 tweets
Feb 12, 2023
Your team is burnt out. They are not getting anything done. Work is "low quality". You can see and feel those things.

But what you are seeing is an output of something—the downstream effects of other things happening.

In some companies this is a black box

1/n Image
…they don’t have visibility into what’s happening.

But it is not that simple (of course).

The outputs are inputs into the black box. And the outputs input into the inputs.

2/n Image
Say the team reactively addresses quality issues.

This creates more “work” (the output inputs into the input), but it also leaves the team more burnt out and they make less-good decisions on whatever is going on in the box.

3/n
Read 10 tweets
Jan 29, 2023
Product Management is an exploration of time.

In product we are always jumping between "Time-full" things and "Time-free" things.

Example:
An improvement project to build a new AI irrigation system vs. the ability to irrigate our crops.

1/n
We project thing time-free things into the future, making them time-full.

Here we imagine our ability to irrigate our crops evolving from a watering can, to the new AI powered system.

And we imagine the capability level increasing.... over time

2/n
This is happening everywhere.

Right now your product exists, a jumble of current capabilities.

You work to improve those capabilities.

And, if you squint, you evolve the capabilities necessary to do that work, and support that product

3/n
Read 9 tweets
Jan 29, 2023
Why do attempts to "reign in" product processes involving multiple teams fail so regularly?

Well...

Here we have a list of features about "the work".

An example of a feature might be something like:

"Amount of customer education needed...."

OK...1/n
So imagine we collect data about our initiatives.

Example:

"Amount of customer education needed" = HIGH

OK, now we're getting somewhere.

Except... 2/n
Sequence matters.

In product, if we try to converge on everything way in advance, outcomes will suffer. We don't want that.

So the sequence...of when and how you attempt to collect data about the initiative matters.

But we're not done... 3/n
Read 9 tweets
Jan 21, 2023
I recently asked Twitter for words describing "great product managers". Here the results in pictures...

The diameter of each circle represents the number of *other* words that were related to the word.

Colors represent "neighborhoods" of words.

Lines = relationships

1/n
"Responsive" was not the most common response. But it was the word that had the most number of similar/related words

It is a broad word...for sure...but I thought that was interesting

2/n
Results and customer orientation...

3/n
Read 5 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(