Share this page!

Maybe Scrolly?
John Cutler Profile picture
Twitter logo
17 Oct, 13 tweets, 4 min read
A collection of things from the vault! Wading through 1000s of images shared on twitter.

1/n: Adding assumptions and constraints to a "tree" of nested bets...
2/n: Getting specific about principles ... and avoiding vanilla statements
3/n: The iceberg of product complexity ... what we don't see when we just ponder "level of effort"
4/n: Describe the role of manager ... some interesting grouping here...
5/n: Some helpful prompts I wrote for @Amplitude_HQ
6/n: Trust ...
7/n: Some thoughts on company culture
8/n Journey to Product Teams ...
9/n: Brainstorming elements of high decision quality ...
10/n: Hi-res WIP IT REAL GOOD
11/n: Feels Like Faster -- But This Makes Us Faster
12/n ...

Thinking out loud for a sec.

Right now there is no home for this stuff. It drives me a little crazy. My only mode of helping is "share more stuff". 1000s of things

What if I gave it a home. Added context.

It would take work, for sure. I might need to charge.

But?
Oh ... and the tables

• • •

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

John Cutler Profile picture
15 Oct
a little product lesson

we often experience situations where we are faced with overlapping problems

it looks a little like this ... 1/n
...except, often no one really takes the time to define the problem(s). Instead they brainstorm a bunch of ideas predicated on implicit perceptions of the problem(s)

the danger here, of course is that... 2/n
...if you bring three people together they might each see different things

One person sees one problem

One person sees two slightly overlapping problems

One person sees a parent problem with three child problems 3/n
Read 7 tweets
John Cutler Profile picture
10 Oct
Funny thing is that I both agree some people are really good at certain things

AND I also believe that certain environments are conducive to elevating everyone such that one person being really good at something doesn’t mean much (though it is helpful)

1/n
The difference boils down to predominantly team oriented views of our work vs individual oriented views.

If you got all the best ppl at doing X in the world together and put them in a room… the differences would be minimal

In their org they are…. 2/n
Much better than everyone at X. They might even be 10x at it. If you leave them alone to do X they will outperform everyone at X.

But in a team setting, you’ll also need to do Y and Z. And A, B, and C.

Being 10x at X doesn’t mean much. 3/n
Read 4 tweets
John Cutler Profile picture
1 Oct
genuine question

the first instinct or product / design folks when getting a new gig is to talk to customers. LOTS of them. As quickly as possible.

...but in other roles, this is a foreign concept.

assuming great intent and high skill in their respective domains...

why?
...could the intent be there, but it is more a question of fear, and feeling like you are being put on the spot?
another could be ...

whereas a product/design person knows what signals to look for

other people will assume that the customer will not be able to tell them something they don't know?
Read 4 tweets
John Cutler Profile picture
18 Sep
A thread on "Starting Together"

1/n Here is how lots of teams work:

1) PMs and designers focus on the "next thing"
2) Developers work on the "current project"

What's wrong with this?

Outcomes suffer, even if it feels more efficient.

Why ...?
2/n While seemingly more efficient -- it causes problems:

1) information loss
2) "resetting costs" during transfer of knowledge
2) distances developer from "the problem"
3) higher work in progress (WIP), less flow
4) split focus for PMs/designer

So...
3/n When thinking about starting together, teams get a little paralyzed because they somehow can't imagine all focusing on research/discovery

You have...

A: The status quo
B: How they imagine starting together
C: How it happens in practice
Read 5 tweets
John Cutler Profile picture
13 Sep
I am a huge advocate for visualizing work.

But there's one huge trap that I see teams fall into.

Start with the Why not the Way

Visualizing work is not the goal. ___ is the goal.

What do I mean?

1/n: Imagine if you emptied out all of your messy drawers just for fun. Well..
2/n: You would have succeeded in making a big mess and reminding yourself how messy you are, and how much you like collecting old subway cards, but you wouldn't have really achieved anything.

Now say you....
3/n: Started by committing to a powerful mission of making it easier to find things. You spend valuable time every day checking multiple drawers.

Or committing to a more public display of keepsakes and caring for your things better?
Read 6 tweets
John Cutler Profile picture
11 Sep
I've met with ~70 teams in the last three weeks.

One thing that sticks in my mind.

Paradoxes.

1/n: you can have...

a mid-stage startup team that is highly dysfunctional

...but due to timing and early product/market fit, they succeed (by some measure) for years
2/n: you can have...

a team of incredibly thoughtful, experienced, people

...but due to disruption of the business model and the inertia of the legacy business, they go circles.

They're stuck.
3/n: you can have...

a bunch of new hire team contributors (engineers and designers) that are excited to tackle the new strategy

...but middle-management is severely underpaid, and burnt out by buffering "the teams" from "the biz".

The new hires leave quickly.
Read 11 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

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!

Follow Us on Twitter!

Like this author's thread?

Get emails when @johncutlefish has new unrolls!

Check out other threads from @johncutlefish!

Read all threads by @johncutlefish

:(