Small Business

New Applications - Taking the First Step

Social networking in business has been receiving quite a bit of press lately with many differing views on just what should or should not be allowed, or how to use various social networking tools now available.  I ran into an interesting read in an article “Social networking in business: Avoid the ‘Kumbaya Zone‘.  Now, the ‘Kumbaya Zone’ is a new term for me, and the article refers to it as “…the place where social media is ultimately a time-waster and has little business value”.  

Now I don’t want to get into any do’s or don’ts about social media - nor do I think that it would be wise for me to do so — but what I do want to address is that perhaps many of us have seen applications which appear to become time-wasters with little business value, I certainly have.  They may be the “old” application never replaced, or they may be an application for which users have developed so many work-arounds to have it fit that there is much time wasted.  Either way, the application has little business value.

The referenced article ends with the statement “Get comfortable taking that first step, and see what works along the way. That is way different from the software model we’re used to.”  Now, I certainly agree with the first sentence concept of getting comfortable and  seeing what works - and while the article specifically is talking about social media, I would posit that this is an approach worth considering for any new application.  As for being a different software model than we’re used to, I must say that working with my customers we’ve been able to create an environment where we do to a large degree follow the concept - it doesn’t have to be “…way different…” than we’re used to.

User Reluctance to Application Changes

Some things just never seem to change, and user reluctance to application changes is one of those situations which it seems, is always present - regardless of the form of change.  Sometimes I’ve found that even changes which had been requested by users, and that they kept looking forward to, once made, the changes are received with grumbling and every excuse possible being used to avoid incorporating the changes into their routine.

The question is, what do you do about it?  What does it take to bring the user around so that rather than condemning the changes, they embrace them with enthusiasm?  The answer is actually quite simple, although time consuming — it’s one-on-one training.  My experience with providing “training” applications which the user can access on their own to learn new application features has been highly ineffective since the users do not spend the time needed.  A “classroom” kind of setting also has been ineffective for my clients since often it is key people in the company that need to use the application, and they have a business to run!  (…read this as they’re TOO busy for training!)

However, the 1-on-1 approach has proven effective consistently since it provides the capability to work with the reluctant user with “real” information, in their setting (…always do 1-on-1 at their desktop!),  and your presence allows for instant answers to questions and concerns as they come up in the session.

This kind of training can also provide valuable feedback for further development of the application — for one thing, it allows for experiencing “real issues” for users “IF” such issues exist.  Certainly as developers we hope that there will be no “real issues” with our pride and joy of application, but I’m sure we all have experienced them.  Seeing exactly how the application performs for a user is important - many a “little issue” that I’ve seen when working with a user 1-on-1 has led to better the next iteration of the application.

Independent Development Business

My work day started today with the usual quick scan through the multitude of emails that I receive daily.  I have always found this activity a gentle way to start my day (which generally begins somewhere between 5:30 and 6:30 AM).  I’ve also found that at times my attention is directed to particularly poignant articles relating to some facet of my business as an independent software developer.  This mornings find is just such an article.

My find?  “The myth of being successfully solo in business” is a brief article that caught my eye and started me thinking about just how dependent an “independent” software developer is.  Let me explain a bit without (hopefully) you not reading the linked article.

The article explores what is described as “…the myth of the successful solopreneur…”, and explores also how “…we can’t do it ourselves”.  Now, THAT is something I’ve realized over and over again through my years as an independent software developer!  However, my memory gets pretty short with certain learning I’ve noticed, and especially when faced with this myth!

The impossibility of doing all the things yourself that are provided for you when you are an employee seems to escape many of us self-employed, and often we think we’re some kind of super human who CAN do it!  I’ve personally had one of those reminders recently as the result of my wife’s broken ankle back in mid May.  Since the time of her injury, ALL of the household responsibilities AND the income producing responsibilities have been on my shoulders. 

Fortunately, I don’t have an office out of the home that I have to go to - but I do have the occasional visit required to my local customers.  All of these activities have at times been very much overwhelming — and certainly indicative that I “can’t do it” solo.  Through this period I have met with exceptional understanding from my clients and considerable help with meals prepared by friends and shared with us.

While what I refer to above might seem more personal than business related, I call it to your attention in light of the referenced article, and as another indication that being an independent software developer still requires others.  Professionally I’m a part of the Northeast Dataflex Consortium, a dedicated group of professional developers who support each other in many ways.  Those of us who are independent software developers are also dependent upon our vendors, customers AND indeed all of those around us in some way.