Search This Blog

Showing posts with label project communications. Show all posts
Showing posts with label project communications. Show all posts

30 September 2015

Name Your Files for the Readers — If You Care

Filenames — A Trivial Time-waster that Adds Up

How do you react when you see a filename like 500002p.pdf? 

Is this a file that you want to open? 

Do you think that the author of the file cares whether you open it? 

This one's a little better, but not much:  BBP3.0FactSheetFINAL.pdf.

What Do You Want to Know?

When I look at a filename, the first thing I want to know is what it is. After that, I want version information. 

Some people put their initials first.  In a team folder, the listing will group the Jim files, then the Joe files, then the John files, and so on.  (And then there's Jack who sometimes uses JB and sometimes JEB.)

Then you have to search up and down the screen to find all the versions of the same file.  The larger the team and the longer the project goes on, the more this wastes time and leads to mistakenly working with outdated versions.

A government website has a folder of presentation files in this format:  

2014_05_15-Draper-6th-AGNC-Welby-final.pdf

Placing the date first is redundant because you could always sort by date in the file explorer view.  Apparently, the Welby made the presentation and worked for Draper, and the topic was some cryptic initialism.  Now, how are we supposed to find presentations on risk management among 74 files with names like that?  Do you have an hour to spend opening all those files?  

There's another human element. When a filename starts with initials or has a serial number instead of a name, my eye says, "random, meaningless letters." Then my amygdala says, "look away!" 

Sometimes my amygdala wins, and sometimes my cerebral cortex wins. That contest creates stress. wastes time, and sometimes blocks communication completely. 

If you have a Content Management System (CMS) or Configuration Management System (also CMS) such as SharePoint, you have ways around this.  You can add fields for author, date, version, and subject.  

Often, however, we are stuck with filenames.  Even if your team has a CMS, you will still sometimes wish to download a file to your own drive.  If you don't remember what's in that cryptically named file three months from now, will you even bother to open it?

Since I read from left to right, and since an alphabetical sort proceeds from left to right, I recommend the following name format:

topic - [rev or yyyy-mm-dd [24-hour time if needed] ] - initials

example

meeting notes, team, 2015-08-01, rev A, rw.docx

Filenames should be in plain English. 

When I download files, I hate seeing files with names like BB097834.pdf.  I should not have to download and open a file in order to determine whether I want to download and open it. 

And by the way, who is JS, and does he or she even work here any more?  Does it feel professionalI to use your initials?  How professional will it seem to others, two years after you've taken that big promotion at another company and nobody here remembers whom JS was? Spell things out.

Some content management systems assign garbage names automatically.  We cannot do anything about that.  And some authors write only for their own vanity.  They do not care whether anybody reads what they wrote.  Try not to obsess over it; I've already done that for you.

A filename is like a headline or the title of an opus.  

A good author or editor knows that Job One is attracting an audience and, therefore, puts a lot of effort into creating a meaningful, eye-catching filename. Which would the classical music lover in your life rather listen to?
  • PITop066.mp3
or
  • Sleeping Beauty, Peter Ilyich Tchaikovsky, opus 66.mp3

It's about more than efficiency. It's about consideration.


Copyright 2015 Richard Wheeler

24 March 2013

Project Management and Open Communications

Project Managers need to guard against setting up an environment where bad news never reaches them. They need to praise and encourage those who communicate risks before they become issues, issues before they become problems, and problems before they become project failures.

Some managers remind me of the Clinton trial in the Senate, following his impeachment in the House.

The Senate set up a rule requiring Ken Starr to keep all the records and evidence in another building. Bringing it to their offices without an invitation would have violated protocol.

Then the majority of senators refused to go view the evidence. A few who did view it said they came away weeping, and the rest (having refused to view the evidence) said that they lacked evidence sufficient to convict.

Does your comfort zone tempt you to maintain willful ignorance? Does your character allow reliance on plausible deniability? The PM has accountability for project success, which any lack of awareness may bring about; but that accountability extends to achieving success ethically.
 
I wonder:  Do PMs ever include ethical lapses as project risks?

06 March 2013

The Lobbyist on the Project Management Team

You are the project manager in an aircraft manufacturing company developing a new range of supersonic fighter planes. Since government approval and involvement are essential, you hire a lobbying firm to get government support to prevent unnecessary changes in your project. Which process is this an example of? (Source unknown)
While aircraft manufacturers conduct some research into designs and materials that they can incorporate into new aircraft, governments usually sponsor development of fighter jets.
 
Scope creep happens in almost all defense projects.
 
For example: 
  • The Defense Department wants the aircraft to provide certain capabilities for the Air Force.
  • Then the Navy wants compromises in the design so the jets can take off from carriers.
  • The Army and Marines add their particular use cases.
  • Allies want introperability with their systems.
  • Later, one politician wants to cut costs,
  • another wants the aircraft to use inadequate landing gear designed by the manufacturer in his home town,
  • and over 600 politicians and thousands of bureacrats want to influence the project.
  • Meanwhile, competitors and the nation's adversaries develop new technologies to which the designers must respond.
  • And one of the political parties, along with the press, begin mocking your aircraft by calling it an Imperial Tie Fighter.
If you let it, the politics will multiply the cost twentyfold, drag out the schedule an extra 15 years, and make your company a laughingstock. By the time of the first production run, the aircraft will already be obsolete.
 
The same sort of changes can happen in any project. One way to control the risk of scope change is to refuse to make changes, but too little flexibility can create customer dissatifaction and cost you future business.
 
For a better way to reduce the risk of scope creep, maintain close personal relationships with the stakeholders, keep them informed of the costs of changes, and negotiate agreements that best serve the business case.
 
The PM cannot always do this, so the company hires a lobbyist with exceptional people skills and knowledge of the bureacratic systems. The lobbyist uses various methods to convince the politicians and bureaucrats to resist tinkering with the project requirements.
 
In process terms, hiring a lobbyist does not proceed from the Project Communications Management processes. Lobbying does not contribute directly to producing the product or providing a service. A first pass through the Identify Stakeholders and Plan Communications processes would assume everything goes as planned and would focus on required reporting and coordination. The lobbyist's job goes far beyond that.
 
If the team identifies scope creep as a risk, they make a note to consider it later when they follow the Identify Risks process. They would, at that time, add recruiting a lobbyist to the Risk Management Plan portion of the integrated Project Management Plan.
 
Don't forget that, as a member of the project team, the lobbyist becomes a stakeholder. For example, the team must add the lobbyist's tasks to the WBS and estimated costs during the next iteration of project planning. They must also consider the lobbyist's information needs during the next iteration of the Project Communications Management processes.