Hank Luhring’s Blog

Checklists - simple, but effective

by Hank Luhring - Published: March 3rd, 2010

A friend of mine, a hospital administrator, sent me an article about the use of checklists in healthcare — http://www.npr.org/templates/story/story.php?storyId=122226184

The article discusses the book “The Checklist Manifesto: How to Get Things Right” by Atul Gawande, a professor of surgery at Harvard Medical School. Checklists are a simple tool, yet amazingly effective. Airplane pilots have used them for years. Dr. Gawande uses checklists himself in surgery. In the article he says “I have not gotten through a week of surgery where the checklist has not caught a problem.”.

Checklists are also quite useful in business. Our IssueTrak customers implement checklists using the tasks function. We have one customer who has a standard set of tasks (or “checklist”) for bringing on a new employee that has over 80 steps.

Internally, we use checklists implemented via IssueTrak to specify all kinds of processes, from adding a new hosted customer, doing an onsite customer visit, sending out an evaluation copy to a prospect, to the old stand-by, adding a new employee.

In the current economic environment, where fewer people are doing more work, it is more important than ever to be sure processes are spelled out, and followed. We see more and more customers doing that with IssueTrak.

Comments: No Comment - Category: IssueTrak, the software

Good Execution

by Hank Luhring - Published: October 19th, 2009

At IssueTrak we like to visit customers at their offices to see first hand the challenges they face, and how our software is working out for them. Recently four of us went on a routine visit to a customer close by. On the drive over I noticed Mike, our support manager, was doing some texting, but I had no idea what it was about.

When we got there, the IT director mentioned she liked IssueTrak a lot, but she said lately it was running slowly, especially when marking tasks on an issue as being completed. We asked her to show us. She brought up an issue that had the most tasks I’d ever seen on one issue — there were over 75. This was an issue to bring on a new employee. It had HR tasks, IT tasks, facilities tasks, and more.

She marked a task as being done, and the speed was not bad. She was surprised. She said it used to take much longer. Mike mentioned that there had been a problem, but it had been fixed. The IT director was very impressed; they had called support just 45 minutes ago!

Here’s what happened — they called support, and spoke to our support rep Patrick. Patrick realized that this was the same customer that his boss Mike was about to go visit. So he immediately went to Mike and told him. They called in other resources and determined that we had a hot fix that would solve the problem. This customer was a hosted customer — their IssueTrak application ran on our servers, not theirs. So while Mike and the rest of us were driving over to the customer’s office, the support people were applying the hot fix. The texting that I saw was Mike and Patrick and others communicating about the progress of the hotfix installation.

The installation was completed just as we walked into the customer’s conference room. They were pleased to see that the problem had been taken care of so quickly.

It would have been very easy for things not to have gone so well. Mike had done a good job communicating to his team that he was going to visit a particular customer. Patrick was on his toes to recognize the particular customer when they called in. He showed good initiative in contacting others within the company to get that hotfix applied pronto. The others who applied the hotfix were great to respond to Patrick’s request for help so quickly.

It can be frustrating sometimes when dealing with a company where lots of different people in the company need to work together to get something done. It seems like often someone drops the ball. It pleases me no end that this rarely happens at IssueTrak. When a customer or prospect has interactions with our people, they come away pleased. And it seems the more contacts an outsider has with different areas of IssueTrak, the more impressed they are that we are a team of people who listen well, figure out what needs to be done, and then gets that done, whatever it might be.

In a software company, the people side of things is very important, and we’ve got that down very well.

Comments: No Comment - Category: IssueTrak, the company

IssueTrak customer service

by Hank Luhring - Published: September 21st, 2009

One of our sales engineers recently received this email from a customer:

“I want to thank you again for all the support and willingness to help. There aren’t many software companies with the level of customer service you guys provide. As a result our business leaders are embracing IssueTrak and our user base is growing. ”

It wasn’t that earth-shattering a situation. The customer had two separate instances of IssueTrak running. He wanted to combine them into one instance because of a company reorganization. He wanted to transfer the licenses from one instance to the other. We told him no problem, there would be no charge. We would just need to send him a new license key reflecting the additional users on the one instance. He was pleasantly surprised, and said great, he’d get back to us.

He called a few days later, apologetic, saying he needed the license keys right away; that day. Again, our sales engineer said no problem, and promptly got the new license key to him so their IT people could make the change quickly. He has some additional questions about how a third group might use IssueTrak, and we’ve set up a meeting with our Professional Services people to give him guidance.

Our software is great, but the product is not the only facet of what makes a good software company. It is especially gratifying to me that the more contact a prospect has with people at IssueTrak, the more likely they are to buy. They find that our sales engineers are top-notch. Our support people are friendly and get problems resolved quickly. Sometimes our developers will get involved when a prospect has a question. When every touch a prospect has with our company results in a good experience, we end up getting more sales, and more satisfied customers.

We enjoy what we do, and we do it well!

Comments: No Comment - Category: IssueTrak, the company

Developing a tracking system in-house can be risky

by Hank Luhring - Published: August 13th, 2009

I enjoy visiting customers, and seeing first-hand how they use IssueTrak. This week several of us visited a very large company who happened to be using IssueTrak in a facility here in Virginia. The reason why they were in the market for an incident tracking application is interesting.

They had developed one inihouse. They showed it to us during the visit. It did the job, but after a few years they wanted to improve it. The person who had written the application had been laid off due to the economy. Another fellow in the help desk knew programming, so he decided to look at the code to see if he could make the improvements they needed.

He looked at the code, and discovered that it was written in Korean! They concluded they could not modify the program themselves, so they searched for web-based ticketing systems, and chose IssueTrak.

There are some circumstances where a custom application is exactly what’s needed. But there are risks involved in creating an application from scratch in-house. Very rarely are such projects completed within the estimated time-frame. Custom applications need to be supported once they are deployed. People are transferred, promoted, or leave for greener pastures. These personnel changes are disruptive on two fronts — when the development and support personnel change, problems with the application cannot be handled. Also, when there are personnel changes on the end-user side, this too can be disruptive, and can create significant support calls to the in-house resource who developed the package.

Problems arising with custom programming because it is written in a foreign language doesn’t happen that often. But we encounter situations on a regular basis where a well-intentioned effort to develop something in-house doesn’t work out, and the organization chooses IssueTrak or some other off-the-shelf package to do the job instead.

Comments: 1 Comment - Category: IssueTrak, the software

Yammer caught on QUICKLY at IssueTrak

by Hank Luhring - Published: June 29th, 2009

I heard about Yammer from the TWIST podcast (This Week In STartups). TWIST is hosted by Jason Calicanis, a frequent guest on TWIT (This Week In Tech), and CEO of Mahalo.com, a human-powered search engine.

I was listening today to Jason talking with David Sacks, the CEO of Yammer. David also founded Geni.com, and before that he was a co-founder of PayPal.

Both Yammer.com and Geni.com are really nice Web 2.0 applications. Check out Geni.com and see how easy it is to get started on your family tree. I don’t think I’ve ever seen anything THAT easy!

At Geni.com, they needed an internal application for collaboration, so they wrote one. It has elements of Twitter and Facebook, but is private, and internal to the company.

The application they wrote worked so well for them that they decided to start another company dedicated to that application. That’s what is now Yammer.

I thought it might be good to try Yammer out at IssueTrak. I thought I’d start small, so I invited just three people, and then quickly jumped over to Outlook and composed an email explaining about Yammer. Before I could hit “send” the people I invited had invited lots of other IssueTrak people, they had uploaded their photos, they had posted messages. I’ve never seen anything take off so fast! I quickly sent a followup email saying go ahead, invite everyone in the company!

IssueTrak has been on Yammer for less than an hour. There is an org chart fleshed out, and 20 people are enrolled already, several with their pictures uploaded! Amazing!

Comments: 2 Comments - Category: IssueTrak, the company, Podcasts, User interface

37 votes to 33

by Hank Luhring - Published: June 2nd, 2009

There is a great new site to get answers to questions regarding servers, networking and general IT. It’s called ServerFault.com. It was set up by Jeff Atwood and Joel Spolsky, the two fellows who created StackOverlow.com, probably the best site on the Internet to get programming questions answered. StackOverflow is now getting over 3.5 million unique visitors per month.

Jeff Atwood writes a blog called Coding Horror. Joel has Joel on Sofware. One of Joel’s popular posts described questions to ask of a prospective employer if you’re looking for a programming job. If the company doesn’t follow certain best practices, you might not want to work there.

Someone on ServerFault asked if there were similar questions to ask to see if a company was doing IT right. Here’s the link to that post.

What was very interesting to me was that the question that got the most votes was “Do you use an incident/ticket tracking system?”. As of this writing, that question got 37 votes.

The question “Do you perform system backups, and do test restores regularly?” got 33 votes.

We like to think that our type of software is important to organizations doing IT. It was surprising to see that the use of tracking software for IT got even more votes than doing backups!

Comments: No Comment - Category: IssueTrak, the software

Good description of capitalism

by Hank Luhring - Published: May 16th, 2009

In her column in today’s Wall Street Journal, Peggy Noonan expresses the concern that with all the government activity taking place in developing spending plans, tax plans, additional regulations, new reforms, energy proposals, healthcare changes — we have to be careful not to kill the goose that lays the golden egg! And what is this goose? As Ms. Noonan describes it:

“The goose of course is the big, messy, spirited, inspiring, and sometimes in some respects damaging but on the whole brilliant and productive and priceless wealth-generator known as the free-market capitalist system.”

Comments: 1 Comment - Category: Business

“There’s a beauty to starting a company in a scrappy manner”

by Hank Luhring - Published: April 24th, 2009

This is a quote from Graham Hill, who was recently on the Venture Voice podcast. Hill started a business called TreeHugger.com using his own money, and sold it several years later to the Discovery Channel for $10 million.

I started the company which became IssueTrak back in 1992, with no outside investment. Not having a lot of money in the beginning can be a good thing. It forces you to focus on what the market wants. And like Graham Hill says in the podcast, the early experiences determine the DNA of the business.

In our case, doing extensive custom programming early on forced us to listen closely to what customers need so that we could implement an effective software solution. Today we continue to add features the customers ask for.

I highly recommend the Venture Voice series by Greg Galant. Here’s a link to the Graham Hill podcast. I especially enjoyed some of the comments he made at the very end. He said too much money can be bad for a company. And you don’t need to be a non-profit to do good in the world. A for-profit company can also be a vehicle for staying true to one’s values, and can give one the wherewithal to make meaningful contributions to society.

Comments: No Comment - Category: Business

Customer does more than help desk with IssueTrak

by Hank Luhring - Published: March 13th, 2009

We occasionally get unsolicited comments from customers telling us their experience of using our software. Here is one that came in recently:

“IssueTrak has gone from a good idea to a business critical resource in less than 12 months. It has been enthusiastically received by our production (printing and forms), Information Technology, HR and Marketing/Communications Departments. I am looking forward to a more productive 2009 as a result.”

Although many companies buy IssueTrak for help desk use, we see growing use of our product in other areas, especially in general issue tracking.

Comments: No Comment - Category: IssueTrak, the software

No Bureaucracy

by Hank Luhring - Published: February 6th, 2009

Yesterday at our company-wide meeting two different people spoke up to praise LaDonna Beauregard, our Vice President for Development. Both people worked in Support, and LaDonna had personally helped them solve a problem that they were working on on behalf of a customer. What impressed both people so much was that they didn’t have to make an appointment with LaDonna or fill out a form or jump through other hoops. Instead, during a casual conversation the topic came up, and LaDonna took it upon herself to look into the problem, and either solve it herself in one instance, or encourage someone in her department to look into it in the other case.

Although we have experienced significant growth in the last few years, even being named to the Inc 500, we are still not a bureaucracy. Outsiders often remark that they like dealing with IssueTrak, because things get done, problems get solved, needs are met, we listen.

For IssueTrak team members to provide first-class service to our prospects and customers, we have to do that for each other as well. I’m glad to see that’s happening.

Comments: No Comment - Category: IssueTrak, the company

Checklists - simple, but effective

Good Execution

IssueTrak customer service

Developing a tracking system in-house can be risky

Yammer caught on QUICKLY at IssueTrak

37 votes to 33

Good description of capitalism

“There’s a beauty to starting a company in a scrappy manner”

Customer does more than help desk with IssueTrak

No Bureaucracy

Search

Categories

Archives

Meta:

Theme Switcher

Search

Categories

Archives

Blogroll

Meta:

Theme Switcher