Product is a Social Practice
You open your product roadmap as soon as you get to work (if you haven't already done so before breakfast). There are forty-two items, twelve stakeholders, along with three “remind me at 9am” Slack threads, and a planning meet that was supposed to get everyone on the same page and create clarity. Instead, you feel the familiar drag: more process, more information to find, fields to fill, less sense of what actually matters. The work isn’t hard because the product is mysterious. It’s hard because everyone is acting in good faith with different pictures of the same thing.
That feeling – overwhelm dressed up as “we need better process” – isn’t a tooling problem. It’s a category error.
The mistake: product as a document factory
Most teams say they “do product.” What they often mean is a factory line of artefacts: briefs, discovery notes, OKRs, roadmaps, tickets, status updates. Each artefact is defensible on its own. Together they can still fail to produce shared understanding.
When confusion shows up, the reflex is to add another layer: a new template, a heavier stage gate, a workshop. Those can help. They can also multiply coordination cost without closing the real gap – which is that people are not yet practising the same product together.
Process confusion is what happens when we treat alignment as a paperwork outcome. Overwhelm is what happens when we run too many social negotiations in parallel and call it “agile.”
A reframing: product as social practice
Product work is a social practice: repeated, situated coordination among people who have partial information, competing pressures, and legitimate expertise in different corners of the system.
A practice is not a ceremony. It is how a group learns to see a problem, name trade-offs, and commit to action well enough to move. The roadmap matters – but only insofar as it supports that collective seeing. The ritual matters – only if it changes what people will do on Monday.
Three implications follow, and they are useful in conversation when the room starts drowning in frameworks.
1. Outcomes are relational before they are numerical.
Metrics describe behaviour after the fact. Before that, product is arguments made visible: whose pain counts, what “good” means, what we are willing not to build. If those arguments never happen – or happen only in side channels – no dashboard will rescue you.
2. Artefacts are scaffolding, not the building.
Documents are memory aids for a team that is trying to think together. When an artefact becomes the goal (“we need the PRD signed”), the practice thins out into compliance. Ask of any template: What misunderstanding does this remove? What decision does it unlock? If the honest answer is “none, but leadership likes it,” you have found your overwhelm – it doesn't help.
3. Skill is distributed – and that is the point.
Engineers sense feasibility. Designers sense coherence. Sales senses narrative pressure. Support senses where the product insults reality. Product’s craft is not to own all of that insight. It is to host the practice where those insights become one story the organisation can act on – without staging a false consensus.
What changes on a Tuesday
If you carry this frame for a week, a few shifts are practical.
Shrink the number of live questions. Not fewer meetings for their own sake – fewer unresolved questions in flight. A social practice advances when a question moves from “many people guessing” to “a few people accountable for a provisional answer everyone can test.”
Make conflict legible. Disagreement is not dysfunction; silent divergence is. Name the trade-off out loud: We can charge for custom development or protect the roadmap that makes us a product company; right now the same engineers are funding both promises. That sentence is often more valuable than another prioritisation matrix.
Close loops in public. When a decision is made, attach it to what will change in behaviour: what we will stop doing, what we will measure, what we will revisit. Practices strengthen when the group can see its own learning and benefits from it.
None of this requires abandoning process. It requires knowing what process is for: supporting joint attention, not substituting for it.
A line you can reuse
When the room is tangled, try:
“We’re treating this like a documentation problem. I think it’s a practice problem – we don’t yet share the same picture of what we’re building or why.”
It is not a magic phrase. It is an invitation to move up one level: from which artefact is missing to what collective capability we are trying to grow.
Seeing practice, not adding process
I'm writing about seeing practice – noticing how product work actually happens before we try to “fix” it with more structure. The social-practice lens is a starting move. It turns overwhelm into a diagnostic: too many threads, too little closure, too much performance of alignment.
You do not need a bigger framework catalogue. You need fewer, clearer rounds of shared sense-making – and the courage to let some artefacts go quiet when they are no longer doing social work.
What would change this week if you asked, of your most painful meeting: What practice are we trying to strengthen here – and what are we accidentally practising instead?
