« brewed awakening | Main | past scribbles »

insomnia

drinking coffee at 11pm on a monday night is a bad idea. even worse when it's followed by half a pack of cigarettes. it's almost 4am, and my brain is still refusing to shut down. i can almost literally hear the churning in my head. just too many things to think about at the same time. damn insomnia.

Posted by on January 13, 2004 03:52 AM |

Comments

Hate it when that happens. Hope it was only a one time occurance.

Posted by: Mona | January 13, 2004 10:21 PM

talk to me! chat with me! :D

Posted by: esge | January 13, 2004 11:47 PM

mona, it's actually not a one-time occurence, but more like a nightly thing, only some nights are worse/better than others... hehehe... i'm a doomed insomniac.

napa sat? kangen ya ceting ma gue? huehehehe... elo sih gak pernah nyalain msn. ym gue gak bisa nyala kalo di kantor soalnya.

Posted by: d | January 14, 2004 12:44 AM

MSN!!! gw nyalain deh! *bela2in!

Posted by: esge | January 15, 2004 09:29 PM

um... i forgot your MSN :D email doong..

Posted by: esge | January 15, 2004 09:31 PM

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear formation Assist in evaluating and improving CRM process and system ASSESSMENTS & ANALYSIS OF ISSUES AND CURRENT IMPROVEMENTS Web User Experience Issues: In terms of usability, design, and contents, MTG websites still had many areas that needed improvements. All the issues listed below could easily frustrate users and these negative web experiences would eventually bring negative impact to the brand image. Many of the websites were cluttered and confusing. It wasn’t very easy for users to navigate to find what they are looking for. Some functionalities on the websites were not working properly. Example: the “Search” function at marthatilaar.com often produced an error page instead of displaying the correct result. Only a few websites were regularly updated, while the rest had only very occasional updates. The websites were very slow to load and had a really slow response time, especially when accessed from outside of Indonesia. Solutions: Design clutter, confusing navigation and functionalities that didn’t work were the result of poor planning. The websites were developed without clearly defined objectives and a timeline. The solution to this issue is to develop a standard process in the project workflow. This would allow sufficient time to plan, develop and test the websites. Sample workflow and timeline can be viewed below: STANDARD WORKFLOW FOR WEBSITE CONSTRUCTION Task IDTask Name & DescriptionDuration (approx. in days)ResourcesPICPre-Production Phase1.Objectives defined:5Mktg Div.Web MgrTarget marketPurpose of websiteTone and look-and-feel2.Scope defined:10Web MgrFunctionalities specification (what user can do on the website)3Mktg Div, Web Mgr, CCContent acquisition3Mktg DivInformation architecture (how user navigate through contents, how flexible the design is to accommodate future growth/changes) including sitemap and wireframes.3Web MgrTimeline1Mktg Div, Web MgrDevelopment & Production Phase3.Design and layout:21Web MgrMock up navigation, homepage and initial sub-page design5Ciptamaya or Web DivDesign Edits (max. 3)7Mktg Div, Web Mgr, CCHTML templates creationDepend on scope, but max. 2 days for eachCiptamaya or Web DivTemplate Edits3Mktg Div, Web Mgr, CCSignoff final design and template1Mktg Div, Web MgrProduction:Depend on scopeWeb MgrDevelopment of functionalities and integration with database & C