Home > Intel Communities > Open Port IT Community > IT@Intel > Blog > 2008 > February > 12
Previous Next

IT@Intel Blog

February 12, 2008
1

 

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

 

 

1 Comments 0 References Permalink
0

Over on the IT @ Intel blogs, I talked about whether Corporate Blogs Really Matter some time back. Several of you provided comments and questions, and I wanted to take a moment to answer a couple of them.

 

Michael commented: "I like reading about what you are thinking about, and how you are making a difference in the lives of Intel staff."

On this topic, I did a two-part post on what we were doing to build a technical community within IT. You can check out these posts at the following links: Building a Community Within IT, and Lets Jam. Those posts are pretty extensive, and talk specifically about how we're making a difference in the lives of IT employees, so I won't repeat that here.

Yvan commented: "I would like to hear some of the management problems you encounter when doing your job."

Here's a specific one that has been a challenge - Many of the employees who post here on the IT @ Intel blog are not directly part of the IT @ Intel program, and therefore don't have social media/networking as part of their job description. That means we have our normal jobs but also participate in this stuff on the side. Making the time for posting and commenting is one thing, but being recognized for it is the bigger challenge. How do you make sure that your manager sees your blog as strategic for Intel and not a waste of time that takes you away from your job?

I've personally been very lucky that part of my job is focused on community development (you can read about that on the links above). On my annual performance review I have an entire section of accomplishments that are directly related to work I've done in support of social media. My manager didn't ask me to put it on my review, I did it because I felt that it was important - but I still had to educate him about it and the value it provides to the company.

Sometimes middle and senior management just don't "get it". Unless they themselves are participating in the community they don't necessarily see the value it brings. To them it's just a diversion from what employees are actually paid to do. But what if the company saw it as a strategic advantage vs. a perk or side effort? What if the entire company, every employee all the way up to the CEO, was actively involved in being a spokesperson for the company?

Paul O., our CEO, is a blogger on our internal systems. It's not a weekly or monthly thing, but he does it, and it's something that employees appreciate and look forward to. Our CIO recently kicked off his first blog as an attempt to change the way he communicates to IT. It's been a huge success already. As soon as we start to see blogging as another form of communication like using the telephone, sending an instant message, or walking down the hall and speaking to a group of people, then it doesn't become a diversion/distraction, it becomes part of your life/job.

Personally, I hate talking on the phone - I'd much rather have someone communicate to me via an email, a blog post, or a face to face conversation.

The way that we communicate as people is changing - blogging is one of those new ways. Making the switch from tapes to CD's was a big change; rotary to touch tone changed the way we dialed; learning how to send a text message instead of calling someone was huge; what's the big deal with blogs and forums??

 

It takes time to educate management on the value of social media, and it takes time for them to formally recognize it and make the time for it. But if you can get there, and you can start to use social media as a strategic advantage for your company, then you've got it made. It just takes the time to sit down with your boss and say - "Here's how my participation in this activity is adding to Intel's bottom line. And here's how it helps me do my job better." Speak their language, and the change will happen.

 

 

Keep the questions coming - let us know what you want to hear about as it relates to IT @ Intel.

0 Comments 0 References Permalink