Hi Jim. I really sympathise with your problem. I used to work
for a company where a similar setup existed and it never ceased to
amaze me how we were expected to use our crystal ball to figure out
what our users wanted. Perhaps you could ask your Marketing
Director if they'd like the users to be provided with the best
possible solution for their needs! Anyhow onwards and upwards!
IMHO I'd only add a browse sequence if I thought it added
value to the documentation OR the user requested them. If you
include them and your users won't know if they exist or not, you're
not loosing much. If you have them and at least one of your users
use them, then you can argue they are useful. Admittedly they are a
bit of extra work. I'd say (hesitantly) that most RH Technical
Authors don't use them although that has probably more to do with
the documentation they produce and its audience.
At the end of the day it is a judgement call that is hard to
make without knowing more about your users and the documentation.
Hope this helped