In this behind-the-scenes look, Postmedia News reporters Jordan Press and Mike De Souza explain how they tag-teamed to cover the rapidly evolving senators' suspension debate. They explain the technical and logistical problems they encountered along the way, and the techniques that served them well.
By Jordan Press and Mike De Souza, Postmedia
Regardless of what you think about the upper chamber and its bright red carpet, golden ceiling, wood-carved walls and murals depicting moments from Canadian history, the scandal involving senators Mike Duffy, Patrick Brazeau and Pamela Wallin—and the debate to suspend them without pay—has been a political drama unlike any other in the Senate’s history.
The only people able to see the debate happen in real-time were those sitting in the Senate chamber. As cameras were not allowed, press gallery reporters armed themselves with smartphones and laptops.
Here’s what we learned live-tweeting and live-blogging the Senate hearings:
1. Everything can be important
Much of the debate was procedural wrangling with senators referring to the convoluted rules of the Senate that are not easy to understand, even if you’re a senator. But that procedural wrangling is part of the debate. Without cameras, the debates became mostly inaccessible. Every word, action and argument was key for our followers. They wanted to know everyything—“dead air” was annoying and unnerving because they thought we were missing something crucial.
Related content on J-Source:
- Covering council: how to survive as a rookie reporter
- Question Period Live: Maclean's and J-Source dissect The House of Commons
- PressProgress: a new way of covering news from Parliament Hill
2. Add value
Colour from the chamber, such as body language or other behaviour, was helpful in illustrating and evaluating what was really going on. We added links to documents referenced during debate. We didn’t think that was a tall order, but doing that while listening to the content of the debate is tougher than it looked.
— Mike De Souza (@mikedesouza) October 29, 2013
— Jordan Press (@jordan_press) November 4, 2013
3. It’s easier to tag team
Unlike in the House of Commons, senators don’t speak in 30-second sound bites. They tend to speak in 300-second sound bites. Having one person keep tabs on the debate while the other person goes searching for value-added content was a helpful tactic. Press kept track of content with a little bit of colour; De Souza focused on everything else going on in the chamber, chiming in with debate details periodically. However, we feel this could have been better coordinated given deadlines and technical difficulties.
4. Be careful
Autocorrect, premature tweeting before completing a message and spelling errors caused some problems. An errant tweet can also distract followers from the debates going on. For example, when De Souza tried to catch a bit of colour during a speech by Sen. Claude Carignan, he noticed the government Senate leader waving a pen in his hand. The problem for De Souza was that his tweet missed a space between the words “pen is,” giving the illusion something else was floating in the air.
5. Be human
This was a complicated debate that at times left more than a few reporters and even senators trying to figure out whose suspension was being debated. When we weren’t too sure what was going on, we simply said three words: “I don’t know.” We followed that with “looking into this” and then tweeted out an answer when we had one. It made sure that while there was “dead air” online, our followers didn’t leave—they knew we were coming back with details. Other times, we just needed a mental break ourselves and did that through an irreverent tweet or observation, which also became a great way to draw more people into our feeds.
From a technical standpoint, here’s how we did it:
Tweeting was one part of an ambitious plan for our newsroom to cover the scandal from all angles, with videos, audio, alternative story formats and live blogs all working together. We have live-tweeted events before—we do it in the House of Commons regularly — but the Senate debates were different and we made a few mistakes along the way. It was, to say the least, a humbling and enlightening experience.
- De Souza went in with a BlackBerry and his personal iPhone. He almost made a key error on one of the first long nights of debate: no charging cord. Lesson learned: Bring a charger, an extra battery, especially if you’re going to tweet pictures and videos, as De Souza found that drained his battery faster.
- For tweeting, De Souza used the BlackBerry Twitter app. Why only the BlackBerry? Mainly for mobility and convenience. A laptop is more helpful if you’re the one writing the story. Speaking of which…
- Press went in with a laptop, his work and personal iPhones, USB charging cord for the iPhone and—of course—a charging cord for his Macbook Pro. Why all the gear? There is no Wi-Fi in the Senate chamber, so the work iPhone was used to create a personal hotspot.
- Press used a combination of Hootsuite (the platform he generally uses) and Twitter to tweet. Why the two platforms? At one point, the Twitter website locked him out, saying he had reached his tweet quota for the day. A jump to Hootsuite changed that. The two platforms also meant that while one message was going out, he could use the other to start on another missive. Hootsuite made it easier to keep track of what everyone in the Senate chamber was tweeting, while the Twitter website was easier to use to track all interactions online.
- Why the two phones? Backups, backups, backups: If either Hootsuite or Twitter was down or the hot spot died (all of which happened at various points during the debates—and even during the final vote), there was a back up device ready to get the information out.
- The devices were also helpful for recording scrums on SoundCloud and adding them to our Twitter and liveblog stream. This was a good idea for two reasons: First, it gave our followers raw audio to put themselves in our shoes; secondly, it allowed a free body back in the newsroom to transcribe any quotes.
Related content on J-Source: