You might have noticed two companies in the photography industry doing things that are frustrating you. It’s possible one of these companies is even confusing you.

Today I want to share two mistakes that I know are frustrating me, and could likely be frustrating you.

My hope is that these companies notice some commentary here on Photofocus and respond to your frustrations.

Nikon

First up is Nikon, but before I dive in, know that I am a Nikon photographer. I have been forever and will continue as such. But when a company does something that I feel is wrong, even if I am a loyal user, I cannot stay silent.

If you were paying attention when Nikon first announcement the Z6 and Z7 cameras, then you might also know about the FTZ adapter. The FTZ costs nearly $250 when purchased on its own.

But until recently, when you purchased the FTZ along with a Z6 or Z7 kit, the adapter was only $100.

Maybe the FTZ wasn’t selling as well as Nikon hoped it would, or maybe they have a second version of the adapter coming out soon. But Nikon decided to make the FTZ adapter free for anyone who buys a Z6 or Z7 camera … in the United States only.

Whatever is driving this decision from Nikon didn’t think through the ramifications they were going to have from making a $250 product free for new purchases.

Because people who purchased the FTZ adapter (like myself), are now out a lot of hard earned money.

I love Nikon. Heck, they’ve been extremely good to me as you will see here.

But this makes me mad, frustrated, and I want answers. I want to know how Nikon will make good on this change, and make their customers happy.

Adobe

Next up is Adobe. Here we are again, so many of us as Adobe users for many years. I’ve been using Photoshop and Lightroom for so long, I cannot even remember a day when I didn’t use it.

You might recall that when Lightroom first came out it was called Lightroom. Sometimes it was referenced as Adobe Photoshop Lightroom. I always thought that was odd.

But really it was just Lightroom.

Then one day, when Creative Cloud became a thing, it was decided that Lightroom was to be renamed. Because a lighter, simpler version of Lightroom was to be released.

Now, instead of calling the cloud-based version of Lightroom, Lightroom Elements — like Adobe does for the lighter, simpler version of many other products — they went with a more confusing naming structure.

Lightroom became Lightroom Classic CC (where CC stands for Creative Cloud). The new Lightroom (cloud version) became Lightroom CC.

This confused users and caused (and continues to cause) problems for developers. Now, when someone is looking to open Lightroom, they wind up opening Lightroom CC. Now, when people want to install a Lightroom (Classic CC) plugin, they get annoyed at developers that the plugin isn’t working with Lightroom (meaning Lightroom CC).

That frustration list can go on and on.

Here we are again, though, and Adobe has done a renaming to both Lightroom versions.

Lightroom Classic CC became Lightroom Classic. Lightroom CC became Lightroom.

As you will notice, they dropped the CC from each of the names. For those finally getting used to the change from Lightroom to Lightroom Classic CC, you have readjusting to do.

For those just now making the “upgrade” from Lightroom 4, 5 or 6 to the Creative Cloud versions, your Lightroom is no longer Lightroom. it’s now Lightroom Classic.

Sorry …

Frustrations and confusions

I know this might come off as a rant, and it kind of is.

My hope is that companies like Nikon and Adobe, and many others, stop making changes without doing further market research. Ask your users, your customers, your loyal fans. Find out if a change you’re going to make will have a positive impact on user experience, emotions and sales.

For example, if you have a pack of pre-release testers telling you to keep Lightroom the way it is, and make the new software Lightroom Elements, there is probably a good reason for that. Just saying :-)

I’m still going to be a loyal Nikon photographer, and I’m still going to be using Lightroom. But boy is it frustrating, and I feel so bad for all the developers and users who are confused by pointless name changes.

Leave a Reply

Close Menu