With roadmaps that contain a lot of information the gaps between the bars is to wide, and being able to reduce the size of those gaps would be useful in bunching the information up closer.
Here is the roadmap
I have attached an example roadmap where I have used the condensed view, and I have highlighted the white space. When you are presenting information particularly to senior Execs a couple of pixels of deadspace is prime retail. Yes if I removed the grouping here it would reduce the width but the reality is that grouping data is in all cases useful and important.
The issue with the Compact view is that you really have no way to controle how the results are organised. Its really down to the UI to "place things" wherever it feels there is space. With the other comments below, although I don't quite have the same issues of mgmnt not wanting to adopt a roadmap, there is a lot of dead space on roadmaps at times, and a few Pixels of movement in many many rows of information can make a big difference. A roadmap which flows onto another page when you could just as easily have a little more control over the width of the colums may make all the difference.
Thank you all for your feedback. I am curious...can you share which roadmap(s) you are trying to use where you run into issues with too much whitespace?
I did also want to note the compact view option on the custom roadmap -- which will condense the rows used.
We're facing the same issue with mgmt as Janice White's comment. Our mgmt team won't adopt the report because they want to see everything in one page.
I agree with Janice's comment. The extra white space requires the users to have to scroll more than they like and it makes it difficult to put the roadmap into a presentation.
This is critical to my use of Aha! roadmaps. In management reviews, they want to see a roadmap all on one page. Currently I cannot use Aha! roadmaps because of all the extra white space.