Showing posts with label visualisation. Show all posts
Showing posts with label visualisation. Show all posts

Lightweight, open-source tools to visualise logs

Mike's Notes

Google Search - AI Mode (Gemini) was used to find a lightweight tool to visualise logs.

This is a first look at what might be possible. The tool needs to run on Windows and Linux. Will start on this job after the Log Engine (log) has been imported.

The output will be embedded on the Mission Control web pages. iframe?

Resources

  • Resource

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

22/04/2026

Lightweight, open-source tools to visualise logs

By: Mike Peters and Gemini
On a Sandy Beach: 22/04/2026

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

Gemini is cool

Several lightweight, open-source tools can visualise logs and are specifically designed for web embedding. These range from full log management platforms with embedded dashboards to standalone JavaScript libraries for building custom visualisations. [1, 2, 3, 4] 

Recommended Log Visualisation Tools

  • [GoAccess](https://goaccess.io/): A fast, real-time web log analyser that can generate a self-contained, interactive HTML report. It is designed for zero-overhead visibility and is ideal for developers who need to embed server traffic statistics into a web page.
  • [SigNoz](https://signoz.io/): An open-source observability platform that unifies logs, metrics, and traces. It is built on OpenTelemetry standards and uses ClickHouse for high-performance, cost-effective storage. It offers a variety of visualisation options, such as charts and graphs, to gain insights into log data.
  • OpenObserve: A lightweight, unified observability tool that can be self-hosted as a single binary. It supports SQL-based queries and uses highly efficient storage (up to 140x compression), making it extremely cost-effective for high-volume logs.
  • Parseable: A lightweight observability platform built on a telemetry data lake architecture. It enables storage, processing, and analysis of logs using SQL or natural language queries, and provides built-in dashboards that can serve as an alternative to the complex Grafana stack.
  • [SigLens](https://www.splunk.com/): A free and open-source log management platform that can ingest data from sources like Vector and Splunk. It allows users to create visualisation dashboards and view data in various formats (tables, logs, or single-line) using a built-in query builder. [4, 5, 6, 7, 8, 9, 10, 11, 12] 

Lightweight JavaScript Libraries for Embedding

If you prefer to build a custom UI, these libraries are frequently used to embed interactive log-based charts:

  • Chart.js: One of the most popular lightweight open-source libraries for creating responsive, customizable charts. It is simple to use with web applications and can easily handle time-series data typical of logs.
  • [Apache ECharts](https://echarts.apache.org/): A comprehensive library that excels at handling large datasets with smooth performance, using WebGL for rendering millions of data points. It supports over 20 pre-built series, including line, bar, and heat maps.
  • uPlot: While not explicitly detailed in the provided snippets, it is a well-known, ultra-fast, and tiny library specifically optimised for time-series data, often used as a lightweight alternative for embedding charts in performance-sensitive web pages.
  • Plotly.js: A declarative charting library that supports over 40 chart types and uses WebGL for high-performance rendering of large datasets, such as IoT sensor data or financial time series. [7, 13, 14, 15, 16] 

Comparison at a Glance

Tool  Best For Deployment Key Strength
GoAccess Real-time web logs Nix / Browser Zero-overhead, standalone HTML report
OpenObserve Unified observability Self-hosted (Single binary) 140x storage compression, SQL queries
SigNoz OTel-native teams Self-hosted / Cloud Native OpenTelemetry integration
Chart.js Custom web charts JavaScript library Lightweight, easy to use, responsive
Apache ECharts Large-scale data JavaScript library High performance, many chart types

References

Design for the People: The US Web Design System and the Public Sans Typeface

Mike's Notes

The article reproduced below is from a fascinating website and is about another useful Design System.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

16/03/2026

Design for the People: The US Web Design System and the Public Sans Typeface

By: Jon Keegan
On a Sandy Beach: 02/07/2024

Jon Keegan is an investigative data journalist who covers technology. His work has appeared in The Wall Street Journal, The Markup and MIT Technology Review. Jon’s work has won several journalism awards, including the Loeb Award, the Society of Professional Journalists’ Excellence in Journalism Award and the Society of News Design’s Best of Digital Gold Award.

The United States has an official web design system and a custom typeface that belongs to the people. This thoughtful public design system aims to make government websites not only look good, but to make them accessible and functional for all.

Before the internet, Americans may have interacted with the federal government by stepping into grand buildings adorned with impressive stone columns and gleaming marble floors. Today, the neoclassical architecture of those physical spaces has been replaced by the digital architecture of website design – HTML code, tables, forms, and buttons. 

While people visiting a government website to apply for student loans, research veterans’ benefits, or enroll in Medicare may not notice these digital elements, they play a crucial role. If a website is buggy or doesn’t work on your phone, taxpayers cannot access the services they have paid for. This can feel like walking up to a boarded-up government building with broken windows, creating a negative impression of the government itself.  

 In the US, there are about 26,000 federal websites. Early on, each site had its own designs, fonts, and login systems, creating frustration for the public, and wasting government resources.

 A survey of the many different styles of buttons from government websites as of 2015. Source: 18F / GSA 

The troubled launch Healthcare.gov in 2013 highlighted the need for a better way to build government digital services. In 2014, President Obama created two new teams to help improve government tech.

Within the General Services Administration (GSA), a new team called 18F (named for their Washington, DC office at 1800 F Street) was created to “collaborate with other agencies to fix technical problems, build products, and improve public service through technology.” The team was built to move at the speed of tech start-ups rather than lumbering bureaucratic agencies. 

The U.S. Digital Service (USDS) was tasked “to deliver better government services to the American people through technology and design.” In 2015, the two teams collaborated to build the US Web Design System (USWDS)—a style guide and collection of user interface components and design patterns to ensure a consistent user experience across government websites. “Inconsistency is felt, even if not always precisely articulated in usability research findings,” said Dan Williams, the USWDS program lead, in an email. 

Some of the sample design elements for the USWDS. Source: https://designsystem.digital.gov/

Today, the system defines 47 user interface components such as buttons, alerts, search boxes and forms each with their own design examples, sample code and guidelines such as “Be polite” and “Don’t overdo it.” The USWDS is now in its third iteration, and is used in 160 government websites. “As of September 2023, 94 agencies use USWDS code, and it powers about 1.1 billion pageviews on federal websites,” said Williams.

USWDS design principles include focusing on real users’ needs, earning trust and embracing accessibility. The system requires websites to be optimized for all users, including people with disabilities such as those using screen readers or those with color blindness. Williams said accessibility is important to the team’s efforts, noting that they “prioritize any accessibility-related bug or improvement we find (or is contributed by our community).”






Some federal websites that use the USWDS. Clockwise from top left: Va.gov, Medicaid.gov, Worker.gov, Supremecourt.gov

To ensure clear and consistent typography, the free and open-source typeface Public Sans was created for the US government. “It started as a design experiment,” said Williams, who designed the typeface, which was released in 2019. “We were interested in trying to establish an open source solution space for a typeface, just like we had for the other design elements in the design system,” said Williams. Based on the Libre Franklin typeface, Public Sans is described as “a strong, neutral, principles-driven, open-source typeface for text or display.” 


Both Public Sans and the USWDS embrace transparency and collaboration with government agencies and the public, inviting contributions to their development via the projects’ GitHub pages. 

To ensure that the hard-learned lessons of improving public technology aren’t forgotten, the projects embrace continuous improvement. One of Public Sans’ design principles offers key guidance in this area: “Strive to be better, not necessarily perfect.”

Groundbreaking visuals capture how our bodies repair damaged DNA

Mike's Notes

Nature is not digital. Beautiful work by animator Drew Berry.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library > Subscriptions > Aeon
  • Home > Handbook > 

Last Updated

20/01/2026

Groundbreaking visuals capture how our bodies repair damaged DNA

By: Drew Berry
Aeon: 9/01/2026

The biomedical animator Drew Berry is known for his dazzling visualisations of biological processes that unfold on microscopic scales.

https://youtu.be/lWbXGIuCsmo?si=2w7e4uPwTKv5HQNP

The biomedical animator Drew Berry is known for his dazzling visualisations of biological processes that unfold on microscopic scales. As enlightening as it is arresting, his imagery straddles the line between science and art, as seen in his work as the in-house animator for the Walter and Eliza Hall Institute of Medical Research (WEHI) in Melbourne, Australia, and in his music video collaboration with Björk. This animation illustrates a process called homologous recombination, in which specialised proteins repair damaged DNA by using an intact copy as a template – failures of which can increase one’s risk of cancer. Through this glimpse into the worlds within us, Berry highlights the intricate biology that plays out inside each of us unseen, shaped by millennia of evolution.

Video by the Walter and Eliza Hall Institute of Medical Research

Animator: Drew Berry

Journey Mapping 101

Mike's Notes

I'm wondering whether Journey Maps could be added to Pipi.

  • To better understand the needs of the different users of Pipi visually
  • As a tool for customers.
I first used Journey Mapping a few months ago while testing Krobar.ai, an excellent simulation platform from Kromatic.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library > Subscriptions > NNg Newsletter
  • Home > Handbook > 

Last Updated

18/01/2026

Journey Mapping 101

By: Sarah Gibbons
NN Group: 09/12/2018

Vice President of Nielsen Norman Group. She works at the intersection of research, strategy, and design.

Summary

A journey map is a visualization of the process that a person goes through in order to accomplish a goal.

Journey maps are a common UX tool. They come in all shapes, sizes, and formats. Depending on the context, they can be used in a variety of ways. This article covers the basics: what a journey map is (and is not), related terminology, common variations, and how we can use journey maps.

In This Article

  • Definition of a Journey Map
  • Key Components of a Journey Map
  • Journey-Map Variations
  • Why Use Journey Maps
  • Conclusion

Definition of a Journey Map

Definition: A journey map is a visualization of the process that a person goes through in order to accomplish a goal.

In its most basic form, journey mapping starts by compiling a series of user actions into a timeline. Next, the timeline is fleshed out with user thoughts and emotions in order to create a narrative. This narrative is condensed and polished, ultimately leading to a visualization.

Most journey maps follow a similar format: at the top, a specific user, a specific scenario, and corresponding expectations or goals in the middle, high-level phases that are comprised of user actions, thoughts, and emotions;  at the bottom, the takeaways: opportunities, insights, and internal ownership.

The terms ‘user journey map’ and ‘customer journey map’ can be used interchangeably. Both reference a visualization of a person using your product or service.

While the argument can be made that the term ‘customer’ does a disservice to the method (because, especially for certain business-to-business products, not all of end users are technically customers, i.e., product buyers), alignment on what you call the map is far less important than alignment on the content within the map.

Key Components of a Journey Map

Journey maps come in all shapes and sizes. Regardless of how they look, journey maps have the following 5 key elements in common:

  1. Actor
  2. Scenario + Expectations
  3. Journey Phases
  4. Actions, Mindsets, and Emotions
  5. Opportunities

Actor

The actor is the persona or user who experiences the journey. The actor is who the journey map is about — a point of view. Actors usually align with personas and their actions in the map are rooted in data.

Provide one point of view per map in order to build a strong, clear narrative. For example, a university might choose either a student or a faculty member as actor — each would result in different journeys. (To capture both viewpoints, the university will need to build two separate maps, one for each of the two user types.)

Scenario + Expectations

The scenario describes the situation that the journey map addresses and is associated with an actor’s goal or need and specific expectations. For example, one scenario could be switching mobile plans to save money, and expectations for it include to easily find all the information needed to make a decision.

Scenarios can be real (for existing products and services) or anticipated — for products that are yet in the design stage.

Journey maps are best for scenarios that involve a sequence of events (such as shopping or taking a trip), describe a process (thus involve a set of transitions over time), or might involve multiple channels.

Journey Phases

Journey phases are the different high-level stages in the journey. They provide organization for the rest of the information in the journey map (actions, thoughts, and emotions). The stages will vary from scenario to scenario; each organization will usually have data to help it determine what these phases are for a given scenario.

Here are some examples:

  • For an ecommerce scenario (like buying Bluetooth speakers), the stages can be discover, try, buy, use, seek support.
  • For big (or luxury) purchases (like buying a car), the stages can be engagement, education, research, evaluation, justification.
  • For a business-to-business scenario (like rolling out an internal tool), the stages could be purchase, adoption, retention, expansion, advocacy.

Actions, Mindsets, and Emotions

These are behaviors, thoughts, and feelings the actor has throughout the journey and that are mapped within each of the journey phases.

Actions are the actual behaviors and steps taken by users. This component is not meant to be a granular step-by-step log of every discrete interaction. Rather, it is a narrative of the steps the actor takes during that phase.

Mindsets correspond to users’ thoughts, questions, motivations, and information needs at different stages in the journey. Ideally, these are customer verbatims from research.

Emotions are plotted as single line across the journey phases, literally signaling the emotional “ups” and “downs” of the experience. Think of this line as a contextual layer of emotion that tells us where the user is delighted versus frustrated.

Opportunities

Opportunities (along with additional context such as ownership and metrics) are insights gained from mapping; they speak to how the user experience can be optimized. Insights and opportunities help the team draw knowledge from the map:

  • What needs to be done with this knowledge?
  • Who owns what change?
  • Where are the biggest opportunities?
  • How are we going to measure improvements we implement?

An example of a simplistic, high-level customer-journey map depicting how the persona “Jumping Jamie” switches her mobile plan. While all comprehensive journey maps should include key components, what the map chooses to prioritize can (and should) depend on the goal of the journey-mapping initiative. (For your convenience, we provide a journey-map template that you can use.)

Journey-Map Variations

There are several concepts closely related and thus easily confused with journey maps.

It is important to note that this section is only meant to help your personal understanding and clarification of these terms. It is not advised to debate or attempt to shift a whole organization’s language to abide by the definitions stated here. Instead, use these definitions to guide you towards aspects of another method that your team has not previously considered.

Journey Map vs. Experience Map

Think of an experience map as a parent to a journey map. A journey map has a specific actor (a singular customer or user of a product) and specific scenario (of a product or service), while an experience map is broader on both accounts — a generic human undergoing a general human experience.

The experience map is agnostic of a specific business or product. It’s used for understanding a general human behavior; in contrast, a customer journey map is specific and focused on a particular business or product.

For example, imagine the world before the ridesharing market existed (Uber, Lyft, Bird, or Limebike, to name a few). If we were to create an experience map of how a person gets from one place to another, the map would likely include walking, biking, driving, riding with a friend, public transportation, or calling a taxi. Using that experience map we could then isolate pain points: unknown fares, bad weather, unpredictable timing, paying in cash, and so on. Using these pain points, we would then create a future journey map for specific product: how does a particular type of user call a car using the Lyft app?

Journey Map vs. Service Blueprint

If journey maps are the children to experience maps, then service blueprints are the grandchildren. They visualize the relationships between different service components (such as people or processes) at various touchpoints in a specific customer journey.

Think of service blueprints as a part two to customer journey maps. They are extensions of journey maps, but instead of being focused on the user (and taking the user’s viewpoint), they are focused on the business (and take its perspective).

For the Lyft scenario above, we would take the journey map and expand it with what Lyft does internally to support that customer journey. The blueprint could include matching the user to a driver, contacting the driver, calculating fares, and so on.

Journey Map vs. User Story Map

User stories are used in Agile to plan features or functionalities. Each feature is condensed down to a deliberately brief description from a user’s point of view; the description focuses on what the user wants to do, and how that feature will help. The typical format of a user story is a single sentence: “As a [type of user], I want to [goal], so that [benefit].” For example, “As a checking account holder, I want to deposit checks with my mobile device, so that I don’t have to go to the bank.”

A user story map is a visual version of a user story. For example, take the user story above (“As a checking account holder, I want to deposit checks with my mobile device, so that I don’t have to go to the bank.”) and imagine writing out the different steps that the team plans for the user to take when using that functionality. These steps could be: logging in, beginning deposit, taking picture of check, and entering transaction details. For each step, we can document required features: enabling camera access, scanning check and auto filling numbers, and authorizing signature. In a user story map, these features are written on sticky notes, then arranged based on the product release that each functionality will be added to.

While, at a glance, a user story map may look like a journey map, journey maps are meant for discovery and understanding (think big picture), while user story maps are for planning and implementation (think little picture).

Although a journey map and user story map may contain some of the same pieces, they are used at different points of the process. For example, imagine our journey map for Lyft indicated that a pain point appeared when the user was in a large group. To address it, the team may introduce a multicar-call option. We could create a user story map to break this feature (multicar call) into smaller pieces, so a product-development team could plan release cycles and corresponding tasks.

Why Use Journey Maps

The benefits of journey maps (and most other UX mappings) are two-fold. First, the process of creating a map forces conversation and an aligned mental model for the whole team. Fragmented understanding is a widespread problem in organizations because success metrics are siloed; it is no one’s responsibility to look at the entire experience from the user’s standpoint. This shared vision is a critical goal of journey mapping, because, without it, agreement on how to improve customer experience would never take place.

Second, the shared artifact resulting from the mapping can be used to communicate an understanding of your user or service to all involved. Journey maps are effective mechanisms for conveying information in a way that is memorable, concise, and that creates a shared vision. The maps can also become the basis for decision making as the team moves forward.

Conclusion

Journey mapping is a process that provides a holistic view of the customer experience by uncovering moments of both frustration and delight throughout a series of interactions. Done successfully, it reveals opportunities to address customers’ pain points, alleviate fragmentation, and, ultimately, create a better experience for your users.

Additional articles are available, discussing: 

  • When to create customer journey maps
  • The 5-step process
  • Journey mapping in real life

How Math is Visual - by Scientific American

Mike's Notes

A great demonstration of visual thinking as a discovery tool in maths.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library > Authors > Benoit Mandelbrot
  • Home > Handbook > 

Last Updated

04/06/2025

How Math is Visual - by Scientific American

By: Marissa Fessenden
Scientific American: 03/01/2013

Papers from Benoit Mandelbrot's office offer a peek into the mathematician's thinking process. His work and that of his contemporaries show how images can inform theory and discovery.

The Spilhaus World Ocean in a Square map

Mike's Notes

The Spilhaus World Ocean in a Square map is an excellent map projection that centres on the seven oceans with distortion of land. It is terrific for understanding ocean circulation.

This map was shared by Huw Griffiths. 

The maps below are by John Nelson of ESRI.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

17/05/2025

The Spilhaus World Ocean in a Square map

Wikipedia:

In 1942 Spilhaus tackled the problem of displaying the world's oceans in an unbroken view. He achieved this by carefully selecting antipodal points as the centers for two hemispheric projections. However it wasn't until 1979 that he published maps using continental shorelines as "natural boundaries", including one that has become the typical example of Spilhaus's technique. It uses locations near Hankou in China and Córdoba in Argentina as poles with a cut joining them across the Bering Strait. In 1991, Spilhaus published Atlas of the World illustrated with a large selection of maps having "geophysical boundaries", typically coastlines, in various orientations and for various purposes. He published several other papers and articles on the topic.






Fundamentals of Data Visualization

Mike's Notes

Note

Resources

References

  • Fundamentals of Data Visualization, by Claus O. Wilke.

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

17/05/2025

Fundamentals of Data Visualisation

By: Mike Peters
On a Sandy Beach: 25/07/2024

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

"As objective as data might be, there’s a human factor that is easily overseen when it comes to creating visualizations that accurately reflect it: bias and misunderstandings. Having worked with students and postdocs on thousands of data visualizations over the years, Claus O. Wilke, Professor of Integrative Biology, knows from experience that the same issues arise over and over when it comes to visualizing data."

"In his book Fundamentals of Data Visualization, he collected his accumulated knowledge from these interactions to help everyone create clear, attractive, and convincing data visualizations. You can read the complete manuscript for free on the author’s website." - Smashing Magazine.

Financial Times Visual Vocabulary

Mike's Notes

Smashing Magazine wrote about the Financial Times Visual Vocabulary, which is available on GitHub as a chart and a website in multiple languages.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

17/05/2025

Financial Times Visual Vocabulary

By: 
Financial Times: 24/07/2024

"Violins, doughnuts, pies, slopes — data can be visualized in many ways. But which type of chart should you pick? To help you select the optimal visualization type for your data, the Financial Times Visual Journalism Team published the Financial Times Visual Vocabulary." - Smashing Magazine.

Financial Times Visual Vocabulary

A poster (available in English, Japanese, traditional Chinese and simplified Chinese) and web site to assist designers and journalists to select the optimal symbology for data visualisations, by the Financial Times Visual Journalism Team.

The FT Visual Vocabulary is at the core of a newsroom-wide training session aimed at improving chart literacy. This learning resource is inspired by the Graphic Continuum by Jon Schwabish and Severino Ribecca. This is not an attempt to teach everyone how to make charts, but how to recognise the opportunities to use them effectively alongside words.

Read the Chart Doctor feature column for full background on why we made this: Simple techniques for bridging the graphics language gap

For D3 templates for producing many of these chart types in FT style, see our Visual Vocabulary repo.

Related reading

The full content of the poster, along with links to related material, including research and examples of best practice. This is a work in progress.

General

  • National Geographic: Taking data visualisation from eye candy to efficiency
  • William S. Cleveland and Robert McGill: Graphical Perception: Theory, Experimentation, and Application to the Development of Graphical Methods
  • Hadley Wickham: A Layered Grammar of Graphics
  • Tracey L. Weissgerber et al: Beyond Bar and Line Graphs: Time for a New Data Presentation Paradigm
  • Numeroteca: Uses and abuses of data visualisations in mass media
  • Andy Cotgreave: The inevitability of data visualization criticism
  • Alberto Cairo: "Our reader" won't understand something as complicated as that!
  • Alberto Cairo: Visualization's expanding vocabulary

Deviation

Emphasise variations (+/-) from a fixed reference point. Typically the reference point is zero but it can also be a target or a long-term average. Can also be used to show sentiment (positive/neutral/negative). Example FT uses: Trade surplus/deficit, climate change

Diverging bar

A simple standard bar chart that can handle both negative and positive magnitude values.

  • Chart Doctor: How the FT explained Brexit

Diverging stacked bar

Perfect for presenting survey results which involve sentiment (eg disagree/neutral/agree).

Spine chart

Splits a single value into 2 contrasting components (eg Male/Female)

Surplus/deficit filled line

The shaded area of these charts allows a balance to be shown – either against a baseline or between two series.

Correlation

Show the relationship between two or more variables. Be mindful that, unless you tell them otherwise, many readers will assume the relationships you show them to be causal (i.e. one causes the other). Example FT uses: Inflation & unemployment, income & life expectancy

  • Chart Doctor: The German election and the trouble with correlation

Scatterplot

The standard way to show the relationship between two continuous variables, each of which has its own axis.

  • Chart Doctor: The storytelling genius of unveiling truths through charts
  • Maarten Lambrechts: 7 reasons you should use dot graphs
  • Tim Brock: Too Big Data: Coping with Overplotting
  • Sara Kehaulani Goo: The art and science of the scatterplot
  • Chart Doctor: The storytelling genius of unveiling truths through charts
  • Examples: FT

Line + Column

A good way of showing the relationship between an amount (columns) and a rate (line)

  • Data Revelations: Be Careful with Dual Axis Charts
  • DataHero: The Do’s and Don’ts of Dual Axis Charts
  • Harvard Business Review: Beware Spurious Correlations

Connected scatterplot

Usually used to show how the relationship between two variables has changed over time.

  • Robert Kosara: The Connected Scatterplot for Presenting Paired Time Series
  • Data Revelations: Be Careful with Dual Axis Charts
  • Examples: Washington Post

Bubble

Like a scatterplot, but adds additional detail by sizing the circles according to a third variable

  • Chart Doctor: The storytelling genius of unveiling truths through charts
  • Examples: FT

XY heatmap

A good way of showing the patterns between 2 categories of data, less good at showing fine differences in amounts.

  • Chart Doctor: Use fewer maps to illustrate data better

Ranking

Use where an item’s position in an ordered list is more important than its absolute or relative value. Don’t be afraid to highlight the points of interest. Example FT uses: Wealth, deprivation, league tables, constituency election results

Ordered bar

Standard bar charts display the ranks of values much more easily when sorted into order

Ordered column

See above.

Ordered proportional symbol

Use when there are big variations between values and/or seeing fine differences between data is not so important.

Dot strip plot

Dots placed in order on a strip are a space-efficient method of laying out ranks across multiple categories.

Slope

Perfect for showing how ranks have changed over time or vary between categories.

Lollipop chart

Lollipops draw more attention to the data value than standard bar/column and can also show rank and value effectively.

Distribution

Show values in a dataset and how often they occur. The shape (or ‘skew’) of a distribution can be a memorable way of highlighting the lack of uniformity or equality in the data. Example FT uses: Income distribution, population (age/sex) distribution

  • Joey Cherdarchuk: Visualising distributions

Histogram

The standard way to show a statistical distribution - keep the gaps between columns small to highlight the ‘shape’ of the data

  • Aran Lunzer and Amelia McNamara: Exploring histograms

Boxplot

Summarise multiple distributions by showing the median (centre) and range of the data

Violin plot

Similar to a box plot but more effective with complex distributions (data that cannot be summarised with simple average).

Population pyramid

A standard way for showing the age and sex breakdown of a population distribution; effectively, back to back histograms.

Dot strip plot

Good for showing individual values in a distribution, can be a problem when too many dots have the same value.

Dot plot

A simple way of showing the change or range (min/max) of data across multiple categories.

Barcode plot

Like dot strip plots, good for displaying all the data in a table,they work best when highlighting individual values.

  • Maarten Lambrechts: Interactive strip plots for visualizing demographics

Cumulative curve

A good way of showing how unequal a distribution is: y axis is always cumulative frequency, x axis is always a measure.

Change over Time

Give emphasis to changing trends. These can be short (intra-day) movements or extended series traversing decades or centuries. Choosing the correct time period is important to provide suitable context for the reader. Example FT uses: Share price movements, economic time series

  • Flowing Data: 11 Ways to Visualize Changes Over Time – A Guide

Line

  • The standard way to show a changing time series. If data are irregular, consider markers to represent data points
  • Chart Doctor: A chart’s ability to mislead is off the scale
  • Office for National Statistics: Does the axis have to start at zero? (Part 1 – line charts)
  • Quartz: It's OK not to start your y-axis at zero
  • Vox: Shut up about the y-axis. It should't always start at zeroEmily Schuch: How to Make a Line Chart that Doesn't Lie

Column

Columns work well for showing change over time - but usually best with only one series of data at a time.

  • Chart Doctor: A chart’s ability to mislead is off the scale
  • Office for National Statistics: Does the axis have to start at zero? (Part 2 – bar charts)

Line + column

A good way of showing the relationship over time between an amount (columns) and a rate (line)

Stock price

Usually focused on day-to-day activity, these charts show opening/closing and hi/low points of each day

Slope

Good for showing changing data as long as the data can be simplified into 2 or 3 points without missing a key part of story

Area chart

Use with care – these are good at showing changes to total, but seeing change in components can be very difficult

Fan chart (projection)

Use to show the uncertainty in future projections - usually this grows the further forward to projection

Connected scatterplot

A good way of showing changing data for two variables whenever there is a relatively clear pattern of progression.

Calendar heatmap

A great way of showing temporal patterns (daily, weekly, monthly) – at the expense of showing precision in quantity.

Priestley timeline

Great when date and duration are key elements of the story in the data.

  • Chart Doctor: Communicating with data: Timelines
  • Examples: FT

Circle timeline

Good for showing discrete values of varying size across multiple categories (eg earthquakes by contintent).

Seismogram

Another alternative to the circle timeline for showing series where there are big variations in the data.

Part-to-whole

Show how a single entity can bebroken down into its component elements. If the reader’s interest issolely in the size of the components,consider a magnitude-type chartinstead. Example FT uses: Fiscal budgets, company structures,national election results

  • Flowing Data: 9 Ways to Visualize Proportions – A Guide

Stacked column

A simple way of showing part-to-whole relationships but can be difficult to read with more than a few components.

  • Robert Kosara: Stacked bars are the worst

Proportional stacked bar

A good way of showing the size and proportion of data at the same time – as long as the data are not too complicated.

  • Chart Doctor: How to apply Marimekko to data

Pie

A common way of showing part-to-whole data – but be aware that it’s difficult to accurately compare the size of the segments.

  • Robert Kosara: Ye olde pie chart debate
  • Robert Kosara: Pie Charts – Unloved, Unstudied, and Misunderstood
  • Robert Kosara: An Illustrated Tour of the Pie Chart Study Results
  • David Robinson: How to replace a pie chart
  • Office for National Statistics: The humble pie chart: part 1
  • Office for National Statistics: The humble pie chart: part 2
  • Ian Spence: No humble pie: The origins and usage of a statistical chart
  • Jeff Clark: In defense of pie charts
  • Stephen Few: Save the Pies for Dessert

Donut

Similar to a pie chart – but the centre can be a good way of making space to include more information about the data (eg. total)

Treemap

Use for hierarchical part-to-whole relationships; can be difficult to read when there are many small segments.

Voronoi

A way of turning points into areas – any point within each area is closer to the central point than any other centroid.

Arc

A hemicycle, often used for visualising political results in parliaments.

Gridplot

Good for showing % information, they work best when used on whole numbers and work well in multiple layout form.

Venn

Generally only used for schematic representation

Waterfall

Can be useful for showing part-to-whole relationships where some of the components are negative.

Magnitude

Show size comparisons. These can berelative (just being able to seelarger/bigger) or absolute (need tosee fine differences). Usually theseshow a ‘counted’ number (for example, barrels, dollars or people) rather thana calculated rate or per cent. Example FT uses: Commodity production, marketcapitalisation

Column

The standard way to compare the size of things. Must always start at 0 on the axis

Bar

See above. Good when the data are not time series and labels have long category names.

Paired column

As per standard column but allows for multiple series. Can become tricky to read with more than 2 series.

Paired bar

See above.

Proportional stacked bar

A good way of showing the size and proportion of data at the same time – as long as the data are not too complicated.

  • Chart Doctor: How to apply Marimekko to data

Proportional symbol

Use when there are big variations between values and/or seeing fine differences between data is not so important.

Isotype (pictogram)

Excellent solution in some instances – use only with whole numbers (do not slice off an arm to represent a decimal).

Lollipop chart

Lollipop charts draw more attention to the data value than standard bar/column – does not HAVE to start at zero (but preferable).

Radar chart

A space-efficient way of showing value pf multiple variables– but make sure they are organised in a way that makes sense to reader.

Parallel coordinates

An alternative to radar charts – again, the arrngement of the variables is important. Usually benefits from highlighting values.

Spatial

Used only when precise locations orgeographical patterns in data aremore important to the reader thananything else. Example FT uses: Locator maps, population density,natural resource locations, naturaldisaster risk/impact, catchment areas, variation in election results

  • Chart Doctor: Use fewer maps to illustrate data better
  • Matthew Ericson: When Maps Shouldn’t Be Maps
  • Mapbox: 7 data visualization techniques for location

Basic choropleth (rate/ratio)

The standard approach for putting data on a map – should always be rates rather than totals and use a sensible base geography

  • Vox: The bad map we see every presidential election
  • Vox: This “bad” election map? It’s not so bad.
  • UX•Blog: Telling the truth

Proportional symbol (count/magnitde)

Use for totals rather than rates – be wary that small differences in data will be hard to see.

  • Stephen Few: What Can’t Be Built with Bricks?

Flow map

For showing unambiguous movement across a map.

Contour map

For showing areas of equal value on a map. Can use deviation colour schemes for showing +/- values

Equalised cartogram

Converting each unit on a map to a regular and equally-sized shape – good for representing voting regions with equal value.

  • Chart Doctor: How the FT explained Brexit
  • 5W Blog: The power of cartograms and creating them easily

Scaled cartogram (value)

Stretching and shrinking a map so that each area is sized according to a particular value.

  • Chart Doctor: The search for a better US election map
  • 5W Blog: The power of cartograms and creating them easily
  • Vox: The bad map we see every presidential election

Dot density

Used to show the location of individual events/locations – make sure to annotate any patterns the reader should see.

  • Chart Doctor: The search for a better US election map

Heat map

Grid-based data values mapped with an intensity colour scale. As choropleth map – but not snapped to an admin/political unit.

  • 5W Blog: The power of cartograms and creating them easily

Flow

Show the reader volumes or intensity of movement between two or more states or conditions. These might belogical sequences or geographical locations. Example FT uses: Movement of funds, trade, migrants, lawsuits, information; relationship graphs.

  • RJ Andrews: Picturing the Great Migration

Sankey (aka river plot)

Shows changes in flows from one condition to at least one other; good for tracing the eventual outcome of a complex process.

  • Chart Doctor: Data visualisation: it is not all about technology

Waterfall

Designed to show the sequencing of data through a flow process, typically budgets. Can include +/- components.

Chord

A complex but powerful diagram which can illustrate 2-way flows (and net winner) in a matrix.

Network

Used for showing the strength and inter-connectedness of relationships of varying types.

Todo:

Uncertainty

  • Scientific American: Visualising uncertain weather
  • Oli Hawkins: Animating uncertainty

Animation

  • Chart Doctor: The storytelling genius of unveiling truths through charts
  • Evan Sinar: Use Animation to Supercharge Data Visualization

Interactivity

  • Chart Doctor: Why the FT creates so few clickable graphics
  • Gregor Aisch: In defense of interactive graphics
  • Zan Armstrong: Why choose? Scrollytelling and steppers)

Map projections

Colour