The Meaning of U in 1010

When I give this talk to the codrschool interns, I titled it 'The Big U in Creating a Product.' Then, when I gave it again on Caresharing's Crazy Friday, I changed the title to 'The Meaning of U in 1010.' The 1010 refers to the binary code 1010, the language in which computer speaks, because I gave this talk to programmers.
So I think I will stick with that title.
I do not have a written version of my talk, so this is my attempt to put it on writing. I don't think I can write it from how I deliver it but I hope you can get the drift of the story I want to share.
This is a story of my short stint with Wakulu, an online coaching application.

My Different Roles
Except for the programmer role, I had to do the different roles when I was part of the Wakulu team.
Tester
'Design' Thinker
Technical and Content Writer
Community Relations Person
Sales
'Coach'
If you look at the different roles, can you point out the common factor among them?

The common factor is the U of 'The Meaning of U in 1010' -- which is the USERS. As a tester, design thinker, writer, marketer, sales person, you always have to do them from the end users' point of view. To be effective with the different roles, you need to have a detailed knowledge of your users. If you do not know well your users, how can you visualize your product from their point of view. Unless you are the user of your product. I believe one of the reason why we feel there is something not right with the workflow of Wakulu because although we have users, but they are not really the right users. This made me realized that when you develop a product for a certain group of users, as much as possible, you must have already a relationship with them long way before the product is created. You just do not go to them when you have the 'finished' product, and expect that they will have a use of it right away. Because, in the first place, they might really do not have a need of your product because their existing workflow works perfectly fine for them.

Why is it important to know your users?
1. It gives you edge - If you work on a start-up, you cannot just be the programmer. You also need to do the content writing, community relations, marketing, and other related stuff that must be done for your product. And, all these roles needs you to have a strong grasp of who the users are.
2. You need their attention, which can lead to trust, and then it's the only time that you can convince them to pay for your product . That's why it is important to have a relationship with the users even before you have the finished product because you cannot just knock on their door and sell them something. You would appear creepy. Even if your product is free, you are already lucky that they trust you with your email address.
3. Because they give meaning . More than the profit you will get, the real value of your product is how it changes the users live for the better. It is the 'thank you' of the users that really feeds your soul. It's the smiles of the users that keeps you going on working for the product. It's how your product change people's lives that makes it worth fighting for, not only by you but also your family.

So I guess a good criteria to consider before you create a product is to what answer you will give when your child or family asks you, 'Why do you need to leave us for work?' Because I am changing people's lives.

Thank you! @owrange http://owrange.com

The Meaning of U in 1010

by Rose Buenconsejo on Jun 08, 2010

Accessibility

Categories

Tags

Upload Details

Usage Rights

2 Embeds 8

Statistics

The Meaning of U in 1010 — Presentation Transcript

http://owrange.com	5
http://www.slideshare.net	3