Where do you draw the line for passion?
Watching Mark Cuban’s behavior as owner of Dallas Mavericks, currently vieing for the NBA championships, is a love and hate fest for me. There’s are hints of goodness in him, but it’s lost in his choices of expression. He’s an echo of some tech-sector VPs and managers I’ve worked with: a core of good intentions, misguided by imaturity and self-centric egoism.
His passion and emotion about what happens to his team is real and wonderful to see: he’s not a guy in a suit, he’s personally invested in what happens (Seen at right wearing the jersey of a suspended player). It must be a boost for players to work for someone so visibly passionate and interested in what’s going on. Finding that kind of empathy from managers is rare in all businesses, including the NBA.
But the problem is how those emotions are translated into behavior. Cuban complains, vents, rants and draws more negative attention to himself as if working only from the Billy Martin & Bobby Knight (Mr. chair thrower) playbook. He deliberately violates rules, challenges not only officials but the league commisioner, showing little respect for the game. Drawing heat away from the team can be a sweet management move, but his behavior often seems more about his own feelings rather than driven by protecting the emotions of the people that work for him.
A noble man, with respect for himself, his team, and the game, would find an appropriate forum to vent his complaints, but Cuban lacks restraint: there seems little wisdom between his feelings and actions.
Instead of spending $1.5 million in fines over 5 seasons, he could pay to bring every single NBA referee to a training camp of his own design, or driven by a coallition of (other disgruntaled) coaches. He could find some positive way to both bring other people to support his view, and to effectively be an advocate for positive change. Why not found an NBA referee recruiting program? Work with other owners to boost their salaries to draw better talent? Regarless of whether his complaints are valid or not, there are more respectable ways for handling them.
But as of late, he makes it all too easy to pidgeon hole him as the spoiled rich kid who expects the world to circle behind his wake and give him what he wants when he cries. Whether he deserves this stereotype or not, being percieved in this way can’t possibly serve whatever his true ambitions for Dallas are.
Working out the final details with the fine folks at Step two designs to teach my workshop on Leading UX teams. More details to follow but tentative dates are:
Sydney, Sept 1st
Canberra, Sept 5th
Melbourne, Sept 8th
The one day workshop will be a crossover between project management and UX design, hiting all the sweet spots folks leading UI efforts often struggle with (including highlights from the ux-clinic list).
If anyone wants to try to meet up for drinks or a bite, leave a comment and I’ll follow up.
An interesting link from Reforming project management: Harvard Business school writes about Morning meetings – a daily meetup where leaders meet to get in sync. The essay is ok, but one passage caught my eye:
In contrast, two qualities characterize high-functioning leadership teams: (1) hard conversations happen—difficult issues move quickly from people’s heads to the conference table; (2) accountability is shared—individuals on the top team feel a responsibility to the organization as a whole, not just for their piece of the action.
What a great goal – hard conversations happen. I can’t tell you how many teams are stuck in the 5th level of hell for the single reason that leaders never let hard conversation happen. And the kicker is accountability – nothing more fun to work in a team culture that’s proactively accountable, with everyone taking their fair share of heat when things go wrong – suddenly people spend more time working instead pointing fingers.
Now if only someone at Harvard would write an essay on how to make hard conversations and accountability happen :)
This week in the pm-clinic discussion forum:
I’m a development lead in a high powered web development company. We beat competitors on speed and quality technology, and engineers like me do the closest thing to project management. We avoid specs and docs, working in small enough teams that fast communication is pretty easy. There is a strong anti-management vibe in the company, as well as a hyper proactive “do it now and fix it later” mentality, but those attitudes have served us really well – our company has been super successful.
The problem is that our organization has grown from 100 to 2000+ people in a handful of years. Many engineers work on several projects at a time, including lots of remote programmers. We have a high number of virtual teams and a super flat hierarchy – things that are liberating, but are suddenly annoying at times. The consensus driven approach we have isn’t as speedy as it was.
My dilemma has two parts:
Tactics: I’m more willing to try changes than many of my peers and reports. So how do I add in more management-y things, a little more structure and clearer division of ownership, without rocking the boat and being called a weenie? (Our lingo for fuddy-dutty management types). I fear it’s a one way ride: These things I’ll add will never be removed and it’s a downward spiral of over-management (And my team of engineers fears this too).
Strategy: How do you work to shift the culture the company was founded on and take pride in, when it’s not working as well anymore? I can’t say I’ve worked anywhere that handled this successfully – either the success ends, or people leave, whenever leaders try to mature the culture.
This week in the ux-clinic discussion forum:
I’m an information designer and developer, aka technical writer. I’ve recently been told that the v1 of our new product will not have context-sensitive help. The engineering team lead says “too bad; no one reads the documentation anyhow.”
I believe it’s impossible to design a totally intuitive UI, since everyone’s intuitive is different, and frankly, we’re not perfect as designers anyway. I think this means documentation has an important role – but since it’s my job, maybe I’m biased :)
So I’m curious about how other organizations either include documentation / support as a first order part of the experience, or how they justify depricating it given how often even the best designs fail their users. Is documentation something easily cut on your projects? How do you justify (or argue against) this?
- Help with help
I’m on chapter 4 of the next book and as part of the research I have a tall stack of books with the word innovation in the title. Many have the same theme: Do these 5 things and magic will happen. Your competitors will stumble in your wake. Profits and promotions will be your dominion. Beautiful people will talk to you. You’ll be 5 inches taller and 10 lbs slimmer. And they assume you have enough power, as CEO or VP, to make innovation happen.
But the better concern, the more interesting and cynical question, is this:
Who has the power to stop innovation in your organization?
We’ve all had good ideas die at the feet of the first person with power and motivation to kill them. Whether it’s a feature, a business plan, a project, they are torn to pieces by the innovation killer’s 5 foot radius idea death circle. Books don’t help much with them, unless they’re slim enough to fling across the boardroom, and heavy enough to knock them out when they strike.
We’ve all worked for idea killers – if we could get out ideas past them, we’d be ok, without all the books.
I’m exploring idea rejection and why it happens – here’s a rough list, but as this pertains to chapter 4, I’m looking for more thoughts and opinions – help if you can.
People in power stop innovation because they:
(Note: Sometimes rejecting ideas is the right move, and the “idea killer” is just a wise leader – so I am looking for less-cynical explanations than the ones above.)
Q: Does this list ring true? Why or why not? What else is missing?