banner



What Is A Mistake That You Have Learned From

  • 13 min read
  • Business organisation, Communication, Productivity, Teams

Quick summary ↬ We all make mistakes. Whether in our design and development work or only in life in general, we all exercise information technology. Thankfully, fifty-fifty the biggest mistakes carry valuable lessons.

As a dissimilarity to the many Web design articles that focus on successes and what we tin can larn from those triumphs, this article looks to the other end of the spectrum to explore what failures teach u.s..

Farther Reading on SmashingMag:

  • Critical Mistakes Freelancers Make
  • Marketing Rules And Principles For Freelancers
  • On Design Systems: Sell The Output, Not The Workflow
  • twenty Time-Saving Tips to Improve Designer'due south Workflow

Along the manner, I will share stories of some of the missteps I take made in the class of my career and the lessons I've learned in the process — beingness always mindful of composer John Powel's words:

"The only real error is the one from which we learn nothing."

More than after jump! Go along reading below ↓

Mistake #1: Putting Process Over Projects (And People)

Anyone who has been designing and developing websites for any amount of time has come with a process for working. Having a procedure is good, but be conscientious that it does not overshadow the project itself or the people involved.

I was reminded of this a few years ago in a project that was going badly. The simple reality was that I was not getting forth with the project managing director who was appointed by the client. Our personalities clashed near from the starting time, equally I found her feedback and requests to be misguided and her personality annoying. At the aforementioned time, I am sure she establish me unhelpful and combative because I was unwilling to honor all of her requests.

As frustration grew, I tried to fall back on our process as a way of adding construction to the relationship and trying to get it back on runway. If she made a request that took usa exterior of our normal procedure, I explained how we could non practice information technology without setting the project back in both time and budget. The worse the project got, the more I deferred to our process, until the client, exasperated to the limit, told me that I seemed to intendance more than nigh our procedure than the project.

My plan had backfired. I had tried to lean on our process in order to fix the problems, instead of having a difficult confrontation and dealing with the real issue — the fact that personality clashes were condign strained to the betoken that naught was being accomplished.

Somewhen, nosotros reset the project by calling for a coming together to clear the air and address the problems honestly so that we could move forward. While I continued every bit the project lead on our side, I brought in some other team member, someone who did not have a rocky history with the client's project manager, to handle the day-to-24-hour interval communications. Even though she acted equally little more than than an interpreter for me in many cases, the fresh voice and personality from our side did wonders for the relationship, and the project managing director responded to our new team member much better than she had to me.

Additionally, nosotros looked at the client's requests a fiddling more securely and, rather than dismissing them outright because they deviated from our normal process, tried to identify the reasoning behind each asking and so that we could honor them in the spirit in which they were fabricated (which we normally do anyway). Nosotros realized that those requests didn't actually bear on our normal process in a large way. Whatsoever deviation was modest, and the relationship and the project were much improve off with the flexibility in our process.

People > Project > Process
People are more important than the projection, which is more important than the process.

Of form, you need to strike a rest. A procedure exists for a reason, and if you carelessness it whenever anyone shows resistance, and so there is picayune point in having a procedure at all. That being said, any good process has some flexibility to accommodate the different needs of clients and projects.

Lesson learned: Followed blindly, no process volition save yous from having to deal with hard personalities or bumps in the road. A procedure is meant to help a projection forth, not to exist hidden backside when the going gets tough. For additional reading on client communications, see my previous articles, "Keys to Ameliorate Advice With Clients" and "How to Deliver Exceptional Client Service."

Mistake #2: Telling Instead Of Showing

I frequently speak with clients most their website needs. I listen to their concerns and the issues they're having with their current website, and I tell them how we can meet their needs. Annotation that I said I "tell" them how nosotros tin help, when I should usually be showing what nosotros tin can do for them.

This might not seem like a large difference, but it could mean the divergence betwixt winning a new projection or losing it to someone else — which is exactly what happened to me recently.

A few weeks ago, I was informed by a prospective client that they had decided to work with another provider. Whenever this happens, I am gracious and give thanks the customer for considering usa in the first place. I also ask them what the deciding cistron was. In this case, they loved our proposal and solutions, but another visitor had given a detailed demonstration of their preferred CMS and showed how they would utilise it to keep the website up to date. That company showed them instead of told them.

I'd be lying if I said I didn't kick myself upon hearing this feedback. I would take been happy to give this client a CMS demonstration, just they didn't ask, so I didn't offering. Instead, I answered their questions — all the while thinking I was giving them what they wanted.

Certain things are more effective when shown instead of told. Image credit: flickr
Certain things are more constructive when shown instead of told. (Image: Joe Penniston)

The other provider's CMS is not necessarily easier to use than the one I was offering, but I never even fabricated that instance considering I told the client how easy our solution was to employ, instead of showing them.

Lesson learned: Talk is cheap. Regardless of whether the customer specifically asks for a demonstration in your proposal, showing them goes a long way past bankroll up your words.

Mistake #3: Not Informing Clients Of Staffing Changes

Staffing changes are a reality in this manufacture. Squad members move onto other positions and opportunities, but business concern must go on. Projects demand to be finished, and websites and clients need to exist supported. As ane team member departs and another joins, you lot volition found a plan for existing projects and clients, assigning responsibilities and tasks as needed. Withal, even so solid and measured your plans may be, don't neglect to inform your clients of these staffing changes.

I learned this lesson when a longtime colleague recently left for another position. We had a program in place for the transition, a program that involved him working with the states part time to continue handling sure clients and services. The impact on our clients would be minimal, and I decided that we didn't demand to inform them of the changes because the services nosotros provided would not suffer and the change in our staff would likely get unfelt. I was wrong.

It didn't take long for one of our clients to reach out to my departing colleague. My colleague's work emails were now being forwarded to me, so I received the client's request. We made the changes requested, and when I emailed the client to notify them that the work was done, I also explained the alter in staffing to account for why the response was coming from me. As y'all can probably guess, they were surprised by this news, and what should have been a non-upshot suddenly became an issue, only because the customer hadn't learned of this sooner and was taken by surprise.

While some staffing changes are certainly not appropriate to discuss with clients, others really do bear upon clients in a pretty big manner. A person may be the customer of a visitor every bit a whole, but if their mean solar day-to-day interaction is with a particular squad member, so that team member "becomes" the visitor in their eyes. If that squad fellow member always decides to get out, the customer could experience every bit though they are switching providers, even though the company is nonetheless more or less the same.

So, exist proactive in informing clients of staffing changes. Past explaining your program for the transition of responsibilities with their account and reassuring them of your continued support of their company, yous testify them that, despite the change in staffing, you are nonetheless thinking about them and their needs.

Mistake #4: Focusing On Money At A Time Of Transition

Speaking of transitions, another reality in this industry is that clients sometimes decide to move onto another provider. When this happens, there is a period of transition abroad from your services, and you will probable demand to be involved in that transition. This tin be a strange and uncomfortable time, in part because you're concerned about coin.

Ongoing clients have an incentive to pay their invoices because they desire to proceed working with you lot. Clients who switch providers are worrying because of the possibility that they won't award any outstanding invoices — including time spent helping them transition away from your services.

This situation is delicate and needs to be handled example by case. Their reason for leaving, their overall payment history, how much they currently owe you (if anything), and how involved you will need to be during the transition are all factors that will make up one's mind how you handle the situation. The big lesson I take learned, yet, is that dwelling on exactly when y'all will become paid during this time of transition, which is often a time of uncertainty and fifty-fifty fright for the client, is rarely wise.

When I've focused on payment and gotten aggressive in making sure the client understands their financial obligation to u.s.a., those clients have really turned out to exist less likely to settle their accounts in skillful time than clients whom I approach more softly.

Providing outstanding service to a client during a fourth dimension of transition is the best way to terminate a human relationship. If the relationship ends on a positive note, then the client will be more than likely to pay what they owe and to say prissy things about your visitor, because the last impression y'all've left them with was helpful and positive.

Again, how yous handle such situations will vary. If the breakdown is messy, or you are owed a substantial amount of money or lawyers have to become involved, and then yous would handle that transition differently than if you had a good client who was leaving just because yous were no longer a good fit.

For more tips on treatment client payment bug, see "Dealing With Clients Who Reject to Pay."

Fault #5: Looking To The Past, Instead Of The Future

When we make decisions on a project, nosotros often look for relevant data to justify our decisions. Referring to website analytics and usage data can help us brand informed decisions, but call back that all of this data refers to the past, not the future.

The Spider web manufacture is constantly moving forward, and if we make our decisions based solely on data gleaned from past usage, then the solutions we develop volition be perfectly suited to those past situations, not necessarily future ones. This happened to me about a twelvemonth agone when nosotros were working with a client to come upward with a mobile strategy for their website. While we absolutely wanted to make the website responsive, the scope of the project and the budget but did non allow information technology. Plans were made and a budget allocated to redesign the website the following year, and a fully responsive blueprint would certainly be part of that project, but for at present, a split mobile-only website would be our short-term solution.

As with many mobile websites, our plan was to include but a small, targeted subset of the enormous content archive found on the current website. Looking back now, information technology was a mistake. Unfortunately, content parity wasn't an selection, and then to determine what content to include, nosotros looked to the analytics to see which pages mobile users were accessing. Part locations and directions, leadership team biographies, and contact details were the most popular pages being requested past mobile users, and so that was what nosotros included on the mobile website. There was, however, a problem with this logic of including but currently popular content on the mobile website: It did not account for hereafter needs.

As nosotros were working on the mobile website, the client began to focus on their blog. They formed a squad of authors among the subject affair experts in their organization and began publishing a lot of quality content — content that apace became popular with their audience. This new web log content was often promoted and shared via social media, and many visitors accessed those links via mobile devices.

You tin probably see where this is heading. Because we had no data to show that the web log would be popular on mobile devices, we left the weblog off of the mobile website. When the weblog picked upward steam and attracted interest from users on social networks and mobile devices, the website we had developed became a major problem. The experience would be as follows:

  1. A mobile user would see a comment well-nigh or link to an article in social media and, beingness curious well-nigh the article, click the link.
  2. The mobile device would navigate to the weblog commodity on the full website, only then quickly redirect to the mobile website'south abode folio.
  3. Considering the blog was not attainable from the mobile website'due south menu, the visitor had to tap the "View full website" link and, on their small phone, try to detect the blog on the total website. If that's not frustrating, what is?

Obviously, this feel was exceedingly poor, and very few visitors went through the entire process just to read the article. About just left when presented with the mobile habitation folio, instead of the article they were hoping to see. Even though we knew from the offset that this mobile-only website was temporary, had nosotros more than effectively planned ahead and non based our decisions solely on analytics from the past, we may have been able to avoid this problem and develop a better solution.

In this case, the answer was to kick off the responsive redesign project sooner and do abroad with this separate mobile-only website and its subset of content. The lesson nosotros learned is that we accept to look to both the past and the future when making decisions on a project.

Always make new mistakes
Making new mistakes helps you learn new lessons. (Image: Elyce Feliz)

This is why clients hire usa in the showtime place — not only for our execution, but for our expertise. This expertise includes knowing where the industry is headed, what principles have to become an integral part of the experience (content parity) and what new technologies or approaches we can bring to a website today to ensure that it works well tomorrow.

The Value Of Mistakes

All of the blunders covered in this commodity are ones I've made that either took a project off runway or strained a relationship or made a production far less successful than information technology could accept been. As soon equally I realized each fault, I wished I could jump back in time and have a practise-over.

Well, I've notwithstanding to notice that elusive time motorcar, but I do get do-overs of sorts. Every time I encounter a like situation, I am able to brand a better decision as a outcome of having learned the lesson from the previous mistake. That is my exercise-over, and that is the value of learning from one's mistakes.


We all make mistakes. (Image: opensource.com)

What about you?

What mistakes take you made, and what lessons have you learned from them? Not many folks like to talk about their mistakes, disappointments and things that just didn't piece of work out, only quite frequently they're just as useful as all those amazing success stories you can read nigh in hundreds of books and articles. What tools worked for y'all and which didn't, and why? Please share your stories and your thoughts with u.s. by using the hashtag #smworkflow!

Smashing Editorial (al)

Source: https://www.smashingmagazine.com/2013/07/mistakes-made-lessons-learned/

Posted by: robertsthenly.blogspot.com

0 Response to "What Is A Mistake That You Have Learned From"

Post a Comment

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel