Hard work under odd conditions, Part 1.

Coronavirus, Leadership, Management, Newsrooms

March 11th was the day everything went to hell.

We had a plan. It might have even been a good plan. The ‘Rona was making its way through the country. We had an inkling things might be getting worse. But a week or 10 days before, my corporation’s COO said we wouldn’t be cowed by it, that we would travel.

The management conversations started about March 2nd or 3rd. What would we need — theoretically — to work remote. We should test it. My team was going to go entirely remote March 9 as a test. We decided this on March 5. It would be a full-on test. I’d be the only in the office, everyone else would work from home. I’d handle my normal duties and some of the technical duties. We’d see how the VPN would work, how workflow might happen.

March 9 was a Monday and it was a Dumpster fire in a train wreck. It was meeting after meeting and not being able to get operational stuff done, because the palace was in flames. The next day, we brought one team member in per shift. Because the message from corporate on March 9 was basically “reduce head count down to a minimum.” We were already working mostly remote, so mostly we did.

We discovered problems — computers weren’t fast enough to edit on, Internet connections weren’t fast enough to transfer files back and forth. Our dependency on Slack slowed us down sometimes. We troubleshot. We built a schedule: Who would come in and who wouldn’t. We adjusted the schedule after people said “I’m not comfortable coming in.” We had a solid few days.

And then came the decree: When we said minimum head count, we meant minimum headcount. Literally, what is the fewest number of people who can put out a daily newscast. Senior managers couldn’t come in. We took producers down to two a day for the evening and late news. The morning show team contracted. The assignment desk went remote and we spent four days fighting with a phone contractor about how to forward. We scheduled employees to come in and get their workstations, there was a pile of monitors in the front of the newsroom for anyone to grab and take home.

We transitioned from “team test” to “gone” in less than five days. It was scary, but it was an adventure.

But it really, it was the beginning of the Dumpster fire. It was the entrance to the tunnel we’re still in. To hard work under odd conditions. And to the biggest challenge most of us had ever faced.

Gimbal and Flight Control Settings

Uncategorized

Can we drone without a phone? Apps to make life easier

Tools and Toys , , , , , , , ,

(This was originally published at rjionline.org in January 2018. You can see the original here).

I’m sitting in my car in a freezing cold field in northern Missouri, waiting for a Phantom 4 Pro’s batteries to warm up so they can recharge. The car is littered with drone stuff — chargers, hand warmers, print outs of maps. But I’m also noticing how dependent I’ve become on my phone for a lot of information regarding how we fly with drones.

I’m not talking about the apps we use to fly the drones (though I have three on my phone). I’m talking about the apps that provide things like airspace clearances and maps and weather. There is no magic bullet app that does everything. And technology isn’t the sole answer to being a better drone journalist. But we’re safer when we remember that we’re pilots first and photographers second. These apps help get us there.

Unfortunately, there’s a lot of apps out there that aren’t good. So here are ones I use every day.

Airspace apps

You’ll need a couple of these to stay legal. This class of apps will tell you what class of airspace you’re in and if there are any Temporary Flight Restrictions. Some apps have additional features like weather and solar activity indices, too, though I look for accuracy in terms of airspace first and then other features second.

I use ForeFlight, which is the only mobile flight logbook app approved by the FAA. It’s for the general aviation community (and at $100/year, it’s priced for it, too) but it updates the sectional maps each month, has detailed information on every controlled airspace and includes industry-common weather forecast METARs and TAFs — as well as translating them. It also has overlays for TFRs and weather. It can be lot of overkill, but it’s a great app.

Hover is a free app that provides airspace and weather information. It’s great for what you’ll pay for it — but I’ve found the mapping is inexact especially when you might or not be in controlled airspace.  In that case, I’ll go to DroneMaps, which is a bare-bones app that does one thing well: It has the FAA’s UAS grids in it, so you can see where an airport’s controlled airspace is and how how you can fly in it.

KittyHawk, which is free, has this functionality, too, and is more of a soup-to-nuts solution. Its airspace maps are integrated into its LAANC (Low-Altitude Authorization and Notification Capability, or automated permission to fly in controlled airspace) functions. KittyHawk has positioned itself as a provider of everything, from checklists to risk assessments to airspace clearance. So its app — which has recently become free to individual users — has a lot of functionality.

Weather apps

There are so many. And there is such overlap between all of the above apps and straight weather apps that it’s hard to define a strict weather app. For what I like to call “regular people weather,” I like Weather Underground since it shows me hour-by-hour when it’s supposed to rain. Most of the time, I just look in ForeFlight. For flying, I’ll often use METARs Aviation Weather which, just like its name says, provides METAR reports for your choice of airports. I’ll also use UAVForecast for its very convenient grid of forecast flight conditions. A word of caution on this app: Its maps can be out of date.

Craft apps

The above apps are nuts-and-bolts functional apps to help you pilot safely. But there are other apps that help you do better drone journalism.

I use TPE — the acronym for the terribly named The Photographer’s Ephemeris app — almost every time I fly. It shows me the angle and direction of the Sun at any place on Earth at pretty much every time. It has 3D maps so I can see, for instance, if I’m going to be shooting in a valley or atop a ridge’s finger. Drone filter and gear maker Polar Pro makes a useful app that does a couple things: It shows you how much time until the next Golden Hour — when we get that lovely soft, diffused light that fixes all the sins in the world. It also has a filter calculator so you can put in either what filter you’re using or what shutter speed you want and it will calculate the other value for you.

Then there are the autonomous apps. For mapping and for gathering photos at regular intervals, I used Pix4D Capture, which is the free autonomous flight app for the very pricey Pix4D mapping software. It automatically flies photo (not video) missions taking pictures at whatever intervals you want. It also has a very handy free flight mode where you can hand-fly the drone while it’s taking pictures every few feet. It’s really nice for modeling. For a more cinematic approach, there’s Litchi. Litchi is an autonomous flight program that lets you program waypoints in, telling the drone to fly at X altitude to Y location and turn on its camera at whatever angle you want, then fly to the next one and the next one and so on. It allows you to make very precise, complex flight plans — and it saves them so they can be repeatable from one day to the next. It’s very handy if your news outlet is doing, say, a progression of a major building and you want to build a time-lapse video over the months.


The Fall 2018 drone highlight reel

Idea Lab, Tools and Toys

I finally got the highlight reel together, after much too long. Now it’s time for critical self-appraisal.

First, the sustains:

  1. I flew in good light. And when there wasn’t good light, I adjusted.
  2. I did a good job of color grading.
  3. My gimbal flips were solid and the rate of gimbal movement matched the rate of ascent or descent.
  4. I built my best reveal ever at :48 coming up over a ridgeline and moving diagonally.
  5. I like the music.

Now, the improves:

1. It’s :20 too long. This is largely because I couldn’t get the music to cut cleanly and still build to that strong finish.
2. That music required me to put in two shots I could have done without. The diving well shot is too static.
3. I need fewer landscape shots and more shots of active things.
4. I should fly more fearlessly. Speed-ramping hides a lot of sins here, but I’m a slow flyer.

 

Storyboxing: Visual outlining and structure

Idea Lab , ,

You have been reporting and reporting. Hours of interviews. Gigabytes of video. You’re ready to write. And then you face it, The Monolith of Your Own Making. You have so much that you don’t know where to go with it. The story is actually 13 potential stories, depending on what material you use. There’s a moment of panic, possibly accompanied by compulsive cookie eating. You have too much stuff and don’t know where to go.
I’d like you to meet a concept called “storyboxing,” which is a way to build structure for multimedia stories. It’s a visual concept and it feels a lot like outlining with one big exception: We group multimedia assets — photos, video, graphics — by themes. That allows us to move an entire theme within a story’s structure without wrecking the rest of the structure. This is predicated on a simple idea: Every asset within a theme directly supports the theme. The theme directly supports a statement about what the story is about. Therefore, every asset supports what the story is about.
Step 1: The Story Statement and the Motor
Ideally we want stories that are “narrow-deep,” tightly focused that don’t wander. So we need to start with a simple statement about the story. I’m a big believer that if you can’t summarize your story in a simple sentence, you don’t know what the story is yet. So I push our students to develop a single-sentence story statement. And because I’m not subtle, it starts with This story is about…
In our story here, the story is about the growing phenomenon of ticks biting people and making them allergic to animal proteins.  The story statement is the beginning of our contract with the audience —we want them to understand what’s going to be in the story. We want it to be narrow and focused. But we want it to reflect the depth we have in the story. The story statement is going to function like our nut graf. It’s going to provide a roadmap to us as we create the story; it’s also going to control what we do and don’t put into our story. Ideally, it will have the foundational fact of the story (essentially the story’s verb that acts on everything else) and the themes that we’re going to approach within the piece. Then we’ll right a motor, or a conflict statement. That’s what propels the story along — where our conflict statement comes from.

Story statement: A bite from a Lone Star tick can make a person allergic to meat — and Missouri’s Lone Star tick population is increasing.

Motor: This once-rare occurrence is happening a lot more than it used to and anyone who is exposed to ticks is at risk.

Step 2: Broad Thematic Areas
The end of the story statement above continues three topics or themes. That’s going to be our structure. They relate directly to and support the story’s overall idea.  I tend to use a three-theme structure, because it mimics the three-act structure that works so well in a 3-minute broadcast enterprise piece. But you can make it longer. Just remember that everything has to go directly back to the story statement.
Here, we’ve introduced three broad thematic areas:
1. A simple tick bite can have serious consequences
2. What happens after the tick bite
3.  The tick population in Missouri is getting bigger and there’s no cure. 
Step 3:  Building Waypoints into the Themes
We’ve spent a lot of time so far on developing the big pieces — what the story is about and how we’re going to get them. It’s time to get into the weeds. And that’s another advantage of storyboxing: I don’t have to think about anything except the theme I’m working on. Because if the details support the theme, everything will work out fit at the end. So let’s look at the theme “What happens after the tick bite.”  I want to hit more than just a simple idea in a theme, so I need to create a mini-outline. I call these waypoints, because they’re essentially navigational checkpoints in each theme that keep me from getting lost.  The first point I want to make in this theme is introducing my two characters, the Alpha-Gal protein and Mary Jones, my central character. Another point I want to make in this theme is the moment where everything changed in the central character’s life.
What’s the advantage of that? Why can’t we just start throwing assets into the box? Because the best stories have a macro-structure and a micro-structure. There’s a place for everything and everything has its place. The waypoints assure us that will happen.
Step 4: Attaching assets
This is the easy part. Assuming you know what your content is. Let’s say you’ve logged or transcribed your footage or whatever. All you have to do is find the right thing for the waypoint. You as yourself a simple question: “Does this directly support the waypoint?” Because if you’ve done the previous steps right, your waypoints support your themes and your themes support your story statement. This approach means you don’t have to worry about killing a darling that would take your story off wandering. Because it will never pass the “Does this directly support the waypoint?” test.
Step 5: The box
When all the assets are attached, we essentially have “themes in a box.” Everything that lines up under a theme is attached to that theme.  Each theme is complete as is. It can stand on its own. We can examine our structure from a 35,000-foot perspective. If something doesn’t fit, we can shift it around. But we’re dealing with structure at a macro level here. So we’re shifting a theme, rather than the minutiae of a single fact; that heavy lifting has already been done in the above steps.
Let’s say that we designed the story with a soft-feature top. But a new case of the disease has been reported and the news director wants it for the top of the newscast, so it needs to have a hard top beyond whatever the anchor’s intro is going to say. We can easily swap out that first theme where we develop the character for the second theme. The character-development theme slides back into the second slot and we’ve saved a bunch of time and heartburn.
That’s pretty much it. Does it work? I’ve had students use storyboxes for six years and I can see a definite difference between stories that use it and don’t. My teaching partner and I have been requiring students in our junior-level multimedia reporting class to storybox every story for the last two years. Stories are coming in more focused and roam less than they used to. And we spend less time in structural revision than we used to.
But I’ll leave the last word to one of my students who still uses it in her work at a major network: “I still go back to this when I have trouble.”
And here’s an example  a team of students did for a story.

3 things to consider about shots

Story

Another semester passes and that means it’s escape from weird b-roll. Like the shot of a cat in a story about a chimney company. Or the inexplicable shot of a college-age woman vomiting in an alley in a story about the elderly.

Thus, today’s mild rant about the concept of intentionality: the idea that every shot that goes into an edit should have a point and propel the narrative forward.

You might want to think about what you’re shooting in these terms:
1) What is the purpose of this particular shot within the narrative? Video is just another kind of sentence and every shot should have a purpose that moves the sentence/story forward. We can’t just throw shots onto the floor and see what the cat licks up. 
2) What is my intention with this shot? Is it to show the location of a pizza place? Is it to show character? Then hew to that intention. 
3) Does this move/shot make the audience conscious that it’s being made? Viewing audiences don’t like to be reminded that they’re watching something that’s being made. They are also fickle and are looking for any reason to go on to something else. You want to avoid those movements that could knock them out of the narrative by reminding them that they’re watching something.
1 2 3 4 5 >»