<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Qlikview User interface best practice in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Qlikview-User-interface-best-practice/m-p/315207#M116321</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't agree with everything that Stephen Few says, but I agree with most of it.&amp;nbsp; Shortly after we started using QlikView, I read a few of his books, and they gave me a good foundation.&amp;nbsp; It's a good place to start.&amp;nbsp; And yes, there have been QlikTech webinars and I'm sure other presentations on dashboard design, and they pretty much repeat everything Stephen says.&amp;nbsp; For all I know, he helped write their training materials, or agreed that they could copy everything out of his books.&amp;nbsp; So if you want to impress someone who believes every word he heard in his QlikView training, then you'll want to know what Stephen Few has to say.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As for my own comments...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The purpose of a dashboard is not to impress, but to INFORM.&lt;/STRONG&gt;&amp;nbsp; The dashboard should be CLEAN, with no wasted pixels, no design element that doesn't serve a purpose.&amp;nbsp; That color gradient you like so much?&amp;nbsp; Get rid of it and use a white or off white background.&amp;nbsp; Those 3D bars?&amp;nbsp; They're just making the data harder to read.&amp;nbsp; You aren't an artist, and even if you are, you aren't here to make art.&amp;nbsp; You're here to give people the exact information they need, comprehended at a glance, with no distractions.&amp;nbsp; Don't worry, there's beauty in simplicity, so you don't have to turn off the right side of your brain.&amp;nbsp; You just have to use it appropriately.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 28 Jul 2011 19:18:01 GMT</pubDate>
    <dc:creator>johnw</dc:creator>
    <dc:date>2011-07-28T19:18:01Z</dc:date>
    <item>
      <title>Qlikview User interface best practice</title>
      <link>https://community.qlik.com/t5/QlikView/Qlikview-User-interface-best-practice/m-p/315205#M116319</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are there any documents which describe best working practices when creating a user interface of a dashboard?&lt;/P&gt;&lt;P&gt;I did a search but I can only find a document to do with mobile applicaiton's not desktop.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am in the process of applying for a Qlikview position and this is one of the quesions they have asked.&amp;nbsp; &lt;/P&gt;&lt;P&gt;I think the guy who asked the question has been on the Qlikview training course where this is covered and I haven't, obviously!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jul 2011 16:02:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Qlikview-User-interface-best-practice/m-p/315205#M116319</guid>
      <dc:creator />
      <dc:date>2011-07-28T16:02:10Z</dc:date>
    </item>
    <item>
      <title>Qlikview User interface best practice</title>
      <link>https://community.qlik.com/t5/QlikView/Qlikview-User-interface-best-practice/m-p/315206#M116320</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; hi BlackburnRovers,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;check out this website&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.perceptualedge.com/"&gt;http://www.perceptualedge.com/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Qliktech were pushing Stephen Few a couple of years ago so that would be a good starting point.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;good luck with the job hunting!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jul 2011 16:51:43 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Qlikview-User-interface-best-practice/m-p/315206#M116320</guid>
      <dc:creator>pat_agen</dc:creator>
      <dc:date>2011-07-28T16:51:43Z</dc:date>
    </item>
    <item>
      <title>Qlikview User interface best practice</title>
      <link>https://community.qlik.com/t5/QlikView/Qlikview-User-interface-best-practice/m-p/315207#M116321</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't agree with everything that Stephen Few says, but I agree with most of it.&amp;nbsp; Shortly after we started using QlikView, I read a few of his books, and they gave me a good foundation.&amp;nbsp; It's a good place to start.&amp;nbsp; And yes, there have been QlikTech webinars and I'm sure other presentations on dashboard design, and they pretty much repeat everything Stephen says.&amp;nbsp; For all I know, he helped write their training materials, or agreed that they could copy everything out of his books.&amp;nbsp; So if you want to impress someone who believes every word he heard in his QlikView training, then you'll want to know what Stephen Few has to say.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As for my own comments...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The purpose of a dashboard is not to impress, but to INFORM.&lt;/STRONG&gt;&amp;nbsp; The dashboard should be CLEAN, with no wasted pixels, no design element that doesn't serve a purpose.&amp;nbsp; That color gradient you like so much?&amp;nbsp; Get rid of it and use a white or off white background.&amp;nbsp; Those 3D bars?&amp;nbsp; They're just making the data harder to read.&amp;nbsp; You aren't an artist, and even if you are, you aren't here to make art.&amp;nbsp; You're here to give people the exact information they need, comprehended at a glance, with no distractions.&amp;nbsp; Don't worry, there's beauty in simplicity, so you don't have to turn off the right side of your brain.&amp;nbsp; You just have to use it appropriately.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jul 2011 19:18:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Qlikview-User-interface-best-practice/m-p/315207#M116321</guid>
      <dc:creator>johnw</dc:creator>
      <dc:date>2011-07-28T19:18:01Z</dc:date>
    </item>
    <item>
      <title>Qlikview User interface best practice</title>
      <link>https://community.qlik.com/t5/QlikView/Qlikview-User-interface-best-practice/m-p/315208#M116322</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks guys, I'll try and get hold of a copy over the weekend before my interview on Monday.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jul 2011 21:43:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Qlikview-User-interface-best-practice/m-p/315208#M116322</guid>
      <dc:creator />
      <dc:date>2011-07-28T21:43:22Z</dc:date>
    </item>
  </channel>
</rss>

