Skip to main content

Perception is Reality

Edit: ironically, this article on the latest security debacle at Facebook was released today on the Wall Street Journal. You can't script this stuff. Really.

The subject for this blog entry is an oft-repeated mantra of mine. I'm not sure if I've discussed this here before, but I would argue that even if I have it is worth repeating. The inspiration for this subject is a recently reported "feature" of Facebook that any of your contacts that were kind enough to enter their phone numbers in their profile have that information visible to anyone in your network unless they were savvy enough to make that information visible to their friends only.

Of course, when one of my Facebook friends found out that the had access to their friends' phone numbers they panicked. "ZOMGWTF!!1!11!!uno" was essentially the response, and all of their friends chimed in with similar ones after they confirmed it. Even Yours Truly responded in kind and dutifully reposted this information to further spread the word that Facebook is Bad, mmkay? while continuing to spend 5 hours per day on the obviously terrible site.

It wasn't until a good friend of mine slapped me in the face with a healthy dose of reality - thanks Tom Bridgman! - that I realized I had fallen victim to the general distrust of a website that has been prominently displayed in the news over the past year or so for questionable information security practices. And yet when I stopped and thought about it, I realized that if I really cared about my phone number being shared then I probably wouldn't have entered it in the first place. Ergo, by doing so I created for myself the expectation that others would see it and, if needed, use it. Therefore, this really wasn't a risk after all.

What's worse is that after digging on the Internet for a few moments I realized that this wasn't something that Facebook decided to do recently. In fact, this feature had been around for several months I read and that reminded me: I had read of Facebook's intention to do this before they actually implemented it. It didn't bother me then - I ensured that my phone number wasn't in my profile - so why did it bother me now?

The answer: perception is reality. The perception that the public has of Mark Zuckerberg et al is that they are clueless idiots with respect to information security and that their chase of the almighty IPO have blinded them to the concept of "respecting your user community." Granted, they have done little to discourage this, but now they are deemed guilty before being proven innocent. In fact, I will admit to being on a witchhunt when it comes to Facebook because it does seem that the website was built to look and feel slick without necessarily thinking through all of the required security architecture at the same time. But that doesn't mean that there's fire where there's smoke in spite of what my perception is of them.

Still, perception is reality. If they are perceived to be the Keystone Cops then they are regardless of the truth. And sometimes it requires a slap in the face by someone named Tom to get one to realize this may not be reality.

In business, this tenet requires us as professionals to ensure that our actions are clearly defined by the intention of those actions. This may require close coordination with your team members and your direct manager, but in the end the extra effort will be worth it. Not only will you avoid any confusion incurred when people wonder what the motivation for one action or another was, but your coworkers will respect you for being an open communicator and a team player. And that is always a good thing.

Popular posts from this blog

Finding Clarity in the Chaos of a Job Search

Job searches are humbling. They test your confidence, your patience, and your ability to stay motivated when things don’t move as quickly as you’d like. But they also teach you things about yourself that you might not have learned any other way. For me, the past few months have been a crash course in rediscovering what really matters: not just in a résumé, but in relationships, self-perception, and how we use technology to help tell our stories. Here are three lessons that stood out. Reach Out to Your Network (Long Before You Need It) Your network is a living thing. It requires upkeep, time, and attention, just like a flower garden. You can’t ignore it for years and expect it to bloom the moment you need it. Start planting early. Stay in touch with people whose paths you’ve crossed - colleagues, mentors, partners, even those you only worked with briefly. Drop a note once in a while. Comment on their posts. Share something that made you think of them. These small gestures are the sunl...

Time to Level Up!

With the recent news out of Salesforce and Oracle, it’s easy to understand why folks affected by layoffs might feel discouraged. Not only are they leaving companies they may have called home for years, but they’re also facing the daunting prospect of job hunting while headlines scream about “AI taking over human jobs.” Not long ago, another company I follow - let’s call it Acme  - went through a similar round of layoffs. Two employees in particular (we’ll call them Jim and John) showed how mindset can make all the difference. Jim had been at Acme for over 20 years. He was reliable, steady, and well-liked, but not exactly the standout type. When he was laid off, he decided to take some time off before even thinking about his next move. After all, he had a severance package. Didn’t he deserve a break after two decades of hard work? John’s story was different. Though he hadn’t been at Acme as long, he’d built a strong reputation and had both technical and leadership skills. Instead of...

So What is this IPaaS Stuff, Anyway?

 In my last post , I discussed how no-code/low-code platforms fulfill rapid development of business applications - addressing the needs of the Citizen Developer (a Gartner term  first used around 2009).  I also commented on how this specific objective limits their ability to provide true integration capabilities, which require the flexibility to adapt to the myriad variations of infrastructure.  This is a concern because companies often have acquired legacy systems via M&A activity while simultaneously investing in new technology solutions, resulting in a mishmash of systems with multiple ways of accessing them. In this post, I'd like to examine how the needs of the latter group are met by describing some key capabilities that are "must-haves" for any company looking to execute on a digital transformation strategy.  In order to do this, let's define who the target user base is for such a technology platform. Disclaimer:   I work for MuleSoft (a division...