Foster Agile: Keep Your Eye on the Ball

Part of the Foster Agile series.

About twenty years ago, I was working for my step-dad’s engineering firm. Deadlines all around, I was paralyzed. I told him that I didn’t know what to do.  He said, “My grandfather always told me: ‘Keep your eye on the ball.'”  I said, “Sure, but what if there is more than one ball?”  Without missing a beat, he responded, “Keep your eye on the one that’s going to hit you first.”

This advice has served me well over the years, but working alongside him renovating my house over the last few years has really made the lesson stick.  At the start of a day, we discuss what we aim to do.  Then, we do that and only that until the end of the day.  I have occasional moments of panic that I am neglecting something important out there, or that I am going the wrong course, but working alongside my hyper-focused step-dad, I stay with the selected task.  There is this strange feeling–perhaps it is Csikszentmihalyi’s flow, I’m not sure–that the rest of the world has been pushed outside a bubble around us.  By the end of the work weekend, we have accomplished an astonishing amount of work.  As for the things calling from the outside world, nothing has burned down as a result of my ignoring them for a while.

I’ve since tried the same thing at work. I noticed that I was letting my focus slide all over the place in the time slots available between meetings. If I could manage to attend a scheduled meeting for an hour, why was I struggling to maintain focus on a task for an hour? So, I set up meetings with myself to focus on those tasks. And I kept my eye on the ball. The same feeling from working with my step-dad came back. The world retreated behind a bubble. The same anxieties came, but I stuck with my tasks (kept my eye on the ball that was going to hit me first), honoring my commitment. When I emerged, nothing had exploded. The only real change was that I was burning through tasks at a much higher rate.

I struggle to exercise the enormous discipline required to give myself this gift of focus. First, I have to plan my time, committing chunks of time to given tasks.  This runs counter to my impulse to just dive in.  Second, I have to make hard decisions when I realize my list is simply too long for the day.  I have to resist impulse #2: rely on wasteful wishful thinking.  Third, even when I have planned my day, yet another impulse presses me to respond when things call, rather than keeping blinders on.  In all cases, I have to fight an ingrained habit in order to avoid distraction.

Focus is a core value of Scrum.  At the daily stand-up, for example, team members have this wonderful opportunity to select a single task, or a set of serial tasks, to take on for the day.  The system explicitly lays out their right to keep the rest of the world off behind a bubble.  Scrum and other Agile frameworks enable this focus through the key structural component of iteration: “Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.”  Breaking a schedule into chunks allows you to break your work into chunks in the same way, leaving everyone the freedom to focus only on the set of work selected for the current chunk.  It keeps you from the much more complicated discussions you have to have when you have a boundless future in which to schedule your boundless list of tasks.  Focus is one reason Agile principles can work. However, it’s not enough for them just to enable focus; one must discipline oneself to apply those principles.

The folly of multitasking is well-known, but I suspect that many people see its danger only at coarser levels. For example, they talk about the problem of having to go to a couple of half-hour meetings a day, or of having to switch product focus from sprint to sprint. While I agree that these switches degrade focus, it is at the grain of minutes and even seconds that I think context-switching does its greatest damage. You click the bookmark for your bug-tracking software and the system is slow. In the moment you wait, you switch to look at an email that just came in reminding you to submit your time sheet. You open the time sheet app. Another delay in loading. You switch back to read the next email. This pattern continues, and all of a sudden you have eight tasks cluttering your mind. The impulses had good intention: “It is a waste of time for me to stare at the screen while the bug-tracking software loads, so I’ll do something else for a minute.”  Unfortunately, it just doesn’t work. It is actually more efficient by a stunning degree to stare at the screen until the system responds. This is the powerful counter-intuitive truth of “keep your eye on the ball”.

Are you as focused as you think?  I offer this challenge. When you are done with this post, figure out your next few highest priority tasks.  Rank them.  Do the first, and focus only on that until it’s done, at which point you move on to the next.  Pay a little attention to yourself as you do.  Are you really focused?  Did you switch over to email for just a second?  Did you make that spreadsheet a little fancier than it needed to be?  Did you remember something “more urgent’ you had to do and switch to get it done because it would just take a second?  If you switched away, try again.  This time, force yourself not to switch.  Once you’ve succeeded in avoiding a switch, look back on how it went.  What was different?

Highfalutin talk aside:  Keep your eye on the ball.  And if there’s more than one, keep your eye on the one that’s going to hit you first.

One thought on “Foster Agile: Keep Your Eye on the Ball

  1. Pingback: Foster Agile: S**t My Step-Dad Said | Growing Truffles

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s