Archive

Posts Tagged ‘Wiki’

Go daddy تخسر أكثر من ٣٧ ألف نطاق بسبب قرار خاطئ


قو دادي Go Daddy تعتبر من أكبر شركات تسجيل أسماء النطاقات وإستضافة مواقع الإنترنت على مستوى العالم. قامت مؤخرا بإعلان دعمها لقانون Stop Online Piracy Act ‪(‬SOPA‪)‬ الذي يهدف إلى إيقاف القرصنة في الانترنت.
لكن هذا الدعم واجه ردة فعل مضاده قويه من قبل المستخدمين وكبرى مواقع الإنترنت.. حيث أنه يسمح للشركات الداعمة لهذا القانون من القدره على رفع قضايا على الأفراد والمواقع إذا ما تم نشر مواد مقرصنة وقد تتمكن هذه الشركات من إيقاف مواقع كاملة، ولهذا تم رفض هذا القانون من كبرى شركات الانترنت مثل قوقل وموزيلا والفيس بوك وموسوعة الويكيبيديا. (عالم التقنية)
وكمحاولة لتدارك الموقف .. قامت قو دادي بسحب دعمها لهذا القانون.. وتم إعلان ذلك رسميا.. ولم تكتفي بذلك بل قامت بالرد على مئات المعارضين في تويتر. (صوره أدناه) 

لكن ولسوء الحظ لم يتقبل الكثير كل ماحدث، فقامت كبرى مواقع الإنترنت مثل ويكيبيديا بنقل مواقعها الى شركات إستضافة أخرى. وهذه الخطوه لاقت إستحسان الكثير بدليل زيادة عدد متابعين مؤسس موقع ويكيبيديا على تويتر بواقع ٤ الالاف متابع. (الصوره أدناه)


ووفقا لتقرير صدر اليوم.. خسرت قو دادي وخلال يومين فقط حوالي ٣٧ ألف نطاق (١٥ الف نطاق خلال يوم الخميس الماضي واكثر من ٢١ الف خلال يوم الجمعه) حيث تم تحويل جميع هذه النطاقات الى شركات إستضافه
أخرى منافسه.. مما يعني أن الخساره هنا مضاعفه. (المصدر)


تمثل هذه الخساره مثال أخر على قوة صوت المستخدمين.. فبفضل الشبكات الإجتماعية أصبح إيصال صوت المستخدم العادي أقصر وأكثر فاعلية .. واذا تظافرت الأصوات والحملات فبالتأكيد قوتها وأثاراها أبلغ.

وأيضا تعتبر هذه الخساره بمثابة الدرس لجميع الشركات التجاريه والخدمية.. فكفة المستخدم في ميزان القوى لم تعد كما كانت في السابق.. هي أقوى الأن بكثير.. لذلك لابد من الإهتمام بردة فعل المستخدمين والعملاء لتفادي مالايحمد عقباه.

Enterprise’s Wiki Strategy: Choose The Right Software

Last week I posted Blogging Strategy, and this week I will talk about enterprise’s wiki strategy. A wiki is a web page(s) and content can be collectively created, structured, viewed, and/or edited, by users with corresponding permissions, removing the distinction between author and reader. Wiki originally is a shortened from the Hawaiian word for quickly (wikiwiki). Perhaps the most recognizable wiki is Wikipedia, the public online encyclopedia that anyone can edit.

Wikis are being implemented in businesses to address concerns with knowledge management/collaboration practices However, with nearly 200 different wiki software packages available, there are many variations in the available offerings in the market.  Very sophisticated software is not necessarily the right software solution for your company. Very often, companies buy software because they were impressed with the features and functions they saw at the demo without realizing that it might be too sophisticated for their users. Thus the challenge is choosing the right tool for enterprise’s use. Here some most important features to look for when choosing a wiki platform:

Fit enterprise’s needs:

Are wiki software able to achieve the maximum benefit to the organisation? Among all the available options, there are software solutions for same domain industry, and there are software solutions that are uniquely tailored to fit the business’ needs and demands.

Ease of use:

As with any technology, ease of use is critical because people will simply avoid using one that’s difficult to learn and use. Make sure the wiki offers rich text editor, image embedding, file attachments, and an intuitive interface. Information should be able to be organized in flexible hierarchies.

Integration and Extensibility

Wikis are not a replacement for email or other software enterprise’s staff use on a daily basis. To fully benefit from a wiki, it should have a rich API that lets the enterprise integrate it with existing systems so it truly is a platform you can extend, customize and use for the long term.

Security:

Security is, of course, a high priority concern when dealing with corporate information.  Wiki tools should have features such as multi-level user permissions down to the page level. In addition, wiki should support LDAP, ActiveDirectory and other authentication and site administration services.

So, for any business, choosing the right software it is a big decision. It is require consideration for many different factors.

Assessment of the business need is crucial because choosing the right wiki software will work with the company’s specific needs and could assist it to achieve or tackling relevant objectives / issues.

References:

التصنيفات :Enterprise 2.0, web 2.0 الوسوم:, ,

Enterprise 2.0 implementation: benefits and risks

Implementing new technologies is about change. Users are involved, work processes improved, and possibly organizational structures will change. With any change, There are always benefits and risks associated with that change. In this post I will talk about benefits and risks of Enterprise 2.0 implementation with relevant case study.

Benefits of Enterprise 2.0 implementation: 

Productivity & efficiency:

  • With quicker access to resources, individuals and teams work more effectively with easier collaboration.
  • Migrating some kinds of organizational communication outside email to create greater personal efficiency.
  • Acceleration of team interaction and more rapid trust-building that lead to improved team performance.

Staff Engagement:

  • More efficient publication of information to employees and communication across the organization.
  • Providing tools and initiatives aimed to facilitate collaboration flows through to changed behaviors.
  • Enterprise tools both provide easier access to content and better collaboration for shared learning.

Knowledge:

  • Making it easier to uncover and connect with relevant expertise, either in people or embedded in documents and processes.
  • Enabling search to quickly provide the most relevant information and resources for the individual.

Reputation:

  • Taking the initiative to implement innovative approaches create leadership position with an industry and with clients and business partners.
  • Attractiveness as an employer, orrgnization that intend to uptake of new technologies, is often seen as an indicator of a innovative culture.

Here is a case study from Janssen-Cilag that highlight some benefits of implementing Enterprise 2.0:


Janssen-Cilag is an Australian pharmaceutical subsidiary of Johnson & Johnson. It was using a static HTML site for an intranet. Called InfoDownUnder, it was originally developed in 2001. Some content was out of date and there was no search capability. Trust in the system was low and demand for change was high.

Nathan Wallace, in the CIO at Janssen-Cilag was progessive in his vision and suggested the organization implement a wiki as their intranet. They needed a system where editing is immediate and very simple. It was more important to let people add content rather than worrying about what they shouldn’t do. At any rate, the risk of letting anyone change anything was low, since the wiki provided a complete history of changes so mistakes can be quickly undone. The history would also allow the administration people to hold irresponsible individuals accountable for improper actions.

Nathan wrote, “our contributions per month has continued to grow since launch. People are engaging and collaborating more with time, they are not losing steam as you might expect. To drive adoption, we’ve primarily focused on owning the flow of new information. Early on, we established a policy that all announcements must be on JCintra. When necessary, they may be sent via email in addition to posting as news on the Intranet. Today, announcements ranging from major restructures to new babies for employees flow through the news page without clogging up email inboxes.”

He went on to add, “Business information that was previously scattered in email (e.g. Business Planning presentations) is now collected into a permanent, secure online space. We have a growing reference and history of information to build on and make available to newcomers. Knowledge management, previously a big concern, has moved off the agenda for the time being.” That is because knowledge management became a byproduct of using the wiki and not a separate activity. Reference

So.. What about Risks of implementing Enterprise 2.0?

Security:

  • The possibility of leakage of Confidential data and competitive information externally.
  • Opening systems can make IT resourse more vulnerable to malicious softwares.

Loss of Control:

  • Mangers cannot control the tremendous amount flow of information in organizations.
  • Individuals make negative or inappropriate comments on discussion forums or other public communication.

Reliability:

  • By posting incorrect or unreliable information.

Reputation:

  • Inappropriate staff behaviour by making negative comments about the company or its clients.


Case relevant to the risk of Enterprise 2.0 Implementation:

Honda Struggles With Negative Reactions to its New Car Model

According to Mashable In 2009, Honda released photos of their new 2010 crossover vehicle, the Accord Crosstour. They’ve set up a Facebook Fan Page as savvy and innovative social media marketers, to revel in all the fan support and social sharing in the aftermath of the big reveal.

Four thousand people signed up as “fans” of the car on the day it was launched, and most immediately began posting negative comments about the car’s design. And the Twitter response has been equally negative.

Honda has attempted several responses. At least one Honda employee – Manager of Product Planning Eddie Okubo – began posting positive comments on the page. Okubo, however, didn’t identify himself as a Honda employee. When Facebook users caught on to his identity, Honda purged his comments from the page. Autoblog says, “His comments and other similar non-sanctioned corporate communique will one day wind up in business textbooks as examples of how social media marketing can go very, very wrong.”

While social media marketing can reap huge word-of-mouth wins for brands, and keep marketer’s in touch with their customers at a very intimate level, marketers must deal with negative comments of as aggressively as they deal with positive statements or comments. Honda’s case clearly shows loss of control and reputation risks of Enterprise 2.0 Implementation.

So.. I hope I explained the benefits and risks of Enterprise 2.0.. and if you have any comment or case that relevant to the risk or benefits of Enterprise 2.0 implementation, please share it in comments.

Reference: