TL;DR: Quality of life work, or QoL, is the set of small fixes that take friction out of someone’s workday. None of them is ever the biggest feature on a project, which is a big part of why they matter. Here are three recent ones.
Every custom system has a few big features that get all the attention: the reason someone bought it, the workflow the whole thing is built around, the capability nobody else could give them. That’s where the scoping conversations go, and rightly so.
But a lot of what makes software pleasant to use, or quietly miserable, lives in the small stuff. The extra click. The step you repeat over and over before lunch. The form that only accepts your data in one exact shape. Around here, smoothing those out has a name: quality of life, or QoL for short.
What we mean by quality of life
QoL work is a fix to a small hiccup in how work flows. It usually doesn’t add a new capability. It removes friction from something people already do every day, so it takes a little less attention and time.
It comes down to one question. Does someone’s day get easier? These fixes almost never sit at the top of a priority list, which is part of why they can hang around for a long time. It also means that when you finally smooth one out, the people who live in the software every day tend to feel it more than they feel the big, headline changes.
A few recent examples make that concrete. They’re worth reading together, because no two of them solve quite the same problem.
Fixing a chore that already existed
Some friction comes from a task the software already handles, just not gracefully.
One team we work with closes out every day by recording how each customer paid. Customer by customer, they mark whether it was a credit card, a check, or an invoice to send later. The system could already handle this. It was just slow. You clicked into a customer’s profile, made the change, backed out, searched for the next name, and repeated that for the whole list.
So we built them a single page that lays out the day’s customers in the order they already work through them, sorted by truck and arrival time to match the paper sheet in their hand. Each customer gets three buttons: check, credit card, or no payment. No clicking in and back out.
They told us it saves them somewhere between half an hour and an hour a day, time handed back to a person at the end of a long day.
Preventing an annoyance before it arrives
Other friction never has to happen in the first place.
On another project, managers open a list of customers and then filter it down to their own name before they can get to work. Two clicks, several times a day. When we looked closely at how they actually use it, that was the case about 99 percent of the time. So instead of shipping the extra step and cleaning it up later, we’re setting the filter to default to the currently logged-in user. Your own customers are on the screen the moment the page loads. Anyone in the other one percent who needs the full list just clears the name out.
This one’s still in progress, and it surfaced in a plain conversation about how the team works, before it ever reached a finished design. That’s the cheapest possible moment to catch something like this, and the nicest, because the annoyance never gets a chance to exist.
Letting the system handle the mess
And some of it comes from the messy shape real data shows up in.
One of our systems brings new users in from a spreadsheet. For a while, it insisted on a first name and a last name in two separate columns. Sensible on paper. The catch was that the person doing the importing pulled their lists from several different sources, and the files rarely arrived in that exact form. So before the system would take a file, they cleaned each one up by hand.
Now the import accepts either two separate columns or a single full-name column, and it could be taught to stretch further than that. The spreadsheets come in the way spreadsheets actually come in, and one recurring chore is gone.
When a fix cuts both ways
Quality of life isn’t a fixed list of good features. The same choice can help in one spot and get in the way in another. A date picker that starts on today and lets you flip through the coming months is perfect for booking a spa appointment next week. Ask that same picker for your birthday, and it turns into a slog, one month at a time, back through the years, and it gets worse the older you are. The trick is fitting the small choice to what the person is actually doing.
Why the small stuff is worth it
Look at those examples together. One made an existing chore faster. One headed off an annoyance before it could ship. One taught the system to accept the mess real data arrives in. Three fixes, one result each time: someone’s day, made a little lighter.
And none of them was the headline feature. That’s the whole point. The big pieces get scoped, debated, and remembered. The small friction is easy enough to put up with, so it usually gets tolerated, sometimes for years. Fixing it won’t ever make a dramatic before-and-after picture. That’s fine. Quiet work still counts. It adds up to a person spending a little less of the day fighting the tool, and a little more of it doing the work they came to do.