He got the stakeholders to agree on a limit on the number of business goals for a release. Then he eliminated superfluous scope by insisting that each feature references a requirement it fulfils, and that each requirement references the goal it supports. Berkun wrote that such mapping allowed his teams to decide which features should or should not be part of a delivery, which ones should be reprioritised when business goals changed and which were critical for success.
