68 episodes

"The user experience is a metric." Brief high-level practical design strategy thinking and strategy by Michael Schofield.

metric.substack.com

Metric UX Michael Schofield

    • Design
    • 4.9 • 16 Ratings

"The user experience is a metric." Brief high-level practical design strategy thinking and strategy by Michael Schofield.

metric.substack.com

    Exnovation, the Iceberg Model, and Expertise is Over-valued

    Exnovation, the Iceberg Model, and Expertise is Over-valued

    I want to share a few totally unrelated pieces of thinking that caught my eye. This will be a shorty but I think you’ll find it interesting.

    1

    I am taken with this concept of exnovation, which is the counterbalance of innovation. To constantly make something new, you have to dismantle the old; to organize your team around iterating and innovating you need to systematize the dismantling. This is from a post on Medium by the Politics for Tomorrow, who - in the same spirit of championing failure with slogans like “fail cheaply” or “move fast and break things” - demonstrate the necessity of embracing the phasing-out of stuff by showing it as part of a larger system of innovation.

    They discovered that stabilizing the new is not enough to achieve systemic change. In order to embed innovation in an existing “regime” or status quo, non-sustainable technologies and the related systems, infrastructures and livelihoods around these technologies had to be phased out in a deliberate and socially responsible way.

    Super cool.

    2

    Subject matter expertise in product design is over-valued. In his advice in hiring a head of product, Rich Mironov describes some of the biases subject-matter experts have in design decision making - usually having to do with lack of respect for the need for constant discovery. “I know about advertising, so I know ….” etc.

    This should probably resonate with you all who value the process and rituals of user experience design, where good design is the result of disciplined practice. This then emphasizes the value of solid practitioners, an de-emphasizes the value of experts.

    3

    Perhaps the best way to sum-up my gripes with personas is that personas are easier to get wrong than right, and wrong personas are more likely to inspire resistance rather than empathy. This insight originated with a post from Christin Roman. In their conclusion they suggest alternatives - but honestly in my conclusion the value of any kind of user archetype is a red herring.

    4

    The near future of remote work is going to be very, very messy. It starts with the illusion that a remote worker moving somewhere with a cheaper cost of living will get to keep their salary, and then it will be encumbered by a struggle for privacy. I mostly just want to share this snippet from an article by the Economist (paywall):

    Already the gig economy has shown that it is out of date. Now new prickly questions about workers’ rights and responsibilities loom: can firms monitor remote workers to assess their productivity? Who is liable if employees injure themselves at home? Any sense that white-collar workers are getting perks will create simmering resentment in the rest of the workforce.

    5

    What underlies patterns in user behavior? Structure. Specific touchpoints in an existing process, organizational pressures, policies and rules of thumb, or even rituals. I don’t know how best to credit this post without an author, but the folks at Eco Challenge (?) added levels of thinking to the familiar Iceberg model. This is interesting to me because I suppose I never really said aloud what this makes obvious: patterns are supported by the things we, or our predecessors, made. That means we can improve or unmake them. This is a powerful observation.

    End

    Consider liking (❤) this issue of Metric if this made you think.

    Metric is a podcast, too. Subscribe to Metric on Apple Podcasts, Google Play, Spotify, Stitcher, and all the usual places.

    I write about design and philosophy in another newsletter called Stoic Designer. Read “Letter 76: Shirking Routine,” then subscribe.

    Get full access to Metric by Michael Schofield at metric.substack.com/subscribe

    • 7 min
    The Value of Design in Hard Times

    The Value of Design in Hard Times

    When the market’s taken a spill, when your earned revenue is down then the easiest line-items to cut are those that involve external consultants. Should you?

    Get full access to Metric by Michael Schofield at metric.substack.com/subscribe

    • 3 min
    What is the difference between UX and CX?

    What is the difference between UX and CX?

    Listen now (6min) | Let’s be clear, many folks have thrown-in. This question has loads of answers, and this writeup will likely not make it to the top of the search engines. So, what more is there to say? This: it’s not the answer that matters so much as is the philosophy that shapes it.

    Get full access to Metric by Michael Schofield at metric.substack.com/subscribe

    • 6 min
    Gutenberg doesn't disrupt WordPress

    Gutenberg doesn't disrupt WordPress

    Gutenberg isn’t a breakthrough innovation that made WordPress better. It’s a disruptive innovation making WordPress more affordable and accessible. — Mark Uraine, “Disrupting WordPress”

    A couple weeks ago I read Mark Uraine’s writeup about the disruptive role Gutenberg — the new block-based editor (and system of editor-extensibility) — performs for WordPress, the open-source juggernaut powering a third of the web. It nails why the WordPress community has been so hyped (and it’s in a language I speak):

    Why would anyone want to change this? The short answer is expressed best in the quote, “If you don’t like change, you’re going to like irrelevance even less.” Software must evolve or it becomes archaic and dies. This bring us to the concept of disruptive innovation, originally conceived by Clayton Christensen. Disruptive innovation describes the process when a more simplified product or service begins to take root in an industry and advances up the market because of its ease of use and/or less expensive entry point. … The great companies plan for this. In fact they make efforts to self-disrupt, or innovate in ways that cause their own service or product to be disrupted. … WordPress has reached this intersection.

    — and for many folks, Gutenberg represents that self-disruption. It is a shot of espresso. A spurt of vitality intended to make the sluggish, successful ol’ man spry. It’s a little bit of good magic that wards off the heebie jeebies.

    I think Mark’s is the best argument for Gutenberg there is.

    I’m also not convinced. I want to use “Disrupting WordPress” as an opportunity to demonstrate how to think about innovation, so I am going to start by putting the kibosh on the idea that Gutenberg is the saving grace the community around it thinks.

    Is Gutenberg disruptive? No - at least not like that.

    Product is a window

    Clay Christensen’s disruptive innovation is key to the point I want to make, and that is that we should be skeptical about the consensus assumption that what has to change about WordPress is the way content is created.

    I phrase it like this because Gutenberg really is more than a UI: it represents a fairly different content model beyond just how pieces of content are chunked together by end-users, but how that content is treated in the database, and how developers interface with all that new tissue. Moreover, the ad hoc governance that has organized around Gutenberg to help ensure its inclusivity and accessibility is functionally of greater importance than the Gutenberg codebase altogether.

    It makes sense that because there are plenty of usability studies betraying WordPress’s ease-of-use as a myth, that we-the-community target these usability problems with our innova-sers. Ease-of-use is a killer differentiator when you choose one product over another - but usability is flavor, not sustenance.

    Disruption requires identifying a misalignment between a person’s core job-to-be-done and the service they’re provided.

    The secret to winning the innovation game lies in understanding what causes customers to make choices that help them achieve progress on something they are struggling with in their lives. To get to the right answers, Christensen says, executives should be asking: What job would consumers want to hire a product to do? — Interview by Dina Gerdeman with Clay Christensen

    The product — and the features of the product — don’t fundamentally matter unless the user needs something that you can provide them.

    Is the WordPress user’s core job to be done to have a usable content-creation experience? No. It’s not even to create content in the first place. Rather, the core job of the WordPress user is to — for example — provide candle-junkies like me with candles, and make a living from it. “WordPress” isn’t really par

    • 11 min
    UX Design is Morally Gray

    UX Design is Morally Gray

    Folks tend to disagree with me whenever I say that user experience design is morally gray: there is no inherent requirement to making user experiences people like and prefer to competing experiences that leave users — morally or ethically — better off. Ethical design is a qualifier.

    This is an important distinction and nuance to design work that is critical to accept if we intend to push best practice in a more deliberately ethical direction. It empowers individual designers, teams, companies, entire verticals, even disciplines to differentiate themselves by choosing to design ethically.

    Assuming that good user experience design work has good intentions is dangerous — and naive.

    This also means we must divorce the relationship by what we do (design to improve the user experience) from how we do it (ethically, or not). It means that to be ethical we must choose to be so at each step of the design process, at each touchpoint between conception and performance of a service.

    To frame ethical user experience design like this make it easier to appreciate how difficult it is to create an ethical product or service. Perhaps not by intent — we all think we’re the heroes of our own story — but because the design of a thing is the culmination of a hundred decisions, hard ones. The CEO in the business of providing an ethical service might fail because of decisions made in engineering, or because they chose to design to optimize a conversion metric instead of some other made-up number.

    It is for this reason we need to make time and resources available to design the design process, creating systems of checks and balances not just for quality assurance that a button can be pressed, but for ethical stresses.

    Liking (❤) this issue of Metric helps signal to the great algorithms in the sky that this writeup is worth your time. Please take the time. If you haven’t already, please subscribe.

    Metric is a podcast, too, which includes audio versions of these writeups and other chats. Look for Metric UX in your favorite podcatcher.

    Remember that the user experience is a metric.

    Michael

    Get full access to Metric by Michael Schofield at metric.substack.com/subscribe

    • 2 min
    Can jobs-to-be-done replace "Front End Developer"?

    Can jobs-to-be-done replace "Front End Developer"?

    The “front end” is pretty nebulous. What makes a good front end developer? Its definitions, and so its answers, are all over the place. It’s not just the introduction of new front end frameworks that have changed how we talk about it, but in terms of the discipline of designing websites we have begun to think differently: in components, in services. We can see front end in flux in Ernie Hsiung’s “A fictitious, somewhat farcical conversation between me and the JavaScript programming language,” where Ernie as a front end developer — a successful front ender, look at his resume — imagines having an existential crisis because the front end changed while he was busy being a boss (a good one).

    Our understanding of the front end as a place no longer holds up to scrutiny. We cannot define it by a specific suite of tools, a kind of user expertise, or even that — if anything — front end development requires a browser.

    If we talk about the front end in terms of distance from a user, the “front” specifically being the interface between the user and the service provided, then we ought to accept that voice user interfaces (among other examples) challenge the notion that the front end has any tangible component at all.

    Even here, we are cherry-picking a particular kind of user, one that is at the tail-end of a complex service provision - presumably outside the “provision” circle of the Venn Diagram altogether. We’ll call this person “end user.” But again, using “front end” as a descriptor of that distance from a user — while accepting there are no constraints on technology or medium (like a browser) — should be applicable to the RESTful API that I design for consumption by a variety of user interfaces. The consumer is my end user. When I design the interface for that user, am I performing “front end development?”

    What I am trying to illustrate is that when we are thinking about user experience and service design, paradigms like “front end” and “back end” no longer align with an understanding of service clusters, ecosystems, or - frankly - users. These kind of identifiers are ephemeral and, as such, pose a problem to companies who organize themselves around these concepts.

    You long time Metric readers and listeners — “Metricians?” — might find this latter concern familiar. The practice of thinking in services reveals that same ephemeral nature around the product itself, given that the product is just a tool in a larger service provision, it is thus — like a tool — replaceable. Choosing to design organizations around products will shape the way in which said organizations develop, which is probably against the grain of good service design. Hot take, I know.

    So, practically, as service providers who make products that require engineers, how do we hire after we thought-spiral ourselves away from terms like “front end developer?”

    I think there is an implied solution. In 2017, Rob Schade at Strategyn suggested a new kind of role called the “Job Manager” in “Product Managers are Obsolete; focus on the Job-to-be-Done.” As an alternative to a Product Manager, the Job Manager focused on the design and development of solutions for a given job-to-be-done.

    If you need a refresher, a job-to-be-done describes a task where the user has a demonstrable need for the solution you provide. That is, if I need talk shop and further develop my own thinking about service design, a company like Substack provides a solution for my shop-talking need. The product — the newsletter editor and mailer that Substack provides — is a means to an end, not the end, and not necessarily crucial to my job to be done.

    In this example, rather than there being a Product Manager in charge of the newsletter editor, there would be a Job Manager overseeing the entire service Substack provides

    • 6 min

Customer Reviews

4.9 out of 5
16 Ratings

16 Ratings

Donovan2324 ,

Amazing work guys

So entertaining and the way you both talk is so approachable. Very good podcast!
Thanks so much for the work and information that you both put in

Jake hazzrd ,

Spread the word

A lot of good stuff in here. Keep it up!

CD Villard ,

Great podcast with a lot of great nuggets

Really insightful talk with a lot of really smart people. Michael's not a bad speaker either. ;)

Top Podcasts In Design

Listeners Also Subscribed To