A resource allocation mistake from Louis Van Gaal?

Yesterday, before they were defeated by Leicester, the Man United manager said that he would get rid of players who stayed on the bench too long. What he meant was if they didn’t make it into the first team, he would get rid of them. At least, that was my interpretation.

van-gall

As a project manager, I thought this raised some interesting issues:

  1. Why buy players – resources – that you’re not sure are up to the mark. Surely you need to do some due diligence first?
  2. As the players have no control of their playing time, why put them on the bench if you don’t intend to play them? Again, this seems a strange way to motivate players, ie employees, who have no direct control of their future. It creates a Catch 22. If they are not playing, how can they prove their worth?
  3. How long is too long? One of the difficulties of motivating teams is that unless there is a very specific time frame, well, things lose focus. What is too long in this case? A month, two months? Maybe he has told the players in private, maybe not, which of course, could be another way to create tension and possibly more efforts from under-performing players.

Let’s go back to the original point: churn.

As a project manager, or a small business owner, you only have limited resources. You can’t always afford to churn resources. It’s expensive, time consuming, and doesn’t guarantee any improvement.

The new resources could be worse than the current ones.

So, what to do?

Personally, I try to:

  • Look at what’s worked in the past, really worked.
  • Ignore current trends, fashions, and fads.
  • Create very specific aims. For example, right now, I want to create more video content. It’s related to a specific goal I have for mobile technologies.

Is Van Gaal doing the right thing?

I suspect he’s trying to do many things at the same time, and under pressure to deliver results almost immediately. This creates a frenzy of energy. Some will work, others not.

Churning people feels wrong. Maybe it’s a language thing I suspect that if people feel they are no more than objects that can be churned on a weekly basis, well, the results will reflect this.

PS: An alternative approach from Gen Schwarzkopf

Thousands of templates to jump start your project

Acceptance Test Plan

Contingency Plan

Software Development Templates

Acquisition Plan

Conversion Plan

Software Requirements Specification

Action Plan

Cost Benefit Analysis

Software Testing

API Documentation

Database Design

Standard Operating Procedures (SOP)

Audience Analysis

Datasheet

Statement of Work

Availability Plan

Deployment Plan

System Administration Guide

Bill of Materials

Design Document

System Boundary

Business Case

Disaster Recovery Plan

System Design Document

Business Continuity

Disposition Plan

System Specifications

Business Plan

Documentation Plan

Technical Writing Templates

Business Process

Employee Handbook

Test Plan

Business Requirements

Error Message Guide

Training Plan

Business Rules

Expression of Interest

Transition Plan

Capacity Plan

Fact Sheet

Troubleshooting Guide

Case Study

Feasibility Study

Use Case

Change Management Plan

Functional Requirements

User Guide

Communication Plan

Grant Proposal

Verification and Validation Plan

Concept of Operations

Implementation Plan

White Papers

Concept Proposal

Installation Plan

Work Instructions

Configuration Management Plan

Interface Control Document

Software Development Templates

Acceptance Test Plan

Maintenance Plan

Software Requirements Specification

Acquisition Plan

Market Research

Software Testing

Action Plan

Marketing Plan

Standard Operating Procedures (SOP)

API Documentation

Needs Statement

Statement of Work

Audience Analysis

Operations Guide

System Administration Guide

Availability Plan

Policy Manual

System Boundary

Bill of Materials

Project Plan

System Design Document

Business Case

Proposal Manager Templates

System Specifications

Business Continuity

Proposal Template

Technical Writing Templates

Business Plan

Quality Assurance Plan

Test Plan

Business Process

Release Notes

Training Plan

Business Requirements

Request for Proposal

Transition Plan

Business Rules

Risk Management Plan

Troubleshooting Guide

Capacity Plan

Scope of Work

Use Case

Case Study

Security Plan

User Guide

Change Management Plan

Service Level Agreement (SLA)

Verification and Validation Plan

Communication Plan

Setup Guide

White Papers

Concept of Operations

Social Media Policy

Work Instructions

Concept Proposal

Contingency Plan

 

Configuration Management Plan

Conversion Plan

 

 

Want More Writing Tactics?

Over 127,000 readers rely on Klariti every month. Sign up now for Ivan’s fresh writing strategies, practical advice, and resources delivered to your inbox each week.