How useful is a framework? And other thoughts at Project Management training

Photo by Andrew Hefter

Photo by Andrew Hefter

A couple of weeks ago, Colman and I went to project management training (something I always dreamed of as a little girl). The Institute of Project Management Ireland ran the 2 day course and, with the exception of the copious Liverpool football metaphors, it was helpful. The basic message was: people are difficult; we shouldn’t complain because otherwise software could do our jobs. But there was something else.

Charts, empty

The instructor gave us, and frequently referred to, this chart:

project-management-graph

It was supposed to sketch how a project is run: initiate, then plan and execute at roughly the same time, monitor throughout, then close out. Now if any project anywhere in the world has actually been run according to that chart, then I’ll eat it. What if initiation trumps the whole planning phase? What if you’re short resources and there’s no time for a close out? And so on.

“Reach for the stars,” i.e. unrealistic goals

Was that chart useless? It depends. I’m sure it’s good to have on the wall to remind yourself to check in on your team (perhaps). But how useful is something so hypothetical that it ceases to be true? Goose has a good article, albeit on an entirely different topic, almost saying the same thing: generalities are useless. The specifics of a project changes the framework.

Wireframes, empty

I liken this to wireframes, with which, as a content person, I have a love-hate relationship. Rahel Bailie, founder of Intentional Design Inc, sums it up nicely:

“Organizations invest tremendous resources on developing the framework for a great user experience — fabulous design, robust content management infastructure. Yet when it comes to the content itself, there’s often a gap. The end result is that the value proposition for customers can’t be delivered because the content is insufficient, inadequate and inappropriate.”

(I got that quote from Rachel Lovinger’s and Karen McGrane’s presentation about content).

“The play’s the thing . . .

Details are more important than frameworks. Case studies are more important than outlines. What is messy probably gives the best result. Does that mean we should get rid of charts and wireframes? No. But it means we should change what accompanies them:

  • Put some content in your wireframes
  • Map a real project with real details

Details move things beyond the hypothetical. Maybe this won’t make me the best project manager. Or maybe it will . . .

Speaking of content, there’s one spot left at Elizabeth’s and my workshop next week at the Content Strategy Forum in Paris. You can last minute register here.

Categories Content, Design