Crisis Management By Photoshop

BP Admits It Altered Photos Purporting to Show Its Response to Oil Spill

2 min read
Crisis Management By Photoshop

The public relations gaffes just keep on coming, which makes one wonder about the decision making processes - or lack thereof - at BP.

On Monday, blogger John Aravosis at AMERICAblog.comwrote that BP had apparently manipulated a photo of its spill command center on its web site. The original photo showed BP's command center personnel monitoring the Deepwater Horizon spill activities, but BP tried to enhance the impact of the photo by placing additional images from the oil well cameras on some of the command center monitors that were originally blank.

The date of the photo was also questioned, with some indications that it had been originally taken in 2001, not 2010.

Mr.Aravosis wryly noted in his post, "I guess if you're doing fake crisis response, you might as well fake a photo of the crisis response center."

The story got picked up by the Washington Post on Tuesday and soon other media outlets which forced BP to admit that it had faked part of the photo, and to issue orders to company personnel not to manipulate any photos in the future.

BP maintained, though, that there was nothing nefarious about what had been done to the photo.

However, soon more Photoshopped BP spill-related pictures started to be discovered (one very crudely done), which has started another round of questions in both the global media and blogosphere asking BP to come clean on all of its manipulated pictures.

BP has only admitted to three so far. In explaining the altered photos, BP said:

"BP's photographic department uses Photoshop to edit images we post on the Gulf of Mexico Response web site. Typical purposes include color correction, reducing glare and cropping. In a few cases, cut-and-paste was also used in the photo-editing process. These cut-and-pasted images have been removed. The original and edited images have been posted here for comparison. We have also included an image that appears cut-and-pasted, but was edited using the color saturation tool to improve the visibility of a projection screen image."

The altered photos has also started a round of "Where's Waldo", as the Washington Post writer Steven Mufson termed it, with a host of folks now scanning every BP photo of its spill response to see whether it too was doctored.

IEEE Spectrum had an article titled "Seeing is Not Believing" on computer-assisted altered photographs and how hard they are to spot last August.

There is also a nice series of articles on determining the authenticity of photographs of historical events by filmmaker Errol Morris that appeared in the New York Times a few years back.

If more altered photos than the three so far found show up, expect BP's management reputation to sink further, if that is possible.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
A plate of spaghetti made from code
Shira Inbar

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less