The Engineering Manager

In an open plan office in a galaxy not so far away…

---

Lisa rotates in her chair and looks upwards at the ceiling. She poses a question:  

“I’m just about to create the repository in Github. What should we call it?”

“Well, we’re not even sure what it’s going to do yet. I don’t even know if what they’re asking for is possible.”

Ben looks back towards his monitor, opens up Google and types in “cool project names” and hits the return key with vigor. Lisa scoots her chair over to Ben’s desk to look at the results. 

“That’s the one.”

“Oh yeah,” she replies.

Switching back to his initial browser tab, Ben types in “Project X” and creates the repository so that the Data Science team can start hacking around with ideas.

Lisa uploads the first file. It’s a Python script that prints “What on earth is Project X? ?” when executed. Ben laughs. He commits a README.md that states:

The first rule of Project X is that you don’t talk about Project X.

Lisa stretches her arms into the air and cracks her knuckles. She sighs.

---

A gentle clinking sound repeats as Lisa whirls the milk into her teacup in the kitchen. She looks through the glass partition that separates her from the breakout area. 

The light in the open space is dimmed, and row upon row of chairs are packed tightly with what looks like the entire commercial team, listening intently to the presentation of the company roadmap.

Leaning against the kitchen wall, she watches the projection as screenshots of the latest iteration of the mobile app are shown. Laptops glow as the audience take notes.

Sipping her tea so that it doesn’t spill over, she turns to leave the kitchen, but is distracted by the reflection of a giant “X” on door. It’s coming from the presentation.

The slide says what she had immediately feared: “Project X”. The CEO is animated. The crowd are clapping. Lisa’s heart sinks. She fumbles with her phone to send Ben a Slack message.

Lisa: They’ve just presented Project X during the roadmap deck.

Ben: Are you serious?

Lisa: Yes.

Ben: But we don’t even know what it does yet.

Lisa: What do we do?

Ben: What did the slides say?

Lisa: It’s coming next quarter, and the whole of downstairs was hyped.

Ben bursts through the kitchen door. 

“What the hell is going on?”

“We are absolutely screwed,” replies Lisa, who is now pacing in circles.

“It’s literally a CSV file with two hundred lines of test data for a feature that hasn’t been designed. How are they announcing it already?”

Lisa stares into her mug. “Will they notice if I leave the country?”

“I’m looking up flights to Siberia,” replies Ben.

---

“Lisa! Our rockstar data scientist! So good to see you!”

It’s the head of sales.

“Oh, hey Mia.”

“Let me tell you this, Lisa. I love the website. I love what you’re doing for this company. It’s going to absolutely blow the competition away. My team are going to push this so hard when it’s done.”

“Website? What do you mean?”

“Double-you double-you double-you dot project x dot com. It looks incredible. The announcement last night on the webinar? Fantastic. Thousands of our customers watched it, Lisa. Thousands.”

“What?”

“I love it, Lisa. Love it!”

Mia is already out of the kitchen and involved in another discussion. Lisa walks back over to her team and taps Ben on the shoulder. After finishing the current line of code with a semi-colon, he removes his headphones.

“What’s up?”

“Can you go to project x dot com?”

“What?”

“Just type it.”

Hitting the return key, the widescreen display is filled with a humongous “X”. Wagner’s Ride of the Valkyries is audible from the headphones on the desk.

“Oh my God.”

The X fades away to reveal a satellite image of the Earth, spinning gently on its axis. Small X markers start appearing all over the globe. London. Tokyo. Hyderabad. Dubai. Lines then arc from city to city, forming an elaborate mesh across the planet.

There is stunned silence.

As the horn section reaches crescendo and the cymbals crash, the globe fades and a tagline appears:

Everything changes. November.

Ben is livid. “What the hell was that? Where did that November date come from? It’s already October!”

Lisa is staring through her hands. “We are so screwed.”

---

Ben is having difficulty moving his mouse cursor because his trackpad is covered in sweat. Usually the Data Science demo sessions have a small handful of attendees, but today is the first live demo of Project X, and there isn’t anywhere left to stand.

Mia has brought her entire sales team. Most of the engineering team are present. Even the CEO is there. Lisa is leaning against the wall for support. Her legs don’t feel like they are able to stabilize the rest of her body.

Ben coughs. His cheeks are burning.

“OK, hello – wow, there’s lots of you here. A couple of demos today, but let’s kick off by showing you the latest build of Project X. Please bear in mind that we’re not finished yet and this is just a preview.”

Leaning over his laptop, he types his username and password into the login prompt and clicks the button to log in. An error pops up: login failed.

“Damn it,” he whispers to himself.

Lisa leans over so she can whisper to him. “It’s not hooked up to the live environment; try your development password.”

Ben enters his credentials again, but manages to type them in the address bar, revealing his password to the entire room. His cheeks flush for a second time.

Somebody from Engineering is humming the Ride of the Valkyries. Another sniggers.

Lisa rapidly shifts over and takes control of the laptop, successfully logging in to reveal a white screen with a text box on it.

“Er, OK, so this is our latest prototype. It’s probably just easiest if we give it a go. Can someone suggest a word to me?”

Somebody pipes up at the back of the room.

“Eggs!”

“OK, let’s type that in.”

Lisa successfully manages to type “Eggf”, which is quickly corrected to “Eggs”. She presses the return key. A table of data is returned with some fairly arbitrary numbers about eggs: their size, the quantity that are produced each year, and the ratio of egg size to the creature that laid it.

“There you go! Cool, huh?”

There is silence in the room. Faces look blank, confused, and disappointed. Ben and Lisa exchange glances. 

“Any other words to try?”

Mia pipes up. “Is this Project X? Is this our biggest new feature of the quarter? How are we meant to sell this?”

---

Ben is leaning over and prodding at the Nespresso machine with his left hand, which has managed to swallow his coffee pod and jam the input tray, much to the dismay of his colleagues who are impatiently waiting for the day’s first shot of caffeine. With his other hand, he is scrolling through a forum looking for instructions on how to hard reset the machine to release the drawer.

“Technology, eh?”

It’s Lisa, back from vacation after the rather intense end to Project X. 

“Why does the drawer have to be controlled by software, rather than it just being a manual latch?”

“Because software is eating the world, Ben. And now it’s eaten your coffee pod.”

Back at their desks, Lisa gets the rundown from Ben on the next project.

“So they’ve asked us to work out whether we can link together the browsing patterns of our users with the best times of the week to send them promotional emails.”

Lisa leans back in her chair.

“OK, sounds reasonable. Have you looked at any prior art?”

“Not yet. I’ve still been dealing with the fallout from this ridiculous Project X thing. I’m answering what feels like hundreds of emails a day about what it is, how it works, and why it didn’t change history, resurrect Martin Luther King or put another man on the Moon.”

Ben pauses for a second. “What did they expect?”

Lisa rests her head on her chin.

“Let’s just forget about that. I’m ready to start on this new thing. I think I saw something about behavior tracking at the last CHI conference that could be a good place to start. But before we do, this project needs a name.”

“Oh, how about we name it after a goddess? Oh, oh – or maybe one of the Grecian Fates? I always liked the name Atropos. Not a huge fan of Clotho though…” 

“No, no, no,” interjects Lisa. “We’re calling it ‘Best Time To Email’. We’re not having Project X happen all over again.”

Lisa commits README.md into the new best-time-to-email project on Github. It reads:

A project to find out the best time to email our users.

“Let’s see them make an animated spinning globe out of that.”

The sum of zero

Have you ever worked exceptionally hard to achieve something and felt utterly crestfallen when you were unable to get it? Worse still, have you ever strived to achieve something, yet when you do, it leaves an ultimately hollow feeling?

These feelings are common. Humans are hardwired to be insatiable: our eternal dissatisfaction has moved humanity ever forward, but it can also play havoc on our minds.

Your parents may have once told you to enjoy the journey rather than seeking a goal, and there is truth in that statement. 

In fact, I was reminded of this when reading the story of Steve House and Vince Anderson completing the first alpine style ascent – that is, without fixed ropes, carrying all of their equipment, and without leaving anything on the mountain – of the Rupal Face of Nanga Parbat.

“Success is the sum of zero. The choices we made, the weather we had, the mountain we climbed and descended, everything we risked: all these factors reached their culmination… and were erased. We lived the answer to every question presented. There is nothing left to ask. There is nothing left of our selves, only the ghost of what transformed us.”

Steve House – Beyond The Mountain

Whether we reach our goals in life, or whether we don’t, the process that we move through whilst working towards them is the valuable reward: it is the part that actually shapes us, makes us better, and defines us.

How can we look disappointment in the face calmly?

Hit the target

Although not comparable to completing a serious piece of alpinism, my work life, as with many of us who work in technology, consists of a horizontal axis of time, studded with milestones from the past to the distant future. 

Product launches, project beginnings and endings, performance reviews, acquisitions, pivots, sales targets; you name it. At any moment in time there are multiple things that we should be aiming for.

As those of you in the software industry will know, the resonance of moments of achievement is often short-lived. Success, once celebrated, yields to the next goal. In day to day operations, when everything in your system is fine, there is often little feeling of success: it is sometimes the case that only when everything is on fire that your name is called the loudest.

Given how complicated software is, and given how complicated entire software companies are, it is extremely rare for everything to go well all of the time. 

You may have an incredible quarter for engineering achievement in your infrastructure, but there haven’t been enough new features shipped. Conversely, there may have been some fantastic new features shipped, but another part of your system is on fire. You may have even achieved both, but something entirely out of your control makes it not matter, such as the commercial team not hitting their sales target, or a round of redundancies swinging the hatchet at morale.

If we work in such a complex system, how can we ever win and feel proud?

Dichotomy of control

Another excellent book that I read recently was a modern re-introduction to the Stoic philosophy called A Guide to the Good Life: The Ancient Art of Stoic Joy by William B. Irvine. One of the themes often written about by both the Greek and Roman Stoics was the dichotomy of control. 

This sounds academic, but it’s actually pretty simple. 

Typically the Stoics would advocate the use of the analytical brain to maintain tranquility over our emotions. One of the emotions was that of worry: how can we worry about the right things?

The Stoics stated that to choose whether to worry or not, simply categorize your issue into these two buckets:

• Matters you have control over such as whether you can do a good job, whether you can be kind and whether you can get a good night’s sleep.
• Matters you have no control over such as whether it is going to rain, whether you may get seriously ill, or whether or not there is going to be a natural disaster.

If your issue falls into the first category – that is, matters that you have control over – then you should absolutely worry about it. You affect the outcome, so do your utmost to make that outcome happen. 

However, if your issue falls into the second category – that is, matters that you have no control over – then no matter the anxiety or worry about what might happen, it doesn’t matter, since you can’t change it. Therefore you should not worry about it. 

Although easier said than done, the Stoics argued that frequent application of this analytical reasoning to problems would strengthen one’s resolve and make him or her more able to maintain their tranquility (the Stoics, as you may have guessed by now, loved their tranquility). 

OKRs

I was reminded of OKRs when I read the above dichotomy. Yes, like the comparison of work to alpinism, it is hardly comparable to philosophy either, but stay with me here.

You may already be familiar with the concept of OKRs, but if you are not, then they stand for Objectives and Key Results: quarterly goals that an organization should be aiming for (e.g. achieve 60% growth) that trickle down into tangible objectives for each department (e.g. sell $1.5M of new deals), every team (e.g. create $150K of upsell) and individual employees (e.g. create 150 new leads). 

We tried OKRs a few years ago, but they didn’t get a lot of buy in. Your own mileage at your own company may vary. 

One of the common difficulties was that the OKR process expects goals to be defined that are of sufficient difficulty such that you generally only achieve 60-70% of each target; if goals are completed then they are deemed not ambitious enough.

The latter point, which is meant to encourage a mentality of challenging stretch goals, was hard for people to embrace; after all, if you’re doing OKRs right, then you should be comfortable with never meeting the targets that you set for yourself. That’s quite hard to take!

Is there a way that we can set lofty goals but not feel disappointed when we don’t achieve them?

Trichotomy of control

In his analysis of the Stoics, Irvine makes an argument that the dichotomy of control we explored earlier in the article is incomplete. He states that life doesn’t present a binary choice between things we can control, and therefore worry about, and things we can’t control and therefore not worry about.

There’s a third dimension.

Take, for example, a competitive tennis match. Each player should care about the outcome of the match: each player trains for it intensely and on the day will play very much like they are concerned about losing. It would be silly not to worry about it.

But to say that each tennis player is in full control of the match would be a lie: sometimes they’ll win, sometimes they’ll lose, and sometimes each of those outcomes won’t necessarily be up to them: their opponent may be on form or off form, be superior or inferior, and there are infinite ways in which the match can unfold.

Therefore the tennis scenario could be described as a situation they can neither control or not control. It is one that they exhibit some control. 

They’ll certainly have a better chance of winning the match if they play their hardest and have a lot of talent and preparation, but ultimately, they cannot guarantee success. 

Does this sound familiar to work?

Since the Stoics aim for maintaining tranquility, how can they cultivate it in situations that they only have some control over? 

Let’s expand our dichotomy into a trichotomy:

• Matters you have control over should we worried about to ensure the desired outcome.
• Matters you have no control over should not be worried about.
• Matters you have some control over should not encourage obsession over external goals, but instead, should be approached by measuring our success against internal goals.

But what does this mean?

Internal goals

In the mindset of the tennis player, an external goal is “I must win this match”. Worrying about this too much can bring pain when the match is lost, especially when it’s due to a fluke or a bad day. After all, the player only has some control over this. 

Instead, they should worry about an internal goal, such as “I will play my best in this match”. Their own success can be measured against this because it is something that they do have control over.

This is the only way that we can maintain some Stoic tranquility in the world of work, where, as we saw at the beginning of the article, goals may or may not be met despite your best effort. 

If we admit that our aim for the company achieving 60% growth is something that we only have some control over, then we can internalize our measurement of progress against that goal and just make sure that we try our best to make it happen. 

The neat trick here is that by internalizing a goal, we simply avoid tying our emotional response to it happening or not. Regardless, we’re still trying our best, which is exactly what we wanted to do by having a goal anyway.

Take some inspiration from Seneca, Epictetus and Marcus Aurelius: internalize your goals.