« March 2009 | Main | May 2009 »

April 2009

Be Heard
Apr 29 Patrick Clements

We are currently looking at some new tools and better ways to get more and more feedback from customers and community members.  We recently rolled our our online community Town Square which will eventually help create positive discussion on what our users are interested in and what they would like to see from us.  We are now looking to add a ‘Feedback’ button on our web based helpdesk software solution encourage our members to vote and be heard on what they need in their solution.

feedback 1

The ‘Feedback’ tab will be dynamically displayed once it’s been clicked.  It will show  the top 5 most requested features and give you the opportunity to write comments on the features, vote on other features you would like to see as well as create your own new feature request.

feedback 2 

We intend for this to be another level of communication where we can connect with our customers.  Please let us know your thoughts!  We have set up a HelpDesk forum on our Town Square site for feedback.

Posted by Patrick Clements on 12:31

Admitting to Mistakes
Apr 28 Patrick Clements

cartoon

 

Making mistakes is sometimes unavoidable.  It would be almost impossible for a company to think they have never or will never make a mistake.  Obviously the more successful companies make far fewer mistakes then the less successful companies, but this is beside the point.  The point is how does a company handle itself and the relationships it has built over time when an error is made.   The number one thing is acceptance.  Accepting the error, rather than avoiding the responsibility, limits the potential damage and sets organizations on the right course.  Companies are operated by human beings, imperfect and prone to making mistakes.  Most of our growth come from learning from our past mistakes and implementing processes and changes to see those same mistakes are not repeated in the future.  Admitting to mistakes is not easy, but admitting to them early and providing honest and direct feedback is great way to show character and over all good business ethics.  Admitting to your error puts you one step closer to dealing with it, and can be the first step towards a successful turn-around.  Taking responsibility, being sympathetic and sincere, and making a plan to ensure these types of issues don’t happen again in the future will go a long way with your employees, your customers, and your partners.

These are policies of bigWebApps.  We keep the lines of communication open at all times when we experience issues with our applications or services.  Being open, honest, and direct with our customers is a part of our companies culture and we will see it remains as one of our cornerstones as we continue to grow and expand.

Cartoon: Life in Hell by Matt Groening

Posted by Patrick Clements on 10:25

Taking a Step Back
Apr 16 Patrick Clements

We just finished our Q2 meeting and came up with a lot of really great ideas.  The main idea was to take a step back and really evaluate the technology we have now and let’s see how can we make it work better.  We have spent a lot of time developing a lot of great and useful features based on our clients’ feedback, however, now it is time to revisit these features.  We need to determine what would make these functions easier to use and more effective.  The main areas we will concentrate on over the next few months with be Assets and Locations.  The first one we will be addressing is Assets.

  • Merging of Duplicate Assets – We now support a more flexible system in allowing organizations to import their assets into the Asset Manager.  In the past we had some pretty strict guidelines and it was causing issues on getting data into the system.  With the newer setup it will allow for easier importation of data, however, there will now be a need to merge duplicate assets into a parent record.
  • Imports and Exports  - We will be looking to continual improve and refine the import and export routines in order for it to be easily self served and self managed.
  • Assigning Assets During Ticket Creation – We will be streamlining the process on searching and assigning assets to a ticket during the ticket creation phase.  Less clicks!
  • UI – We will be looking to do improvements and upgrades to the design and layout of most of the elements of the Asset Manager. 
    • Asset Search
    • Setup Type/Make/Model
    • Asset Profile Page
  • Delete Assets – We will soon be supporting the functionality of totally deleting and removing assets from the Asset Manager database.
     
  • Custom Fields  - Improve the use of custom fields so these values can be set at other levels then just Type. 
  • Asset Filters  - We will be looking at ways to put asset filters on technicians in order to restrict their view on what assets they will be able to view and edit.

    If you have any comments or ideas then please share.  We are always open to hearing your feedback!  You can also go to our web site to learn more about our web based helpdesk software at www.bigwebapps.com

  • Posted by Patrick Clements on 10:46

    Recent Speed Issues
    Apr 15 Jason Moore

    We have had several clients reporting major speed issues in recent days and a degradation of speed over the last few months.  According to all of the reports that we have been monitoring, there is not a bandwidth issue, but it is now clear to us that the real world reports coming from you, our clients, are in contrast to these.

    We have implemented some short-term fixes today, so you should experience a speed increase immediately.

    We are also working on more long-term fixes that will take some time to fully get in place but will have a greater impact on getting the HelpDesk back to the speed that you are accustomed.

    If you have any questions or comments, please do not hesitate to contact me directly.

    We apologize for negatively impacting your ability to perform your job to the best of your ability.

    Jason Moore
    866.996.1200 x 702
    jason.moore@bigwebapps.com

    Or create a ticket for us by sending an email to support@bigwebapps.com

    Posted by Jason Moore on 11:21

    Continual Improvement > Status Quo
    Apr 08 Patrick Clements

    One of the great things about being in technology and especially catering to service management and customer support is the desire for continual improvement.  It is a part of our company’s DNA to always be looking for the next best feature for our solutions and figure out how we can improve what we are providing to our customers.  One of the main things we look to reference is the ITIL framework in handling continual improvement as well as constantly talk to our customers.  Improvements must focus on increasing efficiency as well as maximizing effectiveness and optimizing costs of services.  Thanks to an article, How to Conduct an ITSM Process Assessment, provided to us by Matthew Frederickson of Council Rock School District it helps define the beginning phase how to conduct an assessment for gathering data for continual improvement. 

    The goal of an assessment is to effectively collect the data, analyze this data, and turn it into some useable sense of judgment.  The Pink Elephant team break information into 4 parts:

    • Data – a set of discrete facts about events
    • Information – comes from providing context to data (who, what, when, where?)
    • Knowledge – composed of the tacit experiences, ideas, insights, values and
    judgments of individuals, used to facilitate decision making (how?)
    • Wisdom – the application and contextual awareness to provide a strong common
    sense judgment (why?)

    There are some best practices out there on how to adequately go about gathering data, but the key is to always ensure the data you are collecting is quality data.  Once you understand what the data is telling you then being able able to effectively make sound decisions which are in-line with your business objectives.  Of course everything will then tie back to to measure, measure, measure the results. 

    Posted by Patrick Clements on 11:32

    bigWebApps Town Square
    Apr 06 Patrick Clements

    If anyone has followed bigWebApps closely enough you will know customer experience and satisfaction are some of the things we talk most passionately about around here.  Now we are looking to take the customer experience a little deeper and enable our clients to interact with each other to share tips, advice, and information not just on bigWebApps solutions, but also with what is going on in their industry or their profession.  We have started an on-line ning community site called Town Square (http://bigwebapps.ning.com/) where you can log in and start talking to like-minded folks.  We are looking to get quality discussions led by the community and not by us.  We feel this will be a great way for us to learn what you really need and how we can better assist.  Log in and get setup.  We look forward to your hearing from you!

    To watch a quick demo on how to get started check out this short video

    bigWebApps Town Square
    Posted by Patrick Clements on 11:06

    Is Your Idea Key to SaaS Success?
    Apr 03 Jason Moore

    BrokenLightbulb

    You have probably already guessed that the answer, in my estimation, is no.

    You may be able to garner some attention from friends, a few dollars from friends and family, and a decent amount of attention from local media outlets.  But your idea is worth zero without execution.

    Below is, in my order of importance, the list of the key ingredients to you achieving success (you define what that is) with a SaaS company.

    1. Sales – This is intentionally separated from marketing in this context.  Until you receive money via your product you are still only in possession of an idea.  Selling can be defined in many different ways, though, so it does not have to be a direct sale to a client.

    Seth recently wrote about finding 10 people who want/need your product enough to take you up on your offer.  Once you have ten, find ten more.  If you’re lucky, the first ten will be finding ten more at the same time because your product delivers as promised (or more).

    Some of you may feel that this is marketing. But that’s one of the main problems with a non-sales culture. People are extremely comfortable when they feel they are “marketing” but icky when it’s called “sales”.  If you have a product that is going to positively impact your potential clients, then you are doing them (and yourself) a grave disservice by not getting it into as many people’s hands who need it.  If you get uncomfortable about telling someone you know about your product, then your sub-conscious may be telling you that you are over-promising.

    2. Relationships/Support – the misconstrued dream that many people entering the SaaS world have is that once you build the application and it works well, all your clients will understand it, adopt it easily, hand over their credit card, and never cancel.  Okay, maybe when it’s put like that you deny that you feel that way.  But you’re only lying to yourself.

    If anything this group could have been lumped in with sales because as a SaaS model company, your relationships with your current clients is your on-going sales model. This does not have to be a time-intensive process if you implement the proper tools and controls, but it does take effort.

    37signals are masters at this.  They have a recent post on exactly how important their customer’s experience is to them.

    We had a recent post here about how the relationship goes well beyond your customer service rep.  It is also the responsibility of your billing people, marketing people, collections staff, everyone!

    3. Operations, a.k.a. Bootstrapping – if you are going to survive, you better have the purse strings drawn tight on unnecessary expenditures. No matter how good your sales and relationship teams are, the person in charge of your outgoing expenses can cut the jugular at any second.  Once it’s cut; lights out.

    NOTE: I am aware that there are a few companies out there like Facebook and Twitter that can bleed money for what appears to be forever. Go buy a lottery ticket instead.

    4. Technology/Your Idea – this section does not include all technology involved throughout your company.  It’s impossible to separate any one department from the general term “technology.”  The idea here is that your idea, although the basis of the business being started, is not the most important piece to your future success.  Obviously, you need a viable concept and the development chops to build it (whether on your own or hired), but without the key pieces in place your application is just another piece of unused software… but delivered over the web.

     

    Photo Credit: Kyle May

    Now Where Did I Place that Server?
    Apr 01 Patrick Clements

    One of the main elements in IT support (with the key element being customer happiness, but that is for another discussion) is the asset itself.  Before the days of cool inventory tracking software, proven service management frameworks like ITIL, or automatic hardware failure warnings, technicians would be simple break fix guys like plumbers or electricians.  When something went out or started acting funny they would have to open it up and investigate.  It was a very reactive break/fix approach to IT support and ultimately was proven to be a very expensive way in managing networks.  Luckily for IT folks, business folks saw a need and began filling this need with solutions.  IT infrastructure reliability is as important to a modern day business as a profitable sales force or a skilled management team.  Now knowing where your hardware is located, what each piece contains, and what is the service history and profile information are just entry into today’s game.  Organizations now need to understand what does this asset mean to our business.  What does it’s function mean to our overall organization’s business objective.  How does this asset affect the behavior and performance of other assets related to its work function.  They need to be able to answer the question ‘What happens if I make a change to this asset?  What will be the outcome to my customers and the overall business’s objectives?’.  To help answer these questions a relationship repository is quickly gaining adoption in the form of what is called the CMDB (Configuration Management Database).

    The CMDB is a concept developed from the framework called ITIL (Information Technology Infrastructure Library) which contains details about the important attributes and relationships from one asset to the other.  It documents the technical components of the assets, who has ownership of the asset and what is it’s relationship with other assets it affects.  The foundation of having this information is to be able to easily reference during the change management process.  Meaning any time an IT staff wants to make a change to an asset they will have visibility into it’s true effect on the company. 

    A good asset management system can help root out redundant systems, unused\overused software licenses, and unnecessary overhead expenses.  The more consistent and automated your organization can become in managing it’s IT infrastructure the quicker you can get away from fighting fires and start meeting your organization’s objectives.  Learn more about our web based helpdesk and asset management solution by going to our web site at www.bigwebapps.com

    Posted by Patrick Clements on 16:59

    bigWebApps WareHouse is Here!
    Apr 01 Patrick Clements

     4-1-2009 3-34-18 PM

    After a couple of years of focus group testing and application tweaking we are happy to announce the latest application to the bigWebApps cloud suite, bigWebApps WareHouse.  WareHouse is an on-demand internal inventory tracking system for organizations needing better visibility and accountability into their parts ordering process.  We heard plenty of stories from our customers on how they need to get some control on what parts are being ordered, visibility on where these parts  are located, and a simple way of auditing these storage areas to get up to date counts.  We initially thought of this as an application as an upgrade to the HelpDesk solution, but getting more feedback and requirements we figured it was it’s own stand alone application which would integrate into HelpDesk. 
     3-31-2009 4-52-14 PM

    What we created is a shopping cart format for organization’s users to easily request parts from various departments (i.e. Technology, Facility Maintenance, Operations, etc.).  The system would then be able to be setup in a workflow format allowing items to be approved and marked for delivery. 

    Three key areas the solution addresses are;

    1. Creating better inventory controls – establishing the vendors with whom you choose to work with and with how you process orders from them, setting min/max levels on items to ensure ‘high use’ parts are readily available, and being able to approve or deny which items are requested from your users.
    2. Maximize the utilization of inventory – allowing visibility in where items are being placed and easily being able to transfer items across storage areas
    3. Audits using existing staff – leveraging people in your organization to do physical counts on a scheduled basis.

    We developed the system to allow organization to use local staff and resources to keep inventory levels up to date.  The goals is maximize the use of your parts and inventory across your organization and decrease things such as shortage, over stocking, and spoilage.  The system is built to be flexible and can be used as a simple one closet storage area or can be expanded to accommodate a larger decentralized inventory system which handles large bulk orders and multiple transfer requests.

    Let us know if there is any interest in getting setup on your own demo.  You can contact sales at 1.866.996.1200 ext. 703 or sales@bigwebapps.com. You can also go to our website to learn more about our web based helpdesk solution.

    Posted by Patrick Clements on 15:59
    Copyright © All rights reserved. bigWebApps Inc. 2002—2010.
    Untitled Document