By Ramiro Rodrigues
A great deal of effort is often put into a project kick-off meeting—so why isn’t that visibility just as important on the other end of the project?
What is a project closing party?
A project closing party is an event that intends to provide visibility and recognition to the main professionals involved in a completed project. Obviously, there is no sense in celebrating a project that got aborted or that didn’t reach its main goals and targets. So, we are talking about those projects that managed to get to end with the best combination of its intended results.
Within this proposal, it is reasonable to say that what will drive the size of the closing event will be the size (and budget) of the specific project, since it is necessary to achieve coherence between these variables.
What are the benefits?
I see two arguments for hosting these events at the end of a project—one strategic and one motivational.
On the strategic side, a closing party brings visibility to the executing organization (and, if applicable, the hiring organization) that the project has reached its predicted goals. It will help to reinforce to those at the strategic level of the organization that the team is capable and reliable.
From a motivational standpoint, these events will help recognize the efforts of the project team.
How should they be executed?
If you think a closing event could benefit your project efforts, here are some tips to abide by:
Done well, events like a project closing party can have positive repercussions on your next projects.
Do you regularly host or attend closing events at the end of your projects? I’d love to hear your thoughts!
by Ramiro Rodrigues
Project managers: Are you sometimes looking to make plans faster but without being superficial and therefore riskier to the project?
Developed in the 1980s, design thinking is a structured mental model that seeks the identification of innovative solutions to complex problems. Although the concept has existed for decades, it’s only made its presence known in the corporate environment over the last 10 years.
Swiss business theorist and author Alexander Osterwalder similarly sought to accelerate collaborative reasoning when he introduced the Business Model Canvas. Canvas helps organizations map, discuss, rework and innovate their business model in one image.
But a series of proposals for the use of the Business Model Canvas for various purposes outside of business models has also appeared — including innovation, corporate education, product development, marketing and more.
For project professionals looking at alternatives to developing quicker and more collaborative planning, Canvas may sound like a great option. Of all the proposals that come up for the use of Canvas in a project environment, integrating stakeholders may be the best. Canvas brings stakeholders into the process and will help to minimize resistance and increase collaboration, resulting in a better proposal for planning problems and making the project more aligned to the interests of organizations.
But while the arguments put forward for Canvas all seem positive, there is still a dilemma: Can Canvas fully replace the overall project plan and the planning process? Is it possible to do without a schedule of activities, a detailed cash flow, a matrix of analyzed risks — just to limit ourselves to a few examples?
That is probably too extreme.
The general sense is that the integration of Canvas with specific planning — such as the cost plan and the risk plan — is the most productive and generates the best results.
It may be worth asking your project management office for their thoughts.
Have you ever used a Canvas for your project planning efforts? If so, what tips can you share?
By Ramiro Rodrigues
Among consultancies it’s common to reward project teams for good results with financial incentives.
The question is: Does this practice lead to better results? There’s a clear difference in position depending on which side the respondents are on. The dilemma is easy to understand.
When you’re in the position to be rewarded for the results achieved, it’s natural to see the positive side of this approach. But when you are responsible for delivering the bonus, some doubt will naturally exist. After all, what guarantees that this strategy will lead to projects with better results (regarding time, cost or quality)?
Many feel these rewards act as great incentives for project teams, thus leading to better performance. But one should also consider the concerns of those who fear that, in the name of this search for metrics, some values—such as professional ethics, transparency and lawfulness—may be compromised.
To find out if the bonus strategy should be implemented at your organization, have a look at the following four steps:
Step 1: Evaluate your organization's values.
More aggressive companies that encourage internal competition tend to favor this strategy. Knowing your organizational environment well will help you determine whether to adopt the financial incentive strategy or not.
Step 2: Define quality metrics.
Interpreting success only by the results related to project time or costs may lead to short-sightedness regarding customer satisfaction. Therefore, develop templates for satisfaction surveys that can help measure the quality of the delivered product and the opinion of the customer who receives the final result.
Step 3: Encourage mutual collaboration.
Dividing the bonus between specific members or projects creates a great risk of dissatisfaction among those who have been excluded. Thus, sharing the bonus between all team members, depending on the results of the overall project portfolio of the organization, is an interesting idea to consider.
Step 4: Start slowly and measure results.
Treat the implementation of this assessment as a project and aim to progress gradually, so that you can evaluate any impacts of this strategy on the culture and value perception of your company.
Good luck and much success!
by Dave Wakeman
I recently came across some of management guru Peter Drucker’s thoughts on project management.
As often happens with Drucker’s writing, the lessons he wrote about many years ago are still applicable today.
In his thinking about project management, Drucker came up with the idea that it really came down to three ideas: objectives, measurements and results.
Let’s take each of these areas and think about how we should approach them today.
Objectives: Many projects get stuck before they even begin, due to a poor framing of the project’s objectives. We should be undertaking our projects only when we have moved through the project-planning phase to such an extent that we have a strong grasp of what we are hoping to achieve.
These objectives shouldn’t be fuzzy or wishy-washy. They should be solid and rooted in the overall strategy of the organization you are performing the project for.
This means you have to ask the question: “Does this project move us toward our goals?”
If the answer is “yes,” it’s likely a project that should be launched.
If the answer is “no,” it’s likely a project that needs to be fleshed out more, rethought or not undertaken at all.
Measurements: Drucker is famous for this adage: What gets measured gets managed.
In thinking about project management, measurements aren’t just about being able to improve project delivery. They’re also essential to ensure the project is headed in the right direction.
To effectively measure our projects, we need to have laid out key measurements alongside the project’s objectives.
The measurements should be specific, with expected outputs and completion dates, so you can affirm whether you are on schedule, behind schedule or ahead of schedule.
At the same time, the measurements should inform you of your progress as it compares to your strategic goals.
Results: Ultimately, projects are about results.
To paraphrase another great thinker, Nick Saban: If you focus on doing your job right on each play, you’ll put yourself in a position to be successful at achieving your goals.
Saban coaches U.S. football, but this works just as well for all of us in project management.
If we are focusing our energy on tying our projects to our organization’s strategy, through this strategy we focus our project efforts on the correct objectives in line with our strategy. Then we use those objectives to measure our progress against the strategy. We should be putting ourselves in a position to get the results that we need from our projects.
These results should be measured as positive outcomes. In Saban’s case, that’s wins. In your case, it might be a new technology solution, a successful new ad campaign or a profitable fundraising effort.
To me, reviewing Drucker’s thoughts on project management is a reminder: Even though there is a constant pull of new technologies, never-ending demands on our attention and a world where change feels accelerated, sometimes the best course of action is to step back, slow down and get back to the basics.
Keep These 3 Priorities In Focus
by Dave Wakeman
In today’s project environment, it can be difficult for project managers to know where they should—or shouldn’t—focus their time and energy. Stakeholders, team members, and sponsors, all with their own agendas, pull project managers in different directions.
That said, I think all project managers can gain a great deal by focusing on the following:
1. Opportunities within the project. I’ve never seen a project that’s set in stone. In truth, almost every project I’ve worked on has changed so much throughout the course of its existence that it often becomes unidentifiable with the initial scope.
This can be frustrating, but to maximize your success as a project manager, you should embrace the change process because it allows you to search for and capture opportunities that will enable you to have the highest impact.
Think about this simplified example: Let’s say you are working on a web project. The scope of the project calls for you to build a responsive website that can handle a certain amount of traffic, and you have three months to do it. That’s pretty clear-cut, right?
It is. And, you could definitely go right through the project and deliver. But what if you discovered a more cost-effective way to host the site with a better load speed? Wouldn’t that be identifying an opportunity and creating a better outcome for you, your team and your client?
2. Development of your team. One challenge we often face is resource uncertainty. Essentially, will our human capital sufficiently meet the project’s demands?
This is an ongoing challenge in many organizations. Staff members are often overburdened, and they’re not always up to speed on the newest ideas, techniques, and tools.
To maximize your impact, it pays to spend time thinking about and developing your team. Consider ways you can help build up your team’s skills in a way that will make your life as the project manager easier. It may be as simple as identifying a skill crucial to your project and providing some type of consistent coaching, information or feedback each week that helps improve that specific area.
3. Testing as you work your way through a project. Does this part work the way it should? Did that segment of the project produce the outcome we needed? Are people reacting the way we thought they would or should?
Pay attention to each step in the project and spend time testing your assumptions and your results against the work produced. It’ll pay off in the end.
In some cases, things will work out exactly how you thought they would. But in the cases where that doesn’t happen, testing can be the difference between the success and failure of your project.
Is there anything else you consistently remain focused on during your projects?