Ben Voss

Curious.

[Ben Voss @benvoss]

"Impatience is an expensive emotion."

[Ben Voss @benvoss]

new post: https://t.co/Dba8kt6WJP

[Ben Voss @benvoss]

Friday's reading: https://t.co/uEWmyjKyeO

[Ben Voss @benvoss]

https://t.co/r6ZCBGp6l2

[Ben Voss @benvoss]

New post about Creating Adoption Planning for Internal Dev Tools -- https://t.co/Y31lTTIv5N

[Ben Voss @benvoss]

August post on value stream mapping: https://t.co/KSQu3knwXQ

[CARNUN @carnundotcom]

Unironically (of course) an excellent distillation of meta-advice. Very good practical epistemology here:

"The most common error of a smart engineer is to optimize a thing that should not exist."

[Ben Voss @benvoss]

https://t.co/GGqeg6GPEF

[Ben Voss @benvoss]

“Norman’s Law: The day the product team is announced, it is behind schedule and over its budget.”

― Donald A. Norman, The Design of Everyday Things

[Ben Voss @benvoss]

https://t.co/GOYuL7SDUJ

[Ben Voss @benvoss]

March's post: https://t.co/klL85AYnnJ

[Ben Voss @benvoss]

Today's reading: https://t.co/pUnm12Uilj

[Ben Voss @benvoss]

A reminder as a PM: writing docs and attending meetings are beneficial only in their relationship to influencing change in an engineering roadmap, and then upon release, the features improve a user's life.

[Ben Voss @benvoss]

Today's read: https://t.co/kOycxdH2MQ

[Ben Voss @benvoss]

today's reading: https://t.co/ThcAcqYJLj

[Ben Voss @benvoss]

February's post is released: https://t.co/2IuDyegya7

It's all about clarifying and establishing an internal product process. Let me know your thoughts!

[Ben Voss @benvoss]

“If we have data, let's look at the data. If all we have are opinions, let's go with mine.”

- Jim Barksdale

[Ben Voss @benvoss]

https://t.co/kh68NjMzcs

[Ben Voss @benvoss]

https://t.co/2u3o1IbqTT

[Ben Voss @benvoss]

"We aren't shipping the org to our customers. We're trying to ship products and solutions" - @arogal

So good -- in lieu of defining the products shipping internally, the default usually is the teams (the org) themselves.