@JustAnotherPM I’d ask them “given what you DO know, what’s the forecast range?” The range illustrates their level of uncertainty, it’d be up to me to determine if that is ok. (Ideally I’d have flow data and not worry about estimating at all)
@PatThePM 1: I separate actions from FYIs
2: I write actions in a notebook by hand. I get the time needed slow down and evaluate actions.
3: I review notes often, strike non-essentials
4: I set Slack reminders for FYIs
5: I have a tab group named “to read”
6: Breathe. Slow down.
“Protect Value” is work to ensure validated user value continues. It is NOT tech debt. PV-work is maybe not as fancy as “Create New Value”, but it’s validated and valued, unlike “New Value”. Should be easy to prio most of the time.
If you care about predictability, you should care about product quality first.
Bugs, incidents & tech debt will ruin any attempt at increasing predictability of product delivery.
@tottinge That could be useful! How might one avoid hindsight and/or selection bias? Many things influence flow, couldn’t it be tricky to attribute the “right” cause(s)?
Then again, that problem remains without this feature. It could enable identifying patterns over time 🤔
@PatThePM We use the same word but often expect different behaviors. Should prio 1:
- start first?
- end first?
- get most funding?
- other?
Priority is hard when we don’t agree on what behaviors to expect as a result of using it.