Steve Sandersonš¢
4y ago
I love making important things better, while glimpsing at the patterns that connect
In the previous post, I introduced the idea of using the perspective of supply and demand to begin making sense of how a product team operates. In this post, I'm going to give some examples and the practices I use to get oriented on their work.
š§µš
With a supply-side team, I might encounter something like:
that the large majority of their time was spent focused on what they could build, and little to no time was spent on learnings from users
stories that motivate them such as "we shipped this new feature, yeah!",
With a demand-side team, I might encounter something like:
that they spend time learning from users which affects decisions in the time spent building
motivating stories such as "we found this really painful (customer) problem"
To get oriented, I go through two big steps:
simplify my work with a few assumptions
ask a couple of questions
Assumption 1: it's more useful to learn what's actually true, not what people claim is true.
Assumption 2: the purpose of a product effort is to impact one or more groups of people (i.e. impact on customers, users, business, etc.). I don't assume which group, or whether they're even customers.
Assumption 3: shortcut by categorizing practices in product work as "supply-side" (e.g. writing code) or "demand-side" (e.g. testing customer problem hypothesis); though never absolute, i.e. context matters (e.g. "write code to test a customer problem hypothesis" is demand-side).
Get an idea about their attention direction (is the team focused internally or externally?), by asking "how do you define success?" (or "how will you know when you're done?");
is the focus of their answer:
external - is it about some users outside of Product making some form of progress (e.g. users happier, salespeople more effective, etc?)?
internal - is it about the Product group's own work (e.g. delivered feature, beautiful design)?
Where an external focus implies a more "demand-side" stance, and an internal focus implies a more "supply-side" stance.
Get an idea about their relationship with the users, by asking "what happens when the users fail to make progress with the product" (or "what happens when users can't do their work");
do they see themselves:
relational - concerned with, and interested in learning more, curious, or even consider themselves (partially) accountable for helping users?
transactional - separate (e.g. siloed) from users: "the product is functional, their problems are their problems, and not ours"?
Where relational implies a more "demand-side" stance, and transactional implies a more "supply-side" stance
Understanding whether a team tends more toward "supply-side" vs "demand-side" is a big part of assessing whether the team is a fit for their environment. There is no absolute best stance, it depends on the environment.
Simplistically, a demand-side stance is better in an environment of uncertainty and a supply-side stance is better in an environment of certainty.
Of course, once you can see the (mis)fit, then there's the question: if the fit isn't right, how can you help to improve the fit? I'll save this question for another post.
h/t to @chrisvmcd for his video on Social Practice Theory