Ground Hog’s Day 2.0

The hallmark of a true professional is the ability to treat each person and situation with the same enthusiasm and interest as you did the very first time. This means that you will repeat yourself any number of times on the same or similar topics with the same or new clients. This is especially difficult for developers, who are trained to get to end point as efficiently as possible and, specifically, don’t repeat yourself (DRY principle).

I’ve recently put myself in someone else’s shoes – practicing patience and empathy. All I asked was that they do their job at the same quality level that I do my job. Is that too much to ask? It may in fact be too much to ask if the other person is put into an untenable situation, with no support from the company they represent. Imagine if you lacked the wherewithal to make a difference and had no control over your time or schedule and did not have the tools and resources to get things done. This person is responsible for delivery and installation of expensive equipment. However, the very company that stands to lose from a bad customer experience almost guarantees failure upon final delivery. Why so much emphasis on selling instead of delivery and service?

If you don’t support your team all the way to delivery of the end product you may in fact have a broken process. What kind of feedback loop do you have in place to find out what the customer experience is really like? I highly recommend that you follow your service or product to the end delivery point to see the results from your customers perspective. If you use 3rd-party sales, delivery or service reps then it is even more important to monitor final delivery results and follow up after the sale and delivery. A “Voice of the Customer” survey is not nearly enough to ensure customer satisfaction and good word-of-mouth referrals.

Repeating a broken process on a daily basis will not eventually fix the process.

“Success consists of going from failure to failure without loss of enthusiasm.”
~Sir Winston Churchill

Ask, Don’t Tell

Another interesting “active listening” technique that I’ve learned by observation is: reframing a statement as a question. in other words, Ask, Don’t Tell. For example: if you “ask” someone when something should be completed, instead of “telling” them when it’s due, you will get a much more thoughtful/active response. You also don’t take ownership away from the other person. (You do want them to take ownership and not come to you with every problem or question, right?) Continue reading

WAIT – Why am I Talking

I learned a new acronym last year that may help me become a better listener and better interviewer. WAIT means “Why am I Talking”. In other words, ask yourself if you should be listening instead of talking. It’s an important part of our jobs as web design, developers, and managers (or any job really) to deliver a solution that both meets the client’s needs and our own self-expectations. We can’t interpret our client’s needs if we don’t listen, repeat what we heard, and narrow the scope down to the essential parts crucial to success. Continue reading