I keep an old copy of Macromedia FreeHand MX on my laptop, which can run it comfortably most of the time. I think our IT department bought it off eBay for about $80. I wrote a tips journal on FreeHand ages ago, so I guess that makes me a privileged exec who makes IT maintain legacy systems on my whim.
At any rate, I keep FreeHand solely to make mock-ups of concepts or products that we discuss in meetings. I find this extraordinarily useful -- I can't tell you how often we spend 30 minutes discussing something in what seems to me to be extreme detail, only to find later that five people had pretty different notions of what we talked about. Often, I'm drawing really ugly swags of what a site element might look like, but also find myself creating what I can only assume are low-rent descriptions of business processes and user flows -- ideas, you could call them.
IT managers are used to (read: rely on) detailed schematics to describe data structures, network topographies and other complex concepts. Business owners -- particularly ones in smaller shops (such as ours) that aren't in a position to invest in business-wide BPM systems -- tend not to do visual models all that often, in my experience. Spreadsheets, yes; process flows, no.
Back when I was on the launch team of a genuine pre-bust dot-com, all we process mangers were issued a copy of Visio, which I have to confess didn't work out all that well. Like a lot of dot-com ideas, I think there was a germ of usefulness there, but not a lot of business discipline to execute it. Microsoft still pushes Visio, of course; earlier this year, it announced SQL Server data-mining features for the drawing tool (I'd guess Excel is the big selling point there), so obviously folks are still using it. You don't hear much about it, though, in the era of richer business process tools.
Analyst Bruce Silver takes a passing shot at Visio stencils in a summer column at BPMInstitute.org. That's about the best recent content on Visio and BPM that I found in a quick survey this afternoon. (You still do hear about Visio-based LAN mapping products and the like, of course.)
I'm going to explore employing Visio (or perhaps SmartDraw, but we are, admittedly, a Microsoft shop here) for some of our own process development and documentation. I'm not overly optimistic about getting everybody on board internally for this, and I imagine most smaller shops might have the same issues.
But the very least, I think, that when a business manager asks you what you think about some new model, it's fair to ask, "draw me a picture."