Welcome! 1
Agenda 9.00 Opening words Janne Kalliola, Exove Oy 9.10 Designing Sites Juha Jauhiainen, Union Brand Ltd Case: Finndomokoti.fi Piia Lehesmaa, Finndomo Oy 9.40 Implementing Sites Jani Tarvainen, Exove Oy Case: Fiskars Garden sites Marja-Liisa Matikainen, Fiskars Oyj 10.10 Break 10.20 Maintaining Sites Janne Kalliola, Exove Oy Case: Finnlines.com Hanna-Leena Lahti, Finnlines Oyj 10.50 Discussion Always select a proper tool for the task at hand. 2
Know what you need and get a system that fits your needs. When in doubt, ask help from a professional. 3
About us Exove delivers innovative, reliable and business-driven web services that enable our customers to conduct better business on the Internet. 4
We base our work on our customers strategy and needs that we develop into web services. We deliver sites, community platforms, and Web 2.0 applications. 5
23 people, 70 customers, 1.2 MEur turnover 2009, profitable Agenda 9.00 Opening words Janne Kalliola, Exove Oy 9.10 Designing Sites Juha Jauhiainen, Union Brand Ltd Case: Finndomokoti.fi Piia Lehesmaa, Finndomo Oy 9.40 Implementing Sites Jani Tarvainen, Exove Oy Case: Fiskars Garden sites Marja-Liisa Matikainen, Fiskars Oyj 10.10 Break 10.20 Maintaining Sites Janne Kalliola, Exove Oy Case: Finnlines.com Hanna-Leena Lahti, Finnlines Oyj 10.50 Discussion 6
5/19/10 Käyttöliittymäsuunnittelu Toimintamallimme: 1. Toimintaympäristön määrittely 2. Konsepti 3. Sisältösuunnittelu 4. Muoto 5. Kokemus 7
1.Toimintaympäristön määrittely Liiketoimintastrategia ja liiketoimintaan liittyvät prosessit Brändin määrittely Analyysi: trendi- ja kilpailukenttäanalyysit 2. Konsepti 1. vaiheen kiteytys Tavoitteiden määrittäminen Kohderyhmä Positiointi Vision määrittäminen ja kiteytys 8
3. Sisältösuunnittelu Tavoitteiden määritys Käyttäjien tarpeet Resurssit sisällöntuotantoon Toiminnallisuuksien määrittely 4. Muoto Sisältörakenteet Käyttöliittymä Käyttötilannekuvaus Sisällöntuotantoprosessien määrittäminen 9
5. Kokemus 1-4 kiteytys: Suunnittelun lähtökohta Käyttökokemus ja persoonallisuustekijät Vuorovaikutustekijät Visuaalisen identiteetin määrittely /brändi Käyttöliittymän visuaalinen suunnittelu Agenda 9.00 Opening words Janne Kalliola, Exove Oy 9.10 Designing Sites Juha Jauhiainen, Union Brand Ltd Case: Finndomokoti.fi Piia Lehesmaa, Finndomo Oy 9.40 Implementing Sites Jani Tarvainen, Exove Oy Case: Fiskars Garden sites Marja-Liisa Matikainen, Fiskars Oyj 10.10 Break 10.20 Maintaining Sites Janne Kalliola, Exove Oy Case: Finnlines.com Hanna-Leena Lahti, Finnlines Oyj 10.50 Discussion 10
5/19/10 Pohjoismaiden johtava puurakenteisten pientalojen valmistaja. Päämarkkina-alueet Pohjoismaiden lisäksi Baltia ja Venäjä 70 vuoden kokemus, yli 200 000 pientaloa Energiatehokkaan talovalmistuksen edelläkävijä Liiketoiminta-alueet 1. Kuluttajamyynti 2. Projektimyynti 3. Vapaa-ajan myynti 1. Yksilölliset arkkitehtien suunnittelemat pientalomallistot taajamiin ja hajaasutusalueille. 2. Yhteistyössä rakennuttajien, rakennusliikkeiden, kuntien ja maanomistajien kanssa rakennettavat kaupunkimaiset pientaloalueet. 3. Kuluttaja- ja projektimyyntiin suunnitellut ympärivuotiset vapaa-ajan mallistot. 11
5/19/10 Finndomo Tuotemerkit Suomi: Ruotsi, Tanska, Norja: Venäjä, Baltia, Puola, Ukraina: 12
Finndomokoti on Uusi, rakentajan elämää helpottava täyden palvelun FinndomoKoti on hyvän ja toimivan asumisen suunnannäyttäjä. FinndomoKoti tarjoaa monipuolisten talomallistojen lisäksi yksilöllistä suunnittelupalvelua ja kumppanuutta kaikissa kodin rakentamisen vaiheissa. Koti elämän suuri investointi FinndomoKoti- konsepti: Laatu, Helppous, Nopeus, Turvallisuus 1. Kumppanuus rakentamisen kaikissa vaiheissa: Monipuolinen mallisto Laaja palvelutarjooma: suunnittelu, tontin hankinta, kodinvälitys Valmiusaste rakentajan mukaan Uudiskohteet 2. Ekologisuus ja energiatehokkuus 3. Kattava FinndomoKoti myyntiverkosto (Espoo, Vantaa, Tre, Turku, Jyväskylä, Kuopio, Porvoo, Lahti, Muurame, Hyvinkää, Kaarina, Kotka, Lohja, Kouvola, Tammisaari, Maarianhamina) 13
FinndomoKoti verkkopalvelu - tavoitteet Selkeä Helppokäyttöinen Nykyaikainen Mielenkiintoinen Kiteytys: Suunnittelun lähtökohtana oli verkkopalvelun selkeys, käytettävyyden optimointi ja miellyttävä käyttäjäkokemus, johon haettiin ratkaisu sisustus- ja lifestyle- lehtien raikkaan ulkoasun ja houkuttelevuuden kautta. Rakenne noudattelee pientalon hankintaprosessin vaiheita: ensin on haave omasta talosta, jota seuraa tarkempi tutustuminen tarjolla oleviin vaihtoehtoihin ja varsinaisen toteutuksen suunnittelu. Interaktiivinen Kodin hankinnan vaiheita tukeva FinndomoKoti verkkopalvelu - ratkaisut Kiteytys: 1. Kodinhankinnan vaiheiden kautta (Piia Lehesmaa) 2. Käyttäjäkokemuksen kautta (Juha Jauhiainen) Suunnittelun lähtökohtana oli verkkopalvelun selkeys, käytettävyyden optimointi ja miellyttävä käyttäjäkokemus, johon haettiin ratkaisu sisustus- ja lifestyle- lehtien raikkaan ulkoasun ja houkuttelevuuden kautta. Rakenne noudattelee pientalon hankintaprosessin vaiheita: ensin on haave omasta talosta, jota seuraa tarkempi tutustuminen tarjolla oleviin vaihtoehtoihin ja varsinaisen toteutuksen suunnittelu. 14
5/19/10 FinndomoKoti verkkopalvelu - ratkaisut Kodinhankinnan vaiheiden kautta (Haaveilu, tutustuminen, valinta) FinndomoKoti-konsepti/sivustorakenteen avaus (Etusivu) Haaveilu (Asuminen) Tutustuminen (Mallistot/Rakentaminen) Valinta/päätöksenteko (Asiantuntijamyyjän avulla rakentajalle oikean ja yksilöllisen ratkaisun löytyminen) Sisällöntuotanto (Sisältöjen ristiin linkittäminen) Etusivu 15
5/19/10 Asuminen Mallistot 16
Rakentaminen Agenda 9.00 Opening words Janne Kalliola, Exove Oy 9.10 Designing Sites Juha Jauhiainen, Union Brand Ltd Case: Finndomokoti.fi Piia Lehesmaa, Finndomo Oy 9.40 Implementing Sites Jani Tarvainen, Exove Oy Case: Fiskars Garden sites Marja-Liisa Matikainen, Fiskars Oyj 10.10 Break 10.20 Maintaining Sites Janne Kalliola, Exove Oy Case: Finnlines.com Hanna-Leena Lahti, Finnlines Oyj 10.50 Discussion 17
Site Implementation Choosing the right tools Technical design Integrations Content Migration Internationalization Ideal: Parallel progress Choosing the right tools Content management is a common problem domain A large number of tools on the market One size does not fit all It is likely that you ll have many equally good options Most important attributes (customer point of view) Quality, reliability and adequate performance Future prospects, roadmap Ease of use Should I use a collection of tools instead of one? 18
Technical design Model your content before implementation What type of content do you have and what are their relations? What are the roles of people managing this content? Identify common elements from layouts to avoid unnecessary complexity Faster implementation, increased quality - during AND after the project Prepare for changes, early intervention in problems Identify and manage integration points early Integrations Act early Integrations are generally unexciting and do not provide immediate results Integrations are a team effort Successful integrations delivered on schedule require commitment and resources from the client as well as a possible 3 rd party Prioritize integration points The integration to the stock inventory system of your web store must be ready by launch where as the Google Maps integration displaying office locations might not be crucial 19
Content migration Evaluating the feasibility of content migration Cost: How much content needs to be transferred? Content quality: Is the existing content still relevant? Which migration format to use? Which is more flexible, the source or the target system? If the source system has no default export format, specify an intermediary format in cooperation with the 3 rd party Request data samples early to map potential issues The client knows their content best, reserve time to check migration samples provided by the vendor Internationalization Are you building a Briefly in section or a complete translation of the site structure? Some common issues encountered with complete translations The designed layout does not handle long words well Some features / integrations are not available in all languages Do you have sufficient resources to translate and input all content within the set schedule? Consider scheduling secondary language version launches in batches after the main languages launch 20
Parallel progress Design and implementation The vendor provides the customer with an environment to input content early on Site layout implementation progresses close to the launch Content migration and integrations The vendor, customer and possible 3 rd party proceed early, targetting at an early finish before launch Content creation and input The customer schedules sufficient time for content production The staff gets familiar early on and possible concept and layout issues surface in time Agenda 9.00 Opening words Janne Kalliola, Exove Oy 9.10 Designing Sites Juha Jauhiainen, Union Brand Ltd Case: Finndomokoti.fi Piia Lehesmaa, Finndomo Oy 9.40 Implementing Sites Jani Tarvainen, Exove Oy Case: Fiskars Garden sites Marja-Liisa Matikainen, Fiskars Oyj 10.10 Break 10.20 Maintaining Sites Janne Kalliola, Exove Oy Case: Finnlines.com Hanna-Leena Lahti, Finnlines Oyj 10.50 Discussion 21
5/19/10 22
5/19/10 23
Agenda 9.00 Opening words Janne Kalliola, Exove Oy 9.10 Designing Sites Juha Jauhiainen, Union Brand Ltd Case: Finndomokoti.fi Piia Lehesmaa, Finndomo Oy 9.40 Implementing Sites Jani Tarvainen, Exove Oy Case: Fiskars Garden sites Marja-Liisa Matikainen, Fiskars Oyj 10.10 Break 10.20 Maintaining Sites Janne Kalliola, Exove Oy Case: Finnlines.com Hanna-Leena Lahti, Finnlines Oyj 10.50 Discussion Agenda 9.00 Opening words Janne Kalliola, Exove Oy 9.10 Designing Sites Juha Jauhiainen, Union Brand Ltd Case: Finndomokoti.fi Piia Lehesmaa, Finndomo Oy 9.40 Implementing Sites Jani Tarvainen, Exove Oy Case: Fiskars Garden sites Marja-Liisa Matikainen, Fiskars Oyj 10.10 Break 10.20 Maintaining Sites Janne Kalliola, Exove Oy Case: Finnlines.com Hanna-Leena Lahti, Finnlines Oyj 10.50 Discussion 24
Managing Sites The typical site management actions are (in order of magnitude): Modifying content on a page Adding and removing images, videos, documents, etc. Adding and removing pages, changing menu structure Adding and removing sections, changing site structure Adding translations Adding new sites Changing layouts Decide what you need to be able to do by yourself Implementation cost and complexity grows when more functionality is made available Leave the rest to the implementation vendor Site Manageability The manageability of your site depends on the selected system and the changes done on it Some systems are administrator friendly and others have socalled expert user interfaces only Extending the CMS might break manageability or future development Make sure that your vendor follows the rules and the conventions of the CMS when adding new functionality Admin interfaces might be rewritten, if needed Typically a costly operation Should be done only when absolutely needed typically due to content format or specific needs 25
Your Web Site Management Team There are a few persons in your organisation that do the heavy-lifting with your websites Identify them, their needs and capabilities before starting the project Cultural differences, time differences, and language barriers need to be taken into account Everyone should not be allowed to do everything Decide who owns what If you need to have an approval mechanism built in the system, remember to check with the vendor that the system supports it Typical Roles The following roles are typical in web management Content editors people modifying the content, for example, someone from marketing department in every local office. Access might be restricted. Site managers people that can modify whole sites and assign access rights and roles to content editors. Technical admin a person that checks everything runs a-ok technology-wise, and is used to manage technical hiccups From vendor, you might need Help-desk to help your organisation to perform their duties Support manager to run the help-desk and to manage smallscale development and issue rectification Project team to implement bigger changes 26
Training Make sure that your web development project has a training part You will get a lot more out of your CMS when people are trained Also, number of stupid mistakes drop dramatically If you want to do small-scale development by yourself, ask whether your vendor is able to train you or codevelop with you Transferring silent information is important and really hard Decisions, Decisions, Decisions, Your organisation must be able to make decisions about the site and the content Getting stuck in approval or not having rights to do anything without prior permission leads to stale sites Democracy won t lead anywhere, either Someone must be responsible for the whole site Brand-wise, content-wise, technology-wise They might be different persons Responsibility should flow top-down in natural way for your organisation Escalations happen then bottom-up the same route 27
Budgets Money makes the world turn around Be prepared to spend it when needed but only when needed Understand when it is cheaper to use an expert than to try by yourself Separate site on-going maintenance and development Typically the budgets are owned by different parts of the company Cross-checking and intra-company communication is encouraged! Small-scale development ownership needs to be figured out, otherwise internal costs of getting something small done grow too high Small-scale Development Depending on your business, the need for further development varies Typical corporate sites need one to three small updates a year Media sites require constant attention every week or month SMB sites might have no needs, or they are handled in the next site upgrade that happens every three to five years If you need small-scale development, agree principles during the implementation project The development vendor is the best party to do those Just make sure that you don t get vendor-locked 28
Maintenance in a Nutshell Pay attention to maintenance during implementation project Get your organisation trained Make sure that there is a proper balance of responsibilities and power within site management team Have help-desk and support set-up Agree on details of future development early enough Agenda 9.00 Opening words Janne Kalliola, Exove Oy 9.10 Designing Sites Juha Jauhiainen, Union Brand Ltd Case: Finndomokoti.fi Piia Lehesmaa, Finndomo Oy 9.40 Implementing Sites Jani Tarvainen, Exove Oy Case: Fiskars Garden sites Marja-Liisa Matikainen, Fiskars Oyj 10.10 Break 10.20 Maintaining Sites Janne Kalliola, Exove Oy Case: Finnlines.com Hanna-Leena Lahti, Finnlines Oyj 10.50 Discussion 29
Case: Finnlines.com 3 target groups > 3 sites 2-5 language versions Content management in 5 countries (+ responsibility for content in 8 countries) 30
Background 2 suppliers concept/visual, technical 3 representatives from company pax, freight, company Communication group with representatives from all European subsidiaries Dos and Don ts Do: Plan training, user profiles as part of project Involve people from the start Analyze existing info systems: can they be used in content management Don t: Put information on the site if you don t know how and by whom it will be updated 31
Agenda 9.00 Opening words Janne Kalliola, Exove Oy 9.10 Designing Sites Juha Jauhiainen, Union Brand Ltd Case: Finndomokoti.fi Piia Lehesmaa, Finndomo Oy 9.40 Implementing Sites Jani Tarvainen, Exove Oy Case: Fiskars Garden sites Marja-Liisa Matikainen, Fiskars Oyj 10.10 Break 10.20 Maintaining Sites Janne Kalliola, Exove Oy Case: Finnlines.com Hanna-Leena Lahti, Finnlines Oyj 10.50 Discussion Download slides at http://www.exove.fi/yritys/seminaarimateriaali/ 32