<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>The Metaverse Journal - Latest Comments in Forrester to business: ignore virtual worlds at your peril</title><link>http://themetaversejournal.disqus.com/</link><description>Australia's premiere virtual worlds news service</description><atom:link href="https://themetaversejournal.disqus.com/forrester_to_business_ignore_virtual_worlds_at_your_peril/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 14 Jan 2008 05:33:37 -0000</lastBuildDate><item><title>Re: Forrester to business: ignore virtual worlds at your peril</title><link>http://www.metaversejournal.com/2008/01/12/forrester-to-business-ignore-virtual-worlds-at-your-peril/#comment-1330498</link><description>&lt;p&gt;It sounds a little bit like that Simpson's episode where the 'motivational speaker' tells everyone in Springfield to act like Bart.  Businesses have to have a reason - beyond it being cool and trendy - to be in virtual worlds.  And there needs to be a ongoing plan, not just for the short term but for the medium and longer terms.  If you're in virtual worlds for brand promotion how are you going to draw people to your build 6-12 months after it's opened.  Is it important to have a regular stream of traffic day-in day-out? Or will bursts of popularity suffice?  Have you budgeted for all that? If you're doing meetings in world do you really need to spend $50k or can you get away with a smaller or existing feature?  Same with training in world.  Do you need to drop a few $10ks on a facility you use once per year and is left empty the rest of the time?   There are lots of reasons to use virtual worlds in your business.  Finding the right reason for you - even if that is not now - is far more important than having the most spectacular virtual head-office.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">skribe Forti</dc:creator><pubDate>Mon, 14 Jan 2008 05:33:37 -0000</pubDate></item></channel></rss>