at the end, it has to work

i have not been around for a while. i’ve been busy trying to organise moving to London. it is easy, but it requires my head to be in the details.

i’ve been also working on some interesting projects. now i can say it, cause when i was given the briefs, they did not look so good. but perhaps it was me.

what i mean is that they looked like stupidly designed. and they were. not stupidly, may i be sincere, but not thought from the user’s point of view. and for me, that’s a big drawback (something you might agree with).

but perhaps it was me. i was focusing on one aspect of the whole product that did not work as it might, as it should. let’s cut the shoulds right now, and go back to the big picture, as it has worked for me, not even on purpose.

there are many aspects of a project that have to been take care of: interface design, system development, production, deployment, information management, business plan, and the likes. and in a small company, it comes down to few people managing most of them. so i was lucky enough to be involved in the production side as well.

that flawy interface design also came with some interesting production issues. the front-end designer wanted to give the client a catchy, engaging interface, and she did. the client approved, all in joy and excitement. then it came the time to make it work. oh boy.

but if it did not work, then things would (will) be in a very dodgy place. so it had to work. and then i realise it working is as important as it being designed well. because even ugly, badly designed, dodgy cars take people from point A to point B, and that makes them not good cars, but transport nonetheless.

so this website has to work, and the next, we’ll make it better, designed in a more precise way, worked out from the bottom up and beyond, much better. cause i’ll be in London, not working from 6000 Km away, but just there.

and they’ll work too.