Conflict isn’t really about the work, it’s about trust

When we experience conflict about something we’re working on, that conflict isn’t really about the work. It’s about trust between the people in the room.

I learnt this from a participant at a workshop I was facilitating, who I’ll call Adam. We were role-playing difficult conversations from work. Adam was a product manager, and his scenario was a regular meeting where his team of developers prioritised features for the next sprint. One particular developer always seemed to raise the same issue: a feature he thought was important, even though Adam had explained that it wasn’t a priority for the business. As the role-play started, I suggested that Adam use a listening technique we were working on to find out more about what was going on for this developer who always seemed to speak up.  Continue reading Conflict isn’t really about the work, it’s about trust

Advocating for “quality” content serves our unmet needs, not user needs

When we advocate for “quality content”, we’re expressing our unmet needs by making a judgment. That doesn’t serve user needs.

During my talk at Confab Barcelona—”Use agile methods to work together on content” (slides below)—I suggested that in order to benefit from agile methods, we choose to “serve user need over content quality”:

Although most people in the room seemed to follow, a few objected: someone stated that user needs and quality are the same thing. Later a friend observed that my statement was provocative. I realised that I’m not interested in provoking people and I didn’t actually explain what I meant. I’ll do that here instead.  Continue reading Advocating for “quality” content serves our unmet needs, not user needs