Profile picture
, 3 tweets, 1 min read
My Authors
Read all threads
“Of course we have more individually focused projects ... how else will we do performance management?”

...is one of the most interesting puzzles in collaborative product work. Also related ... (1/3)
...is “you need to give a person something to own and get out of the way with minimal process”. This is interesting as well. It comes from a good place — autonomy, master, purpose — but it is still individually focused (vs. team focused)

These perspective manifest in... (2/3)
How people design tools and frameworks (e.g. DRI or RACI). Can >1 person be assignment to “a ticket” ? Is there accommodation for how the team collaborates? So much stuff... (3/3)
Missing some Tweet in this thread? You can try to force a refresh.

Enjoying this thread?

Keep Current with 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!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

More from @johncutlefish see all

Profile picture
John Cutler
@johncutlefish
Here is a way to build alignment. It is easy AND challenging. It works for groups up to ~5 ppl.

Step 1:
Pick a person at random. Pose this question:
“What do we know about [x]” where X is the problem/opportunity/topic/whatever.

Write that down. Keep it <10 words.

Then.. (1/n)
Step 2:
Move to the next person. They can:
* Ask a clarifying question, ask for data/context
* Propose a refinement of the statement
* Give a thumbs up (they agree 100%)
* Give a thumbs up to a prior refinement
* Propose a “footnote” or caveat

Repeat this.... (2/n)
Step 3:
As you continue you’ll start to get an idea of the situation:

1) lots of unknowns (we can “know” unknowns)
2) lots of competing interpretations of the data
3) convergence on a statement of fact
4) broad truth that doesn’t really help anyone
5) etc.

Keep it up (3/n)
Read 6 tweets
Profile picture
John Cutler
@johncutlefish
Something I hear a ton from larger organizations...

“We need to adopt more *product thinking*. We need to think in products!”OK. Where to start.

How does this manifest? 300 teams and 300 CSPOs and 300 “products” later, “IT” is in the same mess it was in before (1/n)
Except now they have PRODUCTS.

Take something like a bank. If you think of humans out in the world and their needs from a bank, you have ~10 human<—>need combinations.

The bank is using design and technology and a big network of services to meet those needs (2/n)
Yet somehow now everything is supposed to be called a product, because that is how you get budget, and that is what the consultant told you. Product teams! Hurray!

But that kind of misses the point.

We talk about the shift from projects to products, but ... (3/n)
Read 7 tweets
Profile picture
John Cutler
@johncutlefish
Some program level board tips:

1/10 While you should visualize as much of “the work” as possible, you will almost certainly need to sacrifice a bit of detail for accessibility. Can anyone looking at the board see where their work fits in?
2/10 Consider rate of range and cognitive overhead. If items on the board need to be moved by the second/hour/day...well that will be hard to process. But if items don’t move for days/weeks...that will not not be useful and actionable. There is a balance.
3/10 Model the work, not the workers. It is tempting to structure the board around teams, team lanes, etc. Why? The information is helpful! Knowing who is working on what is useful information. But, you run the risk of obscuring dependencies and global priorities...
Read 13 tweets

Embed code for your website

×
Follow Us on Twitter!

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.00/month or $30.00/year) and get exclusive features!

Become Premium

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

Donate via Paypal Become our Patreon

Thank you for your support!