In this first phase we will make sure that the wiki project is properly set up. If you just call out to your employees “Hey everyone! Now we have a wiki and we'd like for everyone to use it!”, you can probably assume that – at least in most cases – nothing is going to happen. Whoever is unwilling to spend time to think about the organizational requirements of a wiki in order to apply these to the company, should lower their hopes for the success and effect of the wiki. Do you already have some experience with wikis? Then you could probably handle some of these services yourself, thereby requiring fewer services from us.
L
Depending on the budget situation, there are some services that are optional or could be done to different degrees. For example: Choosing the correct wiki system, strategies for introducing a wiki, use cases, a wiki best-practices presentation, wiki philosophy in company organization, literature and source recommendations, recommendations for logical steps that companies can take when planning their wiki strategy, preparation of wiki guidelines, walling off from other intranet systems.

Our experience / Our recommendation: 12 x 200 = 2,400
Lower Quartile: 4 x 200 = 800 / Upper Quartile: 20 x 200 = 4,000

You cannot have a successful wiki introduction without a technically perfect system. Don't be satisfied with a system that can be set up quickly without any plugins or quality control checks. Sure, the technology for a successful wiki is just one necessary component. Still, compromises in this area can be quickly devastating.
L
Depending on the budget situation, there are some services that are optional or could be done to different degrees. Here are a few examples: Setting up the basic system, preparing of a test system for the evaluation- and piloting phase, installing and explaining of wiki plugins, adding of users, if necessary the connecting and adapting of LDAP / Active Directory, explaining of basic use and control by telephone/e-mail.

Our experience / Our recommendation: 8 x 140 = 1,120
Lower Quartile: 6 x 140 = 840 / Upper Quartile: 16 x 140 = 2,240

In this project phase, our well qualified communications designers work together with our front-end developer to create your customized enterprise wiki. Many companies believe they can save some money here, thinking “But it's only an internal system!” or “The other internal systems are ugly too. All of our employees are used to this.”
L
It goes without saying that we as a service provider will work according to your wishes. Still, it's not usually a good idea to decide against professional design. Take a look at some examples for wiki designs as well as the best 5 reasons for design in our expert article on this topic.
L
Depending on the budget situation, there are some services that are optional or could be done to different degrees. Here are a few examples: Design customization on the front-end of the wiki (homepage, content pages, portal pages), print view (very necessary!), template for PDF generation with print optimization (very necessary!), content design for wiki content incl. buttons and navigational elements in the content area, picture composition and communication bars for the wiki area, development of color-based guidance system, programmer mentoring during this phase.

Our experience / Our recommendation: 35 x 110 = 3,850
Lower Quartile: 20 x 110 = 2,200 / Upper Quartile: 60 x 110 = 6,600

Wikis are standardized systems. Open-source-systems, and especially their dashboards, should be customized to remove usability problems. This is not an option: it is a fundamental requirement. In addition, our designers' templates need to be programmed and integrated into the wiki. In this phase of the programming, there are particularly high demands regarding the compatibility of different browsers and browser versions, the optimization of designs for various solutions and monitor color settings, and the consistency of source code and sustainability.
L
To avoid problems when upgrading to a newer version of Confluence, we make sure to follow Atlassians' basic structure when we develop a Confluence-Theme. Due to unforeseeable structural changes by Atlassian we can't assure the compatibility to future releases.
L
Depending on the budget situation, there are some services that are optional or could be done to different degrees. Here are a few examples: The eliminating of usability bugs in the dashboard (absolute requirement!), the programming of approved layouts in HTML, the integration of layouts within the wiki, the optimization of the content area, the implementation of the content design work, the development of print views, the development of PDF exporting, the development of Word exporting.

Our experience / Our recommendation: 40 x 140 = 5,600
Lower Quartile: 30 x 140 = 4,200 / Upper Quartile: 50 x 140 = 7,000

Using a wiki that works is incredibly easy. However, you have to know how to help your wiki work. You can learn in our workshops how a wiki needs to be structured and built to work properly. We set up the system for your company and train your administrators so that later on you can do everything yourself. If you like, we'll even show your employees how to use the system. In our recommendation we assume that we'll need 4 hours per workshop. There are also some additional costs associated with workshops (http://seibert.biz/reisekosten). The workshop price calculates the price for our employee at the “Partner” level.
L
Depending on the budget situation, there could be more or fewer workshops.
Here are a few example workshops: Strategy, Design, Wiki-Structuring (important), Wiki Use-Cases, Wiki Administrators (important, User Training and Train-the-Trainer, and Webinars as Discussion- and Rollout Events (minimum 5 users)

Our experience / Our recommendation: 4 Hours per Workshop, 2 Workshops => 2 x 4 x 200 = 1,600 (one Executive-Level Employee, i.e., a “Partner”)
Lower Quartile: 1 x 6 x 200 = 1,200 / Upper Quartile: 4 x 8 x 200 = 6,400 (one Executive-Level Consultantand one Executive-Level Technician)

After the workshops your employees will have a fundamental understanding of how the wiki is constructed, what belongs in the wiki, how it should be structured, and how users can adjust their individual settings. Still, during the development there are always going to be more questions and a need for support that requires fast and uncomplicated answers.
L
Depending on the budget situation, there are some services that are optional or could be done to different degrees. Here are a few examples: Defining of the wiki access configuration, developing of structuring, checking and optimizing of contents, configuring of notifications by e-mail and RSS feeds.

Our experience / Our recommendation: 8 x 170 = 1,360
Lower Quartile: 4 x 170 = 480 / Upper Quartile: 16 x 170 = 2,720

Depending on your company's situation and management's goals, it might be logical to promote the use of the wiki in order to strengthen the positive effects for all employees. It doesn't matter at what point in time you take a closer look at your wiki: You'll always say “The wiki would be even more valuable for all of us if even more employees would begin to use it more intensively.” This is true for the very beginning as well as for the most successful wiki implementations within any company.
L
Depending on the budget situation, there are some services that are optional or could be done to different degrees. Here are some examples: Campaign development (What should be done and when to make the wiki known and successful) (2 hours), use case generation (4 hours), pens (USD 698,00), training videos (6 hours), stickers (4 hours), notepads (USD 1,112,00), and a wiki handbook with “cheat sheets” (6 hours)

Our experience / Our recommendation: 8 x 170 = 1,360
Lower Quartile: 0 x 100 = 0 / Upper Quartile: 25 x 170 + 698 + 1,112 = 6,060,00

Whenever we are finishing our work at a company, we are completely focused on delivering error-free quality. This is why our quality control and tests are only performed by the most experienced members of //SEIBERT/MEDIA. These employees all have at least 10 years of experience in this area. During this phase you could also decide to have additional automated tests performed using Selenium IDE (please see our expert article on this topic at Selenium IDE).

Our experience / Our recommendation: 7 x 170 = 1,190
Lower Quartile: 1 x 170 = 170 / Upper Quartile: 10 x 170 = 1,700

//SEIBERT/MEDIA's project management is professional and flexible. Thanks to our reliable process control, we can offer you any level you need, from “slim and agile” to “the whole nine yards.” Find out more about possible project management processes at our workflows.
L
Depending on the budget situation, there are some services that are optional or could be done to different degrees. Here are some examples: Project planning, project organization, project control, internal and external communication with all project participants, creation of conversation protocols and operating procedures and change management.

Our experience / Our recommendation: 20% of the total hours spent on the project.
Lower Quartile: 20% / Upper Quartile: 30%