EENY, MEENY, MINY, MOE: CHOOSING A PROJECT

MUSEUM PLANNING AND MANAGEMENT
September 25, 2017

BY: EMILY WELSH

Class Learning:

This week our class found ourselves in the beginning of the initiating phase of project planning and management: how do you select and receive approval for a project?

The CADE method was presented as one template for selecting a good project. The acronym CADE stands for:

Criteria
Assumptions
Data
Evaluation

Teams should begin by laying down the groundwork of the criteria for potential projects. Criteria for projects would include compatibility with institutional mandate, resources required, and time required. Then the assumptions should be stated including the constraints on your project, the perceived needs of the publics, and the availability of resources. To inform the process, data should be collected to illustrate which project types would be best, including conducting or reviewing visitor research, completing competitive analysis, and examining institutional needs or priorities. Finally, groups will evaluate potential projects using qualitative or quantitative methods against the criteria, assumptions and data they have just compiled.

During the class three additional strategies were listed as "Decision Making" methods: 

1. Gap Analysis- "where I am / where do I want to be"

In this strategy, project teams should look at their institutions and critically reflect on where they currently are in their missions and where they hope to be. From this reflection, projects may arise that facilitate the journey.

2. Brainstorming

This method is used to create a vast number of project ideas in a quick fashion. However I was intrigued to learn that we often use the brainstorming process incorrectly. In its true form, brainstorming consists of two phases. In the first, project ideas are presented without any discussion on their feasibility or value. If instead the discussion leads to elaborating on one idea, the proposal of alternative ideas is impeded and we lose the opportunity of seeing bad ideas to inform improvements to better ones. The second phase would be where a team debates the merits of the project ideas presented.

3. SWOT Analysis

A SWOT analysis allows a team to take one candidate idea and compete a situational investigation of its feasibility. A team could use this method to compare a couple ideas, but it cannot be used for more than a couple, as the amount of work required would negate the benefit of the tool.

SWOT is an acronym which stands for:

Strengths
Weaknesses
Opportunities
Threats

A SWOT analysis is a useful tool for not only determining if a project is a meaningful one for your institution, but also provides you with a justification to those who need to approve your selection. Source.

I had learned a little about the SWOT analysis in a previous course but we used it as a more qualitative, brainstorming tool to look at an institution and its competitive environment. What I did not realize was that the analysis could be a quantitative tool for examining the feasibility and merit of a project. First you create criteria that would be used to evaluate your project and assign percentage values to them based on important they are to the project. Next, values between 1 and 10 are assigned to each criterion based on how well your project idea fits it. Multiplying the two values gives you scores for the criteria and allows you to enter criteria into the strengths and weaknesses sections of your charts.

To fill the other two squares, you need to create a list of opportunities and risks that are represented by or face the project. These must be external influences or factors. Your internal qualities and factors are represented in your strengths and weaknesses. For risk in particular, this too is a quantitative assignment with risks being evaluated for importance by multiplying values of likelihood and impact. Only risks of above a certain level will be considered threats.

Personally I think it helps to put these multiple strategies in a more coherent sequence by incorporating these three methods into the CADE structure and adding another letter. My model would be CADGE:

Criteria
Assumptions
Data
Generation
Evaluation

Just like CADE, teams would determine the criteria and assumptions for their project and compile data that informs which project are most needed. The Gap Analysis method would be incorporated into the Data section. Once these items are completed, the team needs to generate a series of project ideas. This could be done in different ways but I think inserting the brainstorming method here would be a valuable step; using the information previously compiled, a series of informed ideas could be generated. Narrowing this list down to one or two ideas, the team would then move on to the evaluation stage where a SWOT analysis would be completed to test the feasibility and highlight the potential problems in the project(s).     

So you have a good idea.....now what?

A key part for receiving approval for your project is the value or return on investment for the project and its deliverables. This consideration of value also plays a role when you think about which projects might be worthwhile completing and thus selecting. Value here does not merely mean monetary value. For museums, their visions & missions drive institutional activities which do not focus on making large profits. For some projects, such as exhibitions, revenue would be considered a valuable outcome as museums do need to make money to pay their expenses and stay afloat. However, value may also come from the impacts of the project's deliverables on the public, including affective learning, cognitive learning, the development of community partnerships and giving voices to the communities. 

Is your project valuable? Remember for institutions such as museums value does not necessarily mean profit! What kinds of value can you think of? Source.

To have your project approved you will need to complete a project charter. This is a written document that outlines the various information of the project including project name, team members, objective, vision, funding, budget, deliverables, risks and assumptions. A major part of this document is the rationale or "business case" in which you will need to describe the value of this project.

Not only is this document important for receiving institutional approval, its is crucial to the success of your team. Without a clear understanding of the project, its risks, needs, and description, I do not believe you will have the clarity needed for your team to move forward in a timely fashion. Without a clear rationale and understanding of value, you may also not have the complete buy-in of your team to see this project through to completion.

Reading Insight:

The reading I would like to highlight this week is "Prove Your Project is Worth Your Time." This is Step Two in Russell's book 10 Steps to Successful Project Management.  

Russell brings up the importance of consulting with stakeholders when determining a project's objectives. Without this step you will "begin building the project that you think the stakeholders want, instead of the project they do want" (Russell, 2007, p. 42). As the author explains, it is the stakeholders that will decide whether your project is successful or not. Although the author speaks from a business perspective, this holds true for museums; your visitors, communities, and board of directors among other stakeholders will judge your project, whether they understand or have knowledge of your objectives or not. Since museums lay out missions that serve their publics, they should consult with them and analyze their needs when determining which projects are needed or take advantage of worthy opportunities.


Until next time I will leave you with this quote from the opening page of the chapter that highlights the importance of documenting and communicating your project:

"You see, if people don't clearly understand what a project will deliver,
they'll always be disappointed with what it does deliver" (Russell, 2007, p. 31). 

Happy planning! 

Resources: 

Russell, L. (2007). Step two: prove your project is worth your time.” In 10 steps to successful project management (pp. 31-44). Alexandria, VA: American Society for Training and Development, dba Association for Talent Development.  

OH SO MANY DEFINITIONS: WEEK 1 & 2

MUSEUM PLANNING AND MANAGEMENT
SEPTEMBER 18, 2017

BY: EMILY WELSH

Hello! Source.
Hello there!

Welcome to the first post in my journal for Museum Planning and Management, a course offered as part of the Master of Museum Studies program at the Faculty of Information, University of Toronto. I have decided to complete this assignment in an online blog where I can share my musings in a fun and creative way. In this journal I will share my learning from classes, thoughts on the topics, questions I am left with and insight I gain from a required reading. Feel free to leave me a question or remark in the comments! I would love to hear your insights on project management in the cultural sector!

Class Learning: 

These first two classes have acted as a great introduction to the concepts, and specifically the definitions, surrounding museum planning and project management. To begin, it's best to define a project. Although many of the attributes we discussed in class are quite useful in clarifying what a project actually is, I think the simple three part definition will probably stick with me the most:

Project = objective + interrelated tasks + resources 

Within 'interrelated tasks' I like to include the necessary component of time. Keep in mind a project is a temporary effort and has a start and end date. This is one of the attributes separating a project from a process (an activity that occurs day-to-day).  

However this definition brings up the term 'objective' which likewise needs to be defined and separated from an 'outcome' and a 'output'. An objective accompanies a verb and is the purpose for which you are undertaking this project. An output (or deliverable) is the product of your project. Finally, an outcome is the value your outputs have to your stakeholders. Take for example an exhibition project for a temporary show on Canada's National Parks. My objective for the project would be to create a temporary exhibit. My output would be that exhibit. Some of my outcomes may be increasing visitor knowledge of Canada's National Parks, bringing in revenue for the museum, or inspiring visitors to explore the nature around them. 

I think it was very important to learn these definitions as a class and have a clear sense of what the words mean. This exercise would be helpful in an institutional setting as well so as to ensure everyone on the project understands each other and what is required or hoped for with the project. 

Define your terms! Then you and your colleagues can move forward on common ground. Source.
 
Reading Insight: 

The required reading from Week 2 I would like to highlight here is Robert LaMarre's "Effective Exhibtion Project Management." This is Chapter 22 of Barry Lord's and Maria Piacente's book, Manual of Museum Exhibitions. 

This chapter gave me an excellent introduction to project management including discussions of the purpose of project management, attributes & roles of a project manager and three essential project management tools. I am sure I will come back to this chapter time and time again for guidance.

One of my favourite points by LaMarre was regarding the breakdown of the project into smaller and smaller groupings of tasks. Breaking a project down like this is necessary so that you can understand what needs to be completed, and in what order, to allow for the project to reach completion (on budget and on time). However as LaMarre rightly points out, a project manager, in a museum anyways, needs to know when to stop managing, otherwise the management process becomes overwhelming and cumbersome if you need to structure, oversee or receive reports on every little thing. I also think its an important skill to know when to stop managing because it allows the team members working on your project the room to do what they do best. These team members are experts in their roles and know what is needed of them. Micromanaging can only lead to disastrous results and lack of buy-in to your project.

In the class today the project breakdown was likened to Russian Stacking dolls. I thought this was a clever metaphor! Indeed, within a project their are groupings of tasks which can be broken down into smaller and smaller groups, just as a smaller doll sits within a larger one. I think then you could liken the project manager to the doll maker - when does the doll maker stop making smaller dolls?     

Russian Stacking dolls. A clever way to visualize the breakdown of tasks that sit within a larger project. Source.
  
 Questions Remain: 

 In the final part of class we discussed the stages of a project life cycle: initiating, planning, performing and closing. A useful graph illustrated the effort required in each stage with the stages progressing over time. We looked at the type of tasks situated within each stage but due to time our discussion was mainly limited to general descriptions of tasks required for any project (e.g. initiating - create a project charter, planning - developing a baseline plan and what to put in it). I am looking forward to reading some of David Dean's Museum Exhibition: Theory and Practice to learn more of the specifics related to museum projects, specifically developing exhibitions. I also left the class wondering how much time these stages actually take. From what I understand so far, the planning stage would involve looking at your end date and working backwards to set goals for the other stages. But how much times do you give yourself for each stage? Do I need a month? Two months? How does this vary for a year vs. multi-year long project? What about different types of projects? I am sure much of this knowledge must come with practical experience but I also look forward to looking for information on how other professionals have tackled their projects and what they found they needed in terms of time. This information may come from Youtube videos of professionals speaking about their projects at conferences. Below is one I found quite interesting from today's class; we watched a portion of the discussion regarding the collections management move and inventorying project.


 Until next week I will leave you with my favourite quote from LaMarre (2014, p. 382) regarding project management:


“It is never too late to begin, as the process itself adds only a layer of order to any stage and at all stages.” 

 Happy planning!

Resources: 

LaMarre, R. (2014). Effective exhibition project management. In Lord, B. & M. Piacente (Eds.), Manual of museum exhibitions (pp. 379–391). Lanham, MD: Rowman & Littlefield.