Our Quantified Life
The primary measure of progress
SAFe is oriented around volume, not value
Outcomes decide
Design as an engineering problem
Obsessed with absolute numbers
Lost purposes
The case against heatmaps
It's All Over
An Essay by Justin E. H. SmithIt has come to seem to me recently that this present moment must be to language something like what the Industrial Revolution was to textiles. A writer who works on the old system of production can spend days crafting a sentence, putting what feels like a worthy idea into language, only to find, once finished, that the internet has already produced countless sentences that are more or less just like it, even if these lack the same artisanal origin story that we imagine gives writing its soul. There is, it seems to me, no more place for writers and thinkers in our future than, since the nineteenth century, there has been for weavers.
Time-based analytics
An Article by Ryan SingerAnalytics apps don't tell you much about usage behavior. You might be able to see how many users performed an event, or how many times they did it. But none of the analytics packages out there are good at showing you how often people do things. Are they using to-dos once a week? Every day? Only signing into the app once a month but happily paying for years?
Time matters. You can't understand usage without time.
Fast Path to a Great UX – Increased Exposure Hours
An Article by Jared SpoolAs we’ve been researching what design teams need to do to create great user experiences, we’ve stumbled across an interesting finding. It’s the closest thing we’ve found to a silver bullet when it comes to reliably improving the designs teams produce.
The solution? Exposure hours. The number of hours each team member is exposed directly to real users interacting with the team’s designs or the team’s competitor’s designs. There is a direct correlation between this exposure and the improvements we see in the designs that team produces.
Metrics have a strange hold on the imagination
A Fragment by Shawn WangOnce in place, metrics have a strange hold on the imagination: I've seriously had a CTO carelessly reject my genuine idea out of hand because "it doesn't help OKRs", the same OKRs we previously agreed should not describe all that we do.
I agree with Amir Shevat that we should "do the right things over the easy to measure things."
How would you feel if you could no longer use the product?
An ArticleThe product/market fit definitions I had found were vivid and compelling, but they were lagging indicators — by the time investment bankers are staking out your house, you already have product/market fit. Instead, Ellis had found a leading indicator: just ask users “how would you feel if you could no longer use the product?” and measure the percent who answer “very disappointed.”
Site performance is potentially the most important metric
A Fragment by Kealan ParrSite performance is potentially the most important metric. The better the performance, the better chance that users stay on a page, read content, make purchases, or just about whatever they need to do. A 2017 study by Akamai says as much when it found that even a 100ms delay in page load can decrease conversions by 7% and lose 1% of their sales for every 100ms it takes for their site to load which, at the time of the study, was equivalent to $1.6 billion if the site slowed down by just one second.
The McNamara fallacy
A DefinitionThe McNamara fallacy, named for Robert McNamara, the US Secretary of Defense from 1961 to 1968, involves making a decision based solely on quantitative observations (or metrics) and ignoring all others. The reason given is often that these other observations cannot be proven.
The fallacy refers to McNamara's belief as to what led the United States to defeat in the Vietnam War—specifically, his quantification of success in the war (e.g., in terms of enemy body count), ignoring other variables.
Artifice, blindness, and suicide
A QuoteThe first step is to measure whatever can be easily measured. This is OK as far as it goes. The second step is to disregard that which can't be easily measured or to give it an arbitrary quantitative value. This is artificial and misleading. The third step is to presume that what can't be measured easily really isn't important. This is blindness. The fourth step is to say that what can't be easily measured really doesn't exist. This is suicide.
Weighing up UX
An Article by Jeremy KeithMetrics come up when we’re talking about A/B testing, growth design, and all of the practices that help designers get their seat at the table (to use the well-worn cliché). But while metrics are very useful for measuring design’s benefit to the business, they’re not really cut out for measuring user experience.
Predicted Mean Vote
A DefinitionThe predicted mean vote (PMV) was developed by Povl Ole Fanger at Kansas State University and the Technical University of Denmark as an empirical fit to the human sensation of thermal comfort. It was later adopted as an ISO standard. It predicts the average vote of a large group of people on the a seven-point thermal sensation scale where:
- +3 = hot
- +2 = warm
- +1 = slightly warm
- 0 = neutral
- -1 = slightly cool
- -2 = cool
- -3 = cold
What Do Metrics Want? How Quantification Prescribes Social Interaction on Facebook
A Research Paper by Benjamin GrosserWhat are the effects of this enumeration, of these metrics that count our social interactions? In other words, how are the designs of Facebook leading us to act, and to interact in certain ways and not in others? For example, would we add as many friends if we weren’t constantly confronted with how many we have? Would we “like” as many ads if we weren’t told how many others liked them before us? Would we comment on others’ statuses as often if we weren’t told how many friends responded to each comment?
In this paper, I question the effects of metrics from three angles. First I examine how our need for personal worth, within the confines of capitalism, transforms into an insatiable “desire for more.” Second, with this desire in mind, I analyze the metric components of Facebook’s interface using a software studies methodology, exploring how these numbers function and how they act upon the site’s users. Finally, I discuss my software, born from my research-based artistic practice, called Facebook Demetricator (2012-present). Facebook Demetricator removes all metrics from the Facebook interface, inviting the site’s users to try the system without the numbers and to see how that removal changes their experience. With this free web browser extension, I aim to disrupt the prescribed sociality produced through metrics, enabling a social media culture less dependent on quantification.
Linking Researchers Across Generations
Future value
In the field, there is a continuous flow of information that consists of daily observations, insights, and data. How can I capture these data and thoughts in notes, maps, and images so that they will be of value both to me and to future generations of scientists?
Time capsules
In recording fieldwork I was creating my own time capsules.
Tools of the digital age
The myriad tools of the digital age that provide quick ways to capture words, images, and data have added to the perception that handwritten field notebooks are passé. As someone who routinely encounters objects that can speak to us over millions of years, I may have a bias towards things that have stood the test of time. That said, it is clear that there is still much to recommend preserving records and information in traditional paper field notes.
Over the course of my career, I have developed a habitual field note protocol in which a paper notebook is used both to record information and to integrate records made on standardized data sheets, in computer files, and in photographs.
Five basic rules
Five basic rules:
(1) Record your work as notes to your future self and colleagues.
Write notes so that someone fifty years from now (or more) will understand and be able to use the factual information you collected, perhaps for purposes quite different from the original reasons.
Clearly separate facts from interpretations so these are not confusing to a future reader.
(2) Establish a clear and consistent notebook format and process.
I always include the data, place, main activities or events, weather conditions, and other people involves. The day, month, and year is the most important link between that particular point in time and other people’s records, separate data sheets that I filled out myself, photos, and most important, collected specimens.
Documenting collecting strategies and protocols receives special attention. In the moment, these may seem like common knowledge for the field team, so sometimes no one bothers to write them out.
(3) Don’t lose your field records!
(4) Pack a camera, create a visual record.
No matter how many words you write to describe a fossil locality, you can’t beat an actual photo, taken on the spot, annotated in pen, and pasted into your notebook.
There is no substitute for a photograph you actually mark in “real time” in the field as the best way to preserve a lasting, accurate record for yourself, or for someone who has never seen the site or object in question.
(5) Learning through sketches and diagrams.
Photographs are great, but drawn what you see is a more powerful way to learn about spatial patterns and relationships.
Even if you are not an expert at drawing, you can make sketches that are much more informative than words would be.
Always include a scale, an orientation, and labels in your diagrams.
Bonewalks
Example of a standardized field data collection form used to record all the fossil bones encountered along a transect.
Informally I refer to these as “bonewalks.”
Microstratigraphic
A "microstratigraphic" diagram from Olorgesaille, Kenya.