Skip to main content

Mr. Change?

Ha! And you thought this entry was going to be about the sitting president. Actually, it's about me...or my blog rather.

You may have noticed a change in my blog. Specifically, the title has changed from its previous value to what it is now. The reason for the change came in the form of a Cease and Desist letter that I received on Friday in the mail claiming that I was improperly using a trademarked expression of the client of the law firm sending me the letter.

Google made it easy for me to see that the expression was indeed in use. Being the upstanding citizen that I am, I immediately changed the title of the blog and faxed over a response indicating that I was in compliance with their request. But then something funny happened...

...a number of years ago, I was jilted out of a substantial amount of money owed to me as an independent contractor by the company that placed me at the company where I was working. During the back and forth between the placement company and I, I contacted a cousin who is a lawyer for a prominent law firm who agreed to draw up a legal sounding letter based on what I told him. Even though what I said to him was in actuality true, he required no documentation proving it before writing the letter and mailing it to the other party.

Fast forward to the present: remembering how I got my cousin to send a letter as someone who claimed to be my legal representation, I wondered if something similar was happening here, i.e. not everything was "on the up and up." I visited the U.S. Patent and Trademark Office (USPTO) and found out that the expression was indeed trademarked...but not by the business being represented by the law firm that sent me the letter.

In good faith, I am keeping the new title since a) a web search at the USPTO isn't a guarantee that the results are 100% accurate and b) someone owns the trademark whether it is company A or B. It isn't me, in any case. But I sent back a second letter tonight with a request for documentation supporting their claim, with the added statement that I may take legal action against them for "wrongful claim of infringement," recourse that is afforded people like me in situations just like this.

I have no problem with legal compliance. It is not my intention, after all, to use what is not mine or to cause possible harm to the brand of another company in these mindless wanderings that I call a blog. However, I do expect a minimum degree of honesty if you're going to demand anything of me and - as of this writing - it seems that minimum standard was not met. So en guarde Miss O'Conner because the ball is back in your court, and I've just upped the ante.

What does this have to do with business? The answer should be obvious, but here it is spelled out just in case.

There is nothing wrong with embellishing the truth to favor yourself. In fact, sales people often do just this, i.e. tell the truth without being accurate or while being intentionally misleading. I can remember one sales presentation where it was said "30% - 70% of your time is spent doing this." Hello? That's a 40% swing, and right in the middle of the Gaussian bell curve at that. What that message said was nothing short of pure bunk, but that's the fun of sales.

While it is expected in certain situations that you are going to view yourself with rose colored glasses, it is another matter entirely when you are going to try to claim something is true; that the government, your boss, your spouse, etc. is going to back you up; and you are lying. If the person calls your bluff - and they have every right to do so if you're making demands of them - then not only will your lie be exposed but you will have lost a huge amount of credibility.

Trust is not something that should be taken lightly, especially in a business sense. Toyota (a-Ha! I knew I could find a way to tie this in with the last two blog entries!) has found this out the hard way, but there's no reason why you should too.

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...