Use Timeboxing to Stay Productive


Team-Driven Developer

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

Time is one of our most important assets.


And the best engineers use this to their advantage.

They understand that by being "choosey" with how they spend their time, they can accomplish more than other engineers who might be unfocused or sporadic in how they use their time.


One tool I employ frequently to manage my time (and effort) is timeboxing.

Timeboxing is about switching how you work. Instead of having a goal and taking as much time as neccesary to complete that goal, you instead establish an amount of time to work and see how much can accomplish in that time.


In this week's article, I want to share a few situations in which I've found timeboxing to be especially useful.

Team-Building Exercise

This week's team-building exercise is thinking about using timeboxing to improve and build your relationships within your team.

It can feel daunting to build relationships across your organization or immediate team. It can feel unending and can easily take up all of your time and effort.

When can we apply timeboxing in this regard to help keep us from spending all of our time in 1:1's and in constant conversations that don't help us accomplish our team or business goals.

Here are two ways I use the idea of timeboxing to help build relationships

1) I cap the number of 1:1s I have. I'll focus on the most important relationships given the business goals I have and politely decline the others. I also make sure to mix this up periodically as well.

2) Whenever I have a chance to interact with someone outside of my team, I make sure to take a few moments to catch up with them personally, rather than only being goal-driven. The key is to not spend too much time or you'll get back to the rabbit-hole of spending too much time. But a simple "How are you doing?" at the start of a conversation or "Anything I can do to help you?" at the end of a conversation can go a long way.

Building relationships is a complex topic to be sure. These are just two tactics I've used that have helped me.

Give these a try! And if you do be sure to respond and let me know how it went!


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 Daniel Schaefer

Daniel Schaefer

Subscribe if you are a software developer that has the technical skills, but you're looking for opportunities to enhance your soft skills to advance in your career.

Image for Looking for your next tech job?

Looking for your next tech job?

You're in the right spot. I'm Dr. Kyle Elliott, the founder and tech career coach behind CaffeinatedKyle.com, and I love giving away free resources that help to ensure your job search and career success.

Join 7,435+ fellow job seekers who have downloaded my free Job Search Launch Guide.

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 Hi! This week's newsletter is a bit different. I've suddenly run into some unfortunate build problems 😭 for the website and will need to share this week's article inline vs. on a separate post. Hoping to resolve these issues and return to normal in a few weeks! Related: I'm taking a vacation, so I'll be skipping the second issue this month. I'll pick back up in April! The other week, I heard an interesting...

Team-Driven Developer A newsletter with tips and tools for building software as a team The first time I hit the proverbial "deploy button" as a software engineer, I was anything but calm. While we were confident in our tests, we always feared, "What if something goes wrong?" or "What if we missed a critical test case?" This first deployment went fine, but over the past decade, I've had my fair share of botched deployments or the need to rollback quickly. It's not a fun place to be in. During...

Team-Driven Developer A newsletter with tips and tools for building software as a team Software engineers are all about principles and patterns. Short acronyms like DRY, YAGNI, KIS, etc., are used everywhere within the industry to try and concisely communicate an axiom of how to write software. One principle that arises within software engineering is that of reusability. We have this idea that we can build software components once and reuse them everywhere. The idea is that by building...