Quantcast

The work we have been doing with our relatively new Service Assurance team has not gone unnoticed in the company. In the last 8 months, we have set-up quite some processes that improved the quality and effectiveness of the work done and time spent, and we cut cost by standardising and automating many manual processes and actions. It is a good start, even thought there will always be more to work on.

Now we are asked to apply all this to other offices of the company, under the name of Service Industrialisation. Now I know that in the strict sense, what we’ll be doing will not be industrializing, but applying best practice identified elsewhere.

Many of the problems that can be foreseen in these kind of projects are related to the differences between the organisational structure of these offices, the acceptance of change, and other (mostly cultural) indicators.

In this case the main issues we foresee is the fact that each office is ran completely different, different management structures, with more or less hierarchy and is geographically linked to very different cultures.

Our office, as the “template” is a fairly new one, with a slimmed down management structure. We are increasingly empowering employees on all levels to take decisions and take part in different types of projects aside from their standard day-to-day job, creating a high sense of responsibility and involvement. Also being based in the centre of Barcelona, Spain enables a “relaxed” culture,  that when well managed, adds up to a very nice atmosphere.

If we look at these parameters elsewhere, for example an office somewhere in the south of England, we look at a completely different situation. They work with a complex and strict hierarchy and employees are boxed within their job descriptions. Empowerment is strictly defined per level within the complex many-layered org chart. The office in this example is located in an area, or in the middle of nowhere in an about 3 hours drive from London.

This is just an example of the diversity, between two offices that are geographically not very far apart. Other examples, with even more extreme differences can be found in South Africa, or Malaysia.

I strongly believe that what we have started achieving in our office is due to only a few factors:

  • Empowerment, though the Continuous Improvement feedback cycle, in which employees on all levels give ideas, and volunteer to form task/project teams to work on them and more simple things like assigning intranet admin tasks to them.
  • An Open atmosphere, mostly due to the multicultural aspects (around 20 Nationalities in 1 office) and the location of the office.
  • Improved Communication, thanks to new platforms as the Intranet, or TalkFreely, People are made more aware and participate more with what is playing on all levels, giving a greater sense of involvement.

Now applying these factors to other offices will be the real challenge due to their cultural differences characteristics.

As a start we have identified several risks and dependencies, not surprisingly related to all the above. I believe that there are certain elements we have looked at, that are not packagable or exportable. Mainly because it is not each element as such, but a complex mix, that delivers such an effective outcome. Fine-tuning that mix or modifying it to fit the cultural and organisational characteristics of each office might make exporting our local setup completely unnecessary. If, on the contrary we try to apply this as-is, we might be running into brick walls wherever we go.

The project is still in its initial phase; we are meeting people and will start auditing other teams and other locations soon. I will write about our progress here, as I believe this is or can turn out to be a very interesting challenge.



Possibly Related:

Service: A Navy SEAL at WarService: A Navy SEAL at WarNavy SEAL Marcus Luttrell returned from his star-crossed mission in Afghanistan with his bones shattered and his heart broken. So many had given their... Read More >

Technorati Tags:

One of the main objectives of the team I work in is to run a continuous improvement(CI) plan. In the past, we have seen many ideas, systems and projects pass by. These usually failed due to a couple of reasons. The main reason is that this is often seen as a short-term project, and it does not get the follow-up attention it requires (or actually makes it continuous). I believe this happens because CI is often assigned to a manager as an objective for a specific period of time. Another reason for failure is that CI is something that needs to be embedded in the work-life of every employee to be successful, but it is usually owned and executed by management.

The way we are now working with CI prevents this from happening by involving all the staff in the project. Several changes have been made in the organisation to enable this and to ensure that people can and are getting involved.

The first change has been made in the way people are promoted within the company. In our office, each role has 3 tiers. To change role, or tier, you are required to perform an activity, assigned by our Service Assurance team. These activities are used to give the employee a more broad view of the office and the environment. This is necessary because the it-support staff is usually siloed in projects and or accounts and often don’t see further than that.

On the other side we have opened an Idea Box in Talkfreely (an online  user-feedback tool we use). I know, every company has an idea box. However, we promote it in most communications as the tool for people to suggest improvements instead of the usual “hallway complaining” and submit their ideas. This works as there are always many things to improve, and you need all the (levels of) the staff to pick these up.

Our team, and the company’s CI program is mainly based on the above two inputs. In short:

1. We receive all the ideas, filter them and classify them.

We look at several things, like if it applies company-wide or does it benefit just one team or group…

2. Then we setup an improvement project around an Idea

We use the sharepoint project Tracking template to set-up small project site, define the deliverables and set-up the global project tasks.

3. After that, we pick volunteers who have signed up for an activity.

This is an important step, as we look at the abilities of the applicant, what he or she needs to learn or improve personally.

4. We then manage the volunteers through the activity.

After the selection of a volunteer, we manage them through the project. Depending on the project, the type of work that needs to be done, we manage them differently. However, since empowerment is something that is embraced in our team by our management, we try to cascade this down, and leave as much as possible to the volunteer. Usually underpinned by regular update meetings.

When the improvement has been implemented, giving credit to the person raising the idea and the volunteer running the project this is communicated across the company.

One of the main advantages of the whole system is that it mostly feeds itself. Many Improvement projects fail because of a lack of input, either from the side where new ideas must come in or on the side of finding the right volunteer for the job. Also this system works as a motivator. In our business the job of most people is very monotonous and a change in scenery is often very welcome.



Possibly Related:

Technorati Tags:

Just how does IT spend its time looking after ERP? • The Register.



Possibly Related:

Technorati Tags:

This is a continuing story. Because I was not sure how to reply to the question asked, I did the least effective… I asked my boss. Not my direct report, but his boss.

This caused quite a small storm in Barcelona. (completely unrelated to the devastating effects of wind force 10 this weekend – Pictures here -) the Service Support Manager in question reacted weird. I’m not sure, but to me it looked like he did not really know what to do with my question.

I can imagine partly that that is so (which would not be a big problem to me, as nobody knows everything), However it seemed to me he felt attacked somehow.

The issue is that we currently do not have a Solution Architect and his point was (I guessed) that we don’t want one neither. He did not say it, but I interpreted his way of explaining as: “Get that idea out of your head!”.
When I asked him the initial question, it was more to see if he could maybe help me planning my career path towards such a position and nothing more (I believe carreer management is an important task for a manager?!?).
When he was finishing his wave of discontent he ended by telling me that “this issue is something I will have to raise with the Director!”, making this story… To be continued….



Possibly Related:

Technorati Tags:

Currently as I explained in the past, my role is the one of Technical leader. This, in our company is defined as:

“To identify and exploit opportunities for service improvement within the ISC (our office) environment – both internally and within specific customer accounts. To drive and coordinate initiatives designed to achieve superior levels of service in line with Computacenter’s contractual agreements. To take responsibility for the managing of projects to enable teams to meet & surpass productivity and service standards.”

I received a mail today in which a high positioned manager in my company asked me who in our office acts as a solutions architect.Now the role of Solutions Architect is one I had in the back of my head as a possible next step in my Career. I have never been a person that knows since day one what I want  in the future (being a Gemini in IT), but lately I have been looking into several different career paths ranging from consultancy to Solutions Architect.

When I read that mail this morning, It was the first time the name Solutions Architect role caught my attention. I believe it did not before, due to the enormous amount of job titles available in IT (from which I believe most to be made up by HR staff that was not sure how to classify their staff – Also I sometimes get the feeling that people think that longer job titles are for more important roles, kind of like an extension of their …)

I found that Microsoft offers a Certified Architect (MCA) certification path, which would prepare for this role. On their website they give a good idea what the role consists of(from their point of view):

“Communicate mainly with business owners within a company and with the technical staff that delivers the solution. The projects they work on affect the enterprise and they design the solution to take advantage of the existing assets, integrate them into the existing environment, follow the enterprise architecture, and solve the business problems of the business owner or unit. They are primarily responsible for taking a project through envisioning and design, and are more consultative to the project manager during the development and deployment phases, ensuring the project stays true to the architecture, time-lines, and budgets. If problems occur, they are escalated to the solutions architect.”

This is perfectly in line with my Job Description. Now I am aware of the differences between both definitions, but believe them to be very comparable. (Also the rest of my job description, which I cannot publish because of confidentiality) looks very similar.

The next days Ill be looking into this, and mostly on how I can now direct my role to that of a Solutions Architect.



Possibly Related:

Technorati Tags:

Page optimized by WP Minify WordPress Plugin