Rabu, 14 Mei 2014

Nieman Journalism Lab

Nieman Journalism Lab


Is your news site too slow? Probably, though The Guardian’s trying to speed theirs up

Posted: 13 May 2014 11:30 AM PDT

Web publishers face a quandary in 2014: User expectations for how quickly a website will load are getting faster and faster. But web pages keep getting fatter and fatter, adding custom fonts, bigger art, more video, and more complex JavaScript into the mix. Our 3G reality often falls short of our broadband dreams.

guardian_logoPatrick Hamman at The Guardian gave an interesting talk last week at the FrontTrends conference in Warsaw about how they’re trying to make theguardian.com load a lot faster in its new, responsive design, and there are a lot of ideas in here ready to be stolen by other news site developers. One remarkable fact: A Guardian audience survey found that, of 17 key product drivers, the speed of the site ranked No. 2, behind only whether content was easy to find or not.

A couple of the main ideas:

The order in which a page’s assets load is critical to user perception. Load the most important parts (for a news article, the headline and text) first and load everything else (related stories, ads, comments, bottom nav, etc.) later. Let your user get started with the task she wants to complete right away. (He even suggests inlining CSS in some cases, long considered a little déclassé in modern web circles.) There’s plenty of good stuff about progressive enhancement and lazy loading if you want to learn more.

Determine what an acceptable load time is — set your time budget, in other words — and test, improve, and iterate your way until you hit that goal. I loved this screenshot of a metrics email bragging that the new Guardian site was “142% faster than NY Times”:

guardian-pageload-nytimes

More about the Guardian redesign, including code, on GitHub.

The Texas Tribune launches its new combination op-ed page/sponsored content pitch

Posted: 13 May 2014 10:52 AM PDT

We told you back in November that the Texas Tribune — as successful a news nonprofit, pound for pound, as exists in this country — was trying to get a piece of that sponsored content pie with something called TribTalk.

Well, it launched today. Tribune editor (and, full disclosure, my former colleague at The Dallas Morning News) Emily Ramshaw:

TribTalk will feature pointed, provocative perspectives on Texas politics and policy — from campaigns and elections to education, health care, immigration, transportation, criminal justice, energy and the environment. The thought leaders who write for the site will be both well known and unsung, predictable and unexpected, established and emerging. We hope their contributions will make for the same compelling reading, viewing and listening you've come to expect from the Tribune. We're also accepting columns submitted by readers like you. If you'd like to write for TribTalk, learn how here.

The TribTalk media kit has further details: looks like $2,500 for a piece of sponsored content that’ll be on TribTalk’s homepage for three days and $12,500 for a rich-media, large-format ad that’ll run for 30 days. Sponsored posts will have comments open (moderated by TribTalk staff, not the advertiser) and will stay online indefinitely, unlike at some other outlets where the url is taken down when the paid period ends.

Sponsored content makes journalists feel uneasy, often for good reason — the idea that the ad’s similarity to editorial content is a selling point doesn’t give reporters the warm fuzzies. The TribTalk media kit rides that difficult edge, saying on one hand:

The treatment and design of sponsored content will be clearly differentiated from other submitted and solicited op-eds.

…but also:

Sponsored content will mirror the design of the rest of the site's content and reside in line with it, offering the same functionality as editorial content.

If you’re looking at the TribTalk homepage, the paid posts are pretty well distinguished, visually:

tribtalk-sponsored-content-texas-tribune

But on the article page level, I wouldn’t be shocked if the relatively minor cues — a small Paid Placement banner at top and a grey background — weren’t significant to make it clear what’s paid and what’s not. Imagine reaching one of these articles from a link on Twitter — I think there’s a good chance you wouldn’t pick up on the fact that the second one is an ad.

tribtalk-texas-tribune-notpaid

tribtalk-texas-tribune-paid.jpg

Still, the TribTalk site looks different enough from the (more handsome) main Tribune site that I don’t think the main brand would face much blowback from a misstep. (Consider the contrast with, say, The New York Times’ paid post efforts. At the Times, the straight news and the op-eds look a lot alike, but the paid posts look quite different; at the Tribune, the op-eds and the paid posts look a lot alike, but the straight news looks quite different.)

The Trib’s success is deeply tied with the corporate financial power that surrounds around Texas state government. It gets a substantial share of its revenue from them — more than $2 million from corporate underwriting and sponsored events last year — and the presence of all that money helps makes its model more viable than it might be in, say, Helena or Pierre. If you don’t like that, you’re not likely to like TribTalk. If that doesn’t bother you — if you see this form as just another kind of advertorial, or if you think that revenue paying for a lot of very good journalists is an acceptable tradeoff — then you probably won’t mind it.

Selasa, 13 Mei 2014

Nieman Journalism Lab

Nieman Journalism Lab


Why is The Washington Post holding a live event in Boston?

Posted: 12 May 2014 09:07 AM PDT

In a well-appointed banquet hall at the Westin Boston Waterfront, a balding, disturbingly energetic man in a red bow tie is holding forth on baby boomers, technology, and aging.

"We are not young, but we are youthful," enthuses Joseph Coughlin, director of the MIT AgeLab. A bit later: "And by the way, we never talk about the F-word when it comes to aging: fun!" Well, I suppose.

I had come to the Westin last Thursday for a program called Booming Tech, presented by The Washington Post as part of its Washington Post Live video series. I was less interested in the subject matter — how boomers getting along in years are enhancing their lives with digital technology — than I was in finding out what the Post was up to.

At a time when newspapers are scrambling to make money any way they can, Washington Post Live struck me as unusual and innovative. The two-hour-plus event, moderated by Washington Post Live editor Mary Jordan (with an assist from Sacha Pfeiffer of Boston public radio station WBUR), featured panels on tech and entrepreneurship, a conversation with health-care expert (and Massachusetts gubernatorial candidate) Don Berwick, and a closing one-on-one between Jordan and humorist/curmudgeon P.J. O'Rourke, who was on hand to flog a new book. (Jordan: “Do you like your cell phone at least?” O'Rourke: “No.”)

So how does all this fit with the Post's business strategy? I snagged Tim Condon, the Post's director of new ventures and interim general manager of Washington Post Live, for some insight. (Two days earlier, the Post had announced that former Bloomberg executive Robert Bierman will be taking over as the permanent general manager.)

Washington Post Live launched in 2011, well before Amazon.com founder Jeff Bezos acquired the Post. The idea, Condon said, is to reach an "influential audience," usually in Washington but occasionally outside the Beltway. He described the venture as both journalism and business, and said the Post hosts between 20 and 30 such events each year.

"The content that comes from these discussions are our journalism," Condon said. And though the events are free, they are paid for by underwriters — in this case, the AARP, which was holding a national conference called Life@50+ next door at the Boston Convention and Exhibition Center.

Washington Post Live events are free and open to the public, and other news organizations are invited to cover them as well. The compare-and-contrast that comes to mind is the Post's ill-conceived plan in 2009 to host $25,000 off-the-record salons with the paper's journalists in publisher Katharine Weymouth's home (a fiasco I wrote about at the time for The Guardian).

The Booming Tech event at the Westin featured, inevitably, its own hashtag (#techboomers). About 100 people were on hand, but many of them seemed younger than I — and I've been fending off AARP mailers for the better part of the past decade.

The proceedings were webcast live, and video highlights have been posted. A publication of some sort will follow, Jordan told the audience, after a second "Booming Tech" is held in San Diego on September 4. The idea of the Post holding events far outside its circulation area would seem to line up well with its recent move to give subscribers of some other newspapers digital access to the Post; both aim to extend the power of Post content outside its traditional boundaries.

In his conversation with Jordan, P.J. O'Rourke insisted that he is "not a Luddite," explaining: "A Luddite wants to destroy tech…I just want to point out that there will be tears before bedtime for a long time."

As with so many news organizations, technology has led to a lot of tears at The Washington Post, transforming the paper from a highly profitable enterprise into a money loser hoping that some of Bezos' Amazon fairy dust will somehow rub off.

Washington Post Live is certainly not the answer to the Post's woes, or to those of the news business in general. But it's nevertheless an interesting idea that at least partly answers the question: "Where do we go from here?"

Dan Kennedy is an assistant professor of journalism at Northeastern University and a panelist on Beat the Press, a weekly media program on WGBH-TV Boston. His blog, Media Nation, is online at dankennedy.net. His most recent book, The Wired City: Reimagining Journalism and Civic Life in the Post-Newspaper Age, tracks the rise of online community news projects.

Immediacy vs. importance: The tension underlying how the NYTimes.com homepage gets made

Posted: 12 May 2014 08:06 AM PDT

Editor’s note: Nieman Lab friend and contributor Nikki Usher is out with a remarkable new book, Making News at The New York Times. It’s the result of five months she spent immersed in the Times’ newsroom in early 2010, observing newsroom culture, watching how news turned into stories, and seeing how new norms of digital journalism were established inside America’s premier news organization. (You can read the book online.)

Our own Joseph Lichterman has a Q&A with Nikki, but we also wanted to give you a taste of her findings. Here’s an excerpt from Chapter 3, “The Irony of Immediacy,” which focuses on how perhaps the most watched space in digital journalism — the homepage of NYTimes.com — gets assembled.

One final note: Remember, this is a snapshot from 2010 — a long time ago in web time. People really like to talk about the Times, so I’ll just note that, while elements of any company’s culture persist over time, what Nikki observed then shouldn’t be taken as a perfect reflection of the Times in 2014.

Online newswork departed from the regularly scheduled process of decision making, planning, and editing a story that dominates print production. In fact, it operated according to an entirely different rhythm. Production for the web was a frenetic activity, often with little clear strategy about how, when, and why stories should be posted. Online news production was largely a response to the perceived pressure of immediacy, defined as ASAP, constant updates for online journalism — and in parallel, immediacy emerged as a value that structured and ordered newswork and gave journalists a particular vision of their role as professionals.

Yet journalists did not speak directly about “immediacy.” Editors could not explain to me why they thought stories should be updated as quickly as new information was available, and web producers could not explain to me why they believed there was a need to keep the pages constantly updated, or looking “fresh.” “Fresh” was a quality that web producers and others charged with online journalism associated with their presumed sense of what the audience wanted: something new, something different. But just like “feel” or “news sense,” “fresh” depended on a journalist’s (most often a web editor or web producer’s) individual judgment, honed from the time they’d spent thinking about web production. Determining what is “fresh” is one way to explain how journalists tried to make sense of the constant presence of a never-ending deadline in the digital age.

“Fresh” was also one way for journalists to deal with the fact that they had no control over when audiences might be clicking on web content. However, they did know that, at least at the Times, there were always thousands of people looking at the web page at any given time. The goal was to keep them coming back. The understanding from journalists working on the web was that fresh content was better. Updated content brought in new readers or kept readers coming back, so the homepage could not be static, or at least not for very long. The morning newspaper delivered to your home (if you got one) should look nothing like the homepage you opened at work in the morning.

What the homepage editor did during the day, when most people were getting their news online, was relatively unstructured. While the homepage editor had some sense of when he would add new stories to the page, there were no conversations between him and the managing editors or executive editors, for example, about which stories should remain in place during the day. Instead, it was up to the day’s homepage editor and the continuous news editor, Pat Lyons, to make these decisions.

I asked associate managing editor Jim Roberts why there were no formal web meetings like the print meetings to decide coverage and story placement. He told me, “You’ve seen how fast the web moves. You can’t sit around and plan for that. It’s too quick for people to stand around and debate.” This comment was a clear recognition that the print process couldn’t work for the web. There were some meetings that lasted no more than 10 or 15 minutes, and they didn’t offer much guidance about which stories should lead the homepage and when. The morning web meeting was an opportunity for journalists to tell other staff what stories might be coming down the pipeline, but the homepage editor I followed over the course of one morning, Mick Sussman, said he rarely paid attention to this meeting. In fact, he admitted that he couldn’t hear it from his desk. Decisions as to what column of the web page to put a story in, or how to order the stories, or how long to keep a story in place, were the kinds of things left up to the homepage editor and his or her supervisor, not decisions made by committee — particularly during the day, when most people in the United States come to the site.

And in the evening, there were two “handoff” meetings to make web producers from around the newsroom aware of content from across other sections and to inform the night homepage editor. But there was no debate over homepage play, no extended discussion over what stories merited the most attention, and very little conversation about the stories themselves — just reading down a list of what stories were available. In this sense, consider that an editor for print could spend his or her day in meetings talking about story placement, while on the web, there were virtually no meetings that offered the same kind of opportunities.

Instead, in looking at the online rhythms of web production on NYTimes.com, the picture that emerges is not one that involves many actors, but instead focuses on the activities of a single individual. Thus, in looking at the homepage editors and the online business editor, we get a sense of the rhythm of each page, a rhythm that is articulated through the vantage point of one person. This is distinct from what we saw in the print rhythms, where the portrait of newswork is an extensive detailing of collaborative discussions. The close-ups of individual web editors/producers, though, underscore the imperative of immediacy that faced the online newsroom.

Rhythms on the homepage: Daytime

On April 2, 2010, I spent the day with Mick Sussman, one of the morning homepage producers for the U.S. edition. His shift was from 7 a.m. to 3 p.m. He explained to me that his goal was to have something new up on the homepage about every 10 minutes (keeping the page looking “fresh”). The big changes that he made were in the “A” column, or the leftmost column going down the homepage; the photo spot, which he tried to change every 30 minutes; and the “B” column, or the column underneath the photo spot, which was a prime spot for a news story other than the top of the “A” column. Sussman was also constantly rotating out blogs in the “on the blogs” section, but he admitted, for instance, that he didn’t have much knowledge about style or sports, so he often relied upon other people to alert him when something was important.

nytimes-04032010

Sussman had to write headlines for nearly all the stories he put up on the homepage, though Pat Lyons, the continuing news editor who, in theory, supervised him, would offer suggestions, as would other editors and web producers via IM. Sussman also often had to write the web summaries for the stories (the short blurbs under the headlines), though he relied on what came from copy editors or the web editors. But the nuances of the web page itself often demanded that he do the last-minute editing of these summaries before they went in front of millions of NYTimes.com readers, often going up without any kind of editorial oversight other than his own news judgment and copyediting skills. Lyons would provide feedback if something needed to be tweaked, but this was a publish-first mentality. As I watched Sussman work, I noticed how much hand coding and manipulation of the website he had to do: his job involved not only journalistic judgment but also considerable web skills.

When a new story popped up in his queue, usually over IM, Sussman would send a headline to Lyons, also over IM. If Lyons didn’t respond, Sussman would just put up a headline. When I was observing Sussman, he asked Lyons about putting up a story on a conspiracy movie. When Lyons didn’t respond, Sussman put the story up. His justification was, “I think this is pretty interesting,” and he noted that he always liked conspiracy stories. For about half an hour, this story was in the section right underneath the main photo on the homepage — a prominent spot. This is an indication of the latitude that Sussman had over the page, shaping it to his own interests. A few minutes later, the foreign desk alerted him to a story on Saudi Arabia, and Sussman decided to put this story on the homepage. While these stories often went through layers of debate and discussion at each individual desk, their quality depended on this editorial judgment. A breaking story, for example, might be headed to Sussman without quality checks. To some degree, Sussman depended on the quality of work provided to him. However, Sussman was ultimately in control of who saw what story, and for how long, on the web.

Sussman explained that his goal was to balance the homepage content so it was distributed evenly among all of the different sections of the newspaper (a goal echoed by other homepage editors). His other, perhaps most important duty was to keep the news constantly updated in order to make sure that NYTimes.com had both the latest content and new content, so people would have reason to keep coming back to the page. “In six hours, there should be a complete turnover of the page,” he noted. “There is an imperative to keep the page looking fresh for readers, so I am constantly tinkering with it, looking at blogs, reading subpages, and seeing if there is other content to pull up for the page.”

When I watched him, he spent most of his morning preparing for the jobs-numbers story. First, he had to prepare an alert, and then he had to deal with constant changes to the headline for this particular month’s story (the April 2010 numbers). Sussman also checked to make sure that the Times hadn’t missed anything by watching the wires when he had a chance.

Noon EST was a big time for updates to the homepage, as many people would check the web during their lunch break. Sussman put entirely fresh content on the homepage, such as a story about attacks in Israel and a Times feature story on Senator Kirsten Gillibrand.

On his own, Sussman learned that President Obama was speaking at noon, and decided to make sure he had a video link on the homepage so the president could be featured. Sussman made three other major updates to the B column while I watched him.

Each major update consisted of changing the big picture on the homepage. The course of the afternoon went as follows: At 1 p.m. Sussman’s first update was to put in TimesCast, the five-minute Times video that included (at the time) some highlights of the Page One meeting and interviews with reporters about breaking news. At 2 p.m., he put a photo of President Obama speaking in the main picture space. He then inserted international news into the second slot, underneath the jobs report. Then, by 3 p.m., he had made another major switch, moving news about New Jersey governor Chris Christie into the column beneath the main photo. All of these changes seemed a bit superficial — but they each made the homepage look completely different.

None of the other editors was consulted when Sussman made these changes. To be even more clear: one person was writing the web headlines, as well as the copy that went underneath these headlines. One person for millions of potential readers. And there was no copy editor for these web headlines.

While other people in the newsroom IMed Sussman with suggestions for web summaries and headlines, only he knew exactly what would fit together on the homepage. And ironically, most of the time, he was only giving a very quick read to any of these stories, if he read them at all. His attention was focused on the lead of the story, the headline given by the desk, and the guidance of other web producers. As far as I could tell, he wasn’t making any errors, but the entire process seemed like it could leave the homepage vulnerable to mistakes. Yet the system did seem to work. Only rarely did anyone in the newsroom complain that a web summary did not represent a news story — and of course, that could quickly be changed.

Sussman had figured out a routine to keep the Times’ homepage constantly looking different. Roughly, the rules went something like this: He would put up a new blog post every 10 minutes, which he culled from his RSS feed. Some repositioning of stories took place every 20 to 30 minutes. New stories were added as they came up, if they seemed to meet Sussman’s internal criteria of newsworthiness. A major, visible change to the homepage was made every hour. Sussman checked the competition three times on the day I shadowed him (CNN, BBC, The Washington Post, The Wall Street Journal) but only once mentioned a competitor’s story to Lyons. Rather, he was preoccupied with updating the homepage with Times content and wasn’t paying much attention to anything else.

He barely had time to run up to the cafeteria during the day, and he made sure to do so at about 11:20 in order to be ready for the big noon push. Sussman had tried to make the continual rotation of stories more predictable and routine, but it depended on everyone else in the newsroom feeding him a continuous supply. At a place like The New York Times, with over one thousand people in one building, as well as the International Herald Tribune staff in Hong Kong and Paris, keeping updated original content on the homepage was quite possible, during the New York news day at least. Nighttime presented different challenges, as we will see next. But for the day homepage editor, immediacy, with some undefined sense of “freshness,” ultimately influenced almost everything, from when Sussman ate to his near-continuous workday spent changing and updating content on NYTimes.com.

Where print and online converge in online production

Ironically, while the immediacy of trying to keep the page updated seems to reign during the day, night production of the homepage online relies on cues from the print paper. In this odd way, the two newsrooms converge. The night homepage editor was still concerned with keeping the web page “fresh,” but she had also been instructed to use the guidance of the front page and section editors when selecting news stories for the homepage. And the locus of production of most of the news, the New York bureau, shuts down for paper deadlines in the evening, so the amount of brand-new news that can be placed on the website slows to a trickle.

The night I observed Lillie Dremeaux, April 5, 2010, was also the night of the worst mine disaster in American history. Thus, I got to witness Dremeaux in an on-demand, breaking-news environment, where her web summaries would be the latest anyone coming to NYTimes.com would know about the disaster if they happened to just want a quick headline. Each subsequent web summary that night changed as more details of the story became clear. Thus, Dremeaux’s job took on added importance. She was not just refreshing the homepage to keep things looking interesting; she was also refreshing the homepage with the breaking news coming out of the disaster.

nytimes-04062010

At first glance, her routine was much the same as Sussman’s. She was in constant communication with night editor Gerry Mullany about when new copy would be available from the copy desk, as by this time of the night, most breaking stories were now in their final form, and feature stories set for the print paper were being prepared for the print deadline. Like Sussman, she was continually bombarded by IMs from other web producers with requests to get their desks’ content on the homepage. She also seemed to be making constant changes to the page, and she kept only a minor eye on the competition — with this research never affecting what stories she chose to put where — though she did make a note in an email of which competitors she checked.

Dremeaux paid attention to one of the two night web meetings, the 7 p.m. meeting, where web producers informed each other and Mullany of what content was available. This meeting was to help Dremeaux know what the big stories for the day had been, and each web producer from each desk had the chance to pitch his or her big stories for homepage play. In addition, as the night homepage producer, Dremeaux was also guided by the decisions made by print editors. But it would be up to Dremeaux to decide when, where, and for how long material would appear on the homepage. Her goal was to give each section’s strongest dress page story (or printed section story) play on the front page for at least some period of time.

Over the course of the night, the homepage became increasingly static and began to look more and more like the print paper. Around 9 p.m., Dremeaux printed out a mockup used to guide the print Page One designers that showed where each story on Page One would go. This mockup guided where she placed each story. Using the visual cues about the most important story in the paper (the lead story in the righthand column) and the off-lead (in the left-hand column), she would place these pieces in the most prominent places on the website (the A column or under the B column). She would also be sure to have the other stories that made Page One in prominent places. As Dremeaux put it:

The front page tells me what are the five or six most important stories of the day. I follow that because there are some really important editors — the most important editors at the Times — saying that this is what we think is important. And the homepage should reflect that.

Strangely enough, the homepage late in the evening was most like the paper people would see in the morning. In fact, the individual section pages were remotely copy edited — by a university professor. Web producers could not go home until they had gotten their “Cowling note,” a brief email that alerted them to capitalization issues, spelling problems, and so on. As web producer Cate Doty noted, “The website is most edited when no one is looking at it.”

Dremeaux had an added constraint that Sussman did not — she had to make sure that there was enough new content to keep the homepage looking “fresh” in the morning. Since the homepage had already run through many stories throughout the day, Dremeaux had to be careful to save some of the major stories of the evening (which would be in the print paper the next day) for the morning.

This way, the following morning, when no new news of major significance to U.S. readers had yet occurred, and very few U.S. reporters were on duty, there would still be new content for the page. Thus, the need to keep things “fresh” by keeping the website looking new can be seen as a recent constraint on newswork in the sense that it might shelve news for a little while. In such a case, keeping things fresh may actually make them, like day-old bread, a little bit stale. Immediacy imposes a driven focus for new content on journalists and the web page, but when there isn’t any (or enough) new content, the website tried to balance the desire to keep the homepage looking ASAP with the reality that journalism is not, in the end, ASAP at the Times, at least most of the time.

Still, by the time most people woke up, the homepage would look completely different from Dremeaux’s carefully matched headlines and the carefully edited section pages, with the news that had come in from the foreign desk and the business desk heading the site, and the homepage producer cycling in the remainder of the material that hadn’t made the homepage the night before. As Doty put it:

The interesting thing is that when I wake up at 10:30 the whole website is different. So the website is totally edited when no one is watching. The page will look completely different from now [12 a.m.] to the morning so that’s kind of a fascinating thing to note.

Thus, the life of the homepage producer revealed some particularly important online imperatives and values at the Times. There was considerable importance placed on keeping the web page looking as fresh as possible, particularly throughout the workday. The homepage producer employed the breadth of content available throughout the Times to make this possible. What Sussman and Dremeaux did each day didn’t vary much, and both had their own routines. However, what stories to place where, in the end, was up to them, with perhaps limited supervision from their editors. Writing the web summaries and the headlines fell down to one or two pairs of eyes, at most, versus the multiple rounds of copy edits for a news article. The homepage producers had considerably more latitude and less oversight than anyone working on the print side of the newspaper, and for the most part, they were making decisions about which stories were most important based on what news happened to be available at each particular moment.

Online rhythms on the business desk

Most days when I was doing my research, I would get into the newsroom in the morning and prop myself up comfortably in a chair next to Mark Getzfred, the online editor for the business section, before heading off to do any other research. Some highlights from his work days, which began when he took the train at 6 a.m. from his home in Connecticut and read on his BlackBerry and Kindle until he arrived in New York by 7:30 a.m. or so, then ran to at least 5:30 or 6 p.m., show how the business desk attempted to fill the need for online content. Like Sussman, Getzfred took to his job with intensity, underscoring the obsession with the new and what was now online.

Getzfred began his day trying to find fresh stories for the business web page and the business global page (the main business pages) that had not been in the business section the night before. He started by searching through International Herald Tribune content that had come in from the night before; the business desk relied on the content from the partnership with this paper owned by The New York Times Co. to help fill the morning edition.

So, for instance, on January 12, 2010, he spent his morning (as he did most mornings) reframing a story from the Asia bureau of the International Herald Tribune on Japan Airlines’ struggles with bankruptcy, just to get something new on the page. He followed this up with a story on Airbus, the European airline manufacturer, another story that had come from the IHT. Both stories went up (though in different places) on each of the business pages.

He would constantly scan the wires, and he would begin rewriting a markets story even before the U.S. markets opened. An Asia-based writer would have left off this story in the very early hours of the U.S. morning, it would have been picked up by the European markets writer in the Paris bureau of the IHT by early morning U.S. time, and then Getzfred would begin filling in the details about premarket trading in the United States, gleaning content from the wires. He noted that this was one of the most popular stories on the site — “people like reading about markets and we give it a little context” (again emphasizing how the Times hoped it was providing value-added content). Around 9:45 a.m., he stopped for a brief 15-minute meeting to discuss what was going to be available on the website with the other web editors. This was the meeting that Sussman said he couldn’t hear — despite the fact that this was one of the few moments when web editors got together to talk about stories. Notably, this meeting only described what was available and the importance of these stories at a particular moment.

He would then rush back downstairs and continue to rearrange the business pages. He explained to me on March 1, 2010, his sense of the pressure that he felt on the web: “There is some pressure, but it’s not like we are 24-hour news with always something to fill. But there is some pressure.” And then he began filling the business pages with a series of stories that would generally be trivial by the end of the day, either inside the print paper or not even present at all, such as any story about economic indicators, hearings, or reports. A typical story from that day was one he took from the wires about the fact that personal spending was up at the expense of the personal savings rate. Another was still more about the ongoing Toyota brake failures. He explained: “Akio Toyoda apologized again…[It] probably won’t go in the paper.”

nytimes-03022010

Getzfred told me later that these stories were nonetheless likely to make the homepage, as “the homepage, particularly in the morning, is always looking for news. They want something fresh they can put up there.” While Getzfred declined to say he was working at an immediate pace, he rarely took breaks, even for lunch. His focus was, indeed, on keeping the web page looking new, in part because Times readers, as he put it, “wanted to see something else,” and “we have to respond to what is changing throughout the day.”

On that March morning, he IMed Lyons, the editor who worked closely with Sussman, to alert him that a Federal Reserve Board member would be retiring. His IM said something to the effect of “Donald Kohn is retiring,” to which Lyons replied, “Who is that?” Getzfred explained, and Lyons IMed back to note that they didn’t have much, so it would go on the homepage — even though Lyons didn’t have any idea who Kohn was. The homepage in the morning and the business page in the morning were both hungry for news, even news that wasn’t of much substance, as long as it could be cycled into the spots for readers with news from the day, rather than news from yesterday.

Getzfred continued most of his day filling content as he could with wire stories and updates from reporters and keeping the markets story up to date. He would shuffle around stories and put in new Times content when he had it, but most of the time, new substantive stories from the business desk, the kind talked about in the news meetings, weren’t ready during the day. So as a result, the business page during the day was a mix of blog posts being pushed out by the six or so major blogs and small chunks of news — unless there was something major brewing.

Getzfred spent his day hunched over the computer, constantly scanning stories, rewriting AP content, making sure that his markets reporter was staying on task, and keeping the business web page filled with new content as soon as he had some. Notably, this was not even always “good” content, content that would even be talked about in Times news meetings; it was just new. Stories about corn subsidies, for example, might be leading the page for a good part of the morning — until 10 or 11, when some better content might be flowing in from more substantial Times news. In most cases, there was likely only one story that could really feed the business page with original, print-discussion-worthy content until later in the afternoon or evening.

Getzfred was also the first line of defense for making sure that breaking news got on the website as fast as possible. On January 12, 2010, that meant making sure the Times had two fairly important updates. The first came around 5 p.m., when the Times’ media writer Bill Carter got a scoop that Conan O’Brien would refuse to be The Tonight Show host if Jay Leno was moved back to his old 11:35 p.m. slot. At the time, this was big news: The Times was the first news organization to have news about O’Brien’s decision.

The second was a bigger story, and it underscores the rush to get out big news. Though January 12, 2010, was the day that the Haiti earthquake struck around 5 p.m., EST, no mention of this was made around the business desk. Instead, the news that had Getzfred and the rest of the business desk in breaking-news mode was Google’s announcement that it was — for now — pulling out of China because of security breaches.

The news was broken on the tech blog Bits. Getzfred then alerted the homepage to the news. The homepage didn’t like the wording and, after briefly posting the Bits blog, took it down and put up an AP story. Getzfred quickly wrote a roughly three-paragraph story on the statement to give a “staff presence on the page” and also to give the main reporters for the story a running start. Bits then reposted a new version, which Getzfred passed to the homepage, which the homepage liked. The full article then followed, updating Getzfred’s headline version, which stayed on the homepage until something more substantial was ready. Getzfred was motivated by speed and by his sense of pride in having a Times stamp on the story.

“Update, update, update” was the unwritten mantra for Getzfred, and as such, he kept a steady stream of stories flowing on to the business page website. When the business page went through an update in April 2010 to focus on even more immediate material, with the goal of highlighting new stories throughout the day, the emphasis on newness and constant updates only increased.

After reading a draft version of this book, Getzfred thought this made him appear like he was waiting for news to happen, when in fact, he felt that he was actively preparing for scheduled events he knew would generate news, working with reporters to generate prepared matter to respond to these news events, and making sure that stories were available as soon as possible on the web. Notably, though, this focus on the now, this ASAP need for content, underscores the importance of immediacy in online web rhythms. Though the print and web business pages started to converge in the evening, in part due to the slower trickle of content, the felt imperative during the day was for more new content, now. The business web page, and the homepage too, both paused online as The New York Times in New York went to bed, but in the morning, what was there would be gone, and the cycle would begin once again.

Print and online routines

Thus, two dynamics were at play, print and online, and ultimately, print was the most important factor, not least because it occupied the value system that was most dear to traditional journalists. Immediacy meant two different things in a newsroom that had two processes of newswork ongoing at the same time. There was both the old world of immediacy, where breaking news meant tomorrow, and the new world of immediacy in online journalism, where immediacy meant “fresh” constant updates and where the homepage would not look the same in any way after six hours.

The print news cycle ultimately fed the homepage and the business web page with content — but generally, it took until the end of the day for the authority of print news to begin to inform how web stories would look online and what prominence they would have. By that point, most people would not be paying attention to NYTimes.com. By 9 p.m., when the major print stories for the day had been fully fleshed out, copy edited, and prepared, the homepage finally began to stop its immediate churn. The homepage editor, though, didn’t need any raw numbers or traffic data to have the sense that most people had long ago signed off of NYTimes.com, at least among readers in the United States, and that the busy focus on keeping readers on the page had long subsided. In fact, these numbers were not readily available to the web editors.

Yet by morning, the important stories from the print paper — the value-added content, the front-page stories — would be quickly washed away by stories with relatively small bits of significance. Sussman would be left with the previous night’s leftovers, some foreign stories coming in during the day, and filler stories from desks like business that were of such little significance that they might not even make the print paper.

On the other hand, we might see the website as doing quite well according to Times standards, despite moving so quickly. Even without the layers of editorial judgment, those charged with constantly updating the website do it well; they are trusted for their facile judgment and their competency as headline writers and copy editors, all their work done rapidly. These web editors have their own sense of traditional news norms; they do weigh the importance of each story, given the significance to readers — though in practice, this may not always work in the quest for “fresh” content, as we see with Getzfred and the early-morning business web page.

The compulsion to continually keep providing more content had become woven into the fabric of NYTimes.com; immediacy has created a system of worth, order, practice, and routine for online journalism. In this way, what journalists spoke of as “fresh,” and I conceptualize as immediacy, takes its shape as an emergent value of online journalism at the Times. Immediacy ordered how the majority of Times readers would see the newspaper’s content. What is missing from this conversation is the “why” for the focus on online updating. This had become incorporated into how web journalists understood their mission — and their sense of what was important — but other than the simple explanation that readers wanted to see what was new, there was little reflection on what made immediacy important. This further suggests that this value was emerging, as journalists had yet to define and truly reflect on its importance, beyond daily routine.

Culturally, NYTimes.com was not the print newspaper: there were no long meetings; multiple editors did not labor over what stories were placed where; and online moved quickly, all thanks to the imperative that more readers should see new content. Decisions were left to two people, generally, rather than a group of people debating what would be the agenda for the day. Perhaps at the end of the night, print created a pause, but during the day, a visitor to NYTimes.com would have no clear insight into what the “11 men and 7 women with the power to decide what was important in the world” considered the most important stories.

The great irony for this newspaper was that immediacy was a compulsion, but print remained, at least for the time, more important in setting the tone and significance for news stories in the daily rhythms of top editors and traditional journalists’ senses of order. The seemingly clear rules of print production did not always (and often did not) meet the needs of online news production. Thus, news making based on these two value systems suggested competing work routines. What we see is the process for shaping and creating public-facing content for readers, both print and online.

The tension between print and online immediacy is particularly poignant for traditional reporters, who must serve two masters. Though print matters more, the daily process of the web often captures their attention — creating competing pressures. For journalists, this uncertainty is often unwelcome and makes their lives quite difficult.

Screenshots of NYTimes.com front pages are from the end of the days cited in the text, after midnight, which is why they are dated the following day.

Photo of the Times building by Alexander Torrenegrea used under a Creative Commons license.

Culture change is hard: What Nikki Usher learned in five months embedded in The New York Times newsroom

Posted: 12 May 2014 08:06 AM PDT

In the early afternoon of January 27, 2010, The New York Times’ tech team was ready for breaking news: Apple was set to unveil its long-anticipated tablet computer.

As Steve Jobs prepared to take the stage, Times tech blogger Nick Bilton was preparing to scour the Internet for information on the yet-to-be-named tablet and feed information to the Times’ liveblog. The hype was huge, and readers were desperate for information on the tablet — not least its name. George Washington University professor (and frequent Nieman Lab contributor) Nikki Usher describes the scene in her new book, Making News at The New York Times:

Bilton was shouting out information to his editors, but it wasn't clear how this was getting incorporated back into the liveblog. "The wireless just went out in the room," he said. Then a few minutes later, when it was back on, he went back into monitoring mode. He shouted, "It's starting," as the tech staff in New York wasn't getting much of anything from their staff. Slowly, the tightly edited bits of information began to appear on The Times liveblog.

Bilton saw the name on a competing blog — “iPad, they just said it!” — and immediately tweeted it. The Times' home page editor was ready for the announcement right away with a red alert right underneath the "The New York Times" banner: "Jobs announces new tablet will be called the iPad." But the Times' liveblog took two minutes to get the name up. The Times' home page then put up a link to the liveblog after some wrangling.

Usher spent five months in early 2010 embedded in the Times newsroom, studying its culture and how it was transitioning to the digital era. Usher’s ethnography provides a snapshot of how Times reporters worked their beats, how traditional reporters interacted with multimedia and interactive staffs, how NYTimes.com was managed, and more. The detailed portrait of the newsroom takes readers behind the scenes and illustrates how the paper of record was adapting to the Internet. For instance, Usher describes when DealBook’s Andrew Ross Sorkin learned about TweetDeck for the first time:

"What is it?" Sorkin asked. [Weekend business editor David] Joachim explained the advantages of using this site over the main Twitter platform: "You can post the whole URL instead of going to that link shortening thing [Bitly]. And it updates to Facebook automatically."

Though the book’s events take place in 2010, much of what Usher writes about is still relevant today — the cultural issues the Times was facing then still, to varying degrees, face it and other newsrooms. (See last week’s internal report on how the Times newsroom could continue to evolve and innovate digitally.)

I talked with NIkki about her new book and the lessons that can be gleaned from it; here’s a lightly edited transcript. (You’ll also want to check out the excerpt from her book that we’re publishing in parallel with this interview.)

Joseph Lichterman: You were in the Times newsroom in 2010. What stands out to you as something that’s changed or accelerated there in the time since?

Nikki Usher: One of the biggest has been the speed of the homepage, which has slowed. But it's important to remember that the idea of “freshness” motivating changes — to continual updating of stories, to tweaks across websites, this push to constant immediacy in a hyper-competitive live world — is still something that we see across media outlets. In fact, we can see that accelerating across social media platforms in a way that wasn’t the case in 2010. I think this fundamental compulsion that has always been part of journalism — to be first and fast — has been amplified through the web and is now further amplified through social media. I would say that a lasting lesson is that we are really in a new era of speed — even though, of course, journalism does have a legacy of caring about speed. But there is something fundamentally different about now.

Lichterman: That immediacy is a big focus, but at the same time, the Times is still putting out a print newspaper. In the book, you go into detail about how reporters and editors struggled to find the balance between writing for online and writing for print. How did you see folks deal with that in your time there?

Usher: I think one of the most interesting aspects about what is still facing newsrooms — and is still facing the Times — is the decision about what to put on the front page. Because culturally, it's still that final signifier of what matters. When you look across representations in the press, in movies, and in popular discussion of what people remember and talk about and think is important, it's not what is on the web, even though we might like to think so — it’s what that final, permanent stance is.

As a system of values, it does play a really significant role in how people articulate what's important to their work. And it's this fundamental contrast about what needs to be done to survive in a competitive Internet environment and what needs to be the reality to remain sort of this cultural imprimatur.

That may be the central finding: We've talked about how we're in a digital era for news, and that people aren't subscribing to print and people aren’t reading print — but when you talk about the cultural legacy for newspapers, if you talk about the cultural legacy inside and outside newsrooms, print still fundamentally matters, and it's really difficult to let go of how that works.

Lichterman: You demonstrate that really nicely by describing the page one meetings at 10:30 a.m. and 4 p.m., and how before them the sections meet to decide what they’re going to pitch for page one — but then comparing that to the website, which is essentially just one person deciding what’s going to be placed where.

Usher: The thing about the web is that it moves so quickly that you can't have meetings to make these fast-paced decisions. There may be cases where you can plan out some static content, but as far as making up-to-the-minute decisions, that’s going to be left to one or a very select few individual people who are not going to have these weighty decisions about the construction of stories and the meaning of what these stories mean to the public. They’re going to be making really quick decisions.

Compare that to the kind of intense conversation that happens around the presentation of the print paper and the development of print stories, and how ultimately, that’s a reflection of the in-depth conversations. It's a really fascinating dichotomy. I think one of the strengths of the book is that the ethnography really outlines how stark these differences are, even in an era where we would like to pretend that this stuff doesn't matter.

Lichterman: One of the other things I found interesting was how you described the workflows of the various journalists — like how the traditional print reporters are interacting with the video staff and the multimedia staff. You paint this picture of a top-down approach, where a lot of the reporters weren’t so happy about having to change their routine and deal with these people that they never met. Since you were embedded there, Snow Fall happened, and these big interactive pieces have become a lot more common. Do you have a sense of how those workflows have changed?

Usher: The book points out an important cultural barrier, which is that you can go into any newsroom and there are still going to be fundamental difficulties in organizing any new form of news with an old form of news — whether that be multimedia or interactivity. The rise of interactivity is well noted, but if you look at the intensity of the effort, they’re often devoted to the kind of project stories that are geared to win Pulitzers, the project stories that are geared to win attention. Rarely do you see that happening on a day-to-day basis — and when you do, they’re generally a project of something like The Upshot, which is a specific group of people dedicated to creating these sorts of interactives with data.

When you’re talking about the day-to-day relationship to multimedia to traditional journalism and interactivity to journalism, I think there's still a barrier at the Times. And I think if you think about how that applies to other newsrooms that are less resourced, you’re going to see more of that. Everybody knows that multimedia is important, everybody knows that interactivity is important, but not everyone knows how to make it part of their routines. It still takes work.

Lichterman: I love the scene in the book where Andrew Ross Sorkin is learning what TweetDeck is. I was chuckling to myself as reading it because a number of the reporters you quoted as saying they didn’t want to be on Twitter…

Usher: …are now on Twitter!

There is no doubt that this book, on some level, is a period piece of the Times at this particular moment. But where it draws some of its ultimate value is that it's a clear portrait of how people did their work at a time of conflict and change. That sort of stress on the routines and that type of change isn't something that's going to go away. While the technologies may change, the patterns and processes and conflicts over emergent values and emergent practices — that underlying relationship between change and process — is the consistent thing that we're going to see throughout the evolutions of newsrooms. I think that might be one of the most important things to stress.

Lichterman: Another thing I found interesting was the section you devoted to how the Times dealt with scoops and exclusives, and the issues of immediacy around that. There was this tension between putting something online right away and holding it back to protect it from the competition and make it relevant for the print paper as well.

Usher: One of the things the book highlights is that scoops are ephemeral — but they are an internal fascination inside the newspaper. And that is a really important lesson. Culturally, scoops are something that newspapers and news organizations are generally counting as victories, and as long as we have that mentality of winning and losing, it may actually obscure a strategic approach to thinking about scoops.

Lichterman: Obviously, The New York Times is a unique environment, and most news organizations don’t have the reach or the resources that it does. But do you think there are any lessons that smaller news organizations could learn from how the Times approaches these issues?

Usher: I think the Tow report Post-Industrial Journalism does a great job of saying We can't just talk about the Times, but we always talk about the Times. But I think these are underlying tensions that every newsroom experiences — about how fast to be, the relationship between web and print, difficulties and strategies between how to incorporate multimedia and interactivity into their newsroom, questions about what exactly is the right way to think about social media. You must remember that most newsrooms are totally Twitterified, but not all of them. That may be an East Coast kind of thing. But these tensions over change is something that every newsroom is going to experience for as long as this technological era is present. It doesn’t matter where you are: Cultural change is difficult. So understanding how people really think about change through all of these varying perspectives should give a lot of people some sense about some of the things facing their own newsrooms.

Photo of The New York Times newsroom by Sean Savage used under a Creative Commons license.

Sabtu, 10 Mei 2014

Nieman Journalism Lab

Nieman Journalism Lab


Under consideration: Some interesting entries in the latest Knight News Challenge

Posted: 09 May 2014 08:34 AM PDT

Fifty-six semifinalists in the Knight News Challenge have been hard at work refining their entries and preparing for the next round of cuts. (They’ll be narrowed to a group of finalists next week; the winners will be announced at the Knight-MIT Civic Media Conference on June 23.) There were 704 initial entrants to the challenge, which will offer $2.75 million to the winners. The current iteration of the News Challenge is focused on answering this question: “How can we strengthen the Internet for free expression and innovation?”

The OpenIDEO platform Knight switched to a few cycles back enables a lot of public input into and evaluation of News Challenge applicants. You can see both the semifinalists and other entries that didn’t make the cut online.

After looking through all the entries, here are a few that stuck out to us. These aren’t our predictions for who’ll win, and they aren’t even necessarily the ones we like best — consider this less an exercise in Vegas oddsmaking than an attempt to highlight some of the interesting ideas in the pool with ties to journalism. (No offense — and good luck! — to those we didn’t pick.)

Checkdesk

Checkdesk is a Middle East-focused application that provides news organizations a one-stop platform to verify user-generated content using a variety of methods. “What we propose is not a silver bullet for verifying digital media, but a more structured, easy-to-use and expandable toolkit that makes it easier for you, the journalist, to use the best techniques already out there,” wrote Tom Trewinnard, the research and communications manager of Meedan, the nonprofit behind Checkdesk. Six news organizations across five Middle East countries are already using Checkdesk, and Meedan hopes to use Knight funding to expand access to the platform and make it available on mobile.

MapWhatever

Fed up with the limits of Google Maps, the excessive costs of commercial GIS software, and the difficulty of learning open source mapping applications, James Baughn decided to build his own program that takes advantage of public information and allows users to easily create high quality maps. Baughn, who oversees the websites of The Southeast Missourian and other affiliated sites, wrote in his application that his goals are to create an effective script for downloading and processing data from maps, create a consumer-facing website, and open source the system so others can customize it.

SampleMapWhatever

Though he imagines MapWhatever could be used for a variety of purposes, there is no doubt that it could be used in newsrooms as well, Baughn wrote in his application. “Newspapers wanting to produce map-based infographics (for print or online) could generate a vector base map, import it into Adobe Illustrator or similar applications, and then fine-tune as necessary,” he wrote.

NewsA11y

Many news websites are not accessible to users with disabilities, argues Emily Stewart, who created NewsA11y as a means to connect members of the disabled community and news organizations to overcome these barriers. In her Knight application, Stewart wrote that NewsA11y has three goals: to allow users to point out barriers on news sites, to provide a space where individuals can collaborate on ways to overcome those barriers, and to act as a network where news organizations can look to hire coders or testers to help develop sites on case-by-case basis that better serve users with disabilities.

Stewart built a prototype of NewsA11y as part of her graduate school work at the University of Missouri, and she said she would use the funding from Knight to “transition NewsA11y from a working prototype to a real product. I would have the resources to build a robust application with a passionate user base that connects two groups of people. NewsA11y would motivate news sites to become more accessible and provide a place for rapid testing.”

Overview

Sorting through a large set of documents can often be a nightmare for journalists, but Overview believes it can make that process easier. The platform has been under development since it won a 2011 Knight News Challenge grant — project lead Jonathan Stray is a Nieman Lab contributor — and Overview is already being used in newsrooms as a way to organize and navigate reams of documents being used for investigations. Now, Overview wants to continue to develop the product and build it out into free and paid tiers. (Overview also offers consulting services.)

Still, Overview has recognized that the journalism field won’t be big enough to support the program, so it’s hoping to expand its user base beyond traditional reporters. “It will take sustained effort to reach a critical mass of paying users,” Stray wrote in its application. “Although we have increasing visibility within journalism, journalism alone is unlikely to provide enough revenue to support our organization. We need to broaden our user base into the non-profit sector generally, which means we need to learn what these new users need, build it for them, support their use, and market our product.”

SecureDrop

First developed by the late Aaron Swartz, SecureDrop is an open-sourced application that allows whistleblowers to securely submit content to news organizations. The product is already in use in several newsrooms, including ProPublica and The New Yorker, and the team behind SecureDrop hopes to use Knight funding to improve the tool’s encryption to make it safer for sources to share information.

securedropSecureDrop hopes to redesign the platform to simplify the API to allow newsrooms to simplify how information is submitted and allow for different utilities depending on the level of confidentiality needed for a particular source or type of information. It also plans to implement end-to-end encryption and other security measures.

“While the current version of SecureDrop leverages US legal protections to provide unprecedented protection for sources and journalists, the current version still potentially leaves international journalists at risk if governments are willing to raid newsrooms and seize servers, or hack into the servers themselves in an attempt to find sources,” wrote Trevor Timm, executive director of Freedom of the Press Foundation, the group that manages SecureDrop.

This Week in Review: Weak net neutrality and stifled startups, and a glimpse of U.S. journalists

Posted: 09 May 2014 07:51 AM PDT

This week’s essential reads: The three key reads this week are Stanford professor Barbara van Schewick on net neutrality and innovation, Indiana professors Lars Willnat and David Weaver’s findings from their survey of American journalists, and The New York Times’ David Segal on unwatched online video ads.

Will new FCC regulations harm startups?: The U.S. Federal Communications Commission’s proposed Internet regulations, which are set to be formally presented next week, are coming under fire from all corners, led by commissioners of the FCC itself. Commissioner Jessica Rosenworcel called for FCC chair Tom Wheeler to postpone the presentation of the regulations because of the “torrent” of criticism they’ve prompted, a suggestion Wheeler promptly rejected. Another commissioner, Mignon Clyburn, reiterated her opposition to the sort of Internet “fast lanes” Wheeler is proposing, urging the FCC to revisit its approach to Internet regulation.

Meanwhile, more than 100 Internet companies, including giants like Google, Facebook, Twitter, Amazon, and Microsoft, sent a letter to the FCC expressing their concerns about the proposed regulations, calling them “a grave threat to the Internet.” Recode’s Amy Schatz and Time’s Sam Gustin provided some context for the backlash against Wheeler’s plan to allow Internet providers to make deals with content providers allowing them to provide faster access to their sites than everyone else.

Mozilla, which makes the Firefox browser, went a step further, filing a proposal with the FCC to create a different class of Internet access connecting edge providers like Netflix and Dropbox to Internet users, which would be regulated as a utility like telephone service. The Washington Post’s Brian Fung and Ars Technica’s Jon Brodkin offered good explanations of what Mozilla’s proposing and how it fits into the history of U.S. Internet regulation.

Concerns about the proposal are coming from the startup world in addition to tech giants. MIT Technology Review’s David Talbot reported that some venture capitalists say they’re steering clear of startups that would require fast connections for services like video or audio. Ars Technica’s Jon Brodkin countered that weak net neutrality won’t hurt startups based on fast connections, because the cable TV system is still so ripe for disruption, and startups targeting that system will still be magnets for VC funding.

VC Fred Wilson warned that if the regulations go through, the “period of ‘permissionless innovation’ is likely to come to an end,” and at The Atlantic, Stanford law professor Barbara van Schewick argued that a pay-to-play structure would upend the economics of Internet entrepreneurship, in which costs are low enough that entrepreneurs can make their apps available to users without initial outside funding. Now, up-front capital will be necessary, she said, making it so that investors can’t rely on the market to determine what startups might be successful before they invest.

Despite the protests of a few major companies — most notably Netflix — The New York Times reported that most media and tech companies are simply trying to befriend broadband providers like Comcast, which is in the process of merging with Time Warner Cable. That merger got some stiff opposition from within the industry in testimony before Congress on Thursday. Still, Ron Fournier of the National Journal wondered why we’re seeing so little resistance to the new regulations and the merger compared with the flood of outrage that swamped SOPA and PIPA. Vox’s Nilay Patel wrote that between the FCC regulations, the Comcast merger, and the Aereo decision, this summer will radically change the Internet and media industries one way or another.

utopia-dystopia-cc

A bleak picture of the American journalist: Researchers at Indiana University released results this week from the most recent edition of a survey of American journalists they’ve conducted each decade since the 1970s. Derek Thompson of The Atlantic provided the broadest summary of the study’s widespread findings, highlighting journalists’ decreasing job satisfaction and increasing age and ethical scruples, as well as its continued domination by white men.

Several aspects of the survey drew additional attention: Jim Romenesko noted that the majority of journalists believe journalism is headed in the wrong direction, and The Wire’s Eric Levenson pointed out that the number of journalists who approve of the use of confidential or personal documents without permission is decreasing.

The most newsworthy finding for many media observers (particularly on the right) was the decreasing number of journalists who identify as Republicans — just 7 percent, down from 18 percent in 2002. The number of Democratic journalists is declining as well, with 28 percent describing themselves that way compared to 36 percent in 2002. Instead, the number of journalists identifying as independent is booming. Chris Cillizza of The Washington Post said the shift toward independence mirrors a movement in the broader electorate, The Atlantic’s Thompson suggested that the statistics should be good news for conservative journalists, who should find themselves in demand if public desire for more conservative news truly outpaces the amount offered.

Reading roundup: It wasn’t too busy of a week on the journalism and tech front, but there were a few other stories worth following:

— As The New York Times reported, Russian President Vladimir Putin signed a law this week requiring popular bloggers to register with the government, a measure that many observers believe will serve to more closely track and stifle online speech. A Reporters Without Borders article from last month does a good job of explaining the new law, how it works and where it fits in Russia’s recent recent of online repression, as does an Animal New York piece from this week. Meanwhile, as The Washington Post reported, pro-Russian separatists in eastern Ukraine have been intimidating and attacking journalists and taking them prisoner.

— The Los Angeles Times unveiled a site redesign this week, with a few distinctive new features: Digiday noted that users can move from one story to the next by simply continuing to scroll down, resulting in an endless vertical stream of content. Gizmodo highlighted its Instagram-esque “visual browsing” mode that emphasizing images and horizontal movement. And the Lab’s Joshua Benton wrote about its pre-written tweets and status updates at the top of stories, taking advantage of the fact that many people share stories without reading them.

— New York magazine published a long story by Joe Hagan going deep inside Lara Logan’s tenure at CBS News and raising doubts about whether she will ever return to the network after being put on indefinite leave for her erroneous 60 Minutes report last fall on the Benghazi attack of 2012. Slate’s Amanda Hess flagged the story for its sexist characterization of Logan in various spots.

— Finally, two more pieces to take a look at this weekend: The New York Times’ David Segal went deep into the paltry numbers of people actually watching online video ads and the difficulty in measuring them, and at the Lab, News Corp.’s Raju Narisetti offered a variety of creative ways to make the Pulitzer Prizes more useful in promoting good journalism.

Photo of FCC chairman Tom Wheeler testifying before the House Energy and Commerce Committee in December by AP/Susan Walsh. Photo of graffiti by Jonny Hughes used under a Creative Commons license.