Cross-functional relationships: start with one!
Ethan was enthused and exasperated at the same time.
“OK, I can see there’s this model for sorting out our cross-functional relationships. Tears, tars or something, and a lot of words like audit, monitor, coordinate and stuff like that. All sounds great.”
“You don’t seem to think it’s all great” I offered.
“Well it’s not. We’ve got a million of these relationships. Everyone talks to everyone, and to go through and work out every role relationship in the place would take a decade, and wouldn’t it just turn us into a bureaucracy anyway?”
“Sure would”.
Ethan looked surprised – “but you’ve seen this stuff work before”.
“Yep”.
“So what do I need to do”?
“We fix one“.
“One?”
“Yep, one”.
“Well, how’s that supposed to help?” he asked. But he was intrigued.
“The deal…” I suggested, “…is that you guys aren’t yet used to seeing work occurring through cross-functional role relationships. You see only personal relationships. We need to get some practice in on how roles relate and learn to use this concept. Gradually it will become second nature and you’ll be able to set up things as you need them. The words like Audit, Monitor, Advisory, Coordinate and all the others will be normal. “
“But what use is just one?” Ethan wanted to know.
“Let’s not call it one.” I proposed. “Lets call it the first.”
Ethan rubbed his chin, his standard method for revving up the mind.
“Fine. Let’s do it then” he said after a full 30 seconds of silence. “Who should we start with?”.
“Your Quality Engineer” I put forward immediately. “Roles like that are usually in some sort limbo between having all the authority and none.”
“Sounds great” said Ethan and reached for the phone.
“Don’t do that” I jumped in. Ethan looked surprised. I continued; “it’s not up to your Quality Engineer to decide the work system, it’s up to you. We’re going to get her input for sure, but first, tell me what you are ultimately holding her accountable for”.
Ethan didn’t answer.
“We’ve found our starting point”