The word of the Lorax But now, says the Once-ler, Now that you're here, the word of the Lorax seems perfectly clear. UNLESS someone like you cares a whole awful lot, nothing is going to get better. It's not. Dr. Seuss, The Lorax careconservation
This obsession with permanence I think a lot about the lifecycle of websites. I’m frustrated by so much of the short-term thinking I see in the world today, and the way we think about websites is a part of that: it’s “normal” for them to just go up in smoke as soon as their authors stop paying attention. People switch platforms and providers and break links without a second thought. It pains me to see people build websites with no feeling of obligation to them — when you put something out into the world, it is your responsibility to care for it. At the same time, I wonder if this obsession with permanence is misplaced. Wesley Aptekar-Cassels, How Websites Die care
To love deeply a world of things Care brings the worlds of action and meaning back together, and reconnects the necessary work of maintenance with the forms of attachment that so often (but invisibly, at least to analysts) sustain it. ...What if we care about our technologies, and do so in more than a trivial way? This feature or property has sometimes been extended to technologies in the past, but usually only ones that come out of deep folk or craft traditions, and rarely the products of a modern industrial culture. ...Is it possible to love, and love deeply, a world of things? Steven J. Jackson, Rethinking Repair carecraftproducts
You've got to do this with love Third, you’ve got to do this with love. You’ll need to take a radically different approach to supporting and partnering with customers to help them adjust to new and better ways of working. Dear Microsoft careux
Snipping the dead blooms A Quote by Robin Sloan newpublic.substack.com I recognize this is a very niche endeavor, but the art and craft of maintaining a homepage, with some of your writing and a page that's about you and whatever else over time, of course always includes addition and deletion, just like a garden — you're snipping the dead blooms. I do this a lot. I'll see something really old on my site, and I go, “you know what, I don't like this anymore,” and I will delete it. But that's care. Both adding things and deleting things. Basically the sense of looking at something and saying, “is this good? Is this right? Can I make it better? What does this need right now?” Those are all expressions of care. And I think both the relentless abandonment of stuff that doesn't have a billion users by tech companies, and the relentless accretion of garbage on the blockchain, I think they're both kind of the antithesis, honestly, of care. carerepairwwwgardenstechnology
Maintenance and Care An Article by Shannon Mattern placesjournal.org Maintenance has taken on new resonance as a theoretical framework, an ethos, a methodology, and a political cause. This is an exciting area of inquiry precisely because the lines between scholarship and practice are blurred. To study maintenance is itself an act of maintenance. To fill in the gaps in this literature, to draw connections among different disciplines, is an act of repair or, simply, of taking care — connecting threads, mending holes, amplifying quiet voices. Rethinking RepairWhat this site is repaircareconnectionknowledge
Product vs. Feature Teams An Article by Marty Cagan svpg.com This article is certain to upset many people. Empowered product teamsViability, usablity, feasibilityWhat went wrong? featuressoftwareagile
Empowered product teams When I wrote about the virtues of empowered product teams, I was referring to what I’ll continue to call here as product teams. Specifically, they are cross-functional (product, design and engineering); they are focused on and measured by outcomes (rather than output); and they are empowered to figure out the best way to solve the problems they’ve been asked to solve.
Viability, usablity, feasibility In an empowered product team, the product manager is explicitly responsible for ensuring value and viability; the designer is responsible for ensuring usability; and the tech lead is responsible for ensuring feasibility. The team does this by truly collaborating in an intense, give and take, in order to discover a solution that work for all of us. However, in a feature team, you still (hopefully) have a designer to ensure usability, and you have engineers to ensure feasibility, but, and this is critical to understand: the value and business viability are the responsibility of the stakeholder or executive that requested the feature on the roadmap. What went wrong? teamwork
What went wrong? If something ships from one of the companies I advise, and it is virtually unusable because of poor design (which as we all know occasionally does happen), you can bet I go directly to the designer and ask how this happened? It is absolutely on the designer to ensure this does not happen, so something went wrong. Similarly, if the product ships and performance is terrible you can bet I go directly to the tech lead with the same question. And most frequently of all, if something ships and the analytics show that it’s either not being bought or not being used, or it turns out that it violates some business constraint like compliance or privacy, you can bet I go right to the product manager with that question. Viability, usablity, feasibility