Tuesday, 2 March, 2021 UTC
Summary
Your boss is about to do something stupid.
You know the routine. They make a terrible decision that ends up costing the company money. When they realize they’ve dug themselves into a deep hole, they’re upset, blaming you or your co-workers.
“Why didn’t anyone tell me?”
It’s a catch-22 many developers find themselves in on a routine basis. Their boss makes an unrealistic request then reacts negatively when you’re unable to deliver the results they want.
What’s wrong with them?
Your boss needs you to change their mind
Good decision-making is incredibly difficult.
It doesn’t matter what your boss has on their plate, their job is a difficult one. At any given time, they’re spinning and balancing multiple plates:
- They’re working with legal to address contract or project-level disputes.
- They need HR’s help to deal with the developer on your team that’s lazy and killing morale.
- Directors and executives are hammering, demanding that they produce results they know are impossible.
- They’ve been pushed into a management role they’re unqualified for and disinterested in.
- The majority of their developers are fighting each other for the same opportunities.
- You don’t know it, but their budget was slashed by half; executives are demanding more work for less.
There’s a very good chance your manager is discouraged, overwhelmed, and backed into a corner. Many managers don’t have the knowledge, resources, or support they need to do their jobs well.
This isn’t my problem.
Ah, but it is. Your boss is looking for an employee who’s willing to help carry their burdens for them.
So what?
When you gain the ability to change your boss’s mind, you also provide your manager, employer, and yourself with the ability to:
- avoid serious problems that eventually lead to layoffs or firings (such as projects that are inefficient, overbudget, bloated, or filled with poor quality code)
- generate more revenue for your company (important when you’re looking for a raise)
- find cost-effective, more efficient ways to solve complex problems
- properly evaluate opportunities as they appear — meaning you’re aware of upcoming opportunities before the rest of your co-workers or teammates
- create a work environment where you’re surrounded by allies who are willing to go out of their way to help you.
But it’s a risk.
If you go out of your way to help your boss or manager, and you do it wrong, it could blow up in your face. Besides, you’re just a developer. What are you supposed to do to help your manager?
Why go to the trouble of changing your boss’s mind?
This is how elite developers are made.
When I use the term “elite”, I’m referring to the top one to ten percent of developers in a given industry or profession. These developers receive a string of benefits other developers don’t:
- they’re paid far more than most developers
- they win coveted jobs and promotions in the face of intense competition
- customers and employers wait/fight for the chance to work with them
- they win promotions before they’re publicly available
- they receive special perks and rewards most developers are unable to get
- co-workers, publishers, and thought leaders seek out their knowledge, attracting more rewards
- they can wield a greater degree of control
- customers and employers trust them at the start of the relationship
- customers and employers are willing to pay for their equipment, growth, and development
So what do these elite developers know that most developers don’t?
It’s not about the work.
What does that mean? Elite developers are focused on very different things:
- The value they provide
- The people they serve
Most developers focus on the work, getting better at their craft, increasing their knowledge, producing higher quality work.
Elite developers do this too.
But they understand that being great (not just good) at your job is an entry-level requirement. This is the part most developers miss; they naturally assume that being a great developer is all it takes to improve your career prospects.
It’s not enough.
Elite developers use the value formula to create huge amounts of benefits for their managers.
Do you know it?
It’s a formula created by Peter Thiel, founder of PayPal. This is the formula that elite, top performers use in every industry:
- Create X dollars of value.
- Capture Y percent of X.
Can you see what’s happening?
The more value these developers create for their manager and their employers, the more value they can earn and extract for themselves.
What kind of value can developers demonstrate?
You can:
- Take the initiative by solving recurring or longstanding team problems in your free time.
- Demonstrate the negative impact live code or development processes have on the organization.
- Take on more than is necessary, working to earn their trust and become an indispensable employee over time.
- Consistently exceed key performance indicators and metrics in your organization (such as technical debt, lines of code, ability to ship code, meeting deadlines, etc.). This will vary by organization.
- Create tools, documentation, resources, or libraries that reduce development time across the organization.
- Show clients how your code solves the Five Q’s of strategy.
Not detailed enough?
Think of it this way. There are two kinds of results your manager wants from you: conventional and transformative results. Here’s a quick recap of my previous post.
- Conventional results: being great at your job, going above and beyond, and performing well in general. If you’re a JavaScript developer, your code is pristine, and you’re helpful, productive, etc.
- Transformative results: these are results that make things better for your company, the industry, or customers as a whole. It can be as simple as shared knowledge or as detailed as software that transforms the industry.
Here’s why these results matter. Conventional results build trust. It’s easy for your boss to take a risk on you, to spend more on you when they trust you.
What’s in it for you? Quite a lot, actually.
If you can change your boss’s mind reliably and in a trustworthy fashion, you can write your own ticket (career-wise). These aren’t lofty or unrealistic claims. Elite developers achieve results like these regularly.
What you’ll need to change your boss’s mind
You’ll need two things: a good working relationship and a framework.
When it comes to changing your boss’s mind, you’ll need to know the what, when, and how. Here’s a concise breakdown of each.
Change your boss’s mind when:
- their decision hurts you, the company, or themself
- they’re about to make a decision that will cost the company money, slow a project down, or increase development time unnecessarily
- their decision will make customers or clients unhappy and far more likely to take their business elsewhere
- their decision will make their colleagues and co-workers unhappy or turn others against them
Do you see the pattern?
Don’t attempt to change their mind if:
- the change benefits you exclusively or primarily
- it makes things worse for your boss (obviously)
- it goes against instructions from those above your boss
- the change damages or destroys relationships between managers, co-workers, or customers
Do attempt to change their mind if:
- you’re reasonably confident you can improve the situation for your boss, co-workers, team, or the organization
- your boss is missing crucial information that’s necessary or essential
- they’re asking you for feedback or have a proven open-door policy that solicits feedback
- you’ve developed the trust you need to act on your co-workers’ behalf
See the difference?
This tactic — changing your boss’s mind — is powerful. It’s a career-ender if this strategy is misused or abused. Following the framework listed above insulates you against any blowback that would cost you your job. At this point, the most obvious question then is, how?
Continue reading
How to Change Your Boss’s Mind Without Losing Your Job
on SitePoint.