"obtaining a deep understanding of the information to be conveyed and employing artistic skill to communicate the message visually."
Let's be honest, in #product, we could improve in both information understanding & visualization.
/2
Apr 29, 2022 • 11 tweets • 3 min read
Probably the MOST abused and thus harmful principle of the #Agile Manifesto is:
"Responding to change over following a plan"
Here's a thread 🧵on how to think about it in logical and rational way, that hopeful removes whatever confusion people have.
#product#prodmgmt
1/n
Each of the 4 main statements of Manifesto are structured as
<a> over <b>
e.g.
Customer collaboration over contract negotiation
Meaning that while both may be necessary, focus MORE on the left i.e. <a>, and LESS on the right i.e. <b>
2/n
Mar 7, 2022 • 6 tweets • 2 min read
PRO TIP.
Product managers should explicitly track all the ‘specials’ they’ve done for the Sales org, and then remind them at sales training or sales kickoff of how much revenue this generated.
Also remind Sales of what WASN’T done or what was delayed because of that work.
BTW, this is the process I used in a couple of companies to handle these requests.
To reduce adhoc requests from sales for these "specials" we had an escalation process - first up through sales management and sales engineering, then discussed with Product Management. /1
Jul 26, 2019 • 23 tweets • 5 min read
@H2RProductSci @united Another @united incident that happened to me a couple of years back.
Had flight from DC->Toronto, scheduled for 12:30 pm. Got to airport & flight was listed as 2:00pm departure.
Every 30 minutes departure time would get push out by another 30 minutes. No announcements /1
@H2RProductSci @united Finally around 6:00PM, we were called to board. No explanations were offered about why the delay except "mechanical problems".
We boarded and left the gate around 6:30.
We taxi'd a bit, and then captain spoke that an "indicator light" had come on. /2