The Business Case For ELearning [Electronic resources] نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

The Business Case For ELearning [Electronic resources] - نسخه متنی

Tom Kelly, Nader Nanjiani

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
لیست موضوعات
توضیحات
افزودن یادداشت جدید














Assess Build Versus Buy Options



It doesn't matter whether the Internet learning pilot is built or bought; it is a pilot, not a long-term investment. Identifying economies of scale across large numbers of users might favor a build decision; however, the upfront cash outlay, uncertainty of success, and low estimates of adoption could sway others to pursue a more prudent "buy" approach. Your parameters will determine the right choice for each organization.


A combination scenario might include pursuing a buy decision in the early phases with an eventual migration to a build strategy after the project has a critical mass of users. Engaging with customized solution providers might be a strategy to launch the project and work through the learning curve. A six-month analysis with potential savings and adoption rates backed with a cost analysis might be the first step.




Hindsight Is 20/20: Picking Your Vendor



Suppose that 40 Internet learning vendors are waiting for you to call them back. I personally know the sister of the founder of one of them and recommend his company. How will you select the best partners from your list?


You will select your partner carefully if you are as smart as we think you are. Following are three key steps for selecting your Internet learning partner:




1.



Establish and document business requirements for the projects, tools, and audiences. Do that with a cross-functional team representing IT, the audiences, and your project team.



2.



Write the system and tool specifications with IT, and ensure that they do not contain proprietary information or requirements. Then, obtain cross-functional agreement on those specifications.



3.



Put the specification requirements on a website where potential vendors, partners, and solicitors can access them, or in file, you can attach to an e-mail response to some vendor's inquiry.




If the vendor responds to your specifications in a way that indicates that their product matches your technical requirements, have someone check out its usability, performance, and alignment with your business and learning goals. Without the technical match first, you are both wasting your time. Don't forget to validate each vendor's financial viability.



/ 158