| 
				Β   | 
				
| (One intermediate revision by the same user not shown) | 
| Line 1: | 
Line 1: | 
 | == Notes on company benefits (22.10.2009)<br> ==
  |  | 
 | 
  |  | 
  | 
 | Trying to move my notes and thoughts into wiki, instead of keeping them on paper, and loosing track of them.<br> 
  |  | 
 | 
  |  | 
 | From interviews with Danish people on StrΓΈget in Copenhagen, when asked about what characterized a good leader is, the following was mentioned:<br> 
  |  | 
 | 
  |  | 
 | *Empathy<br> 
  |  | 
 | *Listens 
  |  | 
 | *Remember that all employees are different 
  |  | 
 | *Meets on time 
  |  | 
 | *Shows trust in his / her employees 
  |  | 
 | *Shows that he / she can be trusted
  |  | 
 | 
  |  | 
 | When the same people were asked about benefits, the following came up: 
  |  | 
 | 
  |  | 
 | *Extra days off 
  |  | 
 | *Massage of back, some Danish companies have arranged for massage during working hours 
  |  | 
 | *Free mobile phone 
  |  | 
 | *Company car / paid transport 
  |  | 
 | *Lunch 
  |  | 
 | *Flexible working hours 
  |  | 
 | *Fitness 
  |  | 
 | *Surprises 
  |  | 
 | *Free Internet at home 
  |  | 
 | *Afternoon fruit 
  |  | 
 | *Friday bar
  |  | 
 | 
  |  | 
 | Some thoughts on benefits for our company 
  |  | 
 | 
  |  | 
 | *More vacation days, for long time employees 
  |  | 
 | *Team budgets 
  |  | 
 | *Thoughts about extentions on 2-year bonus and 5-year bonus?
  |  | 
 | 
  |  | 
 | <br> 
  |  | 
 | 
  |  | 
 | <br> 
  |  | 
 | 
  |  | 
 | <br>
  |  | 
 | 
  |  | 
 | == What to share on the wiki (16.11.2009)<br>Β  ==
  |  | 
 | 
  |  | 
 | Extract of some good ideas about what to put on the wiki found in this article (in Danish): [http://www.erhvervsbladet.dk/vaekstmaskinen/brug-af-wiki-kraever-aabenhed Article on wiki usage]
  |  | 
 | *Everything from complex technical questions to daily information has its right to be put on the wiki. 
  |  | 
 | *Knowledge is shared during projects and available to all employees no matter where they are.
  |  | 
 | * Easing the email overload, because employees can find information on the wiki, they don't have to ask everyone on email any more, especially is mentioned the company rules such as:
  |  | 
 | ** Rules for time registration.
  |  | 
 | ** Lunch meetings.
  |  | 
 | ** Who makes the coffee (not so relevant for our company I guess).
  |  | 
 | * The company (Neoconsult) has used wiki for 5 years.
  |  | 
 | * The wish is to make developers put words on what they are working on while they are doing it, share the knowledge which is gathered.
  |  | 
 | * In Neoconsult's wiki the employees can also find information about:
  |  | 
 | ** How the printer works.
  |  | 
 | ** Which magazines and newspapers the company subscribe to.
  |  | 
 | ** How time registration is done.
  |  | 
 | ** What's for lunch.
  |  | 
 | ** Upcoming events.
  |  | 
 | * Limiting the flow of disturbing emails.
  |  | 
 | * Important that the wiki doesn't contain technical stuff only, but also information about the company's day-to-day information.
  |  | 
 | * Wiki fits well with organisations which are based on trust and open structure.
  |  | 
 | * Everybody has access to all information and must be aware that the information must be treated carefully.
  |  | 
 | * Management must backup around the idea of openess and motivate the employees to play along.
  |  |