Do we trust facebook as a shopping cart login?

In: Business

Posted by Geries Handal

13 Jan 2011

image

After reading the Oatmeal’s comic on How to make your shopping cart suck less, I wondered: should we trust Facebook as an alternative for creating an account in our online shop?

Short answer No.

That is too much data, given Facebook’s new policy to push you too share everything, I don’t want all my friends to know what I’m buying. In addition, they have a bad record with stuff like this (that being Facebook beacon)

Consumers don’t need new accounts, just for one purchase, so the best practice is to give them an alternative. Some alternatives could be custom express checkout (without login), Amazon Payments or Paypal. Even if it adds work and costs, customers will thank us, and happy customers are good business.

A “hunter shoots a bear” ad by Tipex (developed by Grouek ) shows how you can build viral branding campaigns on Youtube. The video takes interactivity to a new level by letting the viewer finish the ad. In addition they embrace the freedom of of the internet by dealing with humor with typos (with a nice 404 video) or if you decide to use the word “fuck”.

However the most interesting thing is the “white labeling” effect where the viewer always gets the feeling that is in Youtube. And guess what? This will not have been possible with other technology then flash. The use of CSS3 based animations might become more popular as the web changes, still it will take very long  time (maybe 5 years) for other technology to push the boundaries of the web as it was done in this campaign by Tipex.

Start but never finish

In: Web

Posted by Geries Handal

8 Nov 2010

Sometimes it happens that I’m aware of an idea or concept, but I never put much thought to it. Until suddenly it hits me is that I start to ponder on it. It happened to me while trying to draft a post and for some reason I remembered the following dialog from the movie “The Social Network”:

Eduardo Saverin: So when will it be finished?
Mark Zuckerberg: It won’t be finished. That’s the point. The way fashion’s never finished.
Eduardo Saverin: What?
Mark Zuckerberg: Fashion, fashion is never finished.
Eduardo Saverin: You’re talking about fashion? Really, you?
Mark Zuckerberg: I’m talking about the idea of it. And I’m saying that it’s never finished.
Eduardo Saverin: Okay. But they manage to make money selling pants.

What Mark is talking about is not something new, but for some reason I never gave it much thought until now. So, my (almost) epiphany: any web venture or project needs to start as soon as we can. In addition (and not less important) we never have to finish it. The moment it is done, then is dead.

Why?

Constant experimenting, leads to constant evolution of an idea,  which leads to constant change. For some reason people fear or resist to change, but love to see it in others. Evermore, are delighted when they see new things or experiment new things in our environments.

Remember when you had a new toy and then you found something new and forgot about it. The Internet is the same: is a collections of toys, which embrace our inner child, by providing us with a new one every 20 minutes.

Let embrace the inner child and run wild.

Thoughts on Design Thinking

In: Design

Posted by Geries Handal

7 Oct 2010

Before I start to speak my mind, on my experience with Design Thinking,  here is the definition from Tim Brown:

Design thinking is an approach that uses the designer’s sensibility and methods for problem solving to meet people’s needs in a technologically feasible and commercially viable way. In other words, design thinking is human-centered innovation. -Tim Brown

If that is not clear, here is a simplified explanation:

Design Thinking is a method to solve problems with focus on the people needs, not on what technology it uses. The easier you can build a prototype of the solution the better, because will not cost millions of dollars. You can read more about here (in IDEO’s website) and in this article from the fast company.

Recently, I spent a weekend in a workshop at SSES, on Design Thinking and Experience Prototyping. Like most hyped methodologies, theories or frameworks, design thinking is not a “miracle anybody can use it” tool, it needs time for the people involved to understand how to use it effectively. Like every other tool out there, it has a learning curve.

Think of it as learning how to dance salsa. Sure, at first glance  it may look fun or might look really sexy and cool. However it is hard to get to the level when you dance, it looks sexy and cool, to other people. You need to know the moves, follow the rhythm and tempo. Salsa is a duo team dance, where they have to focus on the the couple as a whole, not in the individual needs, because it will never work. Finally and most important, salsa needs practice, practice and more practice.

image

[Cool salsa stuff, which needs experience to get to that level. Image source]

Same happens in design thinking, you need to know about the process, can’t make cool and fun sequences without knowing the moves. Can’t come up with great solutions, without knowing the methodology. Can’t make sense of all without seeing the results, failing, trying again and continue to fail and learn.

It takes time for people to understand what how to build in each others ideas. We [humans] are selfish beings, which leads us to be more concerned on making our voice heard. We need a balance of noise and signal, it can’t be like twitter where everybody is just screaming or re-screaming what others say.

People sometimes don’t realize why (in Design Thinking) we need to create as much ideas as possible, even if they are nonsense. Ideas is the fuel of Design Thinking, without them the tool will no operate. And the more variety there is, the more powerful “the fuel” becomes.

It may be argued that a bunch of ideas may create just noise, or the more ideas we have the less quality we will have. It doesn’t matter if they are good or bad, they will be consume by the process, which will lead to find the better ones in the pile of noise. Think of it as finding a radio signal, to get to the signal we want, first we have to go through the noise.

One of the key elements in design thinking is to learn from failures. What better way to learn from out failures than doing things and gaining experience. or prototyping. Prototyping helps us achieve two goals:

  • Try, fail and learn
  • Communicate ideas better, because instead of telling or describing a idea we show it, even if its a made of foam or drawn.

We can take the mantra, of learning from our failures further. We can view at every idea that we have as failure. Only a couple will end up being developed and prototyped, the others are dropped. Then why not learn from our ideas that were dropped.

Finally, this is a “team sport”, is not about the superstar or individual. Everybody is good at one thing and bad at another. By working together and complementing each other, the whole group becomes bigger than the addition of individual talents. Which enables the team to deal with bigger problems, that any individual will not be able to tackle by herself.

Had a jQuery ajax call that work great in all browsers but stp working in Internet Explorer after the first time I executed the call. After googling , I found out that that IE (especially IE8) caches aggressively ajax calls. My jQuery code look something like the following:

$.ajax({
   type: "POST",
   url: "/process.jsp",
   data: "data",
   success: function(msg){
     //some function
   }
 });

To tell IE not to cache the call, is by adding the option cache false, as shown bellow:


$.ajax({
   type: "POST",
   url: "/process.jsp",
   data: "data",
   cache: "false",
   success: function(msg){
      //some function
   }
});

If it still doesn’t work after you put the cache false, then use the $.ajaxSetup to setup the default for the ajax calls.

$.ajaxSetup({
  cache: "false"
   });
$.ajax({
   type: "POST",
   url: "/process.jsp",
   data: "data",
   success: function(msg){
     //some function
    }
 });

We forget to recognize the other customer is you

In: Customer Service

Posted by Geries Handal

22 Sep 2010

Kodak introduced the a single-use camera called the Weekender. Customers have called the support line to ask if it’s okay to use it during the week.

The above case is one of those happenings that confirms that we are irrational beings. I found it the book The Dilbert Principle, by cartoonist Scott Adams. The reason he tells that story is to back up his hypothesis, that everybody is an idiot, at least in one topic /field or another. If you think it sounds harsh, remove the noise that comes with the word and you will realize that there is some truth to it. Let me explain why.

Each of us is good at something and bad at another (Adams mentions this in the book). As we progress through our lives, we learn new traits. Sometimes these new skills come in form of using a new tool or service just experience with the world around us, but still we are “idiots” at something else.

Lets say there is a company called WEE tech and they just announced a new product the in a big conference. Since, the weeetator is a new product, only the people at WEE tech can use it. Why? Because they came with the idea, design it, build it, test it, fixed bugs and tested more. In other words they been working on it for the last year, as a result being experts on using it. Everybody else is an “idiot” in using the weeetator, because nobody outside WEE tech has tried to used it and gone through the learning curve.

Sometimes when receiving customer calls or dealing with customers issues, we think that they are not very smart, since they don’t understand how things work. However, we forget that we don’t know how other stuff work, we become very critical about the intellect of our customers, when we do the same thing with other products.

There are people out there that don’t know how to use a iPhone, but hell know how to run a business. Others can disarm and put back together a motor of a car, but don’t know about the Internet of Things.

At the end everybody is a customer, so treat your customers as you want yourself to be treated the next time you have a problem with your phone.

So, now is about the App Stores

In: Business

Posted by Geries Handal

26 Aug 2010

Recently. I saw an article in Read Write Web, were they talked about the upcoming app store for Evernote, called Evernote Trunk. This got me thinking that in the past months, I’ve seen some companies launching app stores. For example, Foursquare has one, Samsung did it for it smart phones, even uTorrent the bitTorrent program has one. You may think this just a buzz word and people are just ridding it, however there is more than just following the success of Apple and facebook (which was the first to have the concept of third party apps, even before Apple.)

Pondering about this topic, I remembered a kind of lecture/conversation, I had not so long ago with an experienced entrepreneur. He told me that having a service is good for starts, but were you want to end up is having a platform, because it gives you a better chance to grow. Facebook is social platform that connects with Internet, Foursquare is a platform for connecting your Web life with the “Real” life and Evernote it becomes a extension of your memory.

Doesn’t matter if they call them plug-ins, widgets, extensions or apps, as we can see with companies like Apple, facebook and others: once you become the base of the pyramid and others depend on you for their business, “you struck gold”.

Debugging by comments

In: Software Development

Posted by Geries Handal

15 Jul 2010

You have written your code, ran it and looks ready to be committed. Once is committed it can be tested by another member of a the team. However,why no write some comments for your code before committing it, which will help you find some bugs.  By writing comments, you will have to dissect your code piece by piece, which will lead you to find common errors and makes your code understandable for other (and your future you).

Is not just about just writing one liners, write them with the following set of mind: it will be read by somebody that knows nothing about the applications or program, imagining the target reader is a new member of your team. This will help you see your code from a different perspective and go into details. By submerging in to details, you will  find bugs in your code before going into the testing stage.

There are two advantages of this method: First your code is readable and readable code is better code. Second, you save resources by saving a bug report. Testers will not test code, find bugs and return it to you. You will NOT stop your current task and go back to fix a careless bug and resubmit it for testing. Instead you will spend your time producing new code.

Let’s start with “Why”

In: Business

Posted by Geries Handal

5 Jul 2010

On the weekend, I went shopping for a pair of sneakers. I needed something comfortable for my summer travels, which provided a much needed arc support. This is due to being flat footed and been giving me problems when walking a lot. In addition, they should later be wearable to work and everyday commuting. My decision: the Nike Air Max Classic BW.

I got to the store and when I saw the high price, plus all the colors and similar models, I stalled and wasn’t totally convinced. Still after some browsing and a coffee, I decided to ask for two pairs to try them all. I was disappointed because they didn’t provide the support I was looking for, although they looked cooled than I thought.

Things changed when the salesman got some insoles with arc support, the sneakers felt  much, much better. When he asked me “what do you think”, I gave him the thumbs up. Then asked if the insoles were included, and he said I had to pay extra for them. At this point, I got turned off.

Note: Looking at this from a third view, when you have a price sensitive customer and then you make him pay more for what he/she has already committed too (in this case more than 10%), then the deal breaks up and there will be no sale.

At that point, I said I wasn’t going to buy them because, it was already an expensive product and I had to add more to actually serve its purpose. While he was trying to convince he can’t give it to me for free and they are good insoles and that they have a warranty and “bla bla bla”, I realized something: what I really need was the insoles with arc support, not a new pair of sneakers.

I bought the insoles and left the store with them in my old sneakers. After three days, I assure you: that was the best possible decision I could have made. It will have been a waste of money, to buy new sneakers when most of the non running shoes come with neutral arc support.

Most of the time, customers want to solve a problem and they think that the product/service you offer is the solution. And most of the time we are wrong, that is why is important to find out: WHY they think that is the best solution.

In that process of finding out WHY, you might not sell them anything and the customers just needs to tweak something in their current solution (that being sneakers, network, website, etc). However, a happy customers has a bigger possibility of returning and even better bring it’s friends. But, if he/she is not satisfied with the overall experience, forget about it. you lost them, because is about building relationships and thinking long term, not just selling.

The Fukunaga approach to UX Design

In: Software Development

Posted by Geries Handal

17 Jun 2010

Sin Nombre” is the title of the independent movie, written and directed to Cary Fukunaga. His approach to writing and directing was that caught my attention some months ago and thought it will be usefull to apply in  User eXperience (UX) design. First lets see what the movie is about, here is the synopsis:

After murdering his gang’s leader, a teenager joins a family of Honduran immigrants making the dangerous journey across Mexico to the United States, avoiding a fellow gang member who has been sent to kill him along the way. [Source Yahoo Movies]

Fukunaga’s approach was to do research before starting to film anything. He travel with illegal immigrants in trains, talked to gang members or “mareros” (the local term for this type of gangs) and even had two ex-mareros help him with the slang and way of expressing.

The movie has been acclaimed internationally and is very well done. One of the strongest attributes is attention to detail (which leads to some strong scenes), high pace and scenery. Things Fukunaga couldn’t have figured out without the research.

In the case of software, research is needed if we want to provide a pleasant UX experience to our customers.

Most of the time we create software to solve a problem. If we follow Fukunaga as example, we should not just interview the people the suffer the problem, but “ride the train” with them. In other words, let them take you through that moment in life where they suffer the problem. If we continue with the movie theme then we can conclude that:

story boards are to sketches as filming is to programming.

UX design is about continuous improvement.

We have done the research, now we need to determine if our conclusions are correct. So, we need make a rough sketch of the software and show it around the future customers or users. Then after some feedback, lets redraw the sketches with more detail. We continue doing so, until we have something that we can take to the next level.

The next level is to build the core of the software. This means that we only include those features and functionality that is the least needed to solve the problem. Once we have a good core, then the rest of the features will be easier to add. In addition it will keep things simple, which will save some resources. But more important it will give you a application that some of your customers can try and give you feedback on.

It is always about continuous improvement through research and attention to details, unlike movies there is no final version.

About this blog

A personal blog where I write about my current projects, work and interests. The posts are a reflection on my current self, varying over time, since change is the only constant.

Welcome to G To The Square, my thoughts on ICT, Business and Life... in a Square.