Weeknotes #230

This week I did:

Service blueprinting

I reworked our service blueprint to take account of a new programme design. I’ve been thinking about where our knowledge and information resides. How do we effectively develop shared understanding of user needs and business requirements across scope definition documents, service blueprints, user stories, etc., and how do we help each other understand how they all fit together. One of the interesting stances we’ve taken is the the user journey within the service blueprint is our single source of truth about what to build. It shifts the focus away from business requirements and what stakeholders want to what experience the user has and how all the parts fit coherently together.

Some thoughts on digital project management

Inspired by Be More Digital‘s post on Simple project management I wrote some of my own far less useful thoughts on managing digital projects, including why digital project management is different from non-digital project management, what is actually managed by project management, and why prioritisation leads to uncertainty.

The Ultimate Digital Tools List

I put my Digital Tools List on Gumroad. I expect the list to be up to a thousand products and tools over the next few weeks. I haven’t made any sales but that’s not surprising because I haven’t promoted (and I have no intention of becoming ‘the digital tools guy’ on Twitter), but the process of writing a product description helped me figure out the usefulness of the list. The Digital Tools List can be used to create a unique tech stack for an indie business. So, for each side-project or maker business someone decides to set up, they can either do it the way everyone else is doing it, or they can think more strategically about what tools to use to help make Twitter be an effective main promo channel, or to stream their video to multiple platforms at the same time. Productising this process was the idea behind Build Better Systems. It would help makers figure out their business model.

Why charities tackle wicked problems

I wrote up some of my ideas on why charities choose to tackle wicked problems rather than tame, solvable problems. The post veered off from what I intended it to be and went on more about my idea of the three spheres of societal life and how they can or can’t respond to wicked problems. My intention was to write about how charities are actually pretty well equipped for tackling wicked problems but maybe that’ll be another post.

2021 Goals

I started writing my goals for next year, which are mostly continuing with what I was working on this year (doubling-down, as they say). As part of ‘Know What You Bring’, one of my side projects, I was working on a method for identifying things like that are you interested in, how those areas of interest intersect, how you develop expertise at that intersection, how you communicate that expertise, and who will find it useful. The process lead me to conclude that I want to spend more time on the intersection of charity, digital and innovation than I do on indie maker side-projects, so I want to try to spend more time writing blog posts about digital charity and innovation than I do working on side-projects.

I also updated my Now page. It’s still a mess but I like the idea and want to try to find a way to make better use of it.


I read:

Learning attitude

I read A Summary of Growth and Fixed Mindsets and I assume I’m below average, both of which deal with having a learning attitude. Derek Sivers says, “To assume you’re below average is to admit you’re still learning.” and Carol Dweck says “There’s another mindset in which these traits are not simply a hand you’re dealt and have to live with, always trying to convince yourself and others that you have a royal flush when you’re secretly worried it’s a pair of tens. In this mindset, the hand you’re dealt is just the starting point for development. This growth mindset is based on the belief that your basic qualities are things you can cultivate through your efforts.”

A foray into Online Film Clubs – a peek into the future of community building

I read Paulina Stachnik’s article talking about how “digital leaders, we have a unique opportunity to create this sense of community for our supporters.” Digital communities isn’t something I know very much about, but as Paulina says, they are more important now than they ever have been. What the article shows is that things that could be done without considering community can also be done with community in mind. That’s really interesting and opens up lots of possibilities. It basically says that anything and everything can be a community-building activity.

Why should community building be important? Well, there is some research that says that it’s intrinsic goals (like feeling a sense of belonging to a community) that improve our well-being, so how we create things that help people achieve intrinsic goals (being part of a community) whilst achieving extrinsic goals (watching a film) matters.

Moving Beyond Command And Control

I read Moving beyond command and control* by Paul Taylor. He talks about different assumptions and perspectives people hold on centralised control and localised communities, and how both are needed in national crisis situations like a pandemic. He goes on to talk about the different narratives around communities and how they shifted from celebrating the ingenuity of communities when they seemed to be abiding by the wants of centralised control to criticising communities for breaking the rules when they seemed to take too much of their own power. He ends with, “In 2021 we all need to get off the fence and state which one we truly believe in, and make that world a reality.” Do we believe that communities can hold their own power and make their own decisions, or do we believe that should not have power communities and so need central command and control in order to make decisions.

Out of context, but it made me think about loosely-coupled systems again. The issue I see with the either/or approach to where the power lies is that it is built on hierarchical structures from previous centuries. If we were building something new today with modern information networks (and what we’ve learned from how a global pandemic disrupted tightly-coupled systems) the available options might look quite different.


Thought about:

Learning from the past

The problem with learning from the past is that it assumes we’re facing the same problem in the present. Often it’s easier to assume we’re facing the same problem, and ignore the differences as inconsequential. Sometimes, saying that we’re learning from the past is a shortcut to conclusions even if the context is different. I don’t know how to resolve this, to tell the difference between when learning from the past is a good idea and when it isn’t. The only sense that I get is that the level of abstraction matters for the relevance of the learning. Too detailed and the differences between the past and the now means there is nothing to learn, too generalised and the lesson becomes so vague as to be useless.

User stories

There’s lots written about how to write User Stories, but I don’t think I’ve ever read anything about how to interpret user stories. Do designers think of user stories differently to developers? How are user stories useful for stakeholders, and for testers? User stories have a form and function, and a language of their own. Without a shared understanding of those how can we expect to understand user stories?

Posthuman charities

I’ve been thinking about writing a blogpost about how charities might work differently in a posthuman society. If we “reject both human exceptionalism (the idea that humans are unique creatures) and human instrumentalism (that humans have a right to control the natural world)” then how might we think about charities and for-good organisations that have their thinking rooted in humanist ideals?


Tweets:

Fake it till you make it

James Heywood tweeted, “Another problem with “fake it until your make it” is that you know you’ve faked it. That can trigger anxiety even as you succeed.” It made me think about how the phrase can be interpreted in a number of different ways. Faking it could be seen negatively as hiding inadequacies or incompetencies. Or it could be seen more positively as demonstrating a growth mindset and courage to go outside your comfort zone. It could be seen in different ways by different people, leading to confusion about how well-equipped a person is and where they might have development needs. I guess that’s the things about short phrases like this, they are purposely ambiguous, which can be a good thing when it leads to conversations to uncover and improve understanding.

Strategy for information products

David Vassallo tweeted, “A reliable info product strategy:

  1. Find something you know very well.
  2. Share what you know on the internet.
  3. Wait until people start asking for more.
  4. Do a brain dump of everything you know about the topic.
  5. Edit for high info density.
  6. Self-publish.”

It implies the idea that well communicated expertise can be part of overcoming the information product paradox, where customers don’t buy because the don’t know what they’ll be getting, but if they are given two much of the information then they don’t buy because they already have most of the value. Expertise signals value. If you’re known to be an expert in a topic then there is the expectation that what you produce will be valuable even without knowing what you’ll be getting.

Select who to serve first

Natalie Furness tweeted, “How to assess product market fit, while generating traction without spending money. A thread based on my experiences on scrappy startup go-to-market strategy.” She goes to offer lots of advice to indie makers including, “Product Market Fit : Select who you want to serve first. Try and make your test audience as narrow as you can to start with. Remember, this can change as your product develops.” The idea that indie makers start by building an audience around their area of interest before they even know what product they’ll be building is opposite to the usual approach of a business where they develop a product that fits their capabilities and then go looking for an audience. Its interesting to see these difference as the majority of business business models have grown out of industrial thinking whilst indie maker business models have grown out of internet-era thinking. I’ve said before that the maker movement will come of age when a single maker disrupts an established incumbent business, but perhaps another measure of success for the maker movement will be when businesses begin adopting their strategies (like they did with startups and software development).

*I don’t normally tag my links, just this once for fun.

Why charities choose wicked problems

Charities and other for-good organisations choose to tackle the wicked problems of our world because no one else can. Wicked problems are complex and interconnected social problems that defy a predefined solution. They are problems that require continual development of solutions that behave like Public Goods, which means they are not viable to be provided by the market. And they are problems that mostly affect the marginalised people in our society, which means the state does not tackle them as they do not affect the median voter. Charities tackle wicked problems through offering services that alleviate some the consequences of the problems and through affecting changes in the systems that cause wicked problems.

What are wicked problems

Horst Rittel and Melvin Webber were urban planners at the University of Berkley in California in the 1973 when they wrote an article called: “Dilemmas in a General Theory of Planning”. In it they introduced what they called ‘wicked problems’; problems that are difficult or impossible to solve because of incomplete, contradictory, and changing requirements that are often difficult to recognise. Rittel and Webber said that wicked problems have 10 important characteristics:

  1. They do not have a definitive formulation.
  2. They do not have a “stopping rule.” In other words, these problems lack an inherent logic that signals when they are solved.
  3. Their solutions are not true or false, only good or bad.
  4. There is no way to test the solution to a wicked problem.
  5. They cannot be studied through trial and error. Their solutions are irreversible so, as Rittel and Webber put it, “every trial counts.”
  6. There is no end to the number of solutions or approaches to a wicked problem.
  7. All wicked problems are essentially unique.
  8. Wicked problems can always be described as the symptom of other problems.
  9. The way a wicked problem is described determines its possible solutions.
  10. Planners, that is those who present solutions to these problems, have no right to be wrong. Unlike mathematicians, “planners are liable for the consequences of the solutions they generate; the effects can matter a great deal to the people who are touched by those actions.”

Why should an almost fifty year old idea about urban planning be relevant to charities and the causes and problems they tackle? Well, the idea didn’t stay with urban planning.

Wicked and messy

By 2007, ‘wicked problems’ had more proponents and a different name. Robert Horn, an American political scientist, called the phenomenon a “Social Mess” and described it as a “set of interrelated problems and other messes. Complexity—systems of systems—is among the factors that makes Social Messes so resistant to analysis and, more importantly, to resolution.” According to Horn, the defining characteristics of a social mess are:

  1. No unique “correct” view of the problem;
  2. Different views of the problem and contradictory solutions;
  3. Most problems are connected to other problems;
  4. Data are often uncertain or missing;
  5. Multiple value conflicts;
  6. Ideological and cultural constraints;
  7. Political constraints;
  8. Economic constraints;
  9. Often a-logical or illogical or multi-valued thinking;
  10. Numerous possible intervention points;
  11. Consequences difficult to imagine;
  12. Considerable uncertainty, ambiguity;
  13. Great resistance to change; and,
  14. Problem solver(s) out of contact with the problems and potential solutions.

Over the decades, the idea has been adopted by designers, software developers, statisticians, economists, and policy makers. And the introduction of the term ‘Super wicked problem”, with additional characteristics of ‘Time is running out, no central authority, those seeking to solve the problem are also causing it, and policies discount the future irrationally’ helped to encapsulate the biggest problem we face as a species; global climate change.

That’s what a wicked problem is. And there are plenty of them.

Why wicked problems aren’t tackled by the market or state

The social contract (the individual’s relationship with the collective) is enacted by three modes of organising in our modern society; the state, the market and the civil space. Each of these use different methods to get people to deliver their part of the social contract. When a government makes a law, it is with the intention of organising people to adhere to a way of behaving (don’t drink and drive). When a business has a hierarchical structure that sends instructions from higher up to lower down, it is with the intention of organising people to maintain authority, responsibility and accountability (do the work you’ve been told to do). When the actions of one man walking around his garden are leveraged to raise money for charities, it is with the intention of organising people to support other people (financially through donations and socially through ‘cheering’).

Tame problems make for easy value exchange

Businesses use market modes of organising which only really allow for choosing easy (or ‘tame’ in Rittel and Webber speak) problems with knowable solutions. If you have neck ache the market can offer a wide range of potential solutions from pain killers to heated neck pillows to posture correcting chairs to a massage. And it’s up to you to know which solution fits your problem. In the eyes of the market the problem is solved when there has been a value exchange. You got what you wanted (something to help with your neck ache) and the business got what they wanted (your money).

Businesses don’t tackle wicked problems because even if they could offer solution they wouldn’t have a customer who was willing to pay a market-rate for that solution. Imagine a tech startup that could actually solve homelessness (stop laughing). What would the business model be? They couldn’t charge homeless people, they don’t have any money. Perhaps they could they sell their serve to local government, but once they’ve solved the problem for all their customers they put themselves out of business.

So, the market can’t solve wicked problems.

Limited resources make for easy spending decisions

Governments use state modes of organising which have some capacity for dealing with the wicked problems that arise from complex society. Running a country with all of it’s interrelated systems of health, education, economy, etc., etc., is a very wicked problem but laws, regulations, policy spending decisions, etc., allow governments to choose which problems to tackle and how much focus to give them.

Burton Weisbrod, an American economist who wrote about nonprofits, education, welfare and poverty, suggested that the nonprofit sector existed (at least in part) because of the failure of governments to provide sufficiently for all members of society. Every government has limited resources and will always direct spending at things that satisfy their median voter to try to ensure they are kept in power. These two thing; limited resources and pleasing the median voter, mean no Government ever spends enough on the marginalised people in society.

Weisbrod said that government spending decisions cause a market failure which nonprofit organisations then attempt to resolve. For example; the government chooses how much to to pay nurses (state spending decision). Nurses find their pay insufficient to feed their family (market failure). Charities operate food banks to help nurses feed their family (nonprofit sector response). If the government was to resolve the problem they would do so by paying nurses more, because that’s an instrument available to them within the state mode of organising, but it wouldn’t set up food banks because they are within the civic modes of organising.

So, the state can’t solve wicked problems.

Why charities choose wicked problems

Charities use civic modes of organising which often means they find ways to get people together over something they care about. Food banks only work within the civic modes of organising because it takes a one group of people (those that operate the food bank) to organise another group of people (those making donations to the food bank) in order for another group of people (those using the food bank) for the benefit.

Causes make for narrow solutions

Charities are cause-focused. The cause, is the primary concern of all charities and for-good organisations. Charities have a charitable purpose to tackle their chosen cause because the Charity Commission (and UK charity law) says they have to be (there are twelve charitable purposes to choose from and an ‘other’ category). Choosing a cause and charitable purpose is one of the first steps in registering as a charity. This makes sense if having regulations in place to ensure that only those organisations that are actually doing some good in the world are to benefit from charity status is what is most important, but it makes less if you actually want organisations that can tackle wicked problems. When a charity talks about their cause, they are referring to the wicked problem they are tackling but the problem with being so cause-focused is that it sometimes leads charities to approach the solution in very narrow ways. (I think cause-agnostic charities would be better equipped to contribute towards tackling wicked problems but that’s an aside). Charities have to tackle a wicked problem because it’s legally a part of what it is to be a charity in the UK, but it also limits what they can achieve.

Impacts make for poor measures

Charities are a response to the market failure of governments. choosing not to spend sufficiently on public goods . If a government was able to solve homelessness through providing enough suitable housing, support for addiction, mental health problems, etc., and all those other things that contribute to homelessness, then there would be no need for charities (or tech startups) to tackle that particular wicked problem. But tackling wicked problems is costly, however it is approached. And reducing the impact wicked problems have on people is almost impossible to measure in order to demonstrate the cost-effectiveness of the charity’s work. Charities have to tackle wicked problems because government spending choices don’t tackle them, but its expensive and almost impossible to measure the impact.

Can charities solve wicked problems?

In an increasingly connected and complex society wicked problems become even more intertwined and impossible to predict what changes will have what outcome. This must be recognised and accepted if charities and for-good organisations are going to have any hope of affecting change. Systems thinking and systems change work offers some chance to positively affect the wicked problems in the direction we might want, but figure out how to truly tackle wicked problems is a wicked problem in itself.

So, can charities solve wicked problems?

What should you do when you find ten pounds in the street?

Walking along the street, I look down and see a ten pound note? What should I do with it? I’ll donate it to the first charity someone on Twitter tells me to.

So I split it three ways and donated £20 each to The Biscuit Fund, the ISA Foundation and The Murray Parish Trust in aid of the iMRI Suite at Southampton Children’s Hospital.

Weeknotes #226

This week I did:

Kanbanning it

We’re going to start using Kanban for our product development process from next week. It’s been a few years since I’ve used it and I’m a bit excited. We’ve been discussing things like what the work in progress limits should be for each part of the process and how to communicate this way of working to stakeholders.

The evolution of technology and innovation policy

This week’s lecture was about the evolution of technology and innovation policy, patterns of uneven technological development and innovation amongst countries, the role of the state and innovation policy and the market failure argument. I find these kinds of ‘interplay’ topics quite interesting. What is the relationship between the state and the market in creating innovation? How is technology development and policy creation connected in driving innovation? Where is innovation investment most effective, in improvements and efficiency gains to existing technologies and business models or on higher risk new new innovations? Utilisng new technology has two aspects, the knowledge about the technology, which is a public good that no one can be excluded from gaining, and the non-codifiable tacit capability which is dependent on organisational routines to make use of the knowledge. That’s an interesting interplay too.

Qualitative data analysis

The other subject of study this week was thematic coding for qualitative analysis. I found this more interesting than I thought I would. The process of formalising an informal body of information, but doing so in a way that is unique to you, is interesting to me. It connects with some of the thinking around note-taking methods like Zettelkasten and Building a Second Brain. I guess the difference is that in academic research the coding must be done after the information is collected to avoid any bias whereas most note-taking methods recommend coding at the same time as creating the note.

30 to go

My digital tools list is up to 470, making the target of 500 by the end of the year easily reachable. At some point I’m going to have to decide what to do with the list. I can either continue to add to it in Notion where no one else really knows it exists or uses it, or I can think about how to make it more public and usable.


Thought about:

Which project?

With so much of my time spent on studying recently I haven’t done very much on any of my side-projects (other than think of a few others to go on the list). I feel uncertain about how to choose which ones to work on, and about starting new projects without ever getting close to finishing any. I like LaunchMBA’s idea of launching twelve products in twelve months but I know I’m not going to have time for the next ten months. And maybe that isn’t the right approach for me because it is about finishing things and maybe what I want is just the creative expression of playing with these ideas.

Layers of abstraction

I’ve wondering about how you might represent the layers of abstraction in product thinking. At the most real and elementary level the digital products we build are just a bunch of electrons that are represented (or abstracted) by 1’s and 0’s in binary code, which is further abstracted through various levels of programming languages to create a graphical user interface that people can interpret and abstract through their actions into ideas that fit into mental models at the highest level of abstraction. However you slice the layers there has to be translation between each layer. How good that translation is matters. Our ideas make electrons move. And electrons move our ideas.

Design principles

How important are design principles? Or any principles for that matter? Does having vague concepts help to provide direction, make decisions, achieve anything? One of Yves Béhar’s principles for design in the age of AI, “Good design works for everyone, everyday”, for example, looks like it makes sense. It’s hard to see how or why anyone would disagree with it. But it’s also hard to see how it could be achieved in practice. Is that the point? Are principles meant to be aspirational, a representation of something we value and so aim towards, even if we never achieve it? But then, how do you stop a principle being a cliché, or just some that sounds good but is meaningless?

Pressure junkie

Under less pressure I’m achieving less. I used to sleep five hours a night, work 15 hours a day, and get lots done. Now, with so much less pressure I’m not being anywhere near as productive. Relying on self-motivation to get myself to do things I’m not too bothered about doing isn’t working. Maybe it’s a good thing. Maybe its time to learn to live without the pressure.

Audience building

The basic business model for the internet indie maker is to start with building an audience, which means figuring out what you want to be known for and by who. I did a bit of thinking about how my audiences might be, one for digital charity stuff and the other for indie maker stuff. All the stuff I’ve written and the ideas for products I’ve started have always been purely for my interest, so thinking about audience building brought up the question, ‘Do I need an audience’? It’s a prerequisite aspect of a business model, you need to have someone to sell to, and based on the thinking expressed in Courtland’s tweet below, everyone should have their own business model.

Permissionless apprenticeship

Permissionless apprenticeship is an idea from Jack Butcher, that if you want to grab the attention of folks that you admire – start apprenticing under them without even asking for permission. It’s interesting on many levels, from the obvious of using it as a way to learn from someone and (perhaps) get their attention, to seeing how the maker community responds. Of course, as is right with the indie maker ways of working in the open and sharing ideas, people from the community jump on the idea and build-out their own ways products from video courses to worksheets.


And read:

What makes a good cucumber?

I read about Gherkin Syntax to remind myself about the behaviour-driven development approach and writing acceptance criteria.

What makes a good charity?

NPC’s guide to charity analysis by Ruth Gripper and Iona Joy from 2016 is really interesting. With statements like: “The starting point when looking at any charity is to understand how it wants to change the world”, “Scale is not necessarily a sign of success”, and “the digital maturity of an organisation is likely to be constrained by its size, budget and leadership”, it seems to take a pragmatic view.

What makes an excellent charity?

The King’s Fund’s ‘Modelling excellence in the charity sector’ report from 2017 with it’s characteristics of GSK IMPACT Award winners list reads like a a bit of a how to guide for making an excellent charity. It includes ‘services strongly rooted in the community’ , ‘strategic partnerships where charities play an active role in identifying issues and finding solutions’, and ‘board skills that reflect the changing nature of the charity sector’. One of the ideas I found interesting was the mention of the ‘added-value’ charities could provide, so that when commissioned to provide a specialist service they also offer more generic related services. In the commercial world this might be called cross-sell.

Service dominant logic

In Systems Thinking in Design: Service Design and self-Services, John Darzentas and Jenny Darzentas state that, “Services have moved from being a peripheral activity in a manufacturing centred economy, to an engine for growth and society-driven innovation… Known more commonly as ‘Service Science’ its aims are to integrate findings from these different disciplines to achieve better understandings, tools and techniques for creating innovative services… Vargo and Lusch (2004) argue that services require a change of perspective or ‘logic’. having been based on a model of exchange they term ‘goods-dominant logic’. In this view, services are being treated as products, as tangible resources with intrinsic values and with a basis in transaction. That is, the customer obtains the goods/services in exchange for money, and that is the end of the interaction with the provider. In contrast, ‘service dominant logic’ (SDL) describes services as intangible resources. Providers do not provide value, but ‘value propositions’; that is customers decide whether or not to make value out of those propositions or offerings, in effect they ‘co-create’ with the service providers.

Triangulation in research

Triangulation is a method used to increase the credibility and validity of research findings. Credibility refers to trustworthiness and how believable a study is; validity is concerned with the extent to which a study accurately reflects or evaluates the concept or ideas being investigated. Triangulation, by combining theories, methods or observers in a research study, can help ensure that fundamental biases arising from the use of a single method or a single observer are overcome.” I wonder how much of the user research that is used to make decisions about websites, digital services, product development and business direction has been triangulated to any level of robustness?


Some people tweeted:

I’m a business, man

Courtland Allen, tweeted “You’re not an employee, you’re a business. We just changed all the names. Posting your resume is marketing, interviewing is sales, salary negotiation is pricing, your employer is your customer“. Like Jay-Z said, “I’m not a businessman, I’m a business, man.” It’s really interesting to think of individuals in this way as it changes the power dynamic between organisations and individuals (which is changing anyway).

Invest in your future self

Julian Shapiro, tweeted, “Judge your days by how much you invested in your future self. Judge your years by how much you cashed in on that investment“. It’s not about getting stuff done, it’s about getting stuff in service of future leverage and benefit.

Nocode, no problem

Whit tweeted, “Want to build your side project for less than $100? It’s very possible. We’ve done it 6 times in the last 3 months.” and goes on the explain the tech stack for each of the side-projects. Of course, building products is the easy part. Building an audience, building them something they want, and selling it to them, that’s far more difficult.

No future but what we make

Jason Crawford offers “Some visions of the future based on different views of technology“, which of course aren’t mutually exclusive unless you state ‘when’ the future is, but all take a dualistic opinion of technology being either good or bad. Perhaps the future for humanity and technology, as we learn more about complexity and systems thinking, is to move away from simplistic narratives.