> ## Content Index > Fetch the complete content index at: https://www.ungvall.com/llms.txt > Use this file to discover other available public pages before exploring further. # Mixtape - URL: https://www.ungvall.com/mixtape/ - Published: 2026-10-22T15:47:00.000Z - Updated: 2026-10-23T16:08:14.000Z - Description: Making a mixtape was a way to show someone you'd paid attention. Building a business asks for the same care: small acts of love that are easy to overlook until they're gone. - Author: Torbjörn Ungvall - Tags: strategy A brand isn't built by one grand gesture. It's built by the small acts of love people remember. In [*Limitation*](https://www.ungvall.com/limitation/), I wrote about the willingness to leave things out. The constraint that gives the work its shape. But choosing what belongs is only half the work. The other half is what we put into it. ## The Cassette Growing up in the eighties, making a mixtape was one way to show someone you cared. You recorded songs from other cassettes or LPs, trying to make the mix right for the person who would receive it. A mixtape was a small thing. A finite amount of space. Songs you didn't write, recorded for someone who might hear something in them that you couldn't quite say yourself. The songs mattered. So did the order. The transition. The one you left out because it was your favorite, not theirs. You weren't just collecting music. You were paying attention to someone. That's what made it a gift. ## The Selection A mixtape could say, "This is who I am." The better ones also said, "I've been listening to who you are." There's a difference between giving someone everything you have and choosing something because you think it will matter to them. One is abundance. The other is care. Brands confuse the two all the time. More products. More messages. More recommendations. A thousand ways to remind someone that we exist, and very few signs that we've understood why they came to us in the first place. In [*Noise*](https://www.ungvall.com/noise/), I wrote about the feed and the archive. The feed keeps arriving. The archive gives you something worth returning to. A mixtape belongs to the second kind of thinking. Its value isn't in how much it contains, but in the attention that brought those particular things together. The same is true of a collection. A store. A conversation with customer service. Different parts, chosen and connected by a point of view. The customer might never see the work behind those choices. But they can feel when the choices belong together. ## The Small Acts Every great business is built by many small acts of love. Someone notices that a product description leaves an important question unanswered, and fixes it. Someone tells a customer that the less expensive option is the better one for them. Someone follows a problem through instead of handing it to the next department and calling it resolved. None of these makes much of an announcement. They are easy to dismiss as details. But for the person on the receiving end, that little extra may be what stays with them. Someone noticed. Someone did a little more than they had to. Not a grand gesture. Just something that made a difference. This is what I mean by small acts of love. Not a warmer tone of voice. Not putting "we love our customers" at the bottom of an email. Care made practical: noticing what someone needs and taking responsibility for it. A good product is part of that care. So is keeping a promise. So is designing a service that doesn't require a customer to become unusually persistent just to get an ordinary problem solved. The acts are small. The pattern isn't. > *What we call a detail may be the very thing a customer remembers.* ## Jenga Jenga gives me another way to think about this. You take a block from lower in the tower and place it on top. The tower gets taller. For a while, you can keep doing it. The gaps are visible, but nothing has fallen. From the top, it looks like progress. Remove the time a service team spends understanding a difficult case. Tighten a policy that used to allow judgment. Stop fixing the small recurring problem because each individual complaint costs less than the repair. Treat the customer as a transaction. Every decision has a reasonable explanation. Lower cost. Greater efficiency. A better number this quarter. And the tower is still standing. What makes this dangerous is that the effect isn't always immediate. A customer may give you another chance. An employee may quietly compensate for the gap. A supplier may absorb the inconvenience because the relationship has been good until now. Their goodwill holds the weight. Until it doesn't. The problem isn't that you don't know how many blocks are in the tower. It's that you don't know how much weight each one is carrying. When the tower falls, everyone looks for the last block. The campaign that failed. The customer who left. The person who resigned. But the last move isn't the whole explanation. We need to look at everything we removed, not just congratulate ourselves on how high we built. Not every old process deserves to stay. Some blocks really are unnecessary. That's the judgment I explored in [*Limitation*](https://www.ungvall.com/limitation/): knowing what gives the work its shape and what merely gets in the way. But removing waste and withdrawing care are not the same thing. The difficult part is that both can look like efficiency on a spreadsheet. ## The Number As CTO, I understand the appeal of the measurable. I can explain a faster page, a lower cost, a better conversion rate. The evidence is there. It gives a decision something solid to stand on. Care asks for a different kind of attention. In [*Dare*](https://www.ungvall.com/dare/), I wrote about making customers feel heard and seen. ***Mixtape*** is the practical side of that argument. What does the business actually do, repeatedly, that gives someone a reason to feel that way? Some of it can be measured. Repeat purchases. Complaints. The number of times someone has to contact us before a problem is resolved. We should look at those things. But a measure is evidence, not the whole experience. A shorter service conversation might mean we solved the problem faster. It might mean we made someone give up. A lower return rate might mean people chose better. It might mean returning something became too difficult. The number tells us what changed. We still have to ask what happened to the person. The number is easier for me to defend. I can explain the savings. The harder question is whether I have understood what made them possible - and who absorbed the cost. ## The People Making It And a business can't keep asking people to deliver care while removing their ability to do it. We tell a team to take ownership, then require approval for every exception. We ask them to listen, then reward them only for ending the conversation quickly. We describe service as a differentiator, then organize it as a cost to contain. Eventually, people learn which instruction is real. In [*Trust*](https://www.ungvall.com/trust/), I wrote about the record, whether our actions meet the expectations our words create. The same record exists inside a business. People notice what happens when someone spends extra time doing the right thing. They notice whether judgment is supported or punished. That becomes the culture, whatever the presentation says. Care shouldn't depend on someone breaking the process, staying late, or absorbing the cost themselves. An occasional act of generosity can be personal. A consistent promise needs an organization behind it. The leader's work is to make those small acts possible. Give people enough context to choose well, enough room to act, and enough support to know they won't be abandoned when a reasonable decision doesn't work out. You can't script every track. You can make the intention clear. ## The AI Tension AI makes the distinction sharper. It can help someone find an answer without searching five systems. It can surface a recurring problem we've missed. It can remove the repetition that leaves people with too little time for the difficult conversation. Those are useful ways to make room for care. It can also help us produce the appearance of care at extraordinary scale. A warmer greeting. A personalized recommendation. An apology delivered instantly, followed by another loop that leads nowhere. The language gets better. The problem stays. A mixtape wasn't meaningful because someone wrote their name on it. It was meaningful because someone had paid attention. The work mattered because of who it was for, not simply how long it took. Personalization isn't the same as understanding, and an empathetic sentence isn't the same as taking responsibility. The question isn't whether a machine helped deliver the experience. It's whether we used the capability to serve someone better. ## What Stays A mixtape was never guaranteed to land. You could choose carefully and still get it wrong. But you had to consider the person receiving it. You had to make something finite out of everything available. You had to decide what you wanted to give, and pay attention to how it might be received. That's a useful discipline for a business. Not every interaction needs to be remarkable. Most people don't need a grand gesture. They need the product to be what we said it was. The answer to be honest. The problem to be owned. The promise to survive the handoff between departments. Over time, those ordinary things become something less ordinary: a reason to trust us. But there's a difference between completing a transaction and making someone feel like one. We can get every step right and still leave someone feeling that we never really saw them. We may never isolate the act that made someone stay. It might be a hundred small things, none important enough to enter a board deck, all important enough to be missed when they're gone. The temptation is to keep adding to the top and assume whatever holds us up will keep doing so. I'd rather pay attention to what is carrying the weight. Make the promise smaller if you need to. Then keep it in all the places someone might encounter it. That's the mixtape. Not everything we could give them. Something chosen with care. In my next post, ***Thinking***, I'll explore what happens when we automate not just the work, but the room people have to question it - and why protecting that room is a leadership responsibility.