IT Business

The documentation quandry & partnerships (help)

I've thought long and hard about this blog post. At the core, some of you may see it as the most insulting thing I've ever put up here and in a certain light I can agree. However, I am really struggling, I do not have a pretty solution and so far none of my advisors / staff / community partners has been able to come up with a good one so instead of seeing it as an insult, read it as a plea for help. If you have any advice please drop me an email.

One of the biggest problems we have at Own Web Now is documentation. Bar none. This isn't exactly an accident - you've seen me write before about how we were trying to source-out the aspect of ExchangeDefender distribution to some of our community friends but for one reason or another, that has never happened.

So now I'm faced with a tough decision when it comes to documenting the solutions we provide because we do not have the kind of support bandwidth required to support the part time paper boy / part time IT guy that seems to be more and more prevalent in todays SMB scene. It's not that those people are inherent idiots by nature, but when you don't understand the basic concepts of how the Internet works the higher up concepts of how the systems interact and operate, as well as troubleshooting, become almost impossible. I am sure every IT department experiences this, I am sure we have been dealing with this for years. But now we have the ability to track it and the numbers look ugly.

Here is the problem - People that are not qualified to support IT systems are going around selling their (managed) IT services but have, at best, just a basic understanding of both management and IT. So they come to us and ask for ___. We explain to them why certain things don't work, we explain to them that certain things are as such by design and behavior, we try to point them to RFCs, we try to help them fix the problems that are holding back the deployment. In the end, we provide better direct support than most companies out there - and in turn become that providers support-bitch. They come to us with all the problems in the world, related and unrelated, and sometimes just "dropped you an email just to see if you have an idea..." - rinse, repeat.

This is your usual 90/10. 90% of our client base knows exactly what its doing, while the other 10% probably shouldn't be allowed near a computer. Now, guess which group causes 90% of the support requests? Right. And half the time, at least according to our stats, they are just trying to pass the bucket and not really come to a solution at all. Unable to use Google. Unable to use Yahoo. Unable to post a question in Microsoft Partner Groups. Etc.

We're a few days from launching the new web sites across our business and I am considering pulling the public documentation sections back. I am scared to death of enabling some of these people to provide our services and I think giving the blueprint to the network infrastructure to someone that just got laid off from a mortgage broker where they were the most technically savvy of the bunch is akin to giving me a pile of bricks and saying "go build that building"

So..

I am asking for advice. How would you discourage someone that shouldn't be messing with cloud services from trying to? Here is what we've considered along with the cons and pros:

Mandatory $500 partnership setup fee, half credit at the end of the year. Pro: eliminates startups and DIYers. Con: might antagonize legitimate IT business.

Mandatory exams. Pro: establishes a baseline. Con: expensive to design, cheating.

Commercial support contract, paid per hour of support. Pro: zero sum game. Con: bitter disputes over what is expected support and what is ad-hoc support.

Higher minimum committments. Pro: keeps startups out. Con: goes against the company spirit, always been startup friendly.

Peer referal requirement. Pro: Establishes a network of people who know/use products. Con: Just passing the problem off to someone else.

Last resort: Purchase a support contract because your technology IQ does not fit the supportable parameters under our standard SLA.

As you can tell, all these "solutions" are ugly and we're getting slaughtered by support requests from a small portion of our customer base that needs help beyond what we can provide. We've collectively thrown our hands up in the air over this one so if you've got some brilliant advice, I'd love to hear it (vlad@ownwebnow.com)

P.S. Someone came up with an idea that I should have some sort of a kindergarten system because my articles seem to be written for IT toddlers (their words, not mine; "Who the heck needs a screenshot to find an SMTP Virtual Server in ESM and if they do shouldn't they not have access to it in the first place???"); While I did consider this for a split second, Own Web Now Corp cannot continue as "Vlad's Own Web Now Corp" and I'm a little too accessible to also provide support activities. As a matter of fact, my name will pretty much vanish from the support portal next week.

The Dip Modified: Are you -er or -ed?

The Dip book has really reaffirmed my long standing (and often criticized) belief that not everything can be fixed with hard work, or at least may not be worth the time investment. However, I disagree that it's a black and white case of stick with winners or kill the losers. There is a lot of room in the middle, especially in business, where there are other options. You can read Seth's excellent book on his take about why people don't know when to quit, but since you are here, let me offer you mine.

In a nutshell: Over the large sample of transactions, there are some in which you are the fucker, or you're getting fucked. Thats the reality of business, you win some, you lose some, and in the middle you're just trying to turn something into a winner or find the least expensive way to kill it. Over the course of time you will lose and win - the key to making it big is making sure the wins are big.

Win
Not much to say here except congratulations. Just don't get arrogant about it. See _every rapper that ever lived_.

Lose
S*** happens. Move on.

Things Suck
This is the big gray area in the middle that requires a lot of consideration because world is not black and white. If you're in a difficult situation you have some decisions to make.

Planning & Evaluation

So, your plan failed. Ok, don’t panic, sit back and lets look at it. Before you decide where you go, you need to find out where you want to go. Or not go. The thing is, before you decide you need to evaluate all your options. Here are the key one in any arrangement, at least as far as I am concerned.


Whats in it for me?
Do you have anything to gain if you stick with the current course of action? Is this a personal gain in monetary terms or are you just doing it for your ego?
Do I control the outcome?
This is the question you need to answer because it controls the outcome more than anything else. Truth is, if you are in control no amount of hard work is going to fix this because someone else controls the outcome - not in direct terms but indirect terms like satisfaction, timing, etc.
What else at stake?
Is it just your ego that will get bruised or will it be your business? Will it be your business in the short term or are you going to lose revenues for years and years after giving up on this project. Does it impact you indirectly (reputation) or directly (revenue).

Now that you've answered those questions and hopefully decided whether you're going to continue down the road, it's time for actions and time to establish the new plan (because if the old one worked you'd never be in this spot to begin with).

Actions

Once you have a new plan to make it out of your dip, put them in play. But its not quite as simple, you’ll have a few things that are guaranteed to happen:

Tears and paralyzing fear
We all have these. The feeling of despair, the feeling of inadequacy, the feeling that if you just got a day or two of good sleep, or a break, somehow the problems would magically go away. They don't. But it's a stage, deal with it in the best way you can and get back to the problem as quickly as possible.
Know the outcome and stick with it
Remember, you need a new plan. Adjust your timelines, adjust your expectations, adjust your schedule, adjust your promises - whatever you gotta do to make it happen.
Or hell, kill it now
And if all else fails, just kill it.

Key to success

You win some, you lose many. Not really a pesimistic view but let's look at a case of a sure way to go broke: Las Vegas coin slots. On the average, the wins are tiny. Losses compound over time and are exponential at least by comparison to the losses. This is why the casino advertises 97% payouts, bags of money, etc: Because people are stupid and like to dream about winning!

The key to success is to win big. To hit the jackpot. There are plenty of business contracts that you will enter into where you'll certainly get the short end of the stick. You're the -ed in this case. And here is what separates the winners from the maraginal successes and the losers:

Winners stick to it.
Losers cut out too quick.
Marginal successes try to curb both the winning and the losing, in the end really having nothing of value.

This applies to a lot of the SMB IT folks out there. What's the biggest and best trade tip for a profitable SMB business? Kill the B,C,D,F clients and only keep those A clients. After all, who the hell cares about the deadbeats, difficult business owners, whine, bitch, moan, repeat. If I had a penny every time I got that advice. I tend to look them straight in the eye and ask them: How do you grow your business. Nine out of ten times they say its the word of mouth: Ok, quick - what kind of word of mouth do you get when you fire a client because they are too difficult to make a profit on? :)

See how that works? The people that try to cut and run in the short term end up with mediocre or even non-existent wins in the long term. Sure, it's better than the folks that stick their head in the sand and end up bankrupt, but if you're looking to be a winner this is not the way to go about it. Business, and entreprenurial enterprise itself, is a game of risks. Sometimes you lose, but if you can win big you can afford to lose more often.

Thats at least how I live.

Why doesn't anyone care about us?

This is an open letter to the reseller community that just cannot figure out why vendors do not write software to support them.

Hypothesis: We, as VARs/ISPs/MSPs/GSIs deploy, manage, maintain and recommend vendor software. It stands to reason that we reduce vendors cost of support, provide free marketing, provide free installation (doesn’t cost vendor anything) and as such the vendor should be writing software to enable us to reduce our costs of the said support, deployment and ongoing migration/maintenance.

Sound reasoning. And if it weren’t a fantasy, no software vendor would ever have a sales force, R&D department or even technical support. Who do you think those folks are working for? What do you think they do all day long? What do you think pays their salary? Here is how the world actually works:

Reality: Indirect sales channel is more expensive to market, support and sell through than direct sales to the end customer. The indirect sales channel has no buying power, no volume, no expertise and generally no loyalty to the product in the same way that an end customer would when it comes to signing multi-year renewal contracts. To top it all off, the indirect sales channel demands free software, free support, free internal use licensing, free trials for their prospects, free sales assistance and most importantly – huge margins that make most indirect sales an unprofitable venture in the long term.

So if that is the reality, why would any company want to have a reseller program to begin with? Because it is all about marketing and getting the product out, even at a loss if it establishes the product within its target segment. Ever notice how low-end commodity software comes with a margin of just a few points? Ever notice how ridiculously overpriced and specialized software comes at an incredibly high profit sharing margin, at times close to 20–40%? Why do you think that is?

Commodity software: Commodity software like antivirus for example comes with a very low discount rate and a margin for the reseller. Why? Because the reseller is given the same level of discount (though usually less) than the retail channel that commits to a much larger volume.

Specialty software: Specialty software like complex accounting and ERP systems, government, custom scientific solutions and others come with a huge profit margin for the reseller because reseller adds an actual value beyond that of getting the sale. They deploy, customize, manage and work with the client day to day or  month to month to keep the software evolving with the requirements of the business.

So, if the software or hardware vendors make most money out of their direct sales, why do they have partnership agreements, APIs, integration frameworks and software development kits?

The key to software and hardware profits is volume. The easiest way to gain volume is to become a preferential vendor or an underlying engine of a third party software or hardware solution that has a massive direct sales force. Again, think antivirus. The dominant SMB VAR solution in the antivirus game is Trend Micro. Reseller friendly, solid product. Surely they are the largest company out there? Surely its dominance in the SMB channel would make them difficult to beat, who in their right mind would install McAfee? Yet, McAfee is larger than Trend Micro (5.8 billion vs. 5.6 billion) because as absent as McAfee happens to be from the VAR space they sell as an engine – to a little company called America Online.

Software and hardware companies look for profitable partnerships. Profitable partnerships happen in large volumes because they mean less time and headcount spent on training, support, sales, feedback and conflict resolution.

That is short sighted, you might say. If you were in charge, you would do all you could to explain these naive software companies that the future is the VAR and they need to integrate with one another if they are to get your business.

This is a statistically unproven myth. If it were a realistic argument there would be hundreds and hundreds of companies out there trying to create mashups of all the APIs and administrative controls to allow the VARs to centrally command and control their entire enterprise.

Yet there are none. Why?

Volume. VARs expect everything for free. Enterprise pays through their ears for solutions like MOM, SMS because they have to manage thousands of seats. A lot more people integrate their software with MOM and SMS than with companies like Autotask, Connectwise. Don’t believe me? They don’t integrate with MOM or System Center because they want to make their products friendly with Microsoft, they do so because they want to sell thousands and thousands of seats at a time – and those companies tend to use MOM.

The most flawed misunderstanding of the VAR community: “Software and hardware companies fail in the SMB space because they are overpriced or provide dumbed down solutions.”

Wrong on both counts.

The key reason software companies fail in their entry to the SMB market is because they underestimate the need for bandwidth for dealing with the SMB market. A thousand run of brochures can cost a company $18,000 to produce, qualify and mail. If they get 1–2% qualified leads they are lucky. By comparison, an enterprise CIO can be flown to Hawaii in first class and 5 star accomodations for $15,000. If you were to put your money, where would you invest?

Dumbed down solutions called “SMB” or “SmallBiz” editions lead to higher sales and higher satisfaction than the enterprise at the lower price. Truth of the matter is, the end customer is buying a feature set that addresses a particular problem and is making a purchasing decision based on budget (if they have one) or on the potential productivity savings to be gained from that solution. So when dealing with VARs a software vendor trying to enter the space can either offer a turnkey version that is easier to deploy and manage but does not have all the features or the flexibilities of the enterprise version, or they can offer the incredibly complex and expensive enterprise version that requires 3 servers and two sales engineeres to set it up. Would you like to guess which one sells better?

Finally, why doesn’t anyone care about us (VARs)?

This is also a flawed, emotional argument made by external parties with no insight into what the companies are doing on the inside. All non-manufacturing companies are first and foremost service companies, we all strive to provide the best possible service to our customers. However, assuming limited budgets and hard release timelines, the primary goal of a software company is timely release and responsiveness to the market demands. People purchase software to address a problem, even for commodity solutions like antivirus.

So, I ask you to put yourself in the antivirus software makers shoes. You have six months to design, develop and deliver your new antivirus program. Your competitors are working on integrating an antispam piece and you are behind. What do you do? Sit down and focus on the API and management consoles to reduce the operating costs of your reseller base that accounts for little if any profitable prortion of your sales, or do you try to beat the other antivirus maker to market in quality or efficiency of your software? If the answer to that isn’t self-evident, take the money factor out of the equation completely. If you were no longer the leading piece of software in the market, and you did not provide the most features that the end customer needed, don’t you think the VARs would dump you for the competitive solution?

Therein lies the problem in the VAR-Vendor relationship. VARs lack loyalty, sales volume and expertise to support the complex or even the most basic solutions on their own (doubt that? how much time did you as a VAR spend to train your first employee? How much productivity did that cost you?) and the software vendors cannot make a profit without huge sales numbers because the commodity software has a lot of competitors.

How do we fix this?

Well, as a VAR you might want to try being more loyal to your software vendor. But let’s face it, thats not going to happen because that will put you in the red and when it comes to your house or vendors house…

How can we as vendors address this? I am going to let you in on a little secret over at Own Web Now. Even though we don’t make most our profits or our revenues from the VAR space, I consider it the most critical piece of our companys future. Rewind through the post to find out the reason why software companies write software: To address end customer problems and make them more efficient and profitable. Now, how do we make the most important and most relevant product for the end user? By working closely with their trusted advisor.

Long term view. In the long term, our VAR partners will give us feedback, feature suggestions, be our front line of support, our support lead, our go-to direct managers and our R of R&D. Most of the features you see in the OWN products today are directly driven by the partner feedback that they get from their customer base. In return, the development at OWN is completely open. As our partner, you have access to our internal and external bug and feature request sheet. Each partner sees the Development tab in our software and can see what we are working on. If there is something missing, our partners tell us about it. In effect, our VARs become our partners with the vested interest in the future of the product development and become more loyal to the solution because it evolves with their needs. In turn, OWN gets the feature set that actually makes the difference in the end users business.

It is a means of artificially creating loyalty through the joint development and distribution effort by the partners and OWN. It no longer stands just as a VAR-Vendor relationship, where one side  is trying to screw the other for the extra revenue basis point. It changes the economics of the relationship as well, because it eliminates support and research headcount and assigns it to development.

However, this is not something you can expect from your software vendors because it is incredibly painful to reorg the business to support such a change in the business model. As a software vendor, you really have no other choice though. As the VARs mature and start offering services, management and monitoring plans, complex support agreements - they too face the same economies of scale that a software  vendor does. Anything that becomes incredibly expensive to support or sell will fail for the VAR. In order for VAR to survive it will have to sacrifice some flexibility in order to provide a predictable cost and a predictable point in time. The key to marginalizing (or commoditizing) any service is having a predictable cost without unpredictable surprises, such as trying to move from one commodity solution to another. 

So…

I hope this post gives you some insight into the business models from someone who is both a software publisher and a VAR. It is not an easy relationship by any means, but companies that trust one another and have the best interest of each other and the joint end user they serve will indeed be the only ones that remain in business. The companies that accept their partners as material foot soldiers will get a more profitable distribution approach while gaining the research and insight into the end user that is very expensive to reach. The companies that show loyalty to their vendors will receive preferential treatment and input into the direction.

There is only one important factor: money. (struck through for people with incompatible RSS readers) Customer service, satisfaction and solutions that adequately address the problems those customer have.

Are you dumber than a New Yorker?

Note to foreigners not familiar with US TV: We have a hit show in the states where adults try to will million dollars by answering 5th grade (or lower) questions with a help of a fifth grader. Play on words title..

I’m on a little vacation in New York City and have been doing the usual tourist stuff. Now its no news that New Yorkers are the most inhospitable and rude people on the face of the earth and displaying that arrogance even in tourist destinations is just incredible.. but this weekend I learned more about my ignorance and showcomings than about NYC. It has been a very ugly mirror to say the least.

IMG_2480

Empire State Building: Typical line ride, more lines, rooms, stairs and elevators than you’d imagine Indiana Jones would take while raiding a tomb. So here is what I’ve noticed – the area is under construction. They obviously have a solution. But it doesn’t involve signs!

They literally had two guys that walked back and forth down the 10’ hallway to yell at tourists “You don’t have to take an elevator, you can take the stairs. Way to go genius. How many times are you going to do that before you figure, hey, maybe I’ll put up a sign.

Irony: I have seen at least 8 tickets opened up during the light weekend about items that we knew about! Routine maintenance stuff. Is it on the blog? No. Is it in the Shockey Monkey? No.

Statue of Liberty Double-Play: I made reservations online for a ticket that included a visit to the Statue of Liberty and Ellis Island. Awesome! But wile picking up the tickets this morning I am told that they can’t give me Statue of Liberty tickets. “So sorry, they stopped selling tickets to third parties so you’re going on a cruise.” – Ok, did they stop selling them yesterday? Last week? Month ago? Oh, no, they stopped doing it in 2005!!!! I made a reservation last week. Think they could have told me that one?

Irony: I announced last week that we’d be closed for business this weekend. But a global company never sleeps – maintenance still goes on. We worked on the ExchangeDefender reports, worked on the backup server, worked on the SharePoint 3.0, worked on ExchangeDefender portal.

And aside from the folks who were doing maintenance, who else knew or was told about it?

Point being – the better I get with the communication with my customers and partners, the more holes I see in the practice as well. What’s worse is, people that get excellent service do not expect anything but. The first time you slip up you lose all the credit and are second guessed for a month. Makes sense – If they didn’t bother to announce that I better check with them again. 

Back to the lab…. Nothing like a mirror to show you how everything you’re up to is nowhere near where it needs to be.

Review: Karl's The Super-Good Project Planner for Technical Consultants

Let’s face it, projects are what IT is all about regardless of whether you manage 5 workstations or 5,000. If you’re successful to a good degree you’re likely running several projects at the same time and tracking those can become difficult. Fear not, Karl Palachuk comes to the rescue with his latest e-book: The Super-Good Project Planner For Technical Consultants.

What’s in it..

Let’s hope that the picture is indeed worth a thousand words..

GLBSGPPTC

And there you go – 133 pages of The Project Book, telling you how to manage the 20 pages of the Project Binder word document. The Project Book is broken down into six chapters covering introduction, project management for SMB consultants, project binder, binder forms, “running” a project and finally sample projects and some closing thoughts. If you’ve never seen any of Karl’s work before he is really good at simplifying exactly whats at hand:

A project is any undertaking that requires more than two steps that can’t be completed at the same time.

 I assure you that the other 133 pages employ the same level of simplicity to make even the most complex projects easy to document and most importantly, easy to control. In chapter four Karl wraps it all up into the actual process of defining and starting a project. Included are plenty of forms, documents as well as questions and actions you need to consider at each step as you move through the project. More specifically:

1. Project Description

2. Define Goals of the Project

3. Define Where the Project is Today

4. Define Where You Want To Be

5. Define All Stages and Steps Needed

6. Final Check-Off for Project Plan

7. Project Evaluation

Of course each of those points could take you hours or days to complete but they serve a very important purpose - they let you control what you do, how you do it, when you do it, at what time you’re complete and knowing exactly where you happen to be at a time. The art is not in the obvious (above) the art is in having all of this put together in a way that you can manipulate it a la carte as you go about your day to day job.

What is perhaps more important than anything else is the steps above are accounted for, so you bill exactly for what you do and it is clear to both the client and the consultant/contractor/employee where the project is.

More projects, more pre-filled templates, more suggestions and ideas on how to go about project management.

The cherry on top..

Half way through the project guide, which at this point shows you how to manage web site moving projects and Veritas projects, Karl departs into sample projects. For example, moving a web site from SBS to a hosting service. Then off to switching to a new ISP. Bringing email in house…

Do any of these sound like the projects you’ve done a few hundred times already?

Now quick – how many of those went off perfectly and exactly as you expected them?

There you go. That is the whole point. The more successful you get, the more busy you get, the more employees you end up getting involved in your day to day operations, the more important project management becomes. Actually, the more important the act of establishing your project management process becomes, and this is why Karl again knocks it out of the park for the SBS consultants.

The Price

The incredibly outrageous $79.99. Believe me, it’s worth it. I am not just telling you this because I get $0.00 commission from selling this book, I am telling you this because I am trying to help you save your time and your effort and get your business more organized.

What is the cost of dropping the ball? Looking like an amateur that is just winging it?

The Bad & The Ugly

Before you get your hopes up about this e-book being all you will ever need to know about projects, management, documentation and more… slow down. There are no chapters in this book on how to manage a project with your favourite PSA, there are no excessive references to implementing this in Microsoft Project, tying it into accounting…

… it is simply a guide on how the projects are established, identified, documented and managed. Which tool, which accounting practice, what language or approach you take is up to you. Karl just gives you a kick in the butt and an awesome starting point to use NOW. Open the project_binder.doc, change the names to fit your company and start filling in the blanks.

Conclusion

I often talk about being a professional. The core of professionalism, aside from honesty, is accountability. How can you be accountable for a project if you don’t have it clearly defined? How can you tell where you are in the project if you don’t know where you started, where the end is and what the next step will be?

This is what Karl and the Super Good Project Planner (lets face it, project management guide) are about. It’s $80, the best money you’ll send this week, it will pay for itself the first time you use it and I’ll be darned if you don’t find more billable time with it or at least save yourself time providing ongoing support for that project down the road.

Bandwidth for Down Under

Wow, finally some good news hit on a Friday! Google is talking about laying fiber under the Pacific to Asia and Australia.

That is remarkably good news for me (well, I suppose for Australia as well) as we have a ton of customers down under and they have been far more receptive of SaaS than the American’s have. Then again, I’ve also noted that they are a lot more business savvy than we are and aren’t as cheap as we are either – so if this fiber ever makes it from San Francisco to Syndey..

P.S. I know this will excite at least a dozen people for all the wrong reasons so I’ll make your  day – If this pans out, you may just see us open a data center in San Francisco. Yes, I know, I know, what kind of an Internet company doesn’t have stuff at 316 Main, uveee, uveee, uvee – Drive to San Jose you lazy bastards

Vlad’s School of Customer Service: Productivity or Courtesy?

Here is another in the series of customer service tips I’d like to share with you: Do your customers expect productivity or courtesy from you? I’d imagine its a little bit of both but it depends on your profession. If your chosen occupation involves a uniform of clear heels and a gstring, you should perhaps be more concerned about courtesy than about productivity. But if you’re not a stripper or a massage therapist then this rule applies to you: smile and do what I’m paying you for. Quickly. 

This applies to everything and everyone. If you’re checking people in at a hotel I would have a far more magical day if you just smiled and hurried up instead of wasting my time with show specials. If you’re making my sandwich I would rather you hurry up than ask me to try your special of the day. If you’re cutting my hair, if you’re changing my oil, if you’re bagging my groceries, if you’re checking in a flight, if you’re selling insurance, if you’re taking deposits, if you have any kind of a job where you provide a good or a service to a customer, I am going to give you this huge, giant, enormous, megalithic tip:

Your customers are not there to see you.

Your customers are there for a product or service.

Shut up, do your job, and let me get to something I’d rather be doing.

There, simple enough? I’m buying a sub, I am not here to hear about your day. I am shipping a package, I don’t care that the lady in the back has a garden. I am getting my oil changed, I don’t care which bolt screws into which nut and what the differences are.

You have no idea how many people confuse customer service for overwhelming personal courtesy and joy. Customer SERVICE is a process of product/service delivery. It is a means by which you, in the most efficient and effective manner, provide that service. If your focus is not on doing a good job, quickly, you’re screwed.

For example, how do you think 15 other people are feeling as they wait for you to finish your casual chat with the customer. What do you think is going through their mind? is it:

A. Wow, I love what they have done with the bank lobby. The clerk certainly had an interesting weekend, I can’t wait for my turn so I can find out what he’ll be doing this weekend. The suspense is killing me, I sure have nothing better to do with my life and I come to this place as a social excursion, not business.

B. Get me the f’ out of here.

If you answered A you’re an idiot. I hope you have a body for a stripper because thats about the only good you are to the world of business efficiency.

If you answered B, good for you! I’d love to be your client. I am sure most other people would, too. At the end of the day your customers are doing business with you because you do a good and efficient job, they are not paying you to be their BFF.

This rant brought to you courtesy of US Postal Service.

I needs a Followup-Cleaning Monkey

_40171838_monkey203I need to hire a followup / cleaning monkey. As we continue to grow the need for a person that does no technical work is rising (ie, is incapable of helping, even if they wanted to); Here is what happens – we process a ton of orders, support requests, DR and other nightmare scenarios during the day. 9/10 times, we know the point of resulution and when we reach it, we close the ticket. Or we wait and after 36 hours of no updates we consider the issue abandoned.

CleaningmonkeyWhat I am after is a slightly technical person to act as a monkey followup / poo-flinging-cleaner that can call the clients and make sure everything that needed to get done got done. For example, if the ticket is closed 90% of the way, I need this person to call the client up, review the ticket, see if there was anything more we could have / should have done. Roll the output into either a bug or feature request or reopen the ticket with a more precise problem definition.

The key to this working is hiring a non-technical person. If I hire another engineer, they’ll try to help and then the feedback loop will break again. If I hire someone thats somewhat helpful they’ll still try to help – and we’ll rope them into doing “something”, I just know it.

So… is this just a general intelligent secretary? Service operations QA manager? Recommended salary? If you’ve got the advice post a comment or contact me privately, I need to catapult this role from my daily tasks ASAP.