:::: MENU ::::


I’ve 1000 contacts on linkedin

Today I just saw I’ve 1000 contacts on linkedin.

I use linkedin more and more everyday.1000 contacts- LinkedIn

First it’s my “evolutive” contact list : every time I meet someone I immediately send a connection invitation, and I don’t keep anymore the paper business card.

If someone I meet is not on linkedin, I’ll not keep his contact information.

I appreciate to keep “light” contact with people and follow their carreer and contact them again later even if they have a new job.

It’s also a place where I share interesting articles (from feedly) and I read trending topics and also parse what my contacts are sharing, which is often good stuff as these people have something in common with me (they are in my network).

Until today my policy has been to accept all invitations (except very strange ones, but they are very few) and I’m quite happy with it as I don’t feel totally overwhelmed by requests and I still see a coherence in my contacts.

Maybe I’ll change that in the future.



Today I’ve removed Dropbox app from my ipad.

Today  I’ve removed Dropbox app from my ipad.

The reason is very simple : I don’t use it anymore since few months.

I store a lot of files in the cloud, and I was an happy early adopter of Dropbox but as Google drive has improved a lot,  it’s now my single place to store files.

I did not plan for this change,  but it happened  because Google Drive makes it easy to share documents and because it can be easily used by several users on the same PC.


The 4 real reasons why cloud computing is not good for your business

The IT world is in mutation. This is now sure. Legacy IT is going to the cloud.

Around me, I see people that don’t really believe it or are reluctant, so here’re the 4 reasons that can explain why cloud computing is not good for your business :

  1. because your IT team does not understand it
  2. because you think it’s safer to keep your money under your bed instead of putting it in a Bank
  3. because  you are afraid of  change and love status quo, and you’re convinced that it was better in the old days
  4. because you produce your own electricity and don’t want to rely on centralized power plants
If none of these are true for you… believe me, you should proceed!
Photo by William Stitt on Unsplash


My definition of “IT system cloud index”

The objective of the “cloud index” is to monitor the cloud level of an IT system in order to monitor and to communicate in a simple way to the level of cloud reached.

Here’s the definition I use.

The IT system is defined as a sum of Business Services (i.e. applications, see ITIL definition).

Each business service is characterized by a “feature_size”.

The “feature_size” express the complexity of the application (kind of  “function point” approach).

For each business service, we express it’s “cloud_level” on a scale from 0 to 100 :

  • 0   : the business service is hosted on dedicated servers on premise
  • 10 : the business service is hosted on shared servers (via virtualization for example) on servers on premise.
  • 20 : the business service is hosted on an external datacenter
  • 50 : the business service is hosted on a IaaS platform
  • 60 : the business service is on a PaaS platform
  • 100 : the business service is supported by a full Saas Solution.

Based on this, the cloud index is defined as the weighted average of the business services “cloud_level” weighted by the “feature_size”.




Crisis management : 4 organisational tips

As a CIO I’ve sometimes to face crisis : a critical system is down, it has to be repaired as fast as possible.

Playing with the ball 3

In this case, a good organisation and good processes are mandatory to be efficient.

When 2 remote teams have to work together to solve the issue, it’s even more critical.

The 4 key points  I check to be sure of the efficiency of the teams are :

1 leader per team. These leaders need to be in close communication and to trust each other. During the crisis they should be very close. These leaders need to be real leaders, not just guys that follow actions.

1 common action list.  A clear action list (who / what / when / status) has to be shared in real time if possible by both teams.

For each action, apply the process : Assign / Acknowledge / Report status. The task is explicitly assign to an owner(a person). The owner explicitly acknowledge that the action is assigned to him (her). The owner  reports on regular basis about the progress.

Regular overall status published by the leaders. This in mandatory to give clear visibility to all the team members, it’s also important because it obliges the leaders to take a step back and make a status.


Photo :  Tambako The Jaguar via Compfight


My ZTD experience, 1.5 year after…

Pasture Juniper  (Juniperus communis ssp. depressa)

I discovered Leo Batauta Zen to done blog in January 2012.

I started to implement ZTD as my productivity method just few weeks after.

In order to help me during the first weeks and to share with the community, I started a series of blog posts during the first weeks (in fact 9 weeks).

The main changes in my personnal organisation since then are :

Create a daily routine !
Take the habbit to create habbits and stick to them.
This is a very powerfull skill that we all should learn ! Leo’s approach is very pragmatic, concrete, and it works ! (at least for me…)
For example , I’ve setup the habbit to run 3 times per week, the habbits to keep my email inbox at 0

Every day, 3 MITs
Every single day I define the 3 (3, not 4 or 5!) MITs (Most Important Things) that I commit to do for this day.
This is really a very simple but VERY powerfull habit.
It helps me to feel under control and achieve most important things, so it’s helps me to be more productive.

 Simplify, simplify, simplify
I’m an engineer, I like complicated and elaborated things. But based on Leo’s advices, I’m now in a ‘simplify’ as much as possible approach.
For example, my action management tool has been simplified drastically. I went from an elaborated GTD oriented system with maybe 150 actions into it in 20 different lists, to a simple system with 3 lists and around 30 actions into it.

So yes, I’m very happy about it.

If you’re looking for a good productivity ;ethod, I highly recommend you to have a look at it.


Talking cloud : The Shadoks effect.

As a CIO one of the biggest challenges I face in my journey to cloud computing  (using SaaS or real public IaaS) is the IT ecosystem resistance.

Traditional IT partners come from the ‘non-cloud’ industry (and often are still into it).

Going to the cloud is for them a big challenge because it will change completely their job (no more licenses to sell, no more big integration projects).
It will impact their business model deeply: fully flexible costs based on usage, no more upgrades, no more  ‘maintenance’  fees.
The Shadoks used to say ‘Why do it easy when you can do it the hard way?’
Many consultants become Shadoks when they talk about cloud computing.
We start from a very simple concept: a multi-tenant application accessible by a single browser and shared by all users and we come to discuss very complicated stuff like ‘private cloud’, ‘PaaS’, ‘IaaS’,  ‘hybrid’, ‘public’, …
All this is explained in complicated charts, with different words.
The problem of that is we often lose the initial objective and finally just discuss implementing some private cloud (which is not the cloud !)
I’m more than ever convinced that the IT world is in strong mutation and that cloud will change everything.
Players need to adapt or disappear.
Cloud is simple and easy to go, don’t make it complicated.


Federal IT dashboard : a fantastic IT portfolio template.

If you are looking for good portfolio management solutions for your IT projects, I highly recommend you the IT Dashboard website.

Building an  IT projects portfolio is very important for CIOs  in order to :

[list_checkgrey][li] list potential projects, decide which projects to launch[/li][li]follow on going projects assing progress and risks[/li][li]have a good communication tool.[/li][/list_checkgrey]


As stated on the welcome page :

The IT Dashboard is a website enabling federal agencies, industry, the general public and other stakeholders to view details of federal information technology investments.
The purpose of the Dashboard is to provide information on the effectiveness of government IT programs and to support decisions regarding the investment and management of resources. The Dashboard is now being used by the Administration and Congress to make budget and policy decisions.


This site presents all US federal IT projects.

The main points I like are :


All projects are presented.

The montlhy report by the project manager with the current status and risk analysis is available.

[h4]3 simple kpis[/h4]

Each project is managed using only 3 kpis :

[list_checkgrey][li]project cost[/li][li]project schedule[/li][li]risk assessement by project manager[/li][/list_checkgrey]

This set of kpi is simple and easy to understand. A FAQ gives all the definitions.

[h4]Nice visual representation[/h4]

The green/orange/red color code helps to have a very good immediate view

Simple graphs are porposed.

[h4] The source code is available [/h4]

Finally, the source-code of the site is available for free.


I use it as a template since 2 years, based on a sharepoint framework. If you’re interested in sharing, let me know.


Enhanced by Zemanta


Go to cloud : culture change for an IT team

Moving from legacy, on-premise IT systems to cloud-based solutions (SaaS or IaaS) involves a cultural change for IT team members.
IT guys need to switch their mind, accept to “loose control” on their hardware.
In order to illustrate it to my own team, I’ve written a few slides with 3 examples.
These examples are of course caricatures, but the idea is there …