One of my team members has tried screen mock-ups with text call-outs for some of the details. They have been very well received by business stakeholders, and are easier for the BA to speak from in terms of describing the functionality. The mocked-up screens with call-outs adds seems to add a needed dimension of context/color to the "BTD".

Only in the last couple of years have a I begun to "come around" to the value of visuals for the audience to review and understand what I deliver. For may years, I think, in retrospect, that I took it personally that my reviewers were not reading the efforts of my labor. However, you're correct. When I ask myself whether I'd like to read my diatribe, it's a resounding "No!" I hear.

That being said, I do think that proper documentation has a very cozy relationship aside visuals and that the two should go together. Visuals alone capture the surface and struggle to define what's occurring underneath the surface. Documentation dries out one's eyelids but does provide a venue to capture things that cannot be described in a visual. As with anything else in life, a healthy balance between the two gives the satisfying experience for any type of audience…..including the analyst …..who now has someone that will actually read what is produced.

Doug