Useful Work versus Useless Toil
Source: https://www.marxists.org/archive/morris/works/1884/useful.htm ↗
Morris's 1884 lecture (later published as a pamphlet) draws a hard distinction between useful work — work that produces something of value to the worker, the community, and humanity — and useless toil, which simply wastes human time.
Morris was a central figure in the Arts and Crafts movement and an unusual voice in Victorian socialism, and the lecture reads now with surprising contemporary relevance.
For product direction the question it raises is foundational: is the product you are helping build useful in Morris's sense, or is it useless toil with better marketing? Read alongside Sennett's The Craftsman, which builds on this tradition.
Short, polemical, disquieting.
Central argument
Morris argues that most work under industrial capitalism is useless toil — degrading, meaningless labour performed purely for survival — while genuinely useful work has three properties: it produces something worth making, it is done with hope of rest, and it is done with hope of pleasure in the work itself. He contends that the distinction is not between mental and manual labour, nor between hard and easy work, but between work that serves human life and work that serves the accumulation of profit. The implication is radical: a large share of what Victorian (and by extension modern) economies produce should simply not be produced.
Critique
Morris's framework depends on a relatively confident judgement about what counts as 'useful' to a community — a judgement he roots in craft aesthetics and a pre-industrial ideal of skilled making that itself reflects a particular class position and romantic nostalgia. He offers no serious mechanism for adjudicating disagreements about social value, which makes the distinction polemically powerful but analytically thin when applied to contested goods. A thoughtful reader will also notice that his vision of pleasurable craft largely assumes small-scale production, leaving little guidance for organising complex, interdependent work at scale.
Why it matters for product
The essay forces a prior question that most product frameworks skip: before optimising how you build, Morris demands you ask whether the thing being built deserves to exist at all — a question product directors routinely defer because discovery processes measure desirability and feasibility but rarely interrogate whether demand itself is manufactured or genuine. For teams drowning in engagement metrics, retention loops, and growth targets, Morris's criteria — does this produce something of value to the user, the community, and the people making it? — function as a diagnostic that cuts through proxy measures. It also has an organisational edge: if the work is toil in Morris's sense, no amount of good team culture or craft investment will fix the underlying problem.