IT Peer Network

2 Posts authored by: TomasMcinerney

So we are on the home run of deploying the new pilot cube

environment, in fact I’m on site helping supporting day one move in at our

third US site installation which has certainly been interesting. Flight over

went quickly, though at some points it was rather roller coaster (to the point

coffee was spilt on laps)

 

But I digress…

 

 

 

I wanted to discuss an item I have brought up before;

benchmarking. The project has moved on and worth asking some questions around.

Intel IT has used classic benchmarking applications to compare platforms when

going to RFP (using standard off the shelf applications) but we discovered this

testing wasn’t helping us improve the performance of our software on the client

it was simply giving us faster clients (not a bad thing) We were missing some

critical decision making criteria for evaluating newer versions of

applications, client builds or software tweaks (identifying performance improvement

or impact) As we drive towards more out of the box applications we will also be

using the tool to evaluate impact on the environment.

 

 

 

So we kicked off a project to begin recording certain

productivity metrics to evaluate user perception performance; not necessarily

aimed at just understanding how fast each client is; but more what impact it

has to users

 

 

 

Some of these timing metrics include

 

 

 

  • Time into operating system

  • Time into email application (first email)

  • Time into first instant message conversation

  • Time to first spreadsheet/document application

 

Once changes are made to the client build or application

stack an impact is recorded through the metrics. This means we can start to set

goals and performance targets (10% faster build in 3 months…etc)

 

We hope to publish this data with some fellow travellers to get

some indicators on quantify the overhead an ‘IT’ build compared to an off the

shelf build (we classify it as vanilla OS)

 

 

 

Are you recording productivity metrics to compare

applications and build generations? Any thoughts on if this data would be

useful to you?

 

 

 

For decades Intel employees have started and ended the day looking at the same gray/blue/brown (depending on your site) sound soak dividers. They provided solace and security, a place to get on with your work. They give you something to pin things to and space to hang your all important white board.

 

 

It's been the norm to start a ‘Meerkat' discussion with your neighbour, or throw foam balls to a team mate whilst a long call drags out. Cubes have been part of Intel's culture, as much as transistors and the bing bong.

 

 

This is about to change

 

 

I'm working on the IT side of a large project currently underway in the halls of several US sites. The project has one focus; challenge the way we currently work. Several organisation reports and visiting other companies have shown it's just not as effective for the employees we now have.

 

 

10 years ago people came in Monday to Friday; they worked in teams within the same geo or even exclusively on the same site. Teams or even whole groups sat near each other (from designers to manufacturers) they went to lunch together and all left for home around the same time.

 

 

This just isn't the case today. Intel's workforce, like many, is globally diverse. Your cube neighbour now manages a team out of the US that is working on a large project in Asia for delivery to a customer in Africa. These changes in workforce have had several impacts

 

 

People are not physically around as much: Technology at home has meant you can be as connected in the office as out of it. Wireless technology coupled with video and voice can mean employees can meet each other when cross over times allow.

 

 

When people are around they want to network, they want to use some flexible space to crunch a problem or perhaps hold private phone conversations

 

 

Private calls are not private any more, people want a smaller space they can make calls with remote managers

 

 

Because of these changes the pilots we are working on aims to re-enforce better facilitate those requirements. We are aiming to achieve this through several things

 

 

Smaller conference rooms designed for just one or two people. Enough space to sit and take calls, but not enough to be booked by teams. These meetings happen today but can hold up larger rooms making it harder for larger teams to meet

 

 

Deploying a more flexible IT environment allowing quick deployment and high demands. Mobile technology is something Intel IT has always focused on, here we are taking it a step further by using 100% wireless, even for desk areas (you can find out more about the primary wireless campus in our IT@Intel site) IT are also integrating phone services into the notebook to remove the need to have a desk phone. Those that specifically want to have a phone can also log into any handset.

 

 

Flexible, open zones to encourage quick white board problem solving, not so much about formally booking 60 mins of meeting time, just pulling around some chairs and working with the team around you

 

 

Free things like coffee and snacks are being introduced, again to encourage employees to come into the office.

 

 

At this stage employees can still choose to have a permanent desk, others have elected to be part of open zones, with no permanent home to call their own.

 

 

None of the things we are doing in these pilots haven't been tried and implemented by others - but this is the first time we are trying them with our employees; and as any good IT shop will tell you each customer group has its own requirements.

 

 

I will be posting updates as we see how the pilots develop.

 

 

 

 

'Flexible areas' with lots of seating and snack areas

 

 

 

 

Unassigned desks

 

 

Filter Blog

By author:
By date:
By tag: