Improve Culture Before Improving Process


Team-Driven Developer

A newsletter with tips and tools for building software as a team

Engineers love to talk about process.

Whether it's how to run a team, the best development methodology, or even the most effective deployments, we are always talking about the “right process.”

And it makes sense. A process is pretty similar to an algorithm, and many of us write algorithms in the form of computer code all day.

When projects go wrong or run late, one of the first things to do is scrutinize the process. What handoffs went poorly? Which steps need tighter boundaries? How can we improve this?

And this is right and good. But I think it misses the point.

Instead, we should focus on building a culture that will solve the process problem on its own.


Team-Building Exercise

Think back to the last project you worked on that went south. What happened?

  • Was it a problem with the requirements?
  • A problem with resourcing?
  • Was there someone making things too complex?
  • Was there someone underestimating the complexity?
  • Conflicts within the team?

Now consider: what could you have done to help improve the outcome of that project?

There are small ways you can help get a project back on track without rethinking an entire SDLC or anything like that.

Instead of avoiding that person who makes things difficult, can you find a way to build common ground on something you both want to see happen in the project?

Instead of complaining about requirements, can you ask questions to understand why and/or provide alternatives that are more reasonable to you?

Instead of forcing someone to do things your way, can you meet in the middle faster on non-critical issues to keep things moving?

There are instances where you couldn't do much of anything - some things are that way.

But by focusing on building the culture you want as best you can, I think you'll find you can course-correct many projects that go wrong and build a stronger team in the process.


Here are some more resources from me to help you build better teams!​

  • Code Review Champion - My book on code reviews will help you become a world-class code reviewer. From giving kind feedback to navigating conflict, this book can help anyone wanting to sharpen their code review skills.
  • Questions for Devs - Building a team takes more than catching up about your weekend at standup. I've used these questions to build relationships with my team and push past the same old surface-level conversations.
  • Pull Request Template - Maximize your efforts in pull requests by giving context right at the beginning of a new pull request. Copy and paste this template into your repo, and voilà!
  • Code Review Metrics - Start measuring how your team tracks against a few common code review metrics. This python script will pull your GitHub pull requests and generate a CSV you can slice-n-dice to get the data you want. It also has graphs! As this is an open-source project, your contributions and feedback would be great!

Other Creators I Recommend

Image for Nerd Notes | Power-up your freelancing

Nerd Notes | Power-up your freelancing

By Chris Hufnagel

Every Tuesday, creative freelancers (like you) learn from my 12+ years out on my own. Pricing, productivity, mindset, and everything in between.

Image for Building Custom SaaS Web Apps

Building Custom SaaS Web Apps

by Thomas McGee

I’m a web developer by trade, but I’m a creator at heart. As such, I constantly find myself making, designing, and coding new things to make life easier for creators of all kinds. Whether it be Radarist for managing your projects and tasks or Startboard for easily organizing your web bookmarks—I’m here to make it easier for anyone to earn online.

113 Cherry St #92768, Seattle, WA 98104
Unsubscribe · Preferences

Dan Goslen | The Team-Driven Developer

Learn the tips and tools for building software as a team! Every other week, I send a long-form article, a team-building exercise, and resources to help you build better software teams so you can build better software.

Read more from Dan Goslen | The Team-Driven Developer

Team-Driven Developer A newsletter with tips and tools for building software as a team A few weeks ago, I co-authored an article with some friends at Greptile about AI vs. human code reviews. It was a blast working with Greptile’s co-founder, Daksh, on the article, as he brings an insider perspective about the new AI technology helping software developers become increasingly effective at their craft. One of our key points was around something that was likely unexpected to a reader: the idea...

Team-Driven Developer A newsletter with tips and tools for building software as a team Hey! Welcome to another edition of the Team-Drive Developer.I'm trying something different this week: I'm including the entire article in the email instead of asking you to click through my site. Let me know what you think! If you’re a frequent reader of this blog and newsletter, you know I’m a big advocate for two core components for building software: Iterative development (constant refactoring, focused...

Team-Driven Developer A newsletter with tips and tools for building software as a team Software companies love to talk about innovation. Whether they are building a product that will “revolutionize the way teams do X” or plan to “disrupt the market”, there is real value in convincing investors that a company is doing something unique and innovative. You’ll also see this idea on job postings or in advice on how to grow your career. "To get to the next level, you must innovate, challenge the...