It’s terrifying when your best developer decides they want to move on. You rely on them so much that you don’t even think about what they’re responsible for half the time – they just get it done. But, that leaves you with a big hole to fill, both in terms of knowledge and time. Wouldn’t it be great if you could make your whole development team as good as your star player?

It’s a horrible feeling when your best developer slides their notice across the desk, or even worse in the modern age, when you receive a resignation email. The anxiety of how your team will handle ongoing work and larger projects builds pretty quickly the moment you know you’re losing a great resource. Unfortunately, when they do go, it’s also likely to shine a light on things that aren’t quite up to scratch.

A Big Hit

Let’s say you’ve got a team of 12 and within that group, you’ve got a long-standing developer who knows everything. That could include what extensions you use, where the database files are, QBD processes, how to put something into production – you know the person we’re talking about. Your star player. The person who when they call in sick makes you dread that day. Well now, they’re gone. Maybe to find a new role, for personal reasons, or because their contract’s up. Whatever the reason, it’s not going to be the same without them.

A few days after they leave, a junior developer is going to ask how to do something. There’ll be murmurs in the team, but no one is really sure. You go to check the documentation. It’s at best out of date. Turns out that, while your star player was so busy doing everything else, they never really documented what they were working on, or how people should carry out tasks – they just made it happen.

What would you do if you didn’t have server keys, licence keys, and logins tomorrow? This is a genuine scenario we have seen with multiple clients.

Without properly documented processes and project logs, development is a nightmare. Because you’re so busy doing the work, you forget what the impact of just ‘getting on with it’ can actually have on your team – and ultimately, on your business. As BI manager, it’s your responsibility, but your best dev was so good you thought you didn’t have to worry about it.

So what do you do?

The Rallying Tool

When you have a tool like PlatformManager everything is already set up for you. It takes away the risks associated with developers leaving – it outlines the rules of engagement; the entire process for testing, development, and deployment. And everyone can use it.

When you find out your best developer is leaving, you’re obviously going to have to replace them. But, if the fact they are going leaves you worried about processes, access, security, or anything development related, then it’s time to re-evaluate what you should be investing in. Tools that help developers share knowledge, follow processes, and speed up development are a great place to start. Rather than having one great developer, why not make your whole team better?

PlatformManager is a way of maturing your development processes, moving away from people shouldering the burdens of the day-to-day, and instead relying on a purpose-built tool to do that job. No more playing catch-up when someone leaves. No more panic. With PlatformManager, you just have streamlined BI development.

Need to fill the hole left behind by a developer who handles everything? Start by talking to PlatformManager.