Leadership Icon

Leadership

Leading and managing, people, orgs, and communities.
34 Stories
All Topics

Miroslav Nikolov webup.org

Arguments for a project kickoff strategy

Miroslav Nikolov:

You may not be a project manager. Perhaps you are a developer who likes to code and solve technical challenges. The organizational matter is something you care less about. After all, your company is likely relying on some agile methods and there are product owners and/or SCRUM masters to handle the process. You just need to build new features.

While that’s true you have to sometimes get out of your comfort zone.

Evgenii Ponomarev evgenii.info

How to deal with pushback to your initiatives

This article covers three main reasons why other engineers may reject your technical initiative (such as refactoring, changing methodologies or switching tools):

  1. The proposed goals look unattainable
  2. They tried the first version and they didn’t like it
  3. They don’t agree that the problem is worth solving

For each of these reasons, there are tips you can use to drive your initiative forward.

Sarah Drasner CSS-Tricks

Mistakes I've made as an engineering manager

Sarah Drasner:

I’ve been a manager for many years at companies of different scale. Through these experiences, I’ve done my share of learning, and made some mistakes along that way that were important lessons for me. I want to share those with you.

The four mistakes that Sarah details, which we can all learn from:

  1. Thinking people give feedback the way they want to receive it
  2. Trying to do everything yourself as a manager is the best way to help
  3. Communicating something one time is enough
  4. You have to have everything together all the time

Culture annashipman.co.uk

Meeting everyone on a new team

I enjoyed reading what Anna had to say about the advice she had been given and the process she created for doing introduction one-to-one meetings with her new team.

When I joined the Financial Times as Technical Director for FT.com, I inherited a team of around 50 engineers. One of the first things I did was meet each of them for a one-to-one. I was initially resistant, but it was extremely valuable, I’m glad I did it, and I would definitely do it again in a future role. I ran each meeting in the same way. Firstly I ran through everything I planned to cover, and then stepped through it…

Jason Warner medium.com

GitHub's CTO on architecting engineering teams that scale

Get some wisdom from Jason Warner, CTO of GitHub on building and leading engineering teams that scale.

If building a high-powered engineering team is hard, successfully scaling it through hyper-growth is near impossible.

The culture of any organization is shaped by the worst behavior the leader is willing to tolerate. Culture isn’t just about the “feels;” it’s about accountability and behavior. Whatever you do as a leader and whatever you tolerate becomes the standard for your entire organization.

Gergely Orosz blog.pragmaticengineer.com

An engineering team where everyone is a leader

If you are a leader or someone aspiring to lead, consider this approach to engineering management.

This post is a summary of the approach and tools I’ve used to build an engineering team, where everyone is a leader - including sharing of the project management expectations Google Docs guide that my team uses. It’s also a reflection on the pain points that came with this approach. I can’t advocate for how universally this approach could work. However, based on my results, it is something I suggest engineering leaders - especially frontline managers - consider as an option.

Culture knowyourteam.com

How to manage up effectively

Claire Lew, the CEO of Know Your Team, shares 5 not-so-often-shared ways to manage up and have a better relationship with your boss.

You want to manage up – but what you really mean is that you simply want to work well with your boss. Who doesn’t? Especially when your boss is pestering you with questions via Slack after work-hours, or failing to give you enough time to complete projects…

Based on research we’ve done over the past five years with hundreds of managers and employees, and the insights shared in our online leadership community, The Watercooler, here are the 5 distinct ways you can manage up to have a better relationship with your boss.

Julia Evans jvns.ca

Not getting your work recognized? Brag about it.

Most people are modest about their contributions in the workplace. We also forget how important our contributions are. Then, when it comes time for recognition, you’ve forgotten, others didn’t notice because they don’t understand all the details and moving parts, and work just moves on. What do you do if/when your work goes unnoticed? Here’s what Julia Evans suggests…

Instead of trying to remember everything you did with your brain, maintain a “brag document” that lists everything so you can refer to it when you get to performance review season! This is a pretty common tactic – when I started doing this I mentioned it to more experienced people and they were like “oh yeah, I’ve been doing that for a long time, it really helps”.

Where I work we call this a “brag document” but I’ve heard other names for the same concept like “hype document” or “list of stuff I did” :).

BONUS — Julia included a basic template for a brag document at the end of the post.

Jonas Van Schoote madewithlove.be

The different skills needed to be a successful CTO

What does it take to be successful as a CTO? The stories of founder/CEO transitions is plentiful, but what about the evolution of a company and the need for a CTO who has a vision of how to do things and the team and skills needed to make it happen?

A CTO at this point still needs to mainly look inward and know how to code, know the structure of the application and infrastructure, but the focus is shifting towards managing a team, establishing a culture and processes to be able to grow quickly. Growing also means hiring but also making sure that every hire is an effective team member as soon as possible.

Startups holloway.com

Fundamentals of product-market fit

For the entrepreneurial type: this is a great dive into the fundamentals of product-market fit by @sparkszilla. The whole read is worth it if you’re interested in raising funds in the future. The heart of the article stems from three axiomatic theories:

  • Rachleff’s Law of Startup Success: Rachleff says, “The #1 company-killer is lack of market. When a great team meets a lousy market, market wins. When a lousy team meets a great market, market wins. When a great team meets a great market, something special happens.”
  • Rachleff’s Corollary of Startup Success: “The only thing that matters is getting to product-market fit.”
  • BPMF and APMF: The lives of startups are divided into two categories, before product-market fit (BPMF) and after product-market fit (APMF).

And the Vohra questionnaire to see if you have PMF is one I’ll keep on hand for the future. 👌

Fundamentals of product-market fit

Lara Hogan larahogan.me

Lara Hogan's guide to writing a "Week in Review" doc

The important thing to remember about leading is you have to have clear lines of communication with those you lead. I love the ideas Lara shared in this guide to writing a “week in review” team update.

This doc helped me set records straight, disseminate info to lots of people at once, and open up conversation internally, while reflecting on the themes that had come up in weekly one-on-ones, backchannels, team meetings, etc. What I chose to write about each time widely varied.

Though the teams who reported to me were the primary audience for this doc, I kept it internally-public, meaning that anyone at the company could read and comment in it. I found that some other managers just weren’t talking about hard things that were happening…

link Icon codeplease.io

On being an Engineering Manager

Hey leadership friends out there — Rui Peres did a great job breaking down his experience being an engineering manager of 10 people in 2017 and how it impacted him as a professional.

My negotiation skills also improved. I used to start a conversation with “no”, now I make a conscious effort to say “no, but” and present alternatives. Thanks to a fellow engineering manager, I learned to make the distinction between what needs to be built and when it needs to be done (big difference). This innocuous detail helps me have better judgement of a situation.

Player art
  0:00 / 0:00