lol .... I clicked on "Think before you click..."

it didn't do anything. but that would have been funny
perfectly normal .... perfectly normal ....

Sam just works like that
I wear my bad to the kitchen and the bathroom ... and when I go out to get the mail
WHAT! I'm clicking on the Hamburgler

• • •

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

15 Apr
10 Core Product Management Lessons (a 🧵)

1. Not all good ideas are worth tackling now (or ever, even)

🧩: But sometimes immediate action is required

ToDo: Listen. Acknowledge. Make decision heuristics visible. Revise them with new information.
2. Your teams capacity to act/focus is, and will always be, limited

🧩: Treating every minute as precious erodes creativity

ToDo: Limit work in progress. Seek unnatural levels of focus.
3. Uncertainty signals opportunity

🧩: Uncertainty can trigger anxiety/fear

ToDo: "Talk about uncertainty with certainty"
Read 10 tweets
11 Apr
having observed "design advocacy" in many orgs, I've noticed some patterns:

1/n: the very things that get design the "seat at the table" become the limiters for further advocacy. So much effort to create a box ... and then you forever get put in it
2/n: @ryanrumsey talks about this eloquently, but you often see a complete resistance to making a cogent "business case" for why people should care.

Part of this is pride -- which is understandable -- but it becomes "design advocacy" vs. "design as a catalyst for X advocacy"
3/n: Instead of partnering to re-imagine a design-outcomes-friendly flow of product development, the focus is on advocating for how design should "fit in with" or "integrate with" X (whatever the engineering team is doing).

This further reinforces a sense of other-ness
Read 5 tweets
9 Apr
not sure this anyone would find this interesting...but this is how I go about doing my "loops" diagrams

1. first I use write simple things like this to get connections out of my head. at this point it is very rough...
2. I get a little more detailed/structured. All the while I validate these along the way and try to involve other people (hence my initials here vs. other contributors).
3. I do a lot of these ... it gets a bit out of control. I might end up with with hundreds of hypothesis connections
Read 8 tweets
4 Apr
anti-pattern: using one process/tool to do too many jobs

1/n teams "hire" processes and frameworks to do certain things. the trouble is that we humans get greedy. when someone says "well that does A,B, and C" we get excited. 3 for the price of 1!

The problem? ...
2/n First, it is hard to do lots of things well. The process rarely delivers across all of those jobs. It might do one thing well, but be kind of crappy at the other things...
3/n Second, communicating the Why can be very difficult. Say you have a process that is meant to promote learning/experimentation AND can be used to manage people and promote accountability.

Those two Whys can be in opposition at times.

"Wait, why are we doing this again?"
Read 5 tweets
3 Apr
Change agent tips:

1/n - There is so much you can do IF you accept that you have to do the old thing AND your new idea. People might look confused, but you will not get fired. Here's what I mean...
2/n - Say you work in a feature factory and features get thrown over the wall for you to "deliver". That doesn't stop you listing the various risks with that bet. It doesn't stop you describing the higher level bet/rationale.
3/n - Nothing is stopping you setting up a decision review a couple weeks after the thing has been "delivered", and your team has moved on to the next project. "We expected this ... but this is what happened.." (tip @Amplitude_HQ helps with this)
Read 10 tweets
3 Apr
Book recommendations that underscore that very little is “new” in terms of frameworks, advice, approaches, etc .... ?

(Think published >10 years ago)
of course ...@mpoppendieck
Read 9 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!