Timely Advice: How long does dataviz take?
Tags: datascience, design, productivity, javascript
Published: 2022-05-26 18:48:12


**_This article is featured by Data Visualization Society (DVS). You can go here to [read it on Nightingale.](https://nightingaledvs.com/timely-advice-how-long-does-dataviz-take/)_**   

<br/>

Every client asks, “How long do you think that will take?” I’ve built software for a long time. I used to resist even answering the question. I’m a [Fred Brooks](https://en.wikipedia.org/wiki/The_Mythical_Man-Month) acolyte and appreciate all the unforeseen ways that a complex project can go sideways. 

I don’t mind it anymore though. It’s an important part of setting expectations (which make for happy projects and happy clients). And, for anyone who's worked for a fixed fee, it’s important for understanding if a given project will be profitable. So, not only do I attempt to estimate timing for every project, I also track the actual time to see if I’m right.

One of the challenges for estimating -- and expectation setting -- is having a track record of similar projects to reference. If you’re a larger shop, with a long history and full portfolio, you have an information advantage. 
Smaller, independent shops, or freelancers, earlier in their careers, don’t have this advantage so it can be difficult to estimate. 

Or, even worse, it can be easy to give into the pressure from occasionally overzealous clients fixated on budget line-items (“You’ll spend <i>how long</i> on research?!”).

The goal with sharing this data is to even out that informational asymmetry, and give a detailed reference of time and effort involved in producing (fairly complex) data visualizations.  

## 3iap’s time-tracking dataset
From the start of 3iap in 2020, the focus was [data visualization services](https://3iap.com) for clients. Since then, 3iap has done a variety of projects, covering the full spectrum of work you might encounter as a dataviz consultant (e.g., research, analysis, data-wrangling, metrics, design, and various types of engineering). I’ve kept a close record of the time spent on each project.

As of early 2022, 3iap has logged ~1,550 hours of client dataviz work (in addition to sales / marketing / paperwork / etc., +300 hours of general product consulting to pay the bills, and an obscene number of untracked hours on [silly](https://3iap.com/radical-dots-simulator-social-judgement-attitude-change-RdrhC8fTRHGbZCvj15ELbQ/) [side](https://3iap.com/winning-at-ratemyskyperoom-elaborate-and-pointless-analysis-3BZT_LMuTrynOe2_EjD5Gw/) [projects](https://3iap.com/work/doom-haikus-ml-data-engineering-product-prototyping/)).

Below are findings about how that time was spent, in addition to highlighting 10 specific projects that represent a range of different dataviz work.

## How much “dataviz” work goes into dataviz?

![Overall activity split](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/in4n4jogn5831171k85s.png)
<figcaption>Distribution of 1,550 hours spent on 3iap client projects, split by activity type.</figcaption>

Roughly 60 percent of the total time was spent directly designing or engineering visualizations.

### Design + Engineering

![Design + engineering distribution](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/bicm35yfr4tmx5ifyfeq.png)

<figcaption>Distribution of dataviz design and engineering time spent on 3iap client projects, split by activity sub-type. Design and engineering activities together made up 60% of total hours.</figcaption>

31 percent of the time was spent on `design`, which can include everything from `story discovery`, typically bouncing between exploratory analysis and sketching story concepts with a pen and markers (4 percent), mocking up specific `charts` in Figma or Google Sheets (6 percent), `prototyping` different design approaches in Observable (3 percent design, 3 percent engineering), and even the occasional `copywriting` (2 percent).

On seeing this, I was surprised that `slides` were the second highest `design` activity (6 percent) -- I suspect this is due to inefficiency of the tool itself, whereas Figma can be componentized and coded dataviz can be automated, Keynote involves a lot of manual pixel pushing.

29 percent of the time was spent developing visualizations, typically in javascript (13 percent `React`, 6 percent `Angular`), but also occasionally in `Data Studio` (4 percent). This time also coincides with `data-wrangling` activities, building pipelines to prepare datasets for visualization.

Note, the design-to-engineering ratio might not be representative for others in the field or of a specific project. My background is computer science, so there’s a selection bias toward more technical work. Prototyping designs in code is also part of my design process, which blurs the lines further. Also, most 3iap projects are either engineering OR design, not both. For a more representative ratio, <i>Interactive Scientific Storytelling</i> and <i>Complex Report: Analysis & Presentation Design</i> were projects that involved both design and development.

### How much “non-dataviz” work goes into dataviz?

![Data, comm, research activity distribution](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/zglznfj1ahxmo7rp92jq.png)

<figcaption>Distribution of data, communication and research time spent on 3iap client projects, split by activity sub-type. Combined these activities made up 39% of total hours.”</figcaption>

This leaves 40 percent of total time on other activities. This remaining time is split between `research`, client `communication`, and `data wrangling`. (All of which are insanely important, but this might be unintuitive from clients’ perspectives.)

18 percent of the total time was spent `communicating` with clients, users and stakeholders, digging for stories and trying to make sure everyone is on the same page. This includes `meetings` (8 percent), and `documenting` designs, plans and code (3 percent), and the rest is email and Slack. While this might seem excessive, communication is a crucial part of the process; a few hours of up-front meetings, mind-reading and documentation can save days of rework. For that reason, a significant portion of `communication` time coincides with other activities. For example: 7 percent of total hours were tagged with both `communication` and `design`, which might include co-design exercises with clients or design reviews.

As expected, at 16 percent, `data wrangling` and analysis takes a significant chunk of total time. This includes `data prep`, which I’ve categorized as fairly mindless data engineering or spreadsheet maneuvering (9 percent) or `data pulls` (3 percent). More interesting data work was more fragmented: ~2 percent of the time was `exploratory analysis` (e.g., for storytelling), ~1 percent of the time was spent `designing metrics` (e.g., exploring different calculations that might best tell a given story) and another 1 percent was creating `mock datasets` (e.g., to compensate for data security constraints or clients who are slow to provide real data).

`Research` / discovery was 6 percent of the total time. The bulk of this was spent talking with clients, and coincides with meetings, email, and Slack. It also includes things like industry research, reviewing related academic literature, and whatever materials the client has available.

* 4 percent of total hours were tagged with both `communication` and `research`, which might include client mind-reading exercises, user interviews or other types of qualitative user research. This is probably the highest-impact time spent in any project: It might seem unintuitive, but at least in my experience the fastest path to a compelling data story isn’t necessarily in the data itself, it’s talking with the people behind the data.

### Chaos / Overkill

![Chaos distribution](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/fpuuhwhciicumb8xmh9y.png)

<figcaption>Distribution of total time spent on 3iap client projects, split by cause of unproductivity. Clients cause “chaos,” whereas “overkill” time is self-inflicted.</figcaption>

For certain projects, I also track a category that I call `chaos`, which is time lost due to client shenanigans. This includes things like adding new scope on a fixed-fee project or revisiting early decisions that lead to rework. This was 8 percent of total hours.

The inverse of this category is `overkill`, where I become overly excited about an idea, fall down a rabbit hole, and devote way more time to it than is reasonable or sane. This was 4 percent of total hours.

## 10x 3iap dataviz projects - timing and details

The previous findings covered overall statistics for all 3iap projects. However, it can be helpful to see how time is used on individual projects. For each of the projects below I’ve tried to share enough about the scope of the project to understand the requirements, as well as overall statistics on how the time was spent. There’s also a timeline showing how the types of work evolve throughout the course of a project.

### 1. Analytics Product Design System (14 Days)
A long-term client asked 3iap to redesign their SaaS analytics app.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/zexfns3gsnj19r8ycf13.png)
<figcaption>Left: Distribution of time spent on a single project, split by activity type. Right: Timeline of activity throughout the course of the project. Each ‘row’ corresponds to eight-ish hours (a “work day”). Each segment represents a single activity. Tile color corresponds to the activity type. Segments with multiple colors had overlapping colors (e.g. user interviews are both ‘research’ and ‘meetings’). Black lines between segments represent the boundaries of a calendar day.</figcaption>
<br/><br/>

A long-term client asked 3iap to redesign their large, complex SaaS analytics product (covering 200+ distinct metrics). There were three parts of the project: 1) a design system of chart components and supporting elements that can be mixed and matched to answer a wide range of analytics questions, 2) detailed designs of four different narrative reports, showing how the design system can address deep dives into various analysis topics, and 3) API designs and technical specifications for similar flexibility / composability when accessing the data from the backend. Because this was a familiar client and topic, there was little research or data wrangling required.

### 2. In-Product Chart Component (11 Days)
3iap developed an interactive chart component and automated testing framework within the client's existing codebase.


![Project timeline](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/sifc1097qqcyepjfnavj.png)

<figcaption>Left: Distribution of time spent on a single project, split by activity type. Right: Timeline of activity throughout the course of the project. Each ‘row’ corresponds to eight-ish hours (a “work day”). Each segment represents a single activity. Tile color corresponds to the activity type. Segments with multiple colors had overlapping colors (e.g. user interviews are both ‘research’ and ‘meetings’). Black lines between segments represent the boundaries of a calendar day.</figcaption>

The goal was to not only deliver the component, but also develop a template for how other charts could be reliably developed and tested within their environment. The component itself was fairly simple, the challenge was making it work (reliably) within their system. This project was fairly chaotic. In addition to last-minute scope creep, startup codebases aren’t known for their quality or engineering practices. No judgment here, but this added significant drag!

### 3. Complex Report: Analysis & Presentation Design (24 days)
Analyzing a complex and novel topic, new to 3iap and the client, designing appropriate visualizations, then telling a cohesive story within a 51-slide deck.

![Project timeline](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/inod2sq98afgeffxny81.png)

<figcaption>Left: Distribution of time spent on a single project, split by activity type. Right: Timeline of activity throughout the course of the project. Each ‘row’ corresponds to eight-ish hours (a “work day”). Each segment represents a single activity. Tile color corresponds to the activity type. Segments with multiple colors had overlapping colors (e.g. user interviews are both ‘research’ and ‘meetings’). Black lines between segments represent the boundaries of a calendar day.</figcaption>

This involved researching a new topic for the client, designing and developing novel visualizations, working closely with their data engineers to develop a novel set of metrics, several iterations of analysis, developing a framework to generate charts demonstrating the analysis, then designing a deck to tell the whole story. While this is the most research / analysis heavy project in the batch, these activities still only made up 38% of the total time (26% data + 12% research).

### 4. Embedded Reporting Tool Design (12 Days)
SaaS startup client with a unique dataset asked 3iap to design, prototype and user-test their in-product analytics UX.

![Project timeline](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/54ee1s14mslq4xu5wr44.png)

<figcaption>Left: Distribution of time spent on a single project, split by activity type. Right: Timeline of activity throughout the course of the project. Each ‘row’ corresponds to eight-ish hours (a “work day”). Each segment represents a single activity. Tile color corresponds to the activity type. Segments with multiple colors had overlapping colors (e.g. user interviews are both ‘research’ and ‘meetings’). Black lines between segments represent the boundaries of a calendar day. The line below shows the actual number of days worked on the project, relative to the original estimate.</figcaption>

The project involved researching their industry, offering and dataset, designing metrics to reflect the activities they wanted to track, designing and prototyping 4 “live reports” across Figma and Data Studio, facilitating user tests, and adapting accordingly. The client was the ideal balance of engaged, open-minded, and data savvy. They also had data available on day one. The project went smoothly and finished ahead of schedule.

---

**_Please check out the rest of the article at [3iap](https://3iap.com/timely-advice-how-long-does-dataviz-take-auC2KawtRB2Gvy2IMHPwLA/) or on Data Visualization Society's [Nightingale](https://nightingaledvs.com/timely-advice-how-long-does-dataviz-take/)._**