3 ms·
Organizational Theory 101 is that there are three levers of power in an organization - relationship, expert, and role in that order. Getting anything done in a
by scarface74 7y ago
Organizational Theory 101 is that there are three levers of power in an organization - relationship, expert, and role in that order.
Getting anything done in an organization means building the right relationships first. Building the right relationships is the difference between being able to ask the infrastructure guys to create some VMs for you in Slack, they do it immediately and then ask you to fill out a ticket and having to fill out the ticket and wait for two weeks.
The second part of that is “pre-wiring” - convincing one of two people of your idea, taking their objections into account and improving on your idea until you can make a convincing argument to your manager. It’s a lot easier to be in a technical meeting where you already have your coworkers buy in than one where you are fighting on multiple fronts.
Once you have the relationships, you have to convince people that you know what you’re doing by having a few successful projects under your belt. It’s a lot easier to convince people once you have a track record of success.
Role power in my experience is the least effective - especially in the software industry. If you don’t have the other two, it’s way too easy for people who report to you to jump ship.
Honestly, in today’s market for software developers. If you live in any major metropolitan area in the US (I’m in Atlanta) and you keep yourself marketable jobs are a dime a dozen. The last thing I worry about is long term unemployment - this has been true for the last two decades.
- xfitm3 7y agoThe problem is finding another job that pays as well - I'm low on the totem pole but earn 4x the average salary for my expertise.
- scarface74 7y agoWhat I’m about to say is meant to be positive not negative. Theoretically, what you get paid is based on what it would take to find someone with your expertise and the additional value you bring to the company based on the relationships you built (it’s a lot easier to get something done when you have the relationships) and based on your knowledge about the business. If they are willing to pay you 4x the average salary, they must respect your expertise enough to listen to you. I can’t help but think you are either underestimating the influence you actually have in your company, your market value or both. If the company you are working for doesn’t value your opinion or insights, why would they be paying you 4x your market average?
- xfitm3 7y ago> If the company you are working for doesn’t value your opinion or insights, why would they be paying you 4x your market average? I should clarify. My salary is not unique. Everyone who is lucky enough to work there is well paid – unrelated to the stock market. It is privately owned. I have been there for almost a decade and I have some big successes under my belt, but not enough to justify a similar salary at other companies.
- scarface74 7y agoAgain, this is meant to be a positive. It’s almost impossible for me to believe that you have been at a company for ten years, have established a reputation, have big successes and you are seen as just “a cog”. I still think you are underestimating yourself and how much the company values you - especially a private company. Any company that is willing to pay far above market rates must value their employees, if not, they would have made cost cutting moves a long time ago. Also, just out of curiosity, what skillset do you think you’re lacking after 10 years?
- xfitm3 7y agoJust a discussion - nothing is being taken personally. I'm manic. I can't produce reliably, and that means I can't present reliably. As I observe the industry grow I find communication is more and more the center of the job. Tech skills are table stakes. I need to prepare for big meetings days in advance with opportunity cost, etc.
- scarface74 7y agoHopefully someone else will chime in with better suggestions, but I do understand. By nature, I have almost no emotional intelligence and it held me back for the first 10 years of my career and so stayed at one company for almost a decade when I left after year 9, I was only making $7K more than year 2. But I wasn’t comfortable leaving because my skillset had atrophied and I knew my interpersonal skills sucked and I would probably be fired from anywhere else. Over the next ten years and five jobs, I had to be very introspective and think about how I could do things differently. It took about seven years for me to get caught up with where I should be. While I have learned how to build relationships and navigate through corporate America, I found at my last job where I was the dev lead, that I still sucked at communicating with non technical and differently technical (IT infrastructure) people and wasn’t great with management. My only suggestion is reading the “48 Laws of Power” and ignore one or two of the less than ethical “laws” and listen to the Manager Tools/Career Tools podcast. They have podcasts that date back to 2005. The easiest way to navigate it is to download the Manager Tools app and go to the “Hall of Fame” section and then go to “Communication”. There are podcasts about “Prewiring a meeting”, the levers of power, and dealing with different personality types (DISC).
- hnick 7y ago> Getting anything done in an organization means building the right relationships first. Building the right relationships is the difference between being able to ask the infrastructure guys to create some VMs for you in Slack, they do it immediately and then ask you to fill out a ticket and having to fill out the ticket and wait for two weeks. Funny, they keep rolling out more 'advanced' helpdesk software where I work to avoid building social connections. In the old days I got to know people, now there's no chance of that. There isn't even a name on the emails. I think in the long run this really hurts the company. It also makes it much easier to be upset at the 'stupid help desk people' rather than individuals you know might just be having a bad day.
- scarface74 7y agoI actually left my last company partially for that reason. I was the dev lead, responsible for getting a green field project out and the company I was working for merged with another company and they instituted so many processes around the IT processes I couldn’t get anything done. We also migrated to AWS and they treated AWS like an expensive colo. Every thing had to be approved, we could only get VMs and no access to any other functionality and I couldn’t even get a separate dev account, isolated from production so we could experiment and work. As soon as I got phase 1 completed of the project, I found another job as “just” a senior software engineer and the day I came in, immediately got full access to everything and admin credentials to our AWS accounts. Before the IT gatekeepers respond about how crazy it is to give software engineers unfettered access to the production infrastructure, I was brought in partially for my AWS architectural experience (adult supervision), I negotiated not to be a team lead and I switch back and forth between development and cloud infrastructure depending on the day of the week.