pdrift

Currently looking for advice on writing, thought this was a useful summary.  Personally, I just stoped at the first one!

Write less often

Use fewer words

Put action words in your subject line

Listen more, “talk” less

Don’t answer, ask

Invert the order; lead with the need

Write a people-proof TL;DR

As a follow up to agile fatigue, I came accross this post from @astralwave

Completely sums up the tension that (bigger) businesses often face when updating/refreshing/transforming their approach to creating value.

I love the question...

How fast can I change course in response to new information that contradicts my prior beliefs? 

Sprint Anti-patterns of the Product Owner

Absent PO

PO clinging to tasks

Inflexible PO

Delaying PO

Misuse of Sprint cancellation

Business tooling is becoming a problem.  As technology hardware has become cosumer led, software is also heading in the same direction.  

Large businesses are constantly fighting the pseudo startup mentality (someone has used xx before at xx) - I know because I am part of this problem.

Underneath is difficulty in recognising that most problems nowadays have a solution and helping colleagues frame their “desire for xx service/software/platfom” as a need to solve a particular business problem can help.