Yes, I did go to Copenhagen and I did presence many of the lectures at Reboot10 in a conscious state. I found pictures to prove it and I'm glad (since I know I was spotted sleeping during one of the lectures, and the photo will be blogged soon). This photo here, will serve me to prove I was awake in most of them :D
Monday, 30 June 2008
Thursday, 22 May 2008
Cholo, una definicion en poema
Cholo soy
¡y no me compadezcas!
que esas son monedas que no valen nada
y que dan los blancos como quien diera plata.
Nosotros los cholos, no pedimos nada
pues faltando todo, todo nos alcanza.
Déjame en la puna, vivir a mis anchas
trepar por los cerros, detrás de mis cabras
arando la tierra, tejiendo unos ponchos
pastando mis llamas;
y echar a los vientos, la voz de mi quena.
Dices que soy triste, que quieres que haga
no dicen ustedes que el cholo sin alma
y que es como piedra, sin voz sin palabra
y llora por dentro, sin mostrar las lágrimas.
Acaso no fueron los blancos, venidos de España
que nos dieron muerte por oro y por plata
¿no hubo un tal Pizarro, que mato a Atahualpa
tras muchas promesas bonitas y falsas?
¿Entonces, que quieres, que quieres que haga?
que me ponga alegre como día de fiesta,
mientras mis hermanos doblan las espaldas,
por cuatro centavos que el patrón les paga.
¿Quieres que me ría?
mientras mis hermanos son bestias de carga
llevando riquezas que otros se guardan
¿Quieres que la risa me ensanche la cara?
mientras mis hermanos viven en las montañas,
como topos escarba y escarba,
mientras se enriquecen los que no trabajan.
¿quieres que me alegre?
mientras mis hermanas van a casas de ricos
los mismo que esclavas
cholo soy ¡y no me compadezcas!
Déjame en la puna, vivir a mis anchas
trepar por los cerros, detrás de mis cabras
arando la tierra, tejiendo unos ponchos
pastando mis llamas;
y echar a los vientos, la voz de mi quena.
Déjame tranquilo, que aquí la montaña
me ofrece sus piedras, acaso mas blandas
que esas condolencias que tu me regalas
Cholo soy ¡y no me compadezcas!
Friday, 25 April 2008
Micro-Interactions and Fuzzy Agencies
This is an interesting speech at Interaction '08 with examples about moving brands beyond typical marketing campaigns into a "micro-interaction" model; and about a company model in which the distinct positions blur into each other to reveal the real potential in that overlap of functions.
Friday, 18 April 2008
Some escencial things new companies that come from old failures should mind
The post was about Maverick: The Success Behind the World’s Most Unusual Workplace,
Treat employees like adults:
Surprisingly, someone has to write about it! so that some individuals with management-delusional* behaviors realize the rest are adult people too, not children.We simply do not believe our employees have an interest in coming in late, leaving early, and doing as little as possible for as much money as their union can wheedle out of us. After all, these are the same people that raise children, join the PTA, elect mayors, governors, senators, and presidents. They are adults. At Semco, we treat them like adults. We trust them. We don’t make our employees ask permission to go to the bathroom, nor have security guards search them as they leave for the day. We get out of their way and let them do their jobs.
* In Ecuador we used to call these people "the clowns who perceive themselves as the owners of the circus"
Looking for the similarities rather than the differences on the description of my job title
Here are some of the descriptions I found:
The Experience Architect is that person relentlessly focused on creating remarkable individual experiences. This person facilitates positive encounters with your organization through products, services, digital interactions, spaces, or events. Whether an architect or a sushi chef, the Experience Architect maps out how to turn something ordinary into something distinctive—even delightful—every chance they get.
Later, more clarification:
1. Interaction Designers are User Experience Architects. They are the primary role responsible for writing scenarios.
2. Business Analyst is also responsible for writing scenarios but less from a perspective of design and more from a perspective of goal writing (where the scenarios come from) and ensuring the scenarios meet the goals of the customer. It's entirely possible for a Business Analyst to not write a single word within a scenario but they should know it well.
3. Business Analysts are the knowledge people. They understand the priorities, the functionality, the domain and provide a bridge between the user experience and technical design.
4. Business Analysts are the primary role to write functional requirements. They could write them side by side with a solution architect or with strong collaboration but they are ultimatly responsible for functional requirements.
5. For domain modeling. I imagine a BA and SA sitting side by side building it together. Both should understand the technique.
(little note: still, me, as an experience architect play all these rolls, we just charge differently per the knowledge of each role)
... tired of researching, I'll conclude this post later