Hacker News new | ask | show | jobs
by aboyeji 5580 days ago
No disrespect to Mr Jefferson but this management method does not work.

It always results in a pyrrhic victory and resentment from the other people on the table from being made to look incompetent (although the truth is that indeed, they are for not coming to meetings prepared).

Let me explain

My last job was President of a College Newspaper. It was a pretty cool job. I had lots of power and I felt like I was "the one" who would usher this paper into a web 2.0 era. I came up with this grand plan and all. Unfortunately, much of the rest of my board was largely incompetent (or this was what I thought). Also, running the college newspaper wasn't as much of a passion for them as it was for me. They all had better things to do.

Ofcourse the natural resulted. Lots of meeting where we would not make quorom. Discussions without reading the background material however earlier on we had sent out a padded agenda etc. Naturally also, I was the most prepared for most of the meetings. I knew our Byelaws and PnP in and out and ofcourse, I knew the operations and management procedure for the newspaper, start to finish at the back of my hand. I got my way at meetings a lot of the time because no one at the table knew better and the people who knew better knew I was (mostly) right.

Soon enough however, resentment had begun to build. I was "arrogant" and an "asshole". We were always moving "too fast" even when it was clearly the right management decision (often taken 2 weeks after it should have). My VP was beginning to overrule management decisions we had discussed at meetings she had failed to attend for one reason or the other. In short, it was chaos.

I started work in May. By October, I was insane, overworked, single and had not spoken to my family in months. I resigned.

Long story short: If you are banking on the ignorance of your team to succeed in a project by pushing through your agenda. You have already lost. Surround yourself with people smarter than yourself, who will come to meetings as prepared as you are. Watch your project, team, committee soar. Surround yourself with morons who are too slow to keep up with you and you'll always be lagging behind.

You can trust I took this lesson to heart when I started building my own startup.

2 comments

I don't intend to be disrespectful to you, but were you perhaps arrogant and an asshole?

In the past, when I was passionate and full of ideas on a particular subject, I have later looked back and noticed my behavior to be.. less than what I would expect from myself. It was too easy to take that energy I had invested in my ideas and snap that around negatively toward others when they came off as ignorant or wasteful of my time.

The historical anecdote of Thomas Jefferson may have left out - for brevity, focus, or other reasons - the notion that Jefferson not only prepared heavily for the meeting, but likely also won over the participants through diplomacy. It's never just one trick that wins the day.

If you're building a team from scratch, that's wonderful. If you are coming into an existing committee or group of people, the soft skills come in very handy.

Before you take my comments as a quick insult, would you be able to look back at the entire newspaper debacle and see if there wasn't anything you could have done better to win people over? In retrospect only, consider those "stupid" and unprepared people a lost cause. It's not for their benefit but yours.

I actually considered this possibility after I resigned. It might sound pretentious but no I wasn't. I was just stuck with a bad board.

Why? First it had a track record for organizational incompetence. I should have known better but few of my predecessors especially the more competent ones had had a good experience in that position. They had all warned me when I began but in my naivete and exuberance I still took the position and assumed I could change everything. Second, after I left, one by one the board turned over and it became very obvious that I had simply been shouldering too much personal responsibility with making sure our organization ran smoothly. I ended up still having to advice the organization from the outside after resigning.

Most importantly, till this day, I still have a good relationship with many of the more competent people in the organization (many of whom were recruited by me). The organization remains moribund however, bound together only by the strings of infrastructure (and personnel) I left behind.

Nonetheless, I think the more useful point I have to admit you make is that when you are joining an existing committee or group of people, there is a bit of compromise that goes on. To that, I say, make sure you check the background of the people you are working with before taking up any position. If they are people with a track record for incompetence or failure (in my case the fact that many of the people I was working with had been staff with this organization for several years should have been a warning signal),don't accept the position. Your peace of mind is way more important than any opportunity to marktime in the name of making a difference.

Given human nature, it was probably both.
The only way this usually works in software is to JFDI (Just Freakin' Do It). The thing that Jefferson did is he did the _work_ , not just present the idea. In software, the "work" is running prototype code.

Even then if you have a "vision" person, they may not be 100% sold if they don't like the design, but know your audience a bit you can be prepared for it.

I understand what you are saying, because very early on in my career I was one of those people that would present ideas, even architectures and expect people to get on board....now I realize that you have to sometimes drag them and in software, you drag by showing them something working and how it is possible...give them something to tweak and criticize that is real working code, not drawings on a page.

"The only way this usually works in software is to JFDI (Just Freakin' Do It)."

Aka "rough consensus and running code" - as used by David Clark and the IETF: http://www.ietf.org/tao.html#anchor3

If you've got an idea - _and_ a plan _and_ a working implementation of that plan, you'll get taken much more seriously that the people who're trying to come up with ideas on the spot (even though occasionally their ideas might genuinely be better than yours).

>"The thing that Jefferson did is he did the _work_"

Jefferson didn't do it alone - his team slaved away for him.

Literally.

University of Virginia's Apology for using slave labor in the execution of Jefferson's plan [2007/4/27].

http://www.virginia.edu/uvatoday/newsRelease.php?id=1933