User Interface Design and Engineering

Two great quotes that summarize my frustrations…

January 9th, 2009 by Russell Wilson

I have come across two quotes that help to summarize common frustrations I encounter in design and in working with teams of varied egos:

1) “The arrogance of hindsight”Joel Trammell, CEO of NetQoS

2) “Arrogance masquerading as humility”source unknown

In the first phrase, Joel was explaining how easy it is to criticize someone’s work after the fact, when more data is available and more is understood about the particular situation, domain, or context.

The second is a little more nebulous, but so perfect at capturing my frustration with people who push their own preferences or goals under the guise of duty or moral obligation.  One example is the person who argues for having meetings far too often, and with far too many people, because “it’s important to collaborate and get everyone’s opinion”, when in reality they simply enjoy “meetings” and can barely stand to sit in their office alone.

I find myself recalling these quotes often.

7 Responses to “ Two great quotes that summarize my frustrations… ”

  1. Interesting. I enjoyed Joel’s quote because I have caught myself in that same trap, and see it so often.

    For the person that argues for too many meetings, far too often, with too many people, I would recommend a book called “Death by Meeting”, and after absorbing the lessons, challenge the meeting participants for their effectiveness.

    Too many people sit in meetings offering no or minimal opinion or alternative thought. Those are the people who do not need to be there.

    Cheers

    JC

  2. I’d like to add that the example I gave is just an example; it was not the reason for this post. Some meetings are very important and often many people are required. But sometimes people can overdue it.

  3. What’s the phrase, too many colors turn to gray…or is it brown?…whatever;

    if you look at all the meetings we have, we can boil them down to two types…

    - decision making meetings
    - informational status or disseminate

    In a decision making meeting, especially in design, you need to have key stakeholders who will be impacted by the decision in that meeting to share ideas and actively discuss alternatives in a constructive manner. In the end, the choices/decisions have to be owned and defended by the group (thus the book suggestion), regardless of the individual preferences – make the decision and stick with it – no backstabbing – we made this decision. Having too many people in decision making meetings, the risk of dumbing down increases and honest exchange may be limited or clouded with too many suggestions by non-key stakeholders.

    Informational meetings (status and dissemination) need to be contexted as such. We’re giving out information here, not making decisions, your feedback can be submitted after the fact.

  4. Ha! A few years ago, I started asking for explanations when I “knew” that something was wrong or stupid about the situation. Then it turned out that I would have stuck my foot in my mouth had I come in with my arrogant assumptions.

    Slowly this behavior of feigning humility has turned into actual humility. Kind of a Pascal’s wager of “you might as well act humble because it costs little and can have huge negative consequences” turned into what he (and the Muslims & Jews) actually espouse: act in the proper way, and the belief will come.

    Alas, this isn’t a direct response to your quotes.

  5. [...] Adaptação livre do artigo da Dexo Design: “Dois grandes pensamentos que resumem minhas frustrações…” [...]

  6. ananddas says:

    Nice post, i mean it :Dhttp://tinyurl.com/9anvp6

    This comment was originally posted on Twitter

  7. Andy says:

    Agree 100%

Leave a Reply

Related Posts: