Happy Holidays from CooperMann

Ninjabread cookies in the kitchen, an appearance by the Christmas Elk, and Minty Fresh (fresh cat, not canned) looking for Frangos all clearly indicate that the holiday season is here.  2013 has been an eventful year – some would say it was “fraught with peril” while others see opportunity in change. It’s all a matter of perspective – pursuing goals and taking action rather than resting on ones’ laurels and trying to wait it out.  This cloud stuff isn’t going away.

With technology and social computing adoption increasing at almost alarming rates, I can’t wait to see how 2014 goes!  This certainly isn’t a time for the tech-timid, as it appears as though the nerds and geeks do rule the world (aren’t we all a little nerdly, really?).

I hope you and yours have a wonderful season.

jmbunnyfeetCheers

J

cooper-mann-top-20

Read the Best of CooperMann.com from 2013

Helping a Small Business Customer Choose Your Solution

In a previous article entitled The Psychology of Small Business IT Adoption, I discussed Icek Ajzen’s Theory of Planned Behavior and how a number of researchers applied it to the process of small business IT adoption.  The concept, which ended up proving to be true, was that IT adoption by small businesses is a function of a number of fairly well-defined elements, and is not so much defined by specific types of businesses or the business leaders.  The elements which lead to the act of business IT adoption (as well as adoption of other services, I’ll bet) can be identified and addressed by the potential provider of the product or solution ahead of time, making the possibility of actual adoption much greater.

Knowing how your prospective customer will approach the decision-making process is important, and getting a little insight ahead of time never hurts.  Particularly when a lot of customers don’t actually reveal their thinking, it can be tough to know where to begin.  You’ve been there before – you’re making your pitch and asking questions, but are getting nothing in return.  Sometimes it’s “deer in headlights”, and they are simply overwhelmed.  Other times they’re thinking about things you’re not telling them… but they’re not letting you know you’re not telling them.  Dead air, and then a lost opportunity.

Boiling it all down to a fairly simple explanation, businesses adopt IT because there is a conscious plan to do so, and that plan is supported by a belief that the solution will do good things for the business, the solution is a recognized (if not expected) approach, and the business believes it has adequate resources and capability to effectively handle it.  It’s all about:

  • Intent,
  • the attitude towards adoption,
  • belief of expected outcomes and their value,
  • expectations and the motivation to comply with them, and
  • evaluating barriers and the adequacy of resources to overcome them.

Intent

The first and most important element is intent, a conscious plan to get or do whatever it is.  If the customer has no plan to get the item and sees no need for it, then the barrier is pretty high.  However, if the need can be created, and the customer can be driven to believe they need to get the item, then there is intent.  Now they’re looking for you and not vice versa.  Consider that the Snuggie wasn’t “something” until folks were told that blankets simply weren’t good enough any more for lounging around (they don’t have sleeves!).  Once people believed there was a problem, they pursued finding the solution.

The attitude towards adoption

Next, what’s their attitude towards getting the item?  Sometimes people go looking for things they don’t think they can actually get, and often they know they need something but don’t think the solution is even out there, so they have a jaded viewpoint from the start.  A prospect with a positive attitude and who wants to actually find a solution is far better to work with than one who has already determined that you can’t help them.  Sometimes all it takes is a good listener to help create a positive attitude and make someone willing to tell you how you can help them.

Belief of expected outcomes and their value

Now, what does the customer think they will get from the deal?  Will the solution actually solve problems or create new ones, and are the perceived problems to be solved big enough to really worry about in the first place?  Small businesses tend to be very cash conscious, wanting as much value as possible for any expenditure.   Further, most small businesses don’t let go of their cash easily and certainly not for frivolous purposes, so a successful sale is often supported by the customer’s belief that they will get a real solution and benefit – something of value which will be realized, and that is important enough to deal with sooner rather than later.

Expectations and the motivation to comply with them

It is interesting how many small businesses go shopping for products or solutions that they don’t actually intend to purchase or adopt.  Sometimes they just want to be able to say “we’re looking in to it”, even if they aren’t and don’t plan to, and sometimes they have a business requirement that they don’t want to have to meet due to cost or complexity or whatever.  Let’s say a business has customers complaining about unresponsive or bad support, and how they should have a ticketing system to help track issues better.  Maybe the customers have the right idea: maybe the business should have a ticketing system (the business provides support and ticketing systems are considered a support service industry norm).  This is the expectation.  Let’s also say the business uses a CRM solution to handle support, and they believe it handles things just as well as a separate “ticketing” solution.  Just because there is an expectation (customers want ticketing system), it doesn’t mean the business is motivated to comply (CRM does just fine).  Expectations come in many forms and from many sources – customers, vendors, employees, contractors, the government and regulatory… on and on.  Expectation and motivation to comply are both high when it comes to legal and regulatory issues, as these things can be tied directly to money and cash and risk.  In other areas, it may not be as easy to identify or address.  The best way to look at this issue is to try to understand what the business is doing now, whether the approach works or may be materially improved in servicing their business and model, and whether or not the business recognizes an immediate need to make the change.

Evaluating barriers and the adequacy of resources to overcome them

The final and perhaps most important factor in SMB adoption of IT is the simple belief that it can be done.  Done at all, I mean, not just done “affordably”.  My dad taught me that it’s not a bargain if you can’t afford it.  Now, this doesn’t mean that there aren’t times when a business needs to bite the bullet and extend itself to become better.  But any small business in this position is a tough sell, simply due to real resources and capability.  No matter how much a business may know it needs something, if it really can’t do it, or believes it can’t – it won’t.

Make sense?

J

Lessons Learned (or Not): Development and the Cloud

Lessons Learned (or Not): Development and the Cloud

Talk about agile technology and how great things are because we can experience rapid software solution development and deployment via the cloud is shining a brighter light on certain IT management issues which have existed for quite some time, but perhaps went largely unrecognized.  One of these issues is product development direction and influence, and where it really comes from.  If you think most IT companies determine their product lines and offerings from the top down, with detailed specifications supported by a strong business case, you may want to think again.  Based on my experience and that of a lot of other folks, there are many companies out there offering products and services  that were crafted in more of an ad hoc manner than through a focused “product development” effort with long term sustainability in mind.  In some cases, this demonstrates ingenuity and a desire to look at things in new ways.  Sometimes it’s just uncontrolled and unstructured chaos with dollar signs attached.

“there’s a school of thought, put forward by the small but influential analyst firm RedMonk, that developers now occupy the role of IT kingmakers. This theory holds that the traditional model of IT adoption, which assumes that major decisions emanate from the top, is wrong. Instead, the decisions that appear to come from a CIO are, in fact, dictated by the choices made by people way down in the IT organization-the traditionally denigrated developers. CIOs merely ratify the decisions made by “lowly” developers.”

It goes like this:  a high level concept comes from upper management… some “great idea”.  This high level idea is communicated (at a high level) to the production teams who will make it real.  The production teams decide what it really is, how it will really work, what it will look like, and how it will be offered – and all of this generally based on the preferences, skill sets, moral guidelines, belief systems, and work ethic of those involved in the development process.  The product details are run back up the food chain, where they then become the defining elements of the new solution.  In many cases, refinements and changes are argued against by the developers, citing various reasons or roadblocks to making changes to their prized construction.  But hey – they got it ready to go out the door, didn’t they?  So what if it’s not quite what you envisioned, and doesn’t necessarily represent a sustainable strategy?

Experience in business does count, particularly if you learn from it.  There is a saying I heard once, and I’m still not sure how I feel about it other than it proves to be so very true each and every day.  The saying is that “there is no morality without context”.  In business, context is often experience, understanding the cause and effect of an action or activity.  Without this learning, without the experience earned within the organization or by others, there is no context guiding the development.

“It’s irresistible to poke fun at some of the most egregious aspects of today’s IT practices-change control committees that only meet once every two weeks;ITIL implementations that place more emphasis on paper trails than actually, you know, getting things done; operations groups that resist application updates in the name of stability, and so on and so forth.

However, the fact is that these functions, if not their manifestation, exist for important reasons. Overlooking them-or outright ignoring them-is not the right solution. Ensuring that updates to production systems are made, and being able to track who makes changes to infrastructure, are enterprise functions are that won’t go away just because cloud computing is in the picture.”

Lessons previously learned will need to be learned again, and addressing problems after-the-fact is generally far more costly than being proactive and trying to avoid them in the first place.  It can be a very painful process, watching the company go through puberty all over again (particularly if it had once reached some level of maturity), yet this is what can occur when the bright and shiny new idea causes management to forget fundamental lessons previously learned.

In a recent article on Computerworld.com, author Bernard Golden makes a number of really good and interesting points about the opposing viewpoints of this “agile” development enabled by the cloud (the article focuses on AWS – Amazon Web Services, but it is completely relevant in the broader context).  Link here to access the entire post, it’s worth the read.

http://www.computerworld.com/s/article/9230040/How_the_Cloud_Brings_Developers_into_Business_Process

Make Sense?

J

Read more about legacy application modernization, and why IT and back-office outsourcing makes sense for a lot of reasons