Hometown Unicorn

Today I start a new challenge,  working for an IBM Premier Business Partner called Portal in Bracknell, Berkshire.  I'll be helping their customers make, and get value from, their investments in IBM Collaboration software of all types : from transactional portal application dressed with user managed web content, through Social Software for organisations on the road to becoming a social business, and not forgetting along the way our Notes/Domino customers who've been getting value from Notes, Sametime and other Lotus products for over 20 years.  Today's the day to meet the Portal people and get connected - many of these people I have known from project work over the years and it's a great pleasure to be linking up with and working with them again. The main thing on my mind today : the decision to embed Lotusphere 2013 inside the IBM Connect event . I have two contradictory thoughts on this : "It's not a moment too soon" : customers are confused about t

Like all triathletes and semi-serious fitness types, I like to record my sessions and for my recent IMUK I made a big effort to plan and record my sessions against my plan.  This is for me was doubly motivational on a rainy morning, the fact that there's a big fat zero in the "actual" column might - just - get you out for the session on the start line, you can only remember all the work you've done that got you to that point if you bothered to write it down I am going to blog separately my overall approach to Ironman training (it's not going to cause a revolution in methods), but I wanted to document here how I recorded it, in case others find the level of detail and overall approach useful. For planning and retrospective analysis, I created a spreadsheet with a main sheet for the whole training time (1 row per week, with single columns for targets for swim, bike and run for the week separate sheets for each 4 week "iteration" (next post wil