The document summarizes a Tableau User Group meeting focused on storytelling best practices for data visualization. It discusses keeping visualizations simple, clear, and efficient. It also covers considerations for audience, layout, color palettes, and appropriate chart and graph types. The meeting included a hands-on training using sales data and an example of a polished baseball ticket sales story point. It concluded with time for questions and discussion.
As a Digital PR firm we use several techniques to get the attention of journalists, but there's one of them that I haven't seen being used a lot by brands outside of digital PR and that's games.
You might think that a game is not suitable for every type of product, but during my talk I'll show several examples on how you can advertise your brand and grab the attention of your audience and the media by "gamifying" your content.
Moreover, we'll explore ways of taking the games further and make them into data that you can outreach and also how to make this content evergreen.
SharePoint projects are wickedly complex. Among the reasons: You are dealing with loosely defined big-picture issues like collaboration, information sharing, portal navigation and information organization; and you are trying to define these solutions within the context of the social complexity that exists in all organizations. The result is that you end up with solutions that may satisfy some of your stakeholders, but which leave others disengaged, disenfranchised and disappointed. Getting to success is dependent on reaching a shared understanding, followed by a shared commitment from all of the participants and stakeholders.
We have discovered that visual tools can very quickly allow groups of people to get to shared understanding and commitment. We will share our techniques with you and teach you how to use free or very inexpensive tools that allow you elicit your clients' goals. We then show you to prioritize, map and construct the solution.
We will cover the use of Gamestorming and Innovation Games, which use the concepts of games to get to serious results in a much less painless way than the usual planning and requirements workshops. We will demonstrate the use of mind mapping for navigational design, taxonomy design, prioritization and capturing the thought process of a team via an interactive process.
Are you tired of attending or leading the same old boring requirements-gathering sessions? Would you like to find a way to get stakeholders excited about requirements gathering? Then this class is for you!
Find out how to use collaborative play to build better solution requirements for SharePoint projects (or any other project for that matter). In this class, you will learn seriously fun ways to do work-seriously! Learn how to tap into true innovation and uncover hidden business requirements. What are you waiting for? Come to this class and learn how to put these tools into action!
By attending this class, you will be able to:
Introduce new and field-tested concepts for creating a clear and compelling vision for SharePoint
Facilitate more effective requirements-gathering sessions
Identify and avoid five problem patterns that plague many project teams
Hit the ground running with new templates that you can use to facilitate your own Innovation Games
As a Digital PR firm we use several techniques to get the attention of journalists, but there's one of them that I haven't seen being used a lot by brands outside of digital PR and that's games.
You might think that a game is not suitable for every type of product, but during my talk I'll show several examples on how you can advertise your brand and grab the attention of your audience and the media by "gamifying" your content.
Moreover, we'll explore ways of taking the games further and make them into data that you can outreach and also how to make this content evergreen.
SharePoint projects are wickedly complex. Among the reasons: You are dealing with loosely defined big-picture issues like collaboration, information sharing, portal navigation and information organization; and you are trying to define these solutions within the context of the social complexity that exists in all organizations. The result is that you end up with solutions that may satisfy some of your stakeholders, but which leave others disengaged, disenfranchised and disappointed. Getting to success is dependent on reaching a shared understanding, followed by a shared commitment from all of the participants and stakeholders.
We have discovered that visual tools can very quickly allow groups of people to get to shared understanding and commitment. We will share our techniques with you and teach you how to use free or very inexpensive tools that allow you elicit your clients' goals. We then show you to prioritize, map and construct the solution.
We will cover the use of Gamestorming and Innovation Games, which use the concepts of games to get to serious results in a much less painless way than the usual planning and requirements workshops. We will demonstrate the use of mind mapping for navigational design, taxonomy design, prioritization and capturing the thought process of a team via an interactive process.
Are you tired of attending or leading the same old boring requirements-gathering sessions? Would you like to find a way to get stakeholders excited about requirements gathering? Then this class is for you!
Find out how to use collaborative play to build better solution requirements for SharePoint projects (or any other project for that matter). In this class, you will learn seriously fun ways to do work-seriously! Learn how to tap into true innovation and uncover hidden business requirements. What are you waiting for? Come to this class and learn how to put these tools into action!
By attending this class, you will be able to:
Introduce new and field-tested concepts for creating a clear and compelling vision for SharePoint
Facilitate more effective requirements-gathering sessions
Identify and avoid five problem patterns that plague many project teams
Hit the ground running with new templates that you can use to facilitate your own Innovation Games
If you want to learn more about emotional design, check out our Skillshare course: http://skl.sh/1jqYHZ5
This talk has been presented at:
- UXPA 2015
- SoCal UX Camp 2015
- SDXD September Meetup
- Zillow Speaker Series
Explore three specific survey gamification examples that can improve engagement in your next online survey, increase response rates, and generally make your survey suck less.
Presented in Gamers in Society seminar in Tampere, Finland (spring 2007). Mainly about introducing phenomenon of casual games and terminology for studying the casual IN games phenomenon.
Collaborative games encourage participants in an elicitation activity to collaborate in building a joint understanding of a problem or a solution. Collaborative games refer to several structured techniques inspired by game play and are designed to facilitate collaboration. During this webinar we will review the elements such as game purpose, process, outcome and various examples of collaborative games (product box, affinity map and fishbowl).
Are we getting the intended emotional response we set out to achieve? In this seminar, we explore the powerful effects of emotion in design; from the way we create interfaces to the way we communicate with our clients.
We focus on methods that help us create engaging digital experiences that impacts the organization's brand entity by focusing on the customer’s wants and needs.
User Story Point estimation method at ConFoo 2015Fred Heath
We'll initially examine how and why estimation in Agile goes so wrong, so often. A new, structured and empirical method for estimating story points will then be introduced. The method involves taking into account human and environment-related factors, as well as technical ones, assigns weighted points to them and uses a numeric formula to derive a user-story's point estimate.
I read, reviewed and digested the excellent The Art of Estimation by Steve McConnell and presented back what I'd learned about software estimation to the team.
Agile User Stories | The complete ReviewDavid Tzemach
The main sections of this presentation
1. Overview
2. Story Points vs. Time Estimations
3. The responsibilities
4. The benefits of using stories
5. How to write great stories
6. The mistake you can do when writing stories
7. A Template for writing stories
8. Key components of stories
The evolution of agile development processDavid Tzemach
The Evolution of Agile Development Process
The main sections of this presentation
1. Overview
2. The Waterfall Model as a baseline
3. Waterfall Model – Phases of the process
4. The problem in traditional models
5. Agile Software Development as the Alternative
6. The Agile Manifesto – The Beginning
7. The Manifesto for Agile Software Development
8. The benefits of the agile methodology
Ever wonder why Agile teams swear by relative estimation? My teams improved sprint planning efforts by a factor or 3, once we started using relative estimation.
Without understanding Agile relative estimation, teams tend to fall back to using time-based methods. This often leads them to spend way too much time on obsolete estimates that will be made even more complex with all the unknowns and constant emergent requirements of an Agile world!
“It's better to be roughly right, than precisely wrong!”
~ John Maynard Keyenes
The Solution is simple: understand that relative estimation is only a rough order of magnitude estimate to quickly organize the product backlog. This empowers your product owners (PO) to quickly make value based trade-offs on backlog items and decide on what stories the team should work next. This gives the business the highest bang for their buck!
PROBLEMS WITH TIME-BASED ESTIMATES
-Teams spend too much time trying to get it right
-Lack of confidence/experience can lead to people being either optimistic or pessimistic
-Timeline you are estimating may be too far in the future
-Due to long timeline, there are too many risks, unknowns, changes or dependencies!
WHY USE RELATIVE ESTIMATION?
-Allows a quick comparison of stories in the backlog
-Allows you to select a predictable volume of work to do in a sprint
-Uses a simple arbitrary scale
-Allows PO to make trade-offs and take on the most valuable stories next
ESTIMATION TIPS
-Relative points or equivalent Tshirt sizes are used to estimate stories, leveraging the Fibonacci sequence modified for Agile.
-The team estimates the story, not management nor the customer.
-Story estimates account for three things: effort, complexity, and unknowns. Don’t short sell yourself by estimating effort alone, that’s where waterfall projects face issues.
-Remember to estimate all Stories, user stories or technical stories. Even estimate research or discovery spikes.
-Refine your backlog as a team on a continuous basis, to get your stories to meet the Definition of Ready.
-Only pull into your sprint, stories that are refined and estimated.
-Break down stories that are large, into smaller slivers of value to optimize your flow.
-Don’t sweat it if you get it wrong, teams often do early on but improve over time.
If you want to learn more about emotional design, check out our Skillshare course: http://skl.sh/1jqYHZ5
This talk has been presented at:
- UXPA 2015
- SoCal UX Camp 2015
- SDXD September Meetup
- Zillow Speaker Series
Explore three specific survey gamification examples that can improve engagement in your next online survey, increase response rates, and generally make your survey suck less.
Presented in Gamers in Society seminar in Tampere, Finland (spring 2007). Mainly about introducing phenomenon of casual games and terminology for studying the casual IN games phenomenon.
Collaborative games encourage participants in an elicitation activity to collaborate in building a joint understanding of a problem or a solution. Collaborative games refer to several structured techniques inspired by game play and are designed to facilitate collaboration. During this webinar we will review the elements such as game purpose, process, outcome and various examples of collaborative games (product box, affinity map and fishbowl).
Are we getting the intended emotional response we set out to achieve? In this seminar, we explore the powerful effects of emotion in design; from the way we create interfaces to the way we communicate with our clients.
We focus on methods that help us create engaging digital experiences that impacts the organization's brand entity by focusing on the customer’s wants and needs.
User Story Point estimation method at ConFoo 2015Fred Heath
We'll initially examine how and why estimation in Agile goes so wrong, so often. A new, structured and empirical method for estimating story points will then be introduced. The method involves taking into account human and environment-related factors, as well as technical ones, assigns weighted points to them and uses a numeric formula to derive a user-story's point estimate.
I read, reviewed and digested the excellent The Art of Estimation by Steve McConnell and presented back what I'd learned about software estimation to the team.
Agile User Stories | The complete ReviewDavid Tzemach
The main sections of this presentation
1. Overview
2. Story Points vs. Time Estimations
3. The responsibilities
4. The benefits of using stories
5. How to write great stories
6. The mistake you can do when writing stories
7. A Template for writing stories
8. Key components of stories
The evolution of agile development processDavid Tzemach
The Evolution of Agile Development Process
The main sections of this presentation
1. Overview
2. The Waterfall Model as a baseline
3. Waterfall Model – Phases of the process
4. The problem in traditional models
5. Agile Software Development as the Alternative
6. The Agile Manifesto – The Beginning
7. The Manifesto for Agile Software Development
8. The benefits of the agile methodology
Ever wonder why Agile teams swear by relative estimation? My teams improved sprint planning efforts by a factor or 3, once we started using relative estimation.
Without understanding Agile relative estimation, teams tend to fall back to using time-based methods. This often leads them to spend way too much time on obsolete estimates that will be made even more complex with all the unknowns and constant emergent requirements of an Agile world!
“It's better to be roughly right, than precisely wrong!”
~ John Maynard Keyenes
The Solution is simple: understand that relative estimation is only a rough order of magnitude estimate to quickly organize the product backlog. This empowers your product owners (PO) to quickly make value based trade-offs on backlog items and decide on what stories the team should work next. This gives the business the highest bang for their buck!
PROBLEMS WITH TIME-BASED ESTIMATES
-Teams spend too much time trying to get it right
-Lack of confidence/experience can lead to people being either optimistic or pessimistic
-Timeline you are estimating may be too far in the future
-Due to long timeline, there are too many risks, unknowns, changes or dependencies!
WHY USE RELATIVE ESTIMATION?
-Allows a quick comparison of stories in the backlog
-Allows you to select a predictable volume of work to do in a sprint
-Uses a simple arbitrary scale
-Allows PO to make trade-offs and take on the most valuable stories next
ESTIMATION TIPS
-Relative points or equivalent Tshirt sizes are used to estimate stories, leveraging the Fibonacci sequence modified for Agile.
-The team estimates the story, not management nor the customer.
-Story estimates account for three things: effort, complexity, and unknowns. Don’t short sell yourself by estimating effort alone, that’s where waterfall projects face issues.
-Remember to estimate all Stories, user stories or technical stories. Even estimate research or discovery spikes.
-Refine your backlog as a team on a continuous basis, to get your stories to meet the Definition of Ready.
-Only pull into your sprint, stories that are refined and estimated.
-Break down stories that are large, into smaller slivers of value to optimize your flow.
-Don’t sweat it if you get it wrong, teams often do early on but improve over time.
This presentation discusses the following:
What is an estimate?
What are the factors influencing estimating?
How are agile projects estimated?
How Agile estimation solves common estimation problems?
Do you want to get your SharePoint project right the first time? It has been our experience that there is no way for a project to succeed if the stakeholders and solution designers are not in alignment, no matter how good the solution. If your technical team and business stakeholders are not on the same page then the project will fail. The problem is that getting the business stakeholders to tell you their vision and understand what success looks like to them is very difficult.
Over the past decade of delivering successful SharePoint projects, we have discovered methods that work very well at eliciting the stakeholders' desires and then ensuring that we have clarified our own understanding with them. These methods involve the use of visual and tactile tools that open the lines of communication and rapidly expose misunderstandings.
We will demonstrate tools such as mind mapping, card sorting, gamestorming, tree-testing and other methods, and we will have you participate in exercises that will give you the confidence to apply these tools in your own practice. Many of these methods are very easy to learn and apply, and this workshop will give you the confidence to do so.
The application of these visual tools has directly influenced the success of the many projects we've worked on over the years. We won't be giving you theory, but rather stories and examples from our real-life experience. We hope you'll join us for a practical, useful, fun and enlightening experience.
Talk presented at the Houston UX Professional Association (H-UXPA) meeting on May 23, 2018
Abstract:
Data visualization is a general term to describe any effort to help people understand the significance of data by putting it in a visual context. Important stories live in our data, and data visualization is a powerful way to discover, understand, and share these stories with others. Conveying the meaning behind the story is most effective when the information is easily and rapidly grasped by our eyes so that our brains can readily understand. Executing this process effectively is much more a science than an art, and requires an understanding of how human perception works. Join me in this journey where we will walk through how our brains decode information and how we can leverage perceptual principles to create meaningful graphical interfaces between people and data.
Visual tools and innovation games workshop - SPTechCon - Apr 2014Ruven Gotz
Half-day workshop presented by Michelle Caldwell and Ruven Gotz on getting to shared understand and better requirements for your SharePoint projects through the use of Visual Tools (such as mind mapping, wireframing, and card sorting) and Gamestorming (also called Innovation Games)
Slides talk about importance & guidelines of sketching and story boarding. It discusses two approaches about "getting the design right" or getting the right design". Steps and Do's/Dont's of storyboarding
SharePoint projects are wickedly complex. Among the reasons: You are dealing with loosely defined big-picture issues like collaboration, information sharing, portal navigation and information organization; and you are trying to define these solutions within the context of the social complexity that exists in all organizations. The result is that you end up with solutions that may satisfy some of your stakeholders, but which leave others disengaged, disenfranchised and disappointed. Getting to success is dependent on reaching a shared understanding, followed by a shared commitment from all of the participants and stakeholders.
We have discovered that visual tools can very quickly allow groups of people to get to shared understanding and commitment. We will share our techniques with you and teach you how to use free or very inexpensive tools that allow you elicit your clients' goals. We then show you to prioritize, map and construct the solution.
We will cover the use of Gamestorming and Innovation Games, which use the concepts of games to get to serious results in a much less painless way than the usual planning and requirements workshops. We will demonstrate the use of mind mapping for navigational design, taxonomy design, prioritization and capturing the thought process of a team via an interactive process.
A date with data - CI’s Great British data visualisation adventureicemobile
Last August our CI team hopped the English channel to learn about Data visualisation from British newspaper the Guardian. This presentation highlights their key learnings.
Data visualization & Story Telling with DataDr Nisha Arora
Storytelling with data using the appropriate visualization is a skill that is well sought-after for data-driven decision making and it spans many industries and roles (technical/non-technical).
In this presentation, we will briefly discuss the importance of understanding the context, selecting the right visuals, key points for effectively using those for storytelling, design dos, and don’ts, etc.
Visual tools and innovation games workshop - spscbus - aug 2014Ruven Gotz
A 'meta' presentation about metadata - tools you can use to explain metadata, taxonomy and content types to your stakeholders. Presented at SharePoint Saturday Columbus (SPSCBUS), Aug 23, 2014 [DOWNLOAD THE FULL DECK TO GET SPEAKER'S NOTES]
SharePoint projects are wickedly complex. Among the reasons: You are dealing with loosely defined big-picture issues like collaboration, information sharing, portal navigation and information organization; and you are trying to define these solutions within the context of the social complexity that exists in all organizations. The result is that you end up with solutions that may satisfy some of your stakeholders, but which leave others disengaged, disenfranchised and disappointed. Getting to success is dependent on reaching a shared understanding, followed by a shared commitment from all of the participants and stakeholders.
We have discovered that visual tools can very quickly allow groups of people to get to shared understanding and commitment. We will share our techniques with you and teach you how to use free or very inexpensive tools that allow you elicit your clients' goals. We then show you to prioritize, map and construct the solution.
We will cover the use of Gamestorming and Innovation Games, which use the concepts of games to get to serious results in a much less painless way than the usual planning and requirements workshops. We will demonstrate the use of mind mapping for navigational design, taxonomy design, prioritization and capturing the thought process of a team via an interactive process.
Similar to Story Point Training - Tableau User Group - October 2014 (20)
Techniques to optimize the pagerank algorithm usually fall in two categories. One is to try reducing the work per iteration, and the other is to try reducing the number of iterations. These goals are often at odds with one another. Skipping computation on vertices which have already converged has the potential to save iteration time. Skipping in-identical vertices, with the same in-links, helps reduce duplicate computations and thus could help reduce iteration time. Road networks often have chains which can be short-circuited before pagerank computation to improve performance. Final ranks of chain nodes can be easily calculated. This could reduce both the iteration time, and the number of iterations. If a graph has no dangling nodes, pagerank of each strongly connected component can be computed in topological order. This could help reduce the iteration time, no. of iterations, and also enable multi-iteration concurrency in pagerank computation. The combination of all of the above methods is the STICD algorithm. [sticd] For dynamic graphs, unchanged components whose ranks are unaffected can be skipped altogether.
Opendatabay - Open Data Marketplace.pptxOpendatabay
Opendatabay.com unlocks the power of data for everyone. Open Data Marketplace fosters a collaborative hub for data enthusiasts to explore, share, and contribute to a vast collection of datasets.
First ever open hub for data enthusiasts to collaborate and innovate. A platform to explore, share, and contribute to a vast collection of datasets. Through robust quality control and innovative technologies like blockchain verification, opendatabay ensures the authenticity and reliability of datasets, empowering users to make data-driven decisions with confidence. Leverage cutting-edge AI technologies to enhance the data exploration, analysis, and discovery experience.
From intelligent search and recommendations to automated data productisation and quotation, Opendatabay AI-driven features streamline the data workflow. Finding the data you need shouldn't be a complex. Opendatabay simplifies the data acquisition process with an intuitive interface and robust search tools. Effortlessly explore, discover, and access the data you need, allowing you to focus on extracting valuable insights. Opendatabay breaks new ground with a dedicated, AI-generated, synthetic datasets.
Leverage these privacy-preserving datasets for training and testing AI models without compromising sensitive information. Opendatabay prioritizes transparency by providing detailed metadata, provenance information, and usage guidelines for each dataset, ensuring users have a comprehensive understanding of the data they're working with. By leveraging a powerful combination of distributed ledger technology and rigorous third-party audits Opendatabay ensures the authenticity and reliability of every dataset. Security is at the core of Opendatabay. Marketplace implements stringent security measures, including encryption, access controls, and regular vulnerability assessments, to safeguard your data and protect your privacy.
Show drafts
volume_up
Empowering the Data Analytics Ecosystem: A Laser Focus on Value
The data analytics ecosystem thrives when every component functions at its peak, unlocking the true potential of data. Here's a laser focus on key areas for an empowered ecosystem:
1. Democratize Access, Not Data:
Granular Access Controls: Provide users with self-service tools tailored to their specific needs, preventing data overload and misuse.
Data Catalogs: Implement robust data catalogs for easy discovery and understanding of available data sources.
2. Foster Collaboration with Clear Roles:
Data Mesh Architecture: Break down data silos by creating a distributed data ownership model with clear ownership and responsibilities.
Collaborative Workspaces: Utilize interactive platforms where data scientists, analysts, and domain experts can work seamlessly together.
3. Leverage Advanced Analytics Strategically:
AI-powered Automation: Automate repetitive tasks like data cleaning and feature engineering, freeing up data talent for higher-level analysis.
Right-Tool Selection: Strategically choose the most effective advanced analytics techniques (e.g., AI, ML) based on specific business problems.
4. Prioritize Data Quality with Automation:
Automated Data Validation: Implement automated data quality checks to identify and rectify errors at the source, minimizing downstream issues.
Data Lineage Tracking: Track the flow of data throughout the ecosystem, ensuring transparency and facilitating root cause analysis for errors.
5. Cultivate a Data-Driven Mindset:
Metrics-Driven Performance Management: Align KPIs and performance metrics with data-driven insights to ensure actionable decision making.
Data Storytelling Workshops: Equip stakeholders with the skills to translate complex data findings into compelling narratives that drive action.
Benefits of a Precise Ecosystem:
Sharpened Focus: Precise access and clear roles ensure everyone works with the most relevant data, maximizing efficiency.
Actionable Insights: Strategic analytics and automated quality checks lead to more reliable and actionable data insights.
Continuous Improvement: Data-driven performance management fosters a culture of learning and continuous improvement.
Sustainable Growth: Empowered by data, organizations can make informed decisions to drive sustainable growth and innovation.
By focusing on these precise actions, organizations can create an empowered data analytics ecosystem that delivers real value by driving data-driven decisions and maximizing the return on their data investment.
As Europe's leading economic powerhouse and the fourth-largest hashtag#economy globally, Germany stands at the forefront of innovation and industrial might. Renowned for its precision engineering and high-tech sectors, Germany's economic structure is heavily supported by a robust service industry, accounting for approximately 68% of its GDP. This economic clout and strategic geopolitical stance position Germany as a focal point in the global cyber threat landscape.
In the face of escalating global tensions, particularly those emanating from geopolitical disputes with nations like hashtag#Russia and hashtag#China, hashtag#Germany has witnessed a significant uptick in targeted cyber operations. Our analysis indicates a marked increase in hashtag#cyberattack sophistication aimed at critical infrastructure and key industrial sectors. These attacks range from ransomware campaigns to hashtag#AdvancedPersistentThreats (hashtag#APTs), threatening national security and business integrity.
🔑 Key findings include:
🔍 Increased frequency and complexity of cyber threats.
🔍 Escalation of state-sponsored and criminally motivated cyber operations.
🔍 Active dark web exchanges of malicious tools and tactics.
Our comprehensive report delves into these challenges, using a blend of open-source and proprietary data collection techniques. By monitoring activity on critical networks and analyzing attack patterns, our team provides a detailed overview of the threats facing German entities.
This report aims to equip stakeholders across public and private sectors with the knowledge to enhance their defensive strategies, reduce exposure to cyber risks, and reinforce Germany's resilience against cyber threats.
3. Introduction
Story Telling Best Practices
- Simplicity
- Clarity
- Efficiency
Discuss Audience, Layout, Color, Charts and Graphs
Introduction to Story Points: Hands on Training with Sales data
Show a Polished Baseball Ticket Sales Story Point
Questions and Discussion
2
5. Story Telling Best Practices
Dashboards
that
Persuad
e,
Inform,
and
Engage
Will…
§ Be easy to read and understand
§ Create actionable insight (moral of the story)
§ Keep in mind if a data visual won’t change how you or
your company behaves, it’s a bad visual.
§ Be more likely to be reused
§ Answer your question within seconds and not a second glance
§ Reflect the truth in the data
K.I.S.S.
Keep it Simple, Stupid.
4
6. Story Telling Best Practices
1. Simplicity
• Understood at a glance
• Think about a Rubik’s Cube
2. Clarity
• Harmony and balance
3. Efficiency
• Minimal complexity
• Maximum ease of use
8. Story
Telling
in
AcEon
“Thank
you,
Chicago….1. Know your Audience we
love
you!”
2. Think through your Layout
3. Choose an appropriate Color palette
4. Know Graph and Chart best practices
9. Audience
Know your Audience
- What does your audience need to know?
- What do they need to do?
- How can you make the data you want to share
meaningful and memorable?
10. Layout
“OrganizaEon
of
data
is
one
of
the
most
overlooked
pieces
of
designing
a
dashboard.
A
dashboard
with
thoughQul
organizaEon
and
the
right
graphical
views
will
create
a
channel
of
clear
and
rapid
data
discovery.”
-‐
Jon
Dugger
(2014)
12. Color
1. Do not distract from the data
2. Use a neutral color palette
3. Use a limited color palette
- No more than 5
4. Minimize the labor for the end user