The ‘consistency before intensity’ quote is attributed to Bruce Lee of martial arts fame. I’ve recently heard it several times related to other aspects of life, such as forming habits, achieving goals, or following procedures.

The philosophy is that it’s important to do something consistently first. Then you can focus on doing it ‘best’ or ‘fastest’. For example, a walk every day is better than running 10km once a month. Creating a checklist of tasks is more efficient than trying to remember every step every time. Or, reading a bit every day rather than a whole book in one weekend.

Some out there have unwarranted confidence. They talk confidently but aren’t up to scrutiny on their statements.

Some have deep knowledge, but due to lack of confidence, they don’t broadcast it. Since they know they don’t know everything, they don’t say anything.

I like the parable about the bird on a branch. They don’t necessarily trust the branch to hold them, but rather their ability to fly if needed. Similarly, have the knowledge and skills to react. Be the one who does the work, produces tangible solutions. Don’t be thinking the branch will hold you up. Be able to fly.

It’s a good analogy, about the type of people we should want around us most of the time. It’s better to be surrounded by fountains rather than drains.

Think of those “fountain-ous” people around you: those fountains of energy, or inspiration, even fountains of humour, grace, professionalism, or independent thinking.

And of course, it’s far too easy to think of the drains: drains on our energy, confidence, time, or well-being.

Be aware that we all have tendencies towards both types. Few are only ever one type at all times. And some fountains to one, might be a drain to another.

Perhaps there is a lost appreciation for the ability to debate with informed, sensible, and considered discussion, in order to reach a consensus.

We should make the effort to develop debating skills. An exercise to try is to have a debate about unimportant things. Like what’s the best food, best movies, or best sport, or the merits or otherwise of hot versus cold weather or watching a movie in a theatre versus at home. Thinking through how to frame an argument for or against would be good practise.

Skills need practise. Practising skills in an adjacent context can be helpful.

There’s a whole cohort of people for whom defining goals and then striving for them is just a natural part of living. The last big goal that I achieved was finishing five ironman triathlons in five years.

I think that when we strive for goals, it’s even better when we have a witness (or many witnesses), whether a work goal or other pastime. Last weekend I enjoyed witnessing a colleague strive up and down the local cliff face here, 63 times, in aid of a deserving charity, and, maybe for him, so he could say he’d done it. With witnesses.

I recently listened to a podcast about Rubik, and his path to invention of the Rubik’s cube. One of the factors in his story was that he didn’t like school, he was bored by it, and got in trouble a lot. A lot of inventors have that background.

Meanwhile, I liked school, had no issue staying focussed, did the work, and rarely got into trouble, and I ended up with an engineering degree.

Engineers can be inventors, but I wonder if a lot of us are just conscientious problem-solvers, who diligently do the work.

There’s nothing wrong with that approach.

Making a (cash) investment usually comes with an expectation of revenue to follow. This is how start-ups, who all want to be unicorns, convince investors. They proffer the unassailable possibility of revenue to come, based on can’t-fail new technology. Think Theranos, WeWork, Jawbone.

Where there’s investment, revenue is expected to follow. Think about that, in the context of any investment you’re making, or others are making on your behalf. Research and understand the revenue stream that must follow. Or you’ll become another Theranos or Jawbone (both claimed technological solutions that didn’t work). Solutions that don’t work ultimately cost the investors.

Desire lines are that worn out track through the grass, where pedestrians would rather walk, when the walking infrastructure has been in the wrong place or the infrastructure is non-existent.

Workflow and procedures have desire lines as well. They show up when procedural steps are skipped, or done differently. It’s not that a person doesn’t want to get from A to B, it’s that it’s easier to do it outside the structure.

The best thing to do is accept it and change the flow. It’s not useful in the long term to punish those who have found a better way.

I was asked yesterday, ‘what is a risk engineer’? Twenty years ago, I was asking of my colleagues, ‘what’s a pipeline engineer?’ (And then I wrote an article about that, and ten years later we had a 240-strong competency framework for pipeline engineers. But I digress).

What is a “insert any modifier” engineer? Civil, mechanical, process, software, the list of modifiers goes on.

The modifier indicates a specialty field, to differentiate the conduit versus codes versus rotating machinery expertise. The modifier changes, but the noun doesn’t: {modifier} engineer.

The commonality being engineer, who inevitably is a multi-dimensional, technically-thinking, collaborative problem-solver.

Here’s an interesting re-frame of the political spectrum: Is the government’s purpose to solve the problems? Or is the government’s role more to set the conditions so that you can go about solving some of them yourself?

But let’s not get political here. Of course, it also depends on a lot of things.

The framing also applies really well to project managers, to organisational structures, and leadership teams too. Is the structure, role, or person, there to solve the problems directly? Or is it there to provide the support and structure and feedback for you to solve the problem yourself?

Everyone has had a ‘to do’ list. There are many forms of to do lists out there. To do lists appear on paper, on an electronic notebook, on calendars or diaries, in a database, in spreadsheets. I think I’ve tried them all at some point through my life.

Another tactic for productivity and time management is establishing, every now and then, a “to don’t” list. These are activities or tasks that you’ve consciously and purposefully said ‘no’ to. For a time, anyway.

Currently, for the month of June, on my ‘to don’t’ list is scrolling social media on my smartphone.

Habits and repetitive workflows help the workday run a bit more smoothly.

Habits and procedures protect us from decision fatigue. They help by being a ‘given’, so there’s no decision. Like deciding whether to have coffee or tea in the morning (coffee. Always coffee).

Habits are “freedom in routine”. Performing the same actions in the same context or location or decision point means that there really isn’t a decision, there’s no emotion, it’s automatic and situational.

The brain can function more smoothly when it spots patterns and can respond without too much effort.

Create repetitive workflows or habits wherever possible.

It goes without saying that there are plenty of problems in the world. Be they personal, cultural, political, or any other possible adjective to describe whatever problem you thought of when you read that title. There always have been problems, and there always will be problems.

The thing is, observing a problem doesn’t solve it. I read many articles and blogs and essays describing problems in all levels of depth and investigation. Millions are being spent to better describe the problems.

Defining a problem is certainly part of solving it, but being really good at defining it doesn’t solve it.

Searching “engineering skills” online yields these results: communication, problem solving, creativity, leadership, teamwork, attention to detail, design, management, critical thinking, collaboration. “Technical knowledge” is just one line item amongst all the others.

I think this is a huge shift in the view of engineering skills. I like it. In my early days, 30 years ago, engineers did do the calculations (by hand, on paper), and worked in the background. What a shift in role through my work life. Engineers are, and should be, collaborators and critically-thinking problem solvers. Importantly, we have an applied sciences background underpinning our approach to work.

Humility is an important factor in career development, and in leadership. Being able to recognise the complexity of current topics and challenges includes the ability to start a conversation with “I might be wrong”.

But it is a slippery slope, as saying that is also fraught with appearing apologetic and uncertain.

So, being humble and gracious is important in a leader, but can also backfire and look like inability to lead, or that you’re unskilled or incompetent. Yikes.

I suppose the “I might be wrong” needs to be stated in the context of strength, confidence, and openness to other information.

I’ve mentioned these four factors before, but I can’t help bringing it up again. Especially while we navigate the new awakening going on, which feels good.

Careers are built on four concepts: connection, mastery, impact and autonomy.

Mastery requires commitment and dedication, impact requires knowing in yourself what makes you feel proud about what you do, and autonomy means you have initiative and drive. But the most important one is first: connection.

Every successful career story is built on connection with others. Engineering is not a solo sport, and so please make sure to connect with people along the way.

Whenever productivity is brought up as a discussion point, the solutions are something around “smarter”, “better”, and “faster”.

A large, and growing, portion of the working population is engaged in ‘thought’ work, aka knowledge work. These are roles that basically create or move documents around, adding value to them (hopefully) as they go past. At its basic level, knowledge work is not much more complex than moving value-added information around.

Adding value to, and moving, documents around, takes thought, assessment, and analysis. Unfortunately, to do that better, it often can’t be done faster. Smart knowledge work should be done slower.

Adam Grant’s LinkedIn post yesterday resonated with me.

“When groups defer to the most assertive person in the room, they reward confidence over competence”.

And, even better: “we learn more from people who explore ideas than those who attack and defend”.

I agree. I’ve experienced conversations with very (over)confident people. It kind of backfires.

Especially for nuanced and complex topics, we definitely need more exploration of ideas, over bluster and telling(yelling) with conviction. Curiosity and exploration of alternatives is so important in these uncertain times.

Don’t be so convinced about complex topics, that you stifle critical thinking and silence dissent.

Six years ago, I registered Sage Consulting Solutions Pty Ltd as a business in Australia. It emerged from the ashes of three too many redundancies. In hindsight, those hurt me more than I realised, each time I went through it.

Being a soloist has been a good fit for me. Though it’s a hard way to make an easy living. But when it’s good, it’s very, very good.

Looking over past the six years, and into the future, I like what I see. The future is bright in the areas of infrastructure engineering, risk and quality management, and skills development.

The word project is a homonym. It has two interpretations with the same spelling, though pronounced differently. Another example of a homonym is write and right. But project and project are harder to discern: one is a noun and the other a verb.

As a noun, a project is a thing or a concept. It’s a planned piece of work or activity, finished over a set period of time, intended to achieve a particular purpose.

As a verb, to project is to extend outwards, forecast, or, proclaim.

Working on projects is satisfying. It’s also important to project professionalism and reliability.