Showing posts with label interpersonal. Show all posts
Showing posts with label interpersonal. Show all posts

Friday, October 29, 2010

How to avoid Information Overload

In the daily course of our works, we come across numerous emails from colleagues and clients as well as countless other unsavory emails uncaught by the junk filters. For the most part, it’s quick and easy to spot those unsavory emails and press the DEL key.

We all know the popular sayings of “Knowledge = Power” and what is knowledge if not information? It implies, then, that having too much knowledge is a bad thing. The real problem is that we often get copied on messages that our friends and colleagues think would help us in our daily duties when in reality they hinder us from completing our tasks effectively and timely. Then there’s the problem of people conversing using emails instead of using the more immediate communication tools such as instant messenger, phone or even simply walking-by for a chat(when it seems a walk-by-and-chat is appropriate).

So when we do get in the crossfire of people’s conversation emails—even when we are in the same project team, conversation circle, etc.—it pays to first know at the beginning whether we really want or even needed to participate in the essence of the conversation. Generally speaking, unless specifically addressed and called to answer a specific question, the simplest thing to do is to decide not to read it and any of the subsequent correspondence within the same thread. And thread is the keyword here.

Most modern email clients feature the ability to organize emails so they look like forum message threads. That’s the first and foremost what I personally do. Keeps things easy to quickly eyeball.

Second, we can (single-click) tag or flag emails that at quick glances seem important to revisit later. Forget about creating folders to categorize those emails. It takes more time than we think we have and won’t necessarily work as emails come faster than our ability to move them to the appropriate folder, especially not when today’s email clients have improved search function that can automatically create smart folders to contain the results of our searches. If anything, we’d be better off ignoring emails whose subjects are too generic to be useful as they indicate no forethought about the email itself. If one sender can’t take one minute to write a proper subject line, why must N recipients spend even one minute trying to decide whether it is worth spending more time to read and understand. It simply would be a disservice (not to mention costly in real terms) to our boss and other colleagues who are expecting us to perform our duties timely and productively unhindered by fly-by emails.

Third, also we can a mental note who among our colleagues are frequent offenders so that when email messages come from them, we can make an educated guess the likely importance of those messages and act accordingly.

Lastly, don’t return the favor, i.e., if we don’t like being blindly copied on messages that we think are not important to us then when we do get involved in an email conversation, remove all other recipients names except for the one with whom we are having it. I am a proponent of respecting everyone’s time and summarizing the conclusion of the conversation in a single email and creating a single attachment for the conversation, if we want to inform the team such conversation had taken place only for a matter of historical curiosity.

More often than not, we’ll be appreciated for not being party to exacerbating the condition of everyone else’s information overload. And most importantly, by going through the aforementioned steps regularly and consistently, we build for ourselves a habit to reduce our own being overwhelmed by things we’re unable to decide their importance.

Monday, October 04, 2010

Simple Creative-Interactive Development Approach

Preproduction:

· Brainstorm quick engagement rules.
· Gather and generate content.
· Construct the site map.
· Develop and approve and interface.
· Determine technical needs.

Production:

· Develop and refine content.
· Establish development, staging, and hosting resources.
· Get graphics production underway.
· Produce server-side support.
· Produce interactive materials.

Publication:

· Test cross-platform and cross-browser compatibility.
· Functional code review.
· Feature review.
· Coding style code review.
· Content (copy & graphics) review.
· Sign-off and deploy.

Post-Publication:

· Schedule maintenance periods.
· Schedule updates and fixes.
· Add content regularly.
· Promote site to targeted audience.
· Discuss expansion and re-design.

Organize and interview feedback and focus groups:

· Internal employees to provide management and organization needs.
· Public audience to provide likes, dislikes, and wish list.

Reuse:

· Create inventory of all existing content (brochures, graphics, interactive media, etc.).

Scheduling:

· Adherence to development schedule is a must; only one exception is allowed: unforeseen technical difficulties.

Project management:

· Although many stakeholders, there should only be single-point of authority in order to have:

  1. a final-say decision-maker; or,
  2. a tie-breaker in a round-table project discussion group.

Saturday, September 06, 2008

Confidence == Self.Comfort in {Knowns, Unknowns}

Confidence != Perfection;

Confidence != Arrogance.Hide(Inferiority);

What do we do when a user asks for a facility for a matter of convenience and where the cost of providing such convenience far outweighs the value of the time saved from the convenience?

There's a dictum that states: "Customer is King." If we want to be responsible subjects to our king, it is our duties to say to the King: "Your Majesty, if you wear this 'clothes' you will be naked; is that what you really want?" and instead of: "Yes Your Majesty, we will use the finest invisible silk thread to match the invisible royal garb you ordered."

Friday, April 11, 2008

Joy is...

A smile in spite of what's around.

You know... these days I sensed a lot of unhappiness around me—not from me, mind you—around me. So I took a few minutes out of my day and scoured the Internet to see if I could find some quick, inspirational statements people say about how we can reach happiness since I don't seem to be doing well in inspiring happiness for others.

Here's what I found:

From Dennis Wholey:
Quote #1: Happy people plan actions, they don't plan results.
Quote #2: Expecting the world to treat you fairly because you are a good person is a little like expecting a bull not to attack you because you are a vegetarian.

Here's another from our favorite genius, Albert Einstein:
Quote #3: If you want to live a happy life, tie it to a goal, not to people or things.

From an unknown smartie:
Quote #4: Happiness is not the absence of problems but the ability to deal with them.
Quote #5: Some pursue happiness; others create it.

How are these useful for me? Eeh, they aren't new to me, really; they're what I already naturally use for me. And I'm happy in a happy-go-lucky-sort-of-way-kind-of-guy; see if these could be as useful for you as they have been for me.

Thursday, March 27, 2008

To be gainfully employed is...

A rather challenging act to perform.

It's not just about having a job nor about the money that the job brings.

It is a constant juggle to balance our personal and professional lives.

I've shared with many people I encounter in my careers a personal attitude that may help reduce one's own stress in a work setting and be able to feel secure on and of our own: that work is just a vehicle for us to meet new friends and earn income to support our family.

Professionally, the level of quality of my output and my team's output is much less driven by our individual talents, but more about the principles we go by and use in our teamwork:

  • Kanban: Just-in time (classic production understanding in manufacturing industry of what's now called Agile in the software industry).
  • Kaizen: Continuous improvement; our work is never done, even when the output has shipped. This translates personally to set a goal where we can pace ourselves according to our health and ability and professionally to always understand that the best we deliver today should hopefully be better tomorrow.
  • Gandhi engineering: A combination of irreverence toward established way with a scarcity mentality that spurns superfluities while at the same time maintaining consistency of applying the principles in play.
  • Einstein tolerance: That can't be paraphrased, but simply understood in what Albert Einstein himself said: "Great spirits have always found violent opposition from mediocre minds. The latter cannot understand it when a man does not thoughtlessly submit to hereditary prejudices but honestly and courageously uses his intelligence and fulfills the duty to express the results of his thoughts in clear form", to help us maintain composure in an adversarial environment. This also relates to what I wrote earlier in my post: The 道 of Writing, the sublime of Work Ethics...

Thursday, March 20, 2008

A customer is NOT always right

1. If he is belligerent and makes my team and employees unhappy.

2. If a customer makes me choose between unreasonably serving his business or my relationship with good colleagues and employees. My employees come first. (This is along the line of: "If an employer makes me choose between unreasonably serving his business or my devotion to my family. My family comes first.)

3. If his business is bad for my business: we all have a finite amount of resources serving a customer that does not further our own goal. For example, serving a bad customer who takes so much more time and efforts where consequently we are unable to provide an equal or better time and service for a good customer, we'll have to say goodbye to the bad customer.

4. If he is unreasonable despite our best effort to serve him/his company with a good service, and that they have been receiving good attention and services.

5. If we happen to get a glimpse, somehow, that he doesn't treat {another person | his own employees | general public} fairly and with dignity as it is a telltale of what is to come for us as an outside vendor.

Thursday, January 17, 2008

What a great {insert a nerdy title here} feels:

  • I don't need to prove I'm 1337 to know I am one.
  • I don't understand the end-user, but I'll always try to.
  • My end-user is the reason I have a job.
  • Patience really is a virtue.
  • Nobody likes complicated stuff.
  • It's better to be perceived as inexperienced but a quick study, than experienced but a slow poke.
  • Knowing the subject well is better than knowing how to code well.
  • If I don't know how to code it well, give it to someone who does, then learn from it.
  • $1/day for 365 days is better than $10 for only 30 days. Long term builds trust, character and wealth; short one brings false sense of confidence.
  • Each new job feels like my first job; done with great excitement, else it could be my last one.
  • Get completely in or get out, capiche?

Thursday, September 20, 2007

The 道 of Writing, the sublime of Work Ethics...

Be it software, technical documents or emails.

If any man wish to write in clear style, let him be first clear in his thoughts; and if any would write in a noble style, let him first possess a noble soul.
~ Johann Wolfgang von Goethe

Learn as much by writing as by reading.
~ Lord Acton

I too am an apprentice, always—learning as much by failing as by succeeding, as much by following as by leading.
~ antonius

So don't despair that no one agrees with you and point your mistakes, for "... when you're screwing up and nobody's saying anything to you anymore, that means they've given up on you."
~ Randy Pausch

Wednesday, March 14, 2007

Doing the right thing to do

It's easy to say; it's hard to understand.

The right thing for a relativist unreliably varies from context to context.
For an absolutist with an extremist mentality, the right thing may turn out to be just the opposite.

It's complex, yet so simple.
For when one's inhibition is gone;
when one's civility is in ruin;
when one's regards for morality, law and politics vanished; and,
when one's regards of relationships discharged,
the right thing will still be there down in the heart of heart.

It is the faintest voice that keeps one awake at night when the world is deep in its slumber.
It is the voice of conscience in one's subconscience.

That is the right thing.

Wednesday, November 22, 2006

State of the consulting industry

Jane Doe and Richard Roe are a couple of consultants discussing and sharing their experiences in the consulting business from their viewpoint.

Jane: "Consulting is not at all what I thought it would be when I started in the field eight years ago."

Richard: "What and how do you think it would be?"

Jane: "My vision was that we would be called in as helpful experts, work with business stakeholders to help them overcome their business problems or get the business to the next level. We would be trusted to analyze every bit of details about their business, uncover the problems and provide recommendations to resolve the problems."

Richard (laughed): "If only it were that easy. I had one like that once, but just once long ago."

"We have to realize that clients call us in for a lot of different reasons only some of which they fully disclose. There were often internal power struggles we may not be aware of. There are also clients who may have heard how wonderful the solutions we had for a different company, and they wanted us to come up with the same solution for them while disregarding the potential adverse effects a similar type of solution may be for their business."

Jane: "So why do consultants have such bad reputations? Many consultants seem to continue to have uphill battles with their clients, where it should have been collaborative. Ideally, we would have the client's good faith trust. After all, we are here to help them succeed in their business and objectives."

Richard: "I think it's because we do the job we think we were hired to do, and maybe that isn't what the client wanted, yet the client may not or does not, for whatever reasons, share in-full their complete objectives in hiring us as their consultants. Even when we find clients who do want us to succeed in helping them, but if no one else in their organizations really cares then we'll find they won't work with us. Sometimes they feel threatened and actually work against us."

Jane said, "Sure, but are we ever the cause of the problem?"

Richard: "Sure."

"It's all simply because consultants are usually seen as outsiders. And the fact as business cost factor, we are pricier than employees—never mind that we are also often better, specialized helps."

"Moreover, we do make mistakes just like anyone else. Unfortunately, once we make mistakes, no matter how trivial it may be, the odds are stacked against us much heavier than even when there had been no mistake. It takes an astronomic remedial effort and outstanding result just to get back to the original standing we had to begin with the client."