Chapter 1: Skills Acquisition – The Foundation of Success

Why I wrote this

I am publishing this chapter online not simply to sell more books, but to pass the message more widely. The people I most want to reach — STEM engineers, technical specialists, scientists, managers and the leaders who develop them — benefit far more from reviewing their own careers honestly than from another marketing message, and this material is intended to help them implement better professional-development practice whether or not they ever buy anything.

There is a lesson about career progression that I wish somebody had explained to me properly when I was in my twenties. Whilst I understood that qualifications mattered, technical competence mattered, hard work mattered and being prepared to take responsibility mattered, I did not yet understand that a successful career also requires deliberate architecture. Careers do not simply develop because we become older, accumulate another five years of experience and continue performing our present role well; they develop because we consciously add capabilities, expose ourselves to increasingly difficult problems, learn from people who know things that we do not, and periodically make deliberate decisions about what we need to become capable of doing next.

I have subsequently worked with thousands of engineers, technical specialists, scientists, managers and leaders, and one of the recurring patterns I have observed is that very capable people can reach a point where their career progression slows — not because they have stopped working hard or become less intelligent, but because the capability that made them successful at one stage of their career is no longer sufficient for the next. An excellent engineer can continue becoming a better engineer for decades, but if the ambition is eventually to become a Chief Engineer, Engineering Director or senior business leader, then there comes a point where technical expertise must be supplemented by commercial judgement, organisational awareness, leadership, communication, financial understanding and the ability to make decisions through other people rather than simply producing brilliant work yourself.

This was one of the principal reasons I wrote The Seven Highly Effective Hacks for Career Progression, and why I made Skills Acquisition – The Foundation of Success the first substantive chapter. I wanted to share knowledge that would have been extremely useful to me much earlier in my career, and particularly the idea that professional development should not be left to the annual appraisal, the corporate training catalogue or the accidental opportunities that happen to appear.

For experienced professionals, and particularly for mid-career STEM professionals, senior engineers, engineering managers and technical leaders, this becomes a strategic issue rather than merely a training issue. The relevant question is not how many courses you have completed, nor how many certificates you can add to LinkedIn, but whether the combination of capabilities you are building increases the scale, complexity and commercial importance of the problems that an organisation can trust you to solve.

A useful distinction exists between doing your present job better and developing yourself for the career that follows it. They overlap, but they are not the same activity, and some of the most professionally dangerous periods occur when somebody becomes so effective, comfortable and respected in their existing role that they stop questioning whether the role is still developing them.

Skills acquisition is not simply a training problem; it is a career strategy problem.

What does skills acquisition really mean for an experienced professional?

At its simplest, skills acquisition means developing knowledge, competencies and behaviours that increase what you are capable of doing — but that definition becomes much more important when you attach it to a destination. A professional development programme with no clear career direction can produce activity without much career value, because there is always another qualification, software package, management theory or technical subject available to study, and being able to learn something does not automatically mean that it deserves your time.

The more strategic question is what the skill enables. Does it increase your technical authority, broaden the type of role you can credibly pursue, allow you to lead a larger organisation, improve your commercial judgement, increase your market value, make you more adaptable or remove a specific limitation that is preventing career progression? If you cannot answer that question, it is worth challenging why you are investing in the skill at all.

In 1993, early in my career, I had already worked on the layout of a mid-engined sports car, including the fuel tank and engine-compartment area of what became the MGF programme, and then moved into Project Oden, within the development lineage that ultimately led towards Freelander 1. I began working with CADDS 4X, which was extremely slow and methodical by comparison with what followed, and then became one of the first handful of people in the organisation trained on ICEM Surf.

Something immediately clicked. Steve Corbett, Phil Johnson and I were all broadly the same age, and the three of us learnt the system extraordinarily quickly. My recollection is that during an intense three-to-six-month period we created roughly 60 per cent of the interior and exterior surface work across the three-door and five-door derivatives, representing somewhere around 60 components, whilst the rest of a team of approximately 37 people refined, improved, secondary-released and picked up other areas. For that relatively brief window, I would argue that the three of us were amongst the most capable ICEM Surf users in the company and potentially much further afield, because the technology was itself new and very few people had yet accumulated meaningful experience with it.

The important career lesson was what happened next. Within months I was moving away from the screen and into programme leadership, ultimately managing a team of around 40 people. I could have remained the ICEM Surf expert and continued deepening that specialism, but I began to recognise that something potentially much larger was available to me.

When technical excellence stops being enough

Technical excellence stops being enough at the point where the organisation begins requiring breadth faster than it requires further depth. I remember looking at the people around me and thinking about what would happen over the following twelve months. They were intelligent people, they were learning the same technology and inevitably many of them would become increasingly competent at ICEM Surf, which meant that the unusual technical advantage I temporarily possessed would begin to narrow. I could continue competing to remain the person who was slightly faster or slightly better on the system, or I could develop an entirely different capability.

The thought I had was fairly uncomplicated: if I could lead 40 people, learn from a group that collectively represented well over a thousand years of engineering experience, and take responsibility for tooling releases worth around £150 million, why would I restrict my development to being the best person operating one particular piece of software? That was probably the point at which I made one of the most important career decisions of my life. I decided that I wanted to lead teams, but I also decided that they would be technical teams, because I did not want leadership to require abandoning the engineering credibility that had created the opportunity in the first place.

Moving into leadership does not require becoming less technical. It requires recognising that technical expertise becomes the foundation upon which another set of capabilities has to be built. At one level of an organisation you may create value principally through what you personally know and personally produce; at another level you create value by making better decisions, coordinating specialists, developing people, resolving conflict, allocating resources and creating the environment in which several disciplines can succeed together.

For many STEM professionals, the career ceiling is not created by insufficient technical capability. It is created because the person continues investing almost exclusively in technical depth after the organisation has started requiring breadth.

The skills that make you an outstanding engineer are not automatically the skills that make you an outstanding Engineering Director.

How do you decide which skill to develop next?

The answer begins with career direction rather than training. Before selecting another course or professional qualification, examine where you want to go, what successful people operating at that level are actually required to do, what evidence you already possess and where the material gaps exist. This is essentially a career skills-gap analysis, but for an experienced professional it needs to go further than a generic strengths-and-weaknesses exercise, because not every weakness deserves improvement and not every strength deserves another thousand hours of investment.

Look at three dimensions simultaneously: the target role; the market; and your personal differentiation. What skills, judgement and experience does the next significant career step genuinely require? Which capabilities are becoming more valuable within your profession and which may be becoming commoditised or obsolete? What are you unusually good at, and can that strength be developed far enough that it creates real professional leverage rather than simply making you marginally better at something everybody in your peer group can already do?

Learning from people, not simply from courses

Some of the most valuable professional development I have experienced did not arrive through formal education at all; it came from watching exceptional people operate, understanding why their judgement was different and then incorporating elements of that thinking into my own leadership.

Steve Windsor taught me something deceptively simple: never guess out loud. His point was not that leaders must know everything before speaking, but that there is a difference between hypothesis and fact, and credibility matters when other people are using your words to make decisions. Ask the question, establish what is known, distinguish fact from assumption and avoid presenting speculation with more confidence than the evidence deserves.

Bob Joyce and Dick Elsy CBE FREng reinforced this at a much more senior level, and both became, in my view, maestros at balancing fact and judgement. Facts make robust decision-making possible, but seeking perfect information can create its own organisational failure, because decisions are delayed, cost continues accumulating, people become frustrated and morale deteriorates whilst everybody waits for one final piece of analysis that may not materially alter the answer. Judgement is the ability to understand how much evidence is enough, where the residual uncertainty sits and when the cost of waiting has become greater than the risk of deciding.

Dr David Hemery CBE DL taught me something complementary: remain calm, resist the temptation to become the loudest or apparently smartest person in the room, and learn instead how to ask questions that unwrap a problem. Questioning creates space for somebody else to think, and the objective is not necessarily immediate agreement; it is first to establish understanding. I can understand your position without agreeing with it, and once we have established what each person actually means, the quality of the subsequent decision usually improves.

Over time I also modified the GROW coaching model that Dr David Hemery CBE DL taught me into what I call GROWS, with the additional S standing for Support. Earlier in my leadership career I placed great emphasis on holding people accountable, which remains essential, but as the scale of my responsibility increased I learnt that accountability by itself is inadequate. If you expect somebody to deliver, you also have to consider whether they have the resources, organisational cover, authority, information, time and personal support to deliver successfully.

• 
  Bob Joyce
  Engineering leader

  A maestro at balancing fact and judgement at the most senior level: establishing what is genuinely known, then deciding when the cost of waiting for further evidence has become greater than the risk of deciding.

  Profile →
• 
  Dick Elsy CBE FREng
  Engineering leader

  Reinforced the same discipline at scale: facts make robust decision-making possible, but pursuing perfect information delays decisions, accumulates cost and erodes morale whilst everybody waits.

  Profile →
• 
  Dr David Hemery CBE DL
  Coach, author and Olympic champion

  Taught me to remain calm, resist becoming the loudest person in the room and learn instead how to ask questions that unwrap a problem — the coaching approach behind my later adaptation of GROW into GROWS.

  Profile →

Why judgement becomes a career skill in its own right

Judgement is difficult to describe on a CV and almost impossible to acquire through a two-day course. Judgement is built through repeated exposure to decisions where the information is incomplete, the consequences matter and several apparently reasonable options compete with one another. It develops when you see what happens after the meeting rather than merely learning the theory before it.

Professional development should therefore include stretch assignments, difficult projects, unfamiliar stakeholders and responsibilities slightly beyond your current comfort zone. Knowledge is useful, but applied competence is what ultimately alters your professional value.

Document not merely the training you complete but the evidence created when you apply it. If you undertook leadership development, what did you subsequently lead? If you learnt a new analytical method, what decision did it improve? If you acquired programme-management capability, what programme did you recover, accelerate or protect? If you became better at negotiation, what changed because of it? Professional development should eventually become professional evidence.

Are additional qualifications worth it in mid-career?

Sometimes enormously so, but the answer depends upon what the qualification changes. At a point when my career could plausibly have continued along a deeply technical research route, I had responsibility for 124 research engineers and university-based PhD researchers and seriously considered undertaking an Engineering Doctorate at Cambridge, using the depth of technical research around me to develop further expertise in advanced aluminium materials engineering or sustainability.

On paper it made complete sense, but I was coached to think differently about the capability I would actually need next. I chose an MBA instead, and that decision changed the breadth of my professional thinking, because it forced me beyond engineering and into finance, operations, strategy, organisational behaviour, marketing and the wider mechanics of how a business operates.

The lesson is not that an MBA is superior to an EngD. The lesson is that the value of a qualification depends upon the capability gap it closes and the future role it enables, which is why professional development needs to begin with direction.

Why career positioning should come before CV writing

Positioning comes first because a beautifully written CV can be pointed in the wrong direction. People naturally begin with the thing they can see: they are unhappy with career progress, or applications are not producing the result they want, and therefore the CV becomes the obvious problem to fix.

There is little value in teeing the ball beautifully on the first hole, buying the finest clubs, taking an immaculate swing and then driving the ball straight through the clubhouse window because you were facing the wrong direction. Career narrative explains the career; positioning establishes what the career is aimed towards. Direction, clarity and positioning come first.

What should career consultancy contribute to professional development?

For an experienced professional, the higher-value contribution is often helping them understand the career system as a whole: what they genuinely want, what they are capable of, where the market may value that capability, which evidence supports the proposition, what is missing and what should therefore be developed next.

At Eich Dyn, Career OS™ deliberately begins upstream of the CV. Career Diagnosis and Positioning Strategy exist because there is little point creating a powerful professional profile until the individual has established where that profile is intended to take them. Only then does Evidence & Profile become meaningful, followed by Search & Networking, Interview Mastery and Offer Negotiation. The process is intended to improve the quality of career decisions that precede the application.

How should an experienced professional build a development plan?

Start with evidence rather than aspiration. Examine the roles you might want in three to five years and identify the recurring responsibilities, decisions and capabilities those roles require. Compare them with evidence from your own career, not simply self-perception.

Then prioritise. There may be ten things you could improve, but only two or three that would materially alter your career options. One may be technical, another commercial and another behavioural. The objective is not the longest possible development plan; it is the smallest number of development priorities capable of creating the greatest meaningful change.

Then create application opportunities. If leadership is the gap, find something difficult to lead. If commercial understanding is weak, seek budget, supplier or customer exposure. If executive communication is the problem, place yourself in situations where complex technical material has to be reduced to a clear decision for a non-technical audience. If AI capability is becoming relevant, test it against a real workflow or decision with a meaningful outcome.

Finally, seek feedback and record the evidence. The learning cycle should not finish when a course ends; it should finish when you can explain what you now do differently, what changed because of it and what further improvement is still required.

1. Step 1Destination
2. Step 2Gap
3. Step 3Priority
4. Step 4Application
5. Step 5Feedback
6. Step 6Evidence

The wider system these ideas became is Career OS™. The MOVE pathway governs a deliberate external move, whilst the PROPEL pathway governs progression inside your current organisation, where judgement, leadership and commercial understanding do most of the work.

Future-proofing a career without pretending we can predict the future

Nobody can genuinely future-proof a career against restructuring, technological disruption, recession, acquisition or changes in customer behaviour. What we can do is build enough adaptability, breadth and professional evidence that a change in circumstances does not leave us dependent upon one narrow capability, one employer or one version of an industry.

For experienced engineers and technical leaders, that normally means retaining genuine technical credibility whilst broadening transferable capabilities such as judgement, leadership, commercial understanding, communication, programme management, problem-solving, stakeholder influence and the ability to learn quickly.

What I would tell my twenty-something-year-old self

Become technically excellent, because credibility matters. Learn quickly, volunteer for difficult assignments, watch how the best people make decisions and never become embarrassed about asking a question when something does not make sense.

Do not make the objective remaining the smartest person operating the tool. The more important career question is what capability you are building once other people can do what previously made you unusual.

• Distinguish fact from assumption.
• Understand that leadership eventually requires judgement, because perfect information rarely arrives on schedule.
• Recognise that calm questioning often creates more influence than being the loudest voice in the room.
• Remember that accountability without support is incomplete leadership.

Look beyond engineering earlier. Understand how the organisation makes money, how customers decide, where risk sits, what drives investment and why technically excellent proposals sometimes lose to commercially stronger alternatives.

Most importantly, manage the career as deliberately as an engineering programme. Establish the direction, understand the requirements, identify the gaps, allocate resources, review progress, respond when circumstances change and keep evidence of what has actually been achieved.

The question is not simply whether you are good at your job today. The more important question is what your present role is making you capable of doing tomorrow.

The question I would ask you now

If you are an experienced professional reading this, particularly a senior engineer, technical specialist, engineering manager, programme leader or STEM professional considering the next stage of your career, do not begin by asking which qualification you should take or which course you should buy.

Identify the role, responsibility or professional direction you genuinely want next, and then ask which single capability gap most materially reduces your ability to reach it. That gap may be technical expertise, but it might equally be commercial understanding, leadership, strategic judgement, career positioning, communication, influence or simply the absence of credible evidence that you can already operate at the level you are targeting.

Once the gap is clear, the development decision becomes considerably easier. Learn deliberately, create an opportunity to apply the learning, seek uncomfortable feedback, measure what changes and convert the outcome into evidence that another organisation can understand. Then repeat the process.

Frequently asked questions