Site icon I Manage Products

PRODUCTHEAD: Permission to collaborate

Producthead logo

PRODUCTHEAD is a regular newsletter of product management goodness,
curated by Jock Busuttil.

a punch-up at a product (no no no no no no no no) #

every PRODUCTHEAD edition is online for you to refer back to


tl;dr

Autonomous teams lacking the incentive to collaborate will create deadlocks

Structure the boundaries of responsibility between teams as interfaces

Autonomy doesn’t mean letting teams run amok with zero direction


hello

For the remaining product people out there who haven’t pivoted career to building with AI, many of the same hurdles persist, and many of them have nothing to do with the technologies in play, but with the social structures that have wrapped themselves around them. All the AI tokens in the world will not help to unlock collaboration with a stubbornly defensive team that owns a critical component and won’t play nicely with others.

Some of the challenges that can face a product person in a larger organisation are perhaps a result of entirely good intention. One team could be tasked with a particular goal, say, to migrate legacy software components onto a more recent platform and language. An adjacent team might be tasked with identifying and patching insecure systems, again a perfectly valid goal.

Where the problem can emerge is when each team is operating in isolation from other teams: neither team has a view of the bigger picture and the relative priority of each team’s mission; each believes its respective mission is the highest priority. Deadlock will occur when their targets overlap because both teams will not cede to the other – often because they feel they do not have permission to do so.

What is lacking in this situation is the higher level context the teams need to determine which of their two competing missions takes precedence. Sometimes each team’s work truly is of equal importance to the other, in which case someone (probably more senior) has to have the authority to break the deadlock by accepting the trade-off and deciding the sequence. There may be logical reasons to guide the trade-off decision, or in their absence it could literally come down to a coin flip. What matters is that the deadlock is broken and work on something can take place.

Some organisations find themselves tied into knots of inaction like this because they set out with the good intention to give teams autonomy to pursue a particular goal, but didn’t share enough of the context to help teams resolve overlaps. What is often also overlooked is the incentive given to each team. If a team is tasked only with succeeding in their primary mission, it has no incentive to deviate from it or to negotiate sequencing with another team when a deadlock occurs – any delay or distraction reflects badly on them. However, if there is a stronger overriding principle of collaboration in the context of a broader goal, then each team has permission to cede ground when needed.

When you encounter deadlocks like this, think about whether the teams involved understand the broader context and have an incentive to collaborate in order to break the deadlock themselves, or whether someone suitably senior needs to step in to make the call.

Get coaching and help us to donate more #

On an unrelated point, Product People has just donated 25% of the product coaching fees from the last year to various charities, as we do each year.

I would be delighted if you’d consider making a donation yourself, or booking a coaching session to help us donate more next year.

Speak to you soon,

Jock



what to think about this week

Breaking Through Bureaucracy: A Leader’s Guide to Establishing Your First Autonomous Team

Your enterprise may be successful today, but market dynamics are rapidly evolving. To thrive tomorrow, you need to innovate faster, get closer to changing customer needs, and respond with greater agility. Yet your traditional operating model—built for stability and scale—is at odds with these imperatives. Hierarchical approvals, functional silos, and complex dependencies may provide control and alignment, but they slow down the teams charged with driving innovation.

Get teams to stop seeking permission and start making better decisions

[Tom Godden & Arvind Mathur / AWS Executive in Residence Blog]

Autonomy Without Isolation: How Engineering Leaders Make Collaboration Work

Autonomy is a sign of a healthy engineering organisation. Teams that own their domain and can make decisions without waiting for permission tend to move faster and feel more accountable. But autonomy has a shadow. The old silo announced itself with “that is not my job.” The new one says “we have got this” and quietly closes the door.

Autonomy without collaboration creates expensive blind spots

[Matteo Bisi / DevOps.com]



recent posts

Common misunderstandings about empowered teams

Have you encountered these misunderstandings about empowered teams?

Nope # 1 – “We’re empowered and autonomous – we can do whatever we like”

Nope # 2 – “As the leader for an autonomous team, I’m not allowed to set direction”

Nope # 3 – “As an empowered team, it’s not our job to explain our Very Important Work to others”

If any of these are familiar to you, I explain some of the reasons why this is happening, and how to fix them.

Autonomous teams can’t do whatever they like

[I Manage Products]

Chess is easier when you can see the board

A Wardley Map is to corporate strategy what a chessboard is to players: you can absolutely play the game in your head without seeing the board, but if you can it’s a lot easier to play, and you have a massive advantage over the people who can’t.

Know what moves you can make, and why to choose this move now

[I Manage Products]

How to form a go-to-market strategy

A go-to-market strategy isn’t something you tack on as an afterthought to an upcoming product launch. Instead it’s about understanding where value exchanges occur, and figuring out how to make them more frequent, consistent and predictable.

Go-to-market emerges from your discovery

[I Manage Products]

can we help you?

Product People is a product management services company. We can help you through consultancy, training and coaching. Just contact us if you need our help!

Helping people build better products, more successfully, since 2012.

PRODUCTHEAD is a newsletter for product people of all varieties, and is lovingly crafted from late nights and conviviality.

Exit mobile version