Highlight from 'Impact-First Product Teams' by Matt LeMay

Some low-impact signs to watch out for: Teams that are only accountable for operational goals like velocity or number of features delivered Teams that reverse-engineer their goals from the work they already have planned Teams that broadly resist estimating impact because it’s “too complicated” or “involves too many things outside of our control”
— Matt LeMay, Impact-First Product Teams