Good point. The terse details are there for two reasons: * Stakeholders need specifics -- While some managers just need to skim, some peers and deeper stakehol

Good point. The terse details are there for two reasons: * Stakeholders need specifics -- While some managers just need to skim, some peers and deeper stakeholders on the thread require details to validate the points because it impacts them specifically. * Managers want access to details -- The manager wants to be able to skim, but also have details on a specific item if they choose to dive into it (now or later). It's hard to tell which ones these will be, so providing extra information after the heading allows them to pick and choose without obstructing their quick-skim-ability.