The most important non-technical lessons my colleagues learned

I asked my colleagues for the one non-technical thing they'd learned that mattered most. Their answers still hold.

I first wrote this in 2020, for the blog of the software consultancy I worked at then. I’m putting it here because I still come back to it.

As a software company, it’s easy to focus on technical excellence and forget that much of what creates that excellence isn’t technical at all. Some of the biggest lessons I’d learned in the years before hadn’t been technical either. So I asked my colleagues a question: what is the one most important non-technical thing you’ve learned while working here? These were their answers.

Meetings, in the right rhythm

Proper meetings, in the correct rhythms, are very important. When you’re doing it right, people leave saying, “Yes, that meeting was great, and now things are better for my work.”

Stop starting and start finishing

Get things 100% done, one at a time, rather than starting many things and getting them only 80% done. Work as if you might be stopped at any minute and need to be as far along as possible when that happens. That way you deliver real, usable value into the world as often as possible.

The next step

Remember what you can do in this moment, and focus on that. Even on a hectic deadline, find the one next step you can take, and take it.

Collaboration

Collaboration is the key to good work. Drawing on the people around you, and what they know, is how people progress and grow.

Empathy

I think the most important non-technical skill for a developer is empathy. There’s a dangerous and misguided trend in our industry to see clients, or really anyone who isn’t a developer, as the opposition. It’s our job to understand their needs and goals deeply, and to help them get where they want to be. Empathy matters just as much inside the team: it’s how we understand each other and build a place where people talk and get things done.

Hold your boundaries

Don’t be afraid to hold your boundaries on scope creep, and on priorities that keep changing in the middle of a sprint. It’s also part of your job to tell a client when you believe that what they’re doing doesn’t serve their best interests.

Own your understanding

It’s your responsibility to communicate clearly. It’s just as much your responsibility to understand what was communicated to you. Take the time to clarify, check, and write it down for later. Writing out my understanding and sending it back to the person, whether a client, a developer, or a designer, is a great way to make sure we agree.

Don’t pad things

Nobody wants to bring bad news to a team mate or a client, but beating around the bush helps no one. With clients, if a piece of work will take far longer than expected, say so clearly. Don’t fall into the trap of “it’ll just take a little bit longer”. With team mates, don’t be afraid to tell people when they aren’t meeting your expectations for quality or pace. You’ll be surprised how much people appreciate the feedback.

Still true

Reading these again years later, none of them has gone out of date. The tools we build with have changed completely since then. Finishing what you start, understanding the people you build for, and saying the hard thing early haven’t.