Slow down to speed up

This weekend, I saw something remarkable that I’ve never seen before: the Northern Lights.

We drove about 30 minutes to Blaine, WA where it’s pretty dark out, parked the car, and waited. At first, we didn’t see much. After a while, we started to see trails in the sky. Then, you could see some faint color in the sky.

Using our phones showed a different story. Using a long exposure (10s) and underexposing the photo let enough light in to show beautiful colors. It was breathtaking and amazing to see the colors change and shift over an hour or two.

The best pictures turned out to be ones that combined the beauty in the sky with details in the background. (In this photo, you can see some details from the Vancouver, BC skyline and some mountains.)

You’re not seeing the 40-50 shots that didn’t work out, and the 20-30 other “good ones” we found. This process is very similar to the learning we have when we’re building new tech for operations.

We didn’t know what to expect

As in many operations situations, we encountered a new situation and needed to wait, watch, and analyze to determine what was going on. Our first photos of the Northern Lights were pretty awful: blurry, overexposed, and poorly composed.

When you get initial results in your ops project that don’t meet expectations, what do you do? Change one variable, and keep doing the process until you get different results.

In this case, changing the default “Night Mode” 3 second exposure on the iPhone to a 10 second exposure made a huge difference. The longer exposure created beautiful colors that we weren’t seeing with our eyes only.

However, our fix also created more blurriness in the resulting image. We needed to adjust the way that we were holding the phone. Nope, we didn’t bring a tripod, so bracing the phone on the ground or with your knees and holding your breath made the best blur-free images.

We made adjustments and collaborated

It took some effort to get from “cool! Let’s take pictures” to “that’s a good picture.” A few different adjustments helped, including:

  1. metering on the sky instead of the dark parts of the ground

  2. changing the exposure (the basic iPhone camera app allows for bracketing without enabling specific ISO settings)

  3. using the wide angle and “normal” lenses to see the difference

  4. taking pictures in different directions and at different angles

We learned that sky pictures without any reference point are pretty dull, even if they include Aurora. Adding a silhouette of a person or a tree adds an interesting compositional choice and makes it easier to read the color.

What does taking night pictures teach you about operations?

When you’re in a unique situation (this is like an event or a conference x100), your typical approach might not be effective due to environmental or other factors. It’s important to adjust based on testing, to do it quickly and decisively, and to redirect when things are not working.

It also reminds your eyes give you different information than your other senses or tools. There are technical details that help you understand why aurora colors look more vibrant in a camera than to the eye, but they don’t compare to the overwhelming feeling of seeing something special and timebound.

Operations is all about rising to the moment, no matter what happens. Nature’s spectacle in a solar storm is a great place to practice those skills.

What’s the takeaway? Don’t discount the value of other skills you have that come into play during a typical operations task. By following a playbook and giving yourself space to improvise, you leave open the chance of real insight every time you encounter a new ops situation.

gregmeyer
gregmeyer
Articles: 566