Management Nugget No 21: Do not delegate the small stuff.

This is something that I personally find drives me crackers, and has done all the way through my professional career, it is also one of the golden rules that I apply now that I spend more time doing management stuff than I do doing technical or support stuff. It is to not inappropriately delegate. What do I mean by inappropriate? In this case, I mean to delegate items that do not have clear owners and therefore, often, managers delegate to anybody they can find rather than just doing it them selves. The worst case for this is to delegate administration tasks to subject matter experts. The classical one is, if you are running a project and you are running a lot of meetings within that project, but have no project office member, or scrum master or general admin, you ask technical specialists or Business Analysts to do admin tasks such as minute the meeting or raise requests Unless there is a hard dependency on a skill set they use, do not waste the time of specialists on such things. I personally believe all minor admin actions fail back on the project manager in the absence of anyone else. If you feel that you are ill equipped to do such administration items because you do not understand the subject matter. For example, to raise a ticket that you don’t know the process for or that requires complex technical details to fill in, you initially take it as your job. Then you ask one of your fellow managers to assist, to see if they can help you. If that fails, then you go and ask one of the subject matter experts if they can guide you through the process the first time so you can learn. In summary, if in doubt, all boring and dirty jobs become the project managers responsibility. Disclaimer: As always these posts are not aimed at anyone client or employer and are just my personal observations over a lifetime of dealing with both management and frontline associates.

Calculating the price of collaboration

As most companies and corporations start pushing everybody slowly back to the office full time 1. It turns out that there are a couple of hidden and not so hidden costs to this, and moreover, they only effect those that are good at remote working.

1)

If you are an efficient remote worker, you plan your days out, and tend to actually commit the same amount of hours to your day working from home as you would for a full office trip.
To explain that better. Once I have my shirt and tie on, I am in work mode. If I’m in my home office, that means I can use that time for calls, emails or genuine work. From my client office, however, that means I waste the first and last 30 to 90 minutes of that day travelling. 2

On a number of international projects I have been a member of, it has reached the level requiring H.R. involvement for permanent members of staff, as meetings that have been going on successfully for years at the very beginning and end of the day due to time zones, suddenly have terrible attendance because people are travelling during those times.

2)

A far more insidious impact, and one that both helps and harms the delivery of work for corporations but requires a long term view , is the time taken to actually socially collaborate with your fellow office drones.

If I go into an office with a clear list of things I’m going to do and how long I will take to do them, i will have to add about 2 hours to that estimated time because I’m sharing a work place with fellow humans not just loud motivational music.

And if you only think like that, for a full week in the office, I would loose 10 hours worth of delivery just being a paid up member of the human race 3.

But then it starts to get complicated. Sometimes, a quick face to face conversation solves hours of meetings and emails, an over heard chat 2 desks down stops you making a costly blunder or makes you aware of something.

All this variance means that there is no clear absolute winner for the move back to the office and no one size fits all. But the points I take away having to manage it for both clients and team members are:

  • Full time in the office hurts the productivity of efficient or hard working people, give the people that plan their days out at least 1 day a week to get their head down and clear backlogs.
  • Measuring improvement based on being back in the office is a long term game, as in the short term there is often a drop on what people actually get done.
  • Much as it is irritating to some team members, if you have made them come in, then make them sit together as if they all go an hide in little booths and corners you have just made the whole thing pointless. If they state they need that space then let them work from home and move to a more delivery focused measurement of work to try and evaluate that.
  • Realize that people are different and just because you as a manager like everyone sitting around you, does not mean that others do and are more productive that way, you are not helping yourself by pulling such people in.
  1. .Denials from the powers that this is not the case are not fooling anyone[]
  2. with a bit of emailing done on my mobile.[]
  3. .ignoring the lost hours due to travelling from point one[]

Corporate term: “Drain the slide”

Definition:

This is the act when giving a presentation of merely reading the slide out verbatim, normally in a flat tone, as if you are just saving the other attendees from actually reading it themselves without bringing anything else to the presentation.

Explanation:

This is caused by people not knowing how to present their slide deck and so just reading from it. If you have been asked to present a slide deck, use your slides as speaker notes rather than a script, add some feeling to them, so you do not bore the hell out of everybody.
If people you know ‘drain the slide’ and just read out everything verbatim. Suggest they get involved in any form of community event. Be it business or technical and start to present on their speciality subject, the feedback and experience from actually doing proper presentations will cure this problem quickly.

Disclaimer: As always these posts are not aimed at anyone client or employer and are just my personal observations over a lifetime of dealing with both management and frontline associates.

 

White Glove Service

White glove service, is a service offered unofficially within a corporation or large company for items that are classified as important from a business or process point of view, but don’t have a genuine importance from a hardcore finance or business impact.

An example of this would be if you had an issue that would stop a project release to production. This is very important to a project and to the leadership team, but does not result in an immediate financial or regulatory cost to the business. Therefore, you could not merely raise it as a Severity 1 issue, and let the existing incident processes manage it.

These needs however are important, but not in a traditional sense, and you need what is often called a white glove service to deal with them.

What does a white glove service consist of?

A white glove service consists of a number of allocated, named individuals. These then take responsibility for issues, they will own such issues and work with the stakeholders or people that raised them to ensure that they are completed.

At no point until the issue is resolved can they let go of it, even if it’s beyond their control, they have to hold on to it until It’s completed.

  • They do this by ensuring departmental walls are breached to reach a solution.
  • They consistently provide reports to the stakeholders, even if there has been no change to report (often the update period required by a stakeholder is far more frequent than there are updates to provide). Communications, however, must be managed.
  • They must be effectively on support call. There is no clocking in and out if an issue is raised, regardless of when it is, they must respond. (It is recommended that there are at least 2 named individuals for each of the 3 main global time regions. Asia Pacific, Europe, The Americas to cater to this).
  • They must maintain trust between the different areas of the corporation , if such a person comes seeking a teams assistance, it will be for a genuine reason.
  • If the issue is caused by a process or other genuine reason (and not merely poor stakeholder and management planning), they must produce a root cause once it is complete.

Skills needed:

Strong areas of knowledge: it must be at least 2 of the following:

  • Business process knowledge and what is important to the business.
  • I.T. knowledge in order to be able to negotiate with the various silos within the corporation
  • Internal process knowledge, who to go to, where to go to, what processes need to be done in a perfect world,

Things a White Glove service must not do:

  • Use up the time of valuable subject matter experts: they must not occupy more time than they save for existing resources, and should stand in for technical and business people on calls to actively free up time to complete requests.
  • They must never be seen as a threat, only as an assist. They must never use words like escalate or name drop, or anything that triggers a defensive reaction.
  • They must not devalue existing processes and people, to do so will just make the problem worse. They must always be someone who can explain the truth to power.
  • Just become a status report proxy, they do not ask subject matter experts to do any admin tasks, they take on such activities e.g. ticket raising, and allow experts to complete genuine work.

How do you get people to do this pain in the butt role in a corporation:

For External Staff Members: Money normally does it for both independent contractors and vendors; they are happy to do this function and do it well if the price is right.

For Internal Staff Members: A stint on the ‘white glove’ service grants broad understanding of your company’s needs at a practical level and shows commitment, this can be used on yearly evaluations, and helps to identify people who should be fast tracked.

Corporate term: “3 vendors in a trench coat”

Definition:

Three vendors in a trench coat is basically a way of saying that a department or function inside a corporation is merely a front for a bunch of vendors trying to get as much money out of you as possible, rather than being a genuine internal department.

Explanation:

This is a corporate corruption of the classic three raccoons in the trench coat, which basically means a group of slightly deceitful critters pretending to be something greater and better than they are.

In a corporate world with so much outsourcing and so much cost cutting paired with the difficulty in getting and retaining internal resources, often support functions or other areas merely become a thin veneer of managers or permanent members of staff over a huge number of outsourced vendors.

This can mean that simple costs can escalate radically, and even asking for a minor item that should be classed as business as usual, can result in a hefty bill that you are not expecting.

Disclaimer: As always these posts are not aimed at anyone client or employer and are just my personal observations over a lifetime of dealing with both management and frontline associates.