Management A good hack feels like cheating

Five Leadership Hacks

MIT has a storied history regarding hacking where the act is viewed as a “clever, benign, and ethical prank or practical joke” at the University. Hack is also defined as the act of breaking into computers or computer networks. My definition is a combination of both.

To me, a hack is a clever or unexpectedly efficient means of getting something done. A good hack should feel like cheating because the value created by the hack feels completely disproportionate from the work done.

With this definition in mind, I present five leadership hacks I regularly use. These are not practices designed to redefine your leadership philosophy. They are hacks. 

Two minutes early. For everything.

Let’s start simple. I attempt to show up for every single meeting approximately two minutes early, and it has to do with Apple. It may have changed since then or been team dependent, but the expectation at Apple was that every meeting started roughly five minutes after the scheduled start time. It was assumed. We called it “Apple Standard Time.”

If everyone is aware that “Apple Standard Time” is the standard then no big deal, everyone ends up accounting for this handy five-minute buffer. But everyone is not aware. There was no onboarding were we learned about “Apple Standard Time,” so there were not infrequent meetings where half the people showed up and stared at each other for five minutes wondering, “Where the hell is everyone?”

The origins of “Apple Standard Time” are unknown to me, but I bet it started decades ago when someone important, someone with an impressive title kept… showing… up… late. No one said anything because everyone assumed there was good reason for the tardiness. There was a reason: this leader was bad at running their schedule. Worse, this behavior was allowed to exist and – even worse – it became part of the culture. 

Two minutes early. For everything. This means I look at my calendar at the beginning of the day and account for transit time. This means I gracefully leave the prior meeting five minutes before the scheduled end. This means I profusely and honestly apologize for wasting people’s time when I walk in two minutes late and this means I don’t let this failure become a habit.

The clock faces you.

Ending a meeting that is going well is tricky. Laura is in the middle of a soliloquy about the powers of a good engineering program manager. It’s great. She’s on a roll, but I need to be across the building for a 2pm meeting, and it’s 1:55pm right now, and I can not hear an ending to Laura’s speech. 

Laura knows nothing about my internal scheduling turmoil and she’s looking straight at me because she knows my support for program managers is critical and if I’m busily checking my calendar rather than listening, I am telling the rest of the room, “This thing she is talking about is not that important.”

The first thing I do when I sit down in a conference room is to find easy sight lines to the clock. Hopefully, it’s on a wall, or maybe I need to turn it face me on the desk. The hack is: “I should be able to know the precise time of day at any moment without a single human noticing.”

By having an intimate understanding of the time, I can shape my exit. I can listen for the ever-so-small pause Laura lands at 1:58pm. She’s not stopping, she’s taking a deep breath, so I can jump in and say, “This is great. I have a 2pm across the building, can we continue this discussion later?”

Whether you’re running the meeting or attending the meeting, being frictionlessly aware of the time is the first step to getting a meeting to end on time.

Office hours.

At my last gig, I wanted to meet everyone. First all hands, I committed, “I will personally meet with each and every one of you.”

Admirable. Doesn’t scale.

I started with 1:1s, but it was quickly obvious it’d take six months to get through the entire team, so we quickly pivoted to round tables. Five to ten folks plus me – every week. These meetings were more time efficient, but in each, it was clear that there were always a handful of folks who simply didn’t want to be there. I have work to do.

You can flatten your organization by creating as many communication conduits in as many unexpected directions as possible, and this was the goal with my flawed “meet everyone” strategy. The question is how do you create this communication serendipity for all the humans?

Office hours. They’re announced broadly every two weeks. Two hours total. 30-minute slots. Google Calendar makes this super easy. 

The result: my office hours are filled every time I announce them by the folks who want to talk and have an agenda. These are some of the most interesting meetings that I have with the team on a week to week basis. Random thoughts. Emerging concerns. Criticism. Growth conversations. Deep strategic concerns. Communication that only happens 1:1 and in person on a regular basis.

Three questions before any meeting.

Another morning calendar hack: I glance at my day and make a quick assessment: what is the value being created by each of the meetings on my calendar? In a moment, I should be able to answer that question. It’s a new director and we’re going to get to know each other. It’s a weekly sync with a team in crisis. It’s a regularly scheduled 1:1. 

Once I understand the why, I then focus on the what. Whether I run the meeting or am a participant, I write three questions that I’d like to get answered at this meeting. For a day full of meetings, the three question exercise should only take a few minutes and it achieves two important outcomes:

First, it frames my goals for this meeting. What is top of mind for me and what am I going to ask when given a chance?

Second, if I am failing to come up with three questions, I ask myself, “Why am I going to this meeting?” Meetings are a virus. They infect and they multiply. The longer they exist, the more likely the humans forget why the meeting was called. If it takes more than 30 seconds to think about my three questions or if I can’t think of a single question that I want to ask, I decline the meeting with a clear explanation. 

Continually fix small broken things.

There’s a stack of books on the right side of my desk. They’ve been slowly growing over the past month; I keep telling myself I’ll deal with them, but today I’m dealing with them. The one good book goes in my backpack for reading; the rest go to the bookshelf because I have decided I will likely never read those books.

Sticking with the desk. I’ve been collecting pens, and my pen cup is too full. So, I pour them on the floor and decide which pens are staying in the cup and which pens will be declared free. It takes a little over a minute, but I reduce my pen load by 50% and a lucky someone in the office is going to find a bunch of exceptional pens in our office supply cabinet.

There are five more small broken things on my desk that – in less than 10 minutes – I could fix. These are small broken things I’ve been staring at and stressing about for a month, and in 10 minutes that compounding guilt is better. That 10 minutes made standing at my desk more joyful. 

As you walk around your office, you constantly see little things that are broken, but you often ignore them because you are urgently working on the big things. The last hack is the easiest and it’s the best: fix small broken things. Always. It takes seconds to clean that whiteboard, to plug in the clock in the conference room, and to stop, lean down, and pick up a piece of trash. Seconds.

The value created isn’t just the small decrease in entropy, it’s that you are actively demonstrating being a leader. I understand the compounding awesomeness of continually fixing small broken things.

Leave a Reply

Your email address will not be published. Required fields are marked *

12 Responses

  1. Cujo 1 year ago

    I’ve long had a policy of starting my meetings promptly on time and ending them promptly on time. No exceptions. People seem roughly evenly split between thinking I’m an asshole vs. thinking I’m awesome for this.

    Also, why would you put a book you’ll likely never read on your bookshelf?

  2. CdrJameson 1 year ago

    ‘Continually fix small broken things.’ also works well for build process/code etc.

    Those small improvements really do add up over time, and remove a thousand irritations from your day.

  3. Five Leadership Hacks linked to this.
  4. fozbaca's WordPress linked to this.