I'm of the mind that you've answered your own question, with a couple of caveats. You have two examples, so effectively you have your own A/B test.

If you are already talking to end users and consumers of this data and have garnered their opinion, after you have explained why you believe the second example is better (quick scan overview, simple to download, can't interact with the data on screen anyway) and they still prefer the 1st option, then it really isn't the job of the UX'er to persuade them otherwise.

They've given you the feedback.

What is the best way to show the user large amounts of data?
Let me start off by saying that I know just enough about electronics to be dangerous (how to solder, follow a simple schematic, and check for connectivity problems and usually figure out what each wire is for).

I've installed a cruise control kit in my car, and I want to use a set of Honda steering wheel controls instead of the stock controls from the kit.  The cruise kit controls are expecting 12 volts, but I'm not comfortable running any more than 5 volts through the small steering wheel wires next to the airbag wiring.  I'd prefer even less, like 2-3 volts.

So I need to build a switching circuit that will provide the 12 volt signals to the cruise kit.  I was thinking of keeping it solid-state, since I don't know of any relays that will switch on 2-3 volts.  However, if there's a good reason to use relays then I can.

Here's a rough drawing of what I need:



How can I get started with this project?
