Transitioning from Engineering to Management – Part 3 “Now and Beyond”

I am no longer a manager. I moved back to being an individual contributor for Amazon Web Services. A Senior Technical Account Manager in the Enterprise Support organisation working with customers across Scotland, the UK and the World. It’s been over three years since I posted the first blog post in this series and at the time I had anticipated the third post being more focused on developing as a leader and the challenges of staying in front of technical developments whilst also being a good manager. Instead I took an opportunity to work for AWS a leader in cloud computing and an organisation I’ve hoped to work at for a long time.

So this post is going to be about my decision making process to move from management at a small/medium sized business punching above its weight to individual contributor at one of the biggest tech companies in the world. The decision was not terribly difficult in the end.

It is fair to say that my time at brightsolid was formative. I joined the organisation as an IT Engineer working on internal IT services and providing support to staff at the company. At the time this was around 300 people across several sites. By the time I decided to move on from brightsolid I had been a Systems Engineer, Service Desk Manager, and latterly working as Head of Technology developing the Hybrid Cloud vision of the product team as well as a number of other transformative initiatives for a company that had divested and was now around 50 employees but focused on a specific set of service offerings as an MSP in Scotland. I learned a lot over the years, about technology, about leadership, about the nature of commercial relationships and about business in general. Not all of it was comfortable or easy to learn, and some of it was associated with behaviours and attributes of leaders that were not fit to be in the positions they were in. Learning how not to do things, I guess, is sometimes as important as learning how to do them well.

Given the above it would have been easy for me to stay where I was familiar and comfortable and feel like I’m delivering something more impactful to a smaller business than AWS. But as you’ll perhaps remember from the first post in this series, I always try to push myself out of my comfort zone and move my career forward. By the end, I felt I had outgrown brightsolid. And so despite the fact I felt deeply passionate about brightsolid and the work I was doing there, I couldn’t pass up the opportunity to learn from the amazing smart folks that work for AWS.

Jumping in to a role at AWS is like nothing I’ve ever experienced, the phrase “sipping from the firehose” came up a lot in my initial onboarding and it’s not wrong. You have to learn a lot and quickly. But you’re not alone, you have a lot of people in the same position or have been in the same position and are happy to help. I’ve loved every day of the past 18 months at AWS and can’t wait to see where I can take this.

The conclusion to this series is short, the message of this post is simply this, be sure you know when you have outgrown your role and your place of work, find new opportunities to push yourself and grab them with both hands.

Transitioning from Engineering to Management – Part 2 “Learnings”

This is part two of the three-part series reflecting on my decision to move away from direct engineering into management. You can find part one here.

Part 2.

In the more than two years since taking on the role of Service Desk Manager, I have learned a lot about myself. My style of management and who I want to be as a leader, as well as gaining a deep insight into the world of the customers I worked with. It’s been a journey with ups and downs but overall has been a hugely positive experience.

I want to share some of the most important things I’ve learned in that time, the things that have shaped decisions I’ve made and how I conduct myself at work. This is a list, I’m sorry about that.

1. Bring Solutions

Starting out on the Service  Desk there were various challenges, gripes and issues that were coming at me from senior management, from the team itself and from the other teams within the business. This was a bit overwhelming and it is easy to get sucked into the moaning and complaining about the problems, then instead of solving the problems, you perpetuate them. Always endeavouring to see the problem at hand objectively allows you to come up with solutions rather than perpetuating the problem. It’s almost always exclusively better to bring a solution to your team or colleagues in other teams than it is to perpetuate. Even if ultimately your solution is wrong or doesn’t get implemented you’re trying to make things better and people will respect that.

It’s not easy though, especially if you care about your work. You get emotionally invested and it can be hard to remove that emotion once it’s there. The thing that works for me in these cases is to attempt to gain an objective viewpoint from someone else. It doesn’t always work but it does more often than not.

2. It’s not always a technology problem

As an engineer, I was always naturally inclined toward finding technology solutions to problems. While I could academically agree that not all problems can be solved by technology it took until I was leading a team and working on higher level business problems that this became reality to me. A truly successful business is composed of three elements. People, Process and Technology. In that order. 

This is not a grand revelation, I’m sure most people know that. But it’s easy to forget and even easier to get the order wrong. You absolutely have to have the right people around you, governed by the right processes or the technology is waste of time. You can have the best tool in the world but if your processes are inefficient and clunky then the tool can’t stop that from being true. If the people you have are ineffective then if you have the best tool in the world with the best processes it still doesn’t stop the ineffectiveness. Always start with people and process, then worry about the technology. 

3. Aptitude and Attitude

Speaking of people, the way to find the best people is not to focus on what they already know, focus on their potential to learn and their desire to learn. This is not a new lesson to me but one that was crystalised during my time as the Service Desk Manager and beyond. If the person before you has the aptitude to learn what you need them to learn and the attitude that shows they want to learn then there’s little that will stop them from developing into what you need them to be.

In the MSP business, and in IT in general, you are never going to be an expert in everything. there’s too much to know. Instead, you need to be an expert in thinking on your feet, researching problems to resolution and learning as you go. 

4. Listen!

This one seems obvious. In my experience, though it’s one of the skills a leader needs the most and yet many leaders I’ve worked with have been very bad at it. I don’t just mean using your ears either, I mean actively listening to what other people have to say, taking it in, ensuring you have an accurate understanding of what they have to say and then integrate that feedback into any decisions you need to make.

It’s not always easy to listen like that, it’s tiring, and takes time. But it is assured to produce the best outcomes. People feel engaged and valued, whether their say has made it into a final decision or not because they will feel heard. 

5. If you ask for feedback, do something with it!

Following on from listening, if you send out a company survey or ask a team for feedback via any mechanism, you absolutely must do something with the responses. 

People will stop giving feedback to you if you don’t ever act on what you’re being told. You don’t ever want people to stop giving feedback. You don’t always have to do the things being asked in feedback but it’s important to respond to the feedback with rationale as to why that is the case. 

6. Say what you mean, mean what you say!

Now this one is stolen directly from my Insights profile. I lead with Blue (factual, data driven) and Red (directorial, stubborn) energies and this struck a huge chord with me when I read my profile for the first time.

I cannot abide people saying one thing to you then acting completely differently to how they had stated. I get that people don’t always control this, I get that they don’t always mean to stray from what they said and so I can forgive it. But if you routinely say things that you don’t mean or say things without conviction then we are going to disagree at some point. 

For me it’s about being reputable amongst my colleagues, it’s about them knowing that if I say something will be done it will be done. It’s about being trustworthy.

7. The Art of Compromise

As a leader, a great deal of what you do is actually about finding the middle ground between two opposing views, alternative solutions or whatever. Sometimes it’s harder than others to find that middle ground but it’s something that you must be able to do. See things from the other side, identify the compromise and get buy-in on that basis.

More often than not you don’t have to compromise your view or solution that much to find the compromise as there’s typically an overlap, simply because the chances are you are working towards a common goal.


I put a lot of time considering what sort of leader I want to be versus what sort of leader I am. Leading is something you should never just assume you are good at, it’s something you need to work on, a lot.

Transitioning from Engineering to Management – Part 1 “The Decision”

As I’ve recently changed role within the past two months I have decided to articulate my reflections on a decision I made over 2 years ago regarding the transition away from direct engineering roles, this is part one in a 3 part series discussing my decision to make the move, the things I’ve learned along the way and what it has ultimately led me to.

Part 1.

In the summer of 2015, I’d made the decision to start the transition from IT engineering roles that I had been in for ten years previous to more leadership focused roles.

As a stereotypical logical technical person, I spent a long time thinking about the pros and cons of doing this. Here are a few that I came up with during that process:


  • Opportunity to lead and develop others in their careers
  • Opportunity to develop myself as a leader
  • New challenges and diversification of skills
  • Opportunity to contribute at a higher level to the business
  • Raising my profile within the business


  • Time available for technical work will be significantly reduced
  • The number of meetings will be significantly increased
  • Perceptions may be that I’m “past it”

It’s worth noting that these lists are not exhaustive as I’m reflecting upon this I am recalling what I considered at the time and in discussions with friends and family and so no tangible list like this ever existed while I was making the decision is does roughly reflect the pros and cons I had considered.

In the end, I decided that the pros outweighed the cons by a significant margin and so in November 2015 I officially took on the role of Service Desk Manager at brightsolid. This list of pros and cons were not the only deciding factors. I had been in the engineering role I was in for just over 3 years at that point which is a personal limit for when I start to feel like I’m stagnating career-wise.

I feel a pretty strong affinity for the phrase that Pop used to say to Luke Cage. “Always Forward. Forward, Always.” This pretty much sums up how I like to progress my career if it’s a step backwards or sideways it doesn’t feel like forward so taking the leap into leadership satisfied this need.

I need to feel that I am being challenged as that’s ultimately what leads to progression. If you’re never out of your comfort zone you’re not learning and not improving.

Making a decision like this is something that most engineers will face in their careers in IT. To stay an engineer usually means to become an expert or consultant in a specific field, to move to management and leadership usually means to let go of a lot of the hands-on engineering. Ultimately it’s a very personal choice and will always come down to each individual’s personal values.

To satisfy my own personal value, to push myself forward, it was really an easy decision. Hopefully when it comes time for you to decide it will be equally as easy but if not then maybe this article will help in some way.

Mini-ITX Gaming Rig – Part 2

Continuing on from my last post then, all parts had arrived by Tuesday therefore that evening was build time. All in the build took about four hours, most of that time spent trying out the Corsair H60 in various mount points to see which would be the best fit. It turns out the first one, with the radiator and fan mounted on the rear is the best.

bitfenix Prodigy

Despite my concerns about the AX750 fitting the case it seems fine to me. So long as you’re careful with your cable routing you’ll do little damage to the cables. You do need to push pretty hard to get it in there though as the sleeving on the cables makes the whole thing less pliable. A lot of modding forums show people using the individually sleeved cables you can buy separately but I didn’t particularly want to spend an extra £50 for the pleasure.

AX750 installed
AX750 installed

The build went as expected once I had decided where I was to put the radiator. I did have an OCZ Vertex 2 60GB SSD in my old machine that I intended to use for the system drive until I could upgrade to a Crucial M4 but it turns out that drive is dead. Unfortunately it’s also out of warranty now so in the bin it went.

Unfortunately the only other drive I had was the 500GB Seagate Momentus XT Hybrid which has been gathering dust since I RMA’d it last year. So for now it’s running with a 120GB partition which I’ll move to the new SSD in a few weeks.

Windows 8 installed quickly but I got the system stuck slightly by installing the latest Nvidia driver before Windows had finished properly installing the WDDM drivers which resulted in a screen just flashing on and off repeatedly. Booting in to Windows 8 recovery and “refreshing” the install fixed that, and it was finally done.


System Details
System Details

The WEI score is so low because of the hybrid. Default settings for RAM and CPU score at 8.4 and the GTX 460 scores at 7.3. Ultimately these numbers are fairly meaningless but they are a handy quick benchmark.

On Wednesday I decided to do some overclocking, for now just to test the H60’s capabilities. First impressions are that it’s excellent for such a small radiator, though the overclocks I tried were not exactly extreme.

Using an application called CoreTemp I monitored the temps inside the CPU while trying several overclock speeds. In a default configuration the i7 3770K idles somewhere between 20°C and 30°C, my first instinct was that this wasn’t great but Ivy Bridge runs a little hotter than Sandy Bridge. Stressing the CPU using Prime85 shows the quality of the H60 (remember this is a default configuration in a small form factor using the lowest end of the Corair H series of liquid coolers), temps max out at about 55°C.

The first overclock was gentle, pushing the CPU to 4.1GHz, at 100% load the temps were 58-59°C with occasional hits up to 62/63°C still well within tolerances. So time to up it some more, 4.4GHz at 100% load and the temps remained very close to the 4.1GHz overclock, excellent performance from the cooler.

Before resetting back to default, which I plan to run the system at for a little while before applying an overclock, I decided to use the software supplied by Asus and apply the “Extreme” overclocking to see what it would do. It put the CPU up to 4.6GHz in a heartbeat, it tested as stable so I left it at that and stressed it. 100% load was hitting 70°C +/- 4°C again an excellent performance from the H60.

I’m pretty happy with the build. Still some improvements to make though before I’m completely happy. As is always the way with these types of projects!

Mini-ITX Gaming Rig – Part 1

My main desktop computer died some time last year (in fact so long ago I can’t actually remember when!). Since then I’ve been relying on my laptop which has done admirably considering its age – coming up for four years. Obviously then there was no impetus for me to replace the desktop, until a colleague at work and I started discussing our ideal builds. Well builds that we can afford that is.

Where my colleagues build was based on a Full Tower case (the CM Storm Trooper) I was opting for a much smaller but hopefully equally as powerful a system. Here’s my final kit list.

  • BitFenix Prodigy
  • Asus P8Z77-I Deluxe
  • Intel i7 3770K
  • Corsair H60 Liquid Cooling Kit
  • Corsair Vengeance 16GB (2 x 8GB) DDR3 1600MHz CL10 LP
  • Gigabyte GTX 460*
  • 60GB OCZ Vertex 2*
  • 500GB Seagate Momentus XT
  • Corsair AX750 PSU

* These items were rescued from my previous system, I plan to upgrade the SSD to a Crucial M4 and the Graphics Card to a GTX 680

I have most of the parts for the build but I’m still waiting on the case and the liquid cooling kit. In the mean time I’ve been successfully freaking myself out by reading about the failure rates of the various components I’ve purchased. To be honest the only one that is still on my mind is the Power Supply. I take solace in the statistic I read yesterday that Corsair ship in the region of 150,000 power supplies per month meaning the number of failures discussed online is more likely just a reflection on the sheer number of units sold rather than something fundamentally wrong with the hardware.

How to reset web console password of a LifeSize Video Conference unit

Searching for this online to resolve a problem with one of these units proved fruitless so I decided to throw this up here for reference and perhaps it will help someone else out in need. The unit in question is a LifeSize Team MP.

  1. SSH to IP or hostname of the unit
  2. Login as

    using password

  3. Reset the password using the command
    set admin password 12345

    The password can be anything of 0-9 * and # and is truncated if greater than 16 characters

Full reference for the command line interface can be found here on the LifeSize website.

Web Security

With almost six months since my last post you may have been fooled in to thinking this blog had died a death. The truth is I’ve just been really busy at work and still am but I had to post about this subject as its really starting to get on my nerves.

Web security, or rather your informations security on the web, is something everyone should be concerned with at all times and yet the majority of my friends not in the tech industry couldn’t give a crap. I’ve witnessed passwords shared across multiple services, passwords written down with the web address and username, passwords as simple as password. It’s all very frustrating when trying to explain why these things are bad to these friends as they have no idea of the scale of the threat.

Up until recently the threat was not actually that widespread, sites being compromised as little as two years ago were usually small communities that impacted relatively small numbers of users. Then LulzSec and Anonymous came along and ostensibly attacked sites they were protesting against but also raising awareness of tools that can be used to attack websites and networks.

The chaos that has ensued was easy to largely ignore until consumer networks starting getting hit.

Some examples:

  • Playstation Network is brought down, millions of users personal details are stolen.
  • Gawker Media network of websites is attacked, I discover that two of my email addresses were used in accounts I did not sign up for
  • Facebook account lists and passwords are published
  • my web host DreamHost has its account directory service compromised meaning they have to change passwords on every FTP account
  • This week alone LinkedIn has 6.5 million accounts published online and now there are reports of being compromised

What is at risk then?

Name, Address, Job History, Email Address, Password, Credit card information, date of birth. On their own most of these things aren’t a big deal (credit card info is a big deal!) combine them and you have everything you’d need to steal an identity. If you get in to someone’s primary mailbox you have their life!

When these attacks happen the sites tell you to change your password and reiterate that you should use different passwords on different web sites. It’s not enough. It has been the standard advice for as long as I can remember on the web and has been ignored equally as long. The password as we know it is not secure.

What are the alternatives though? Some sites have multi-factor authentication, usually this means a small keyring sized device is assigned to your account, using pre-defined algorithms on the device and on the authentication server you enter the verification code on the devices screen as well as your password to log in. This is something more recently being offloaded to smartphones making it vastly more accessible to your average user. It means to login you need to remember something (your password) and have something (the smartphone or token device). It does increase security but at the cost of convenience.

Other sites rely on the authentication of OAuth or OpenID vendors like Google, Yahoo, Facebook or Twitter. Not ideal either, these vendors may be better protected from threats but they are constant targets!

We need to rethink our approach to web security as an industry or these attacks will only increase in frequency and severity, my advice is to enable multi-factor authentication on every site you use that offers it, keep all your passwords different (try the advice of this xkcd comic to help you pick memorable passwords), change them frequently and maybe one day there will be a method of authentication that we can trust again.

Office 15

Office 15, the next iteration of Office, has been made available to selected partners via the Technical Preview program.

That in itself is fairly unremarkable (for more info read the official announcement on the Office Blog) but there is something in the blog that seems to have gone widely un-noticed by most places.

“With Office 15, for the first time ever, we will simultaneously update our cloud services, servers, and mobile and PC clients for Office, Office 365, Exchange, SharePoint, Lync, Project, and Visio.”

This means that presumably this year (though no evidence of a release date anywhere) there will be an update to their entire Office product line and their supporting server applications, so Exchange, SharePoint, Lync Servers 2012? I’m not sure if this is brave, clever or really stupid. Time will tell I suppose. In the mean time I’m pretty keen to get my hands on the product, here’s hoping the Preview is open to a wider audience soon!

Planning 30th birthday celebrations

In September I’ll be 30. It’s a milestone for most people and so myself and a group of seven friends (four of who are also 30 this year) have decided that to celebrate we shall take a trip in October – it falls pretty much in the middle of all our birthdays, and a number of them are Teachers.

After quite literally months of debate and a vote (using proportional representation to tally the winner – everyone had to choose three locations) we decided on Barcelona.

Flights are booked, and I’m really looking forward to it now.

Cisco AnyConnect, OS X and Firefox

When I started work at brightsolid one of the tasks given (or rather one of the tasks I gave myself) was to get the Cisco AnyConnect client working on OS X.

The symptoms are not very helpful in diagnosing the issue, the error you get will be something like “posture assessment failed”. Fortunately Cisco provide an excellent logging tool known as DART (Diagnostic and Reporting Tool). Looking through the DART bundle it was pretty clear that the firewall was rejecting the connection attempt due to a missing user certificate.

On Windows you just need a certificate (issued by a CA that the firewall trusts) installed to the users Personal certificate store.

On OS X adding the certificate to the keychain made no difference. I’m still not 100% sure why but I suspect Apple changed the way certificates worked between major releases and Cisco never got around to fixing it. I do plan to talk to Cisco about this issue at some point so I will post an answer once I have one.

The workaround, which I discovered by looking through the DART logs, was to add the user certificate to the certificate store in Firefox.

Further testing has revealed that it only works for Firefox 3.X anything newer and AnyConnect fails in the same way.

Currently then OS X users with AnyConnect version 2 or newer will need Firefox 3 installed too.

If anyone out there has any further information about this I’d love to learn more or get a permanent fix that doesn’t rely on old browsers!

EDIT: I’ve found that this may be a policy setting on the firewall, despite having been assured this has been checked you can force OSX clients to not check the Keychain for certificates. There may be a way to override this locally so I’ll be trying that first then will look at the firewall config again.