As I mentioned in one of the last posts, we released the first build of our Intranet site, built on Windows Sharepoint Services.

The release went very well. Mainly because of the preparation and planning on forehand. I am now (2 months down the line) seeing some things that could have gone a bit faster or differently.

We built and configured the server first, set up the outgoing mail settings, and the main structure of the site. After that we started setting up all the standard content for the sub sites, such as the calendars, some templates and so on.

When the main structure was set-up, we moved to the front page. We made a static block in which we added a lot of links to pages we believed would be either difficult to find or needed more attention. Also we created templates for the announcements from different departments.

When we where ready, we organised small sessions in which the team leaders could go, or send people from their teams to. Since we are mainly a call-center, it si hard to get people off the phone, so these sessions took about 30 minutes and spanned the whole day during 4 day’s. This, we believed, would give everybody interested the chance to have a look.

To remove administrative overhead, and also make sure the intranet will be used by the staff (of all levels) we decided to ask for volunteers in each team to administrate their account sites. This generated some quite positive feedback, and within a week, I had the team of administrators complete.

This created a small gap. I did not expect to have the team of admins ready that soon. Therefore, had no training material ready yet. The problem here is, that as soon as the site went online, the last think I want to think about now is writing How-To documents!  Therefore, be advised, make sure all documentation is ready before!

For the launch we started 3 competitions:

• The Naming competition, to get a name for our intranet, untill now we where still using the server name to access.
• The Logo or Template Design competition and a
• Bug Hunt. I hid images of little bugs in the site, and people had to find one, and accompany it’s location with a real Bug in the site.

The Bug hunt, really helped me a lot in the first day’s to get a list of all the little things I still had to work on/fix. To be honest I can really recommend something alike.

These competitions really helped to get most of the people online. That together with the Site-Admins, coming from all levels in the organisation and from all teams.

Aside from the standard set-up, I have also been creating some List templates, for things we know will be used in several Sites, and can be easily set-up this way. Examples are FAQ, Policies & Procedure Libraries, etc.

Resuming the first two months, I am very impressed by the capabilities of WSS, out of the box. Also about the manageability and ease with you can set up basic lists forms and such. Well, the fact of me, Solo, running an intranet for 350 employees divided in 25 teams while developing applications speaks for itself.

I am sure that my enthusiasm for this platform will diminish, as soon as I will try to customise a bit further than the help-file likes… after all, this is a Microsoft product

At the moment, I am looking into two different things. I am trying to find out how (if..?)  the custom workflows work, and trying to publish a .Net application I built in the sharepoint site as a webpart.

To be continued…!

This summer, just a week before going to Brasil, I received a new gadget (I prefer to call them Toy’s). The Nokia 5800 Xpress Music.

I love it! Really, it joins together the kind of functionality you’d like in a mobile device. It has a few drawbacks which I can imagine more advanced and experienced smart-phone users miss. However for me, as the first phone with a camera on it (..!!..) I love it!

PRO’s

• WiFi
• GPS
• 3.2 mp Camera + Low res camera for video calls (if you do any ?)
• position sensor (screen rotates as you rotate the phone)
• Easy to extend, make your own apps and widgets
• Quite long battery life

CON’s

• No keyboard (on screen keyboard works fine though)
• GPS is slow, assisted GPS uses a GPRS carrier making it very expensive (believe me! I was roaming in Brasil and forgot to switch that off :S )
• 3.2 mp Camera is considered low res for some people nowadays’
• Not too many free applications to download
• Menu’s too static, no real (android) desktop feeling

Im really impressed! I have seen the iPhone, and thought it was too big. The blackberries…, I simply find they have too much of the “Business Flavour” and are just boring (sorry!?). The only phone I actually had in my hand and can be seen as serious competition, is the HTC Touch running the Android OS. I liked the Desktop idea I miss a bit on the 5800. This all, looking at the low cost range of course!

I already built a small application for it, a rip of the iPhone mosquito repellant. If you’re interested, drop me a comment, and I can send you a copy.

The holiday season officially ended yesterday with the Kids going back to school in Spain. Bad Weather came to Barcelona this weekend, with the local weatherman declaring the end of summer. My holiday’s ended already more than a month ago, and it looks like there will be none at least untill X-mas. It is all over!

The last few months where great though! I really enjoyed my trip to Brasil, and the summer months in Barcelona are great too. The Neighbourhood parties, day’s and Nights at the beach and loads of Kite Flying!

I really managed to recharge batteries for the sprint ’till christmas. Due to the above reasons, it has been really quiet here (on this blog). The last post was even before FC Barcelona won the 3 titles they opted for and broke almost all historical records.

At work quite some things changed too! The management structure has been made more agile and I moved to a new team. At the moment, we are analysing my Job-Title, and description, to see if it still fits my position.

The new team I am working in now is called Service Assurance. This name explains most of what this team takes care of. Make sure the service is running, work on improvements and raise the quality of the work done. I also increased a level within my position, meaning … a little bit more cash in hand, and quite some more responsibilities and tasks.

The good news here is that in my new team I am tasked with the Intranet project. This is nothing new, but the new part is that I can dedicate 100% of my time to it, and I can make use of more resources.

During the last month, I have been working hard to get the first version of the Intranet online. It is there, and we launched it officially last week.

Since I changed teams, I am managed differently. Differently in Italic, as I was very close to write better. To be honest, there where quite a lot of discrepancies between me and my manager in many things. Even though I could understand, or at least try to understand most of his decisions. Now I have a new manager. after now 2 months, I can easily say I have the feeling we are on the same line. Which is good. This helps me a lot in Completing projects, as I have a sense of support from higher up the chain, which I had the feeling I lacked a bit before.

As I mentioned before the intranet project is really getting a shape. We have launched the first version running on a small (20gb) Virtual 2003 Server running WSS. This is, after all the investigation and plan-making a lot less than we originally aimed for, and the effect is visible.  Now we have to start making a case to upgrade the server to a full moss, and an SQL server for storage.

We also decided to make release 1 of the intranet as standard as possible. Fully based on templates, and only a few custom lists. This to make sure we could build a case for a more expensive MOSS Server (the idea was that if we could show that we could do it, we’d have a better buy-in from the management team).

To be honest, the possibilities of the standard WSS installation, with the 40 Famous Microsoft templates is giving us about 75% of all the functionality required.  The gaps we have identified will be mostly filled when we move to a full MOSS Server and are mostly related on how we store information and to align that with the spanish law on data protection.

Today, first 1-2-1 personal review with my new manager. She was happy, the intranet is there, on time and with a lot more functionality then we all expected… -> Im Happy!

It is all starting again!

I Gooool!!!

Aquí teniu el fragment d’audio del gol d’aquesta setmana. Possiblement el millor que es pot baixar de l’internet en aquest moment

(en mp3, així ho pots posar en el mobil)

Here’s the audio fragment (the one I liked most) from the goal against Chelsea in the Champions league Semi-final:

http://alex.k.bcn.googlepages.com/GOL3.mp3

!!Gol de lo puto gusiluz!!

This morning I finished building the WSS Webserver we will use to build our intranet on. To be fair, it was very straight forward and did not gave me any issues aside form the speed, as I was working on a VM copy of the real server.

I made a virtual copy of the live server, to do a test run of the set-up. I used the VMware converter which is simple to use, and gives me an exact copy of the live server. I used this to complete the setup and configuration. This way, if any problems appear, I am aware of them and can prevent them from occurring on the live machine.

I did however encounter one small issue, which is completely my “fault”. I did not check in advance how to set up the email configuration for outgoing and incoming mail. The server is a standalone installation, not part of a farm, and I believe the WSS server, although standalone, should be able to benefit from the UK exchange environment for the mailing purposes.

Another thing I now have to have a look at is the way we will “upload” the custom applications we will be building. My best guess is that we will set up a site in IIS for each which we will link to from within the WSS site. However, I would have to have a look on how this can be done. Shared folder, Frontpage extensions, don’t know yet. We will be developing in wither visual studio, or on the VS Web developer express edition, and I’m not 100% sure what is the best way to publish the applications we build in there.

For about 5 years I have been working with IBM software. Mostly using Lotus Domino and Notes, designing applications. However I also looked at other technologies, like Websphere and DB2.

I have recently switched (well, I’m still switching) to comparable products from Microsoft. Mainly becasue the company I work for made the decision to stop using IBM for their internal mail and databases.

I do however believe that IBM, known as Big Blue, a big and slow organisation, was ahead of Microsoft concerning intranet software and ease of development back in the day’s they launched Websphere. I have been looking at an article on their website, that states that in 2006, their Intranet was listed in the Nielsen Norman Group Report: Intranet Design Annual 2006: Year’s Ten Best Intranets.

I never heard of that report before, and headed straight over for a look: http://www.nngroup.com/reports/intranet/design/. The report is for sale. 224$ and its yours. For me that is too expensive, and Im sure that my boss (who is likely to leave soon), would have a good laugh if I walk over to ask him for the money!

(reports from previous years still cost about 200$, which I still find very steep!)

However, it gave me a good impression what points to look at for our Intranet:

Some of the key areas for which best practices are presented in the report are:

• Company and industry news
• Integrating internal and external information sources
• Editorial control of the intranet homepage
• Keeping the intranet up-to-date
• CEO blogging
• Employee and department weblogs
• Onboarding of new employees
• Consistent navigation
• Multilingual intranets; supporting international employees
• Multimedia and video on intranets
• Data visualization
• Web 2.0 features on intranets
• Community
• Polls
• Collaboration tools and discussion boards
• Internal wikis
• Employee self service
• Search
• Governance
• Development process for intranet redesigns
• Web analytics for intranets
• Staffing of intranet teams; where they report in the organization
• Updating and maintaining standards and guidelines for intranet design
• Intranet branding
• Promoting new intranet features
• Staff directory and employee profile pages
• Corporate calendars
• Personalization
• Customization
• Alerts
• Working with external design agencies

These points are things (call them features) they look at when evaluating intranet sites. I believe this to be a very complete list, and I’m sure that in a company our size (just looking at our office in Spain, we are about 300 people) can and will have to remove some of the points. Either because of difficulty of implementation (read: cost), Irrelevance or plain Overkill.

It looks like we have a Feature Checklist, with which we can start planning!

Intranet budgets and staffing

Seems like someone in the company has read the post about the intranet re-design. We received communication that a complete organisational layer will be disappearing! This was actually what I hoped for because I firmly believe in flat layered organisations. From what Ive seen in different companies, is that flatter organisations tend to embrace employee empowerment, are quicker in their decision making and more flexible in fast moving/changing markets (like the IT business we operate in).

I also believe that this will enable me to design the intranet in a much more useful way. The platforms we implemented lately are web based platforms to enable and improve both horizontal and vertical communication. My biggest fear was that with the classic org-chart the company has here these platforms would not be used to the fullest. Especially when I received the first ideas from management, in which they actually wanted to implement the full structure of the organisation in the intranet design.

As it looks now, I’d have to go back to the drawing board, which I’m happy with, because now it looks like we can design a modern intranet, that will actually enable cross-team communication and combine that with a sound knowledge management strategy.

Yesterday afternoon I read about the new Ubuntu version (9.04) which was just launched, the Jaunty Jackalope.

I had a look and thought it would be interesting to install, but noticed some other distributions for netbooks. Among which the moblin (moblin.org). This interested me, as Im allway’s into trying out something different. I downloaded the image and used the Ubuntu DiskImager tool to get it on a 4Gb USB stick. This all worked fine!

The tool is great, I have been doing magic in the past to make a bootable USB install which is now a piece of cake! I set-up the Eee Bios to boot from it, and it presented me with a nice bootmenu. But any option I selected, left me with a black screen and an eternal hourglass. I tried switching to console, but it did not let me log in!

So, after a few hours I decided to get the Ubuntu IMG for Netbook remix, and give it a go. To be fair, a piece of cake! in about 45 minutes I had a running system. Another hour to get all the updates, and that’s it!

The touchpad and the wifi worked fine directly. It also detected the screen resolution fine. I switched back to the standard desktop because I hardly used the netbook remix mode from the Easypeasy distro.

Thats all for the moment. One of these day’s Ill try to fine-tune it a bit more as from my first impression it was running a bit slow. Ill keep you posted!

ah, and I have one question which people might be able to respond… why is everything Brown in ubuntu?

As we are currently about to start implementing a sharepoint environment, this also implies that we will have to plan the Intranet.

Currently we do not have any. Well, we have the intranet site of our English company headquarters, but that is hardly used, and does not interact with us. Meaning that we cannot add our content, links to our tools, etc. The Sharepoint implementation will give us the possibility of having our own intranet site. This is, I believe, very important. Mainly because being an IT company with a lot of different teams, spread over different floors using only email as a way of “digital communication” is … say… a bit outdated (Heavy understatement). This is especially true if you know that most problems we experience internally are due to communication problems (either lack of, incorrect or simply non-existing).

The intranet could change that. Could, I say, because I believe that if not planned and managed correctly and across the board, an intranet can cause more problems than it was designed to resolve.

Management manages this company in a very typical style, you could really apply the machine metaphor to this one! Top-Down and in very linear streams. It is really hard here to make different dept. managers talk with each other and even more if they have to work together.

Lately there is a lot if buzz about 2.0 technologies, and how they can benefit communication outside work, but also in the office. Examples are company wiki’s, facebook-style people profiles etc.

I am now looking into planning the whole new environment. Not because I’m asked to, but because “I can see the cloud hanging above me, and don’t feel to wait till its raining”… Call it being pro-active (but I will dedicate another post to that;) ).

Personally I would like to make sure the intranet will give us these communication advantages and I believe that is also has to be future proof. My biggest fear is that the intranet ends up to be absorbed by “the Machine”, managed by a few upstairs who only care about their specific parts/departments or tools.

I see that the modern organisation is flat, as flat as possible without interfering with operations. If you look at these new communication technologies, you see that these are enablers for this. Maybe they even push organisations is this direction. The problem is: “how to apply modern tools in a company whose management thinks in an old-fashioned way”

As mentioned in the previous post, we are now looking into setting up a whole new knowledge management strategy for our office.

Currently this is dealt with per team. We have approx 250 people working in 15 account teams, giving IT support. Each of these accounts have their knowledge base and their knowledge management processes (if any). As you understand this is not an ideal situation. It is impossible to benefit from each others’ information, and there are a lot, really a lot of double, even triplicate documents. (after all most of us troubleshoot a printer in a similar way).

For a company that is trying to standardise all over the place, this is one of our worst areas.

According to many KM specialists, the first step in this whole plan should be to make sure we have senior management support. This to be honest is more difficult as it seemed. I was convinced that knowing the above, and actively trying to standardise, they would listen to a plan like this, but soon found out the “the idea is good, but it will be too expensive, or take you too long”. Yes, there will be a cost, and a considerable effort, but the return will be a very valuable asset; Knowledge! The work we do at service desks is for a huge part based on the knowledge we have at hand. An analyst can be great in troubleshooting and phone skills, but without documentation…. After all, none of us knows everything.

We are now at the stage that the senior management team is interested in our plans, but we are still not getting a clear go-ahead. This causes us to have to work on the plan outside office hours…

We already have the main outline of the plan. We have the platform (wss) and bit by bit we start to get support. I’m sure that one of these day’s well get the “official” project request. Then we can start gathering people to set up a small project team, and present our plans to the different teams, to get their feedback.

Also, we made a SWOT analysis of the current tools we use, which will help a lot identifying the requirements once we reach the lower level of our plan, which is how the database design would look.

At the moment we are putting everything we’ve got in a high level project plan. Mainly to keep ourselves on track and focused on the parts that are important at the moment and not get in to too much detail (which is a common mistake techies make!). As soon as we have it ready, Ill post an update!