"In Pulse surveys and conversations with many of you, we’ve heard that too much work requires coordination across teams, debates take too long, and decision-making rights are unclear. I’m sure many of you have felt that you spend too much time “aligning” rather than building, shipping, or serving customers. To improve this, we have reduced roles primarily focused on coordination, and have clarified the remit of the coordination roles that remain. "

Well, in theory this sounds reasonable. But who knows what will be the real consequences.

▲

sznio a day ago | parent | next [-]

I don't get it. Too much time is spent coordinating, so fire those who are responsible for coordination? Am I reading this wrong?

▲

jerjerjer a day ago | parent | next [-]

People whose primary job is to "coordinate" often, either in a well-meaning attempt to be thorough or just to be relevant, try to pull as many different people into any decision-making as possible.

So instead of me just getting approval from my manager, I need to get approval/buy-in from departments A, B, and C.

In that case, firing the "coordinator" person increases velocity because parts of the business processes they prop disappear.

	▲	locknitpicker 8 hours ago \| parent \| next [-]
		> In that case, firing the "coordinator" person increases velocity because parts of the business processes they prop disappear. So you get rid of the coordinator. What then? Does this magically unblock people? Let me frame this differently: if coordinating teams creates as much problems and impedance as you claim, how come Uber hired them to begin with? I mean, either Uber was shooting itself in the foot then, or it is now. Which one is it?
	▲	a day ago \| parent \| prev [-]
		[deleted]

▲

etse a day ago | parent | prev | next [-]

That's how I read it, too.

They pinpointed the problem of over-coordination to the messenger (coordinator) instead of the teams demanding final approval over launches (coordination).

Won't merging different teams under a single owner only push the problem further down the org chart?

	▲	icepush a day ago \| parent [-]
		The thinking in these types of reorgs is typically to push it so far down the chart that it comes out the other side

▲

csande17 a day ago | parent | prev | next [-]

There were too many meetings, so they got rid of the people whose jobs were to create lots of meetings.

▲

MattGaiser a day ago | parent | prev [-]

The coordinators enable extra coordination that is not worth doing. The coordination itself is the problem.

▲

threetonesun a day ago | parent | prev | next [-]

I've heard this at other companies and it's almost always an issue of upper management holding too much control over decision making, or poorly communicating actual business objects, but it's project managers and middle management that will bear the brunt of the layoffs.

▲

Synthetic7346 a day ago | parent | prev | next [-]

"Complain about coordination, get laid off" is what this reads like

▲

nitwit005 a day ago | parent | prev | next [-]

It's logical if you view them as unsuccessful.

But if "decision-making rights are unclear" is listed, it seems unlikely those people were the problem.

	▲	s1artibartfast a day ago \| parent [-]
		I think the idea is that if you go from 10 decision makers to 5 decision makers, coordidination and securing a decision will become easier

▲

jms703 a day ago | parent | prev [-]

So TPMs are getting the axe? Product managers too?