Skip to main content

Closing the deal

I realize that many of you are thinking that this entry is about sales. It is not. Rather, it is about execution of a plan, any plan. Do you aspire to have that managerial job? Or perhaps you're eyeing that roadster down the block in the driveway with the "For Sale" sign in it. And is that a model that I see sitting two tables down from me in this restaurant?

Regardless of the situation, you need a plan if you wish to reach your goal. And the first stage of any plan is understanding exactly what needs to be done and what the potential risks are that would prevent you from succeeding.

In sales this is called qualification. Everyone else calls it discovery or, simply put, asking questions. And it is essential to do this or else you run the risk of making an avoidable mistake because you simply didn't know any better.

What about that model? "Who is she?" (Check Google via your smart phone.) "What are her interests?" (Again, Google it.) "What is she eating, and do I know a good wine pairing?" "Are there any paparazzi waiting around outside of the door that she needs to be aware of?" Knowing the answers to these questions will allow you to approach her and sound intelligent enough to catch her interest.

You also need to understand the risks in each situation. "Is it true that she's married to Vin Diesel?" "Is that her lesbian lover that she's kissing?" Either of these are a show stopper, obviously, but if you weren't aware of her marriage to the esteemed Mr. Diesel and he shows up while you're hitting on his wife then it will probably be more than just a spurned advance that you'll receive in response.

There is a cliché that says, "you have to learn how to walk before you can run." My response to this is that before you can walk, you need to know not only where you're going but what the best method is to get there. Understanding the answers to these questions will provide you a head start in successfully executing your plan of action.

Popular posts from this blog

It's Easier to Fail at DevOps than it is to Succeed

Slippery when wet Since the term DevOps was coined in Belgium back in 2009, it is impossible to avoid the term whether in discussions with colleagues or in professional trade magazines.  And during the years while this movement has gained momentum, many things have been written to describe what elements of a DevOps strategy are required for it to be successful. Yet in spite of this, there is an interesting data point worth noting: not many organizations feel there is a need for DevOps.  In a Gartner report entitled DevOps Adoption Survey Results (published in September 2015),  40%  of respondents said they had no plans to implement DevOps and 31% of respondents said they hadn't implemented it but planned to start in the 12 months after the survey was conducted. That left only 29% who had implemented DevOps in a pilot project or in production systems, which isn't a lot. "Maybe it's because there truly isn't a need for DevOps," you say.  While t...

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

Application Development Done Right

In a previous article, entitled DevOps as the Ultimate Panacea? , I described how developing code without thinking about the current needs of the end user as well as the future needs once they've become accustomed to using your application ends up not only frustrating them but also can result in customer churn and ultimately lower revenues.  In this article, I'd like to describe something simple that I came across today that shows a definite degree of effort to do quite the opposite. Recently, we had a severe snowstorm, one with blizzard-like conditions, which is unheard of in central New Jersey.  Being responsible adults, my wife and I went to the grocery store to stock up on essentials (read:  chips, chocolate, etc.) in case we get stuck at home. As we were ringing up our order, the cashier mentioned to us that the store has a mobile application.  Since both of us are in technology oriented professions, we were skeptical about the need for a grocery store mob...