90 Percent

Project management, productivity, change management, and more!

1 Comment

Change: Before, During, After

Source: jscreationzs

Source: jscreationzs

When planning to move forward with a change that will impact your colleagues, it is important to remember that you must manage what comes before the change, during the change, and after the change.


Before you proceed with changing a process, a tool, or anything else, you have to keep in mind that the more informed the others are, the better. In times of change, people need to feel safe in what’s coming and the more unknown their is, the less safe they will feel. Therefore, explain the reasons of the change, the plan, and how they will be supported not only throughout the change, but after.

Make sure people can ask questions or talk to someone to express their concerns or their ideas. How you communicate with colleagues at this stage will give them a first impression on what’s coming, and you want to make sure they have a good first impression in order to reduce resistance.

Another important aspect to plan before the change occur is training the other, and prepare the proper documentation for them (i.e. tutorials). This could range from preparing them on how a new process will work, to teaching them how to use a new tool.


While you are in the midst of your change, this is where many questions will come up since people will start to be actively affected by the change. It’s also when the most frustration or confusion can rise so it’s important to make sure people know they can contact someone who will give them prompt support.

There is also a time where you might need to adjust your change (change the change!). With more people coming onboard, you may find out that there is a flaw in the process that needs to be tweaked, or the tutorial created wasn’t as clear as you thought. Adjust this immediately, people will appreciate that these are being adjusted to accommodate them or improve what is happening.


Once the change is completed, a bad habit is to think it’s all over and you can “let go”. That is far from true. Even with a proper training and several questions answered, people will need a good amount of support for a while, and it’s important to still give prompt support as it happens. Fortunately, as time passes, support needed will reduce.

Lastly, like any project, it is a very good practice to have a lessons learned meeting and assess what to improve for next time. It’s also very important to gather feedback from the others to find out how they thought the experience was and how it could be better.

Leave a comment

Continuous improvement – Part 4 – Tips


Source: ratch0013

In case you missed Part 1Part 2, or Part 3,  don’t forget to read the articles!

To end this 4 part article about Continuous improvement, here are several tips that will help you overcome the challenges that you may meet while trying to bring change in your team or agency:

1. Create a habit out of it

Just like everyone can get stuck in the routine of doing everything the same way all the time, you can create a habit of listing ideas, grabbing feedback, or adjusting/fine-tuning anything you can.

For example, every 3 months you can set yourself a reminder to ask people if they have feedback on a tool, or ideas to improve how everyone uses it. As time goes by, pay attention to the evolution of the feedback as it may change from “Everything is great” to “I found out about a new tool…”.

2. Gain buy-in from managers

If you do not have any power to use resources to make change happen, than sell your ideas to people who do have it. If they agree and make available the necessary resources for the change, then you will obviously have a better chance of making it happen.

To gain buy-in, there are several ways to convince someone:

  • Show the monetary gain of the change;
  • Show how things can go faster;
  • Show how better quality will be produced;
  • At the same time, you can use the current situation and show how slow, inefficient, or low quality things are at the moment;
  • Show people’s feedback;
  • Show are things are being done elsewhere and the result;
  • etc.

3. Accept mistakes

One of the reason we don’t want to tackle change is because we are scared of making mistakes. The thing is, you will learn a lot from your mistakes, and what’s important is to adjust right away when it happens.

If a new process just doesn’t work, either fine-tune it, or go back to what it was. Just don’t let it stop you, learn from it and let it bring you even further.

4. Find others

Usually, you will be able to find others who feel changes needed. Discuss with them, gather their feedback, their ideas, and get them on board to help you bring that change to life.

If you think you are alone thinking things need to change, you are wrong. Although at first it may look like nobody wants things to change, a lot do but are scared or just don’t think they can have an impact. People will join in, and make sure to include them as much as possible throughout the process of the change.

5. Think small / Think big

Changes can be very small and they can also be big. Do not neglect the small changes that can fine-tune your big changes into something even better. Just like sometimes the biggest, toughest changes are the ones that are going to bring the best results.

Vary the sizes of the changes you tackle. Even a small change sometimes keeps you motivated for the next change, just like finishing a small task during your day.

6. Think of others while planning

Unless the change is only going to affect yourself, think of others when planning how the change will impact everyone. The others will make your change live or disappear, if you neglect them, they will surely make your change revert to its original state.

How? Simple, talk to them, ask them what they like, don’t like, what’s their opinion on the path your change has taken, if they agree or disagree, ask them to test whatever your doing, involve them. Avoid doing this behind everyone’s back and then imposing the change suddenly without the proper training/support; your change will surely fail and everyone will just keep doing what they were doing before.

7. Ask these simple questions: “How can we be better?” or “How can this be better?”

The title says it all; just by asking yourself (or others) this question, you can be surprised of how many ideas can come out of it.

Do a brainstorm session and use those questions to start some discussions, and you’ll see there are many ideas that will pop out.

Also, ask these questions even if things are going well; just because a tool is great or a process is going well, doesn’t mean it can’t be even better.

In conclusion

This concludes the 4 part article on continuous improvement, I hope you enjoyed. Do share your ideas or stories of when you brought change within your team.

Where to start?

Leave a comment

Continuous improvement – Part 3 – Where to start?

Where to start?

Source: Stuart Miles

In case you missed Part 1 or Part 2, don’t forget to read the articles!

So you want to tackle continuous improvement, you have many things that could use an efficiency boost, you have people willing to help… So where do you start with all this?

Treat continuous improvement as a project

It’s the same core idea as changing a website, it’s a project! So if you keep this in mind, you will have an easier time figuring this out. Just like you would with your project, start planning.

First you would normally gather your client’s needs. Here, your clients are probably your colleagues, or maybe even just you. You need to gather requirements and create a list of all the ideas to improve anything around you.

To help you, gather feedback and ideas from others, don’t limit yourself to your ideas only. Although I’m sure you have many great ideas, you will find that most ideas you will want (or need) to fight for will come from others.

From there, just like managing a project and it’s many tasks, you have to prioritize, and assign people responsible for those tasks.

This can be tricky if you have no authority or power inside the team. If this is the case, than gaining managers’ buy-in can prove to be very useful. Show them the list you made and explain how it can positively affect the team to improve certain aspects of your daily lives.

This buy-in will help obtain the resources needed to make the improvements.

Once improvements have been clarified and resources are available, set objectives of when they can be done, just like you would when managing your project. Here, you’ll want to create a schedule. Note that it’s not impossible that creating the schedule may come before finding resources, this can actually be a tool to gain buy-in by showing that the change can be done within only one month for example.

By the way, as the work gets done, you will probably have to adjust that schedule too, just like you would a normal project, maybe even more, as mentioned, it will often be pushed aside by other projects that are considered more important, so you have to work around that. It’s nothing new in the project management world, so adapt to the circumstances, do your best, and keep communicating to your team until you are all done.

Also, you can even throw-in some risks management in all this, just like any projects, there can be risks that could be mitigated. For example, the new tool you plan to use could have a similar functionality to the old one but with a very distinct difference that may frustrate your team members; so mitigate the frustration by making sure to point it out in training and showing how to use it differently as opposed to letting them hit the issue and complain.

Making the change is half the work

As you work improving something, one important thing to keep in mind is that releasing a new tool, changing a process, or adjusting anything can be relatively easy; the next big step is maintaining it, which means, plan for what happens after. This includes training team members, giving support to the team who needs to adjust, or even having to make changes to adjust to feedback or issues faced.

The change/improvement cannot be simply “released” hoping that everything will go perfectly, it must be supported and maintained just like you would a mobile application for example, and you need to “fix bugs”.

So again, threat all this as you would when managing a project. Here, you would manage stakeholder expectations, plan maintenance, plan post-launch fixes, etc.

An important thing here is too always keep gathering feedback and improve the change with it (yes, you will need to change the change!). Mobile apps developer use the precious feedback given in the app-store and update their mobile application accordingly; this makes their app much more popular amongst the users. Here it’s the same thing, don’t think feedback was important only before the change, it’s just as important after as it will help people keep the change rather than requesting to go back to what it was before.


Stay tuned for part 3!

Are you too busy to improve?

Leave a comment

Continuous Improvement – Part 2 – Why not?

Are you too busy to improve?

In case you missed Part 1, don’t forget to read the article!

Continuous improvement seems obvious to consider, why doesn’t everyone do this all the time?

Continuous improvement is great and should be practiced on a regular basis, but it does come with its set of large challenges:

Improvement means change

The natural tendency around change is to be reluctant.

People are scared of the unknown and this adds stress to their daily lives. If for example they are handed a completely new software to use every day compared to the old one they mastered, they may become worried they won’t master the new one, or that they won’t be able to be as efficient.

It’s also important to note that people love their routine, some more than others, and changing that can bring frustration from team members.

It requires time and it’s secondary

When it comes to prioritizing between a client project against an internal project of adopting a new process, the client project will always come first as it is considered more important.

This constraints continuous improvement a lot because it generally becomes the thing we’ll do “when we have time” and this can be very rare or even nonexistent.

It’s a long-term view rather than a short-term view

People often go for the instant gratification, and the long-term benefit is often put aside. Continuous improvement is always working more now to benefit soon or much later.

For example, if installing a new project management tool means lots hours of work transferring projects to the new tool, more hours to train people to use it, not mention the initial learning curve where everyone will be less efficient and will need constant support, this can mean 50 hours of work.

If you look at it short-term, it will look like we just spent 50 hours only to be slower. Crazy, right?

If you look at it from a long-term point of view, once everyone is ramped-up, every project going forward will benefit from the added efficiency and will be more on budget. This means you could get back your 50 hours in 2-3 projects for example, and every additional project would be even more benefit again and again.

It’s hard to know where to start

Since everything can be improved all the time, people don’t know where to start, and this infinite number of choices can make people freeze and avoid the situation completely.

No power

You may be someone with no authority inside a team, so even if you want to bring improvement, it doesn’t mean it will accepted nor that you will be able to secure the resources needed to make the change.

It can also be more challenging to have the change be adopted by everyone since they might not listen to you.


It’s a constant fight

Continuous improvement is challenging, and the bigger the improvement or the team, the bigger the challenge. You often feel like you have to fight your way through change, whether to create the change or to maintain it. All of this makes continuous improvement hard to adopt, but who said the best things in life were the easiest?


Stay tuned for part 3!


Leave a comment

Continuous improvement – Part 1 – Summary


Source: twobee

In April, I had the chance to be invited as one of the presenters of the virtual event called Project Manager Success Summit. I had selected a topic that I feel strongly about; Continuous improvement of tools, processes, our team, ourselves.

For those who missed the event, I’ll be sharing articles around the subject in the next weeks.

So what is it?

Continuous improvement is an ongoing effort to improve products, services, or processes, without an end.

For me, it’s more than that, it’s a state of mind, a “will” to always challenge how things are currently done, how a team currently works, how we currently are, in order to always bring in more the next day.

It’s embracing changes, and also thriving to be out of our comfort zone.

Where can we apply “Continuous improvement” inside an agency or a team?

Continuous improvement can be applied everywhere around us, here are a few examples:

  • Assessing/fine-tuning our processes to make them more efficient;
  • It can also be about creating templates, improving those templates;
  • Install or change tools that are in place for ones that will make everyone’s life easier.
  • It’s about the people too: it’s about assessing the efficiency of a department, a team, or individuals; finding what could be improved to make each of them better for tomorrow.

Depending of the agency and its size, it can be challenging to bring changes, it’s more than having a “Lessons learned” meeting after a project, it’s about looking at everything that’s around us, everything that’s being used, everything that’s being done, and asking ourselves “how can it be better?”.

How can it affect project management?

Project managers are involved in all aspects of a project in order to bring it from its planning state to its closing state. This means that wherever there is improvement, their projects will be more efficient going forward.

In other words, continuous improvement affects project management everywhere.

It can be directly, for example:

  • Improved tools and templates that project managers use on a daily basis means higher efficiency from them, increasing the probabilities of bringing projects on schedule and on budget.
  • Tools, used correctly, can improve overall communication, and as we know, project managers communicate about 90% of the time; this means that any improvement to what tools are used and how we use them as a team can have a major impact on project managers’ daily lives.

In can be indirectly, for example:

  • If a department has improved the technology they used to create their part of the project, it will bring more success to the project, and potentially raise chances to be on budget.
  • If overall communication between different departments improves by adjusting a few processes, it simplifies a project manager’s daily life where facilitating communication is something that be a challenge sometimes.


Stay tuned for part 2!

Project Manager Success Summit

Leave a comment

Project Manager Success Summit presentation on Continuous Improvement

Project Manager Success SummitRecently I’ve had the privilege to be contacted by Michael Charles, host of the Project Manager Success Summit, and was asked to be one of the presenters.

I’m grateful that I will be able to share with everyone about a subject that I hold dear: Continuous improvement in tools, processes, our team, ourselves.

I believe Continous Improvement is important in all aspects of our lives, but in project management, especially with IT projects, you have to evolve non-stop to follow the technology that’s growing at a fast pace.

I’m hoping you’ll enjoy! The summit is a free virtual event that hapenning April 25-27 2014 where you can to hear lots of great presenters share their knowledge, go subscribe 🙂


5 tips to help make changes happen

Bringing change is always a challenge. The human reflex towards changes is pushing-back due to being scared of the unknown it may bring. This constant resistance could bring a halt to even the best of ideas if they are not shared appropriately with other.

From changing software, to changing process, to anything really, changes are a challenge, especially when dealing with a large team.

Here are a few tips to help with that:

1. Explain why

One of the top reasons people are not motivated to change is not knowing why the change is being done in the first place. Not only that, this demotivator is often worsened by giving other limited information because “They don’t need to know everything” which brings frustration and can even damage the trust they have in you.

Changes have reasons, and people who are affected have a right to know why; let them know and you reduce a lot of resistance right at the start.

2. Provide relevant information

First, avoid drowning the others with too much information that they will simply disconnect or run away from whatever you are trying to bring into their lives.

You may be passionate about what it is and the fact that you can make it happen, but giving everyone so much information about it will just scare them, not to mention the waste of time for you since people will probably not listen/read most of it.

Be sure to share relevant information that will be useful to them right away. As for all the detailed information, make it easily available somewhere and invite people to refer to it if needed.

3. Provide easy/accessible support

If the changes will most likely bring up questions or issues, then it is very important to let everyone know how to ask for help. If they have any roadblocks and no one to help them go forward, then they will abandon and your opportunity to make a change will be lost.

Make sure it’s clear for everyone who to reach and how when they need something; and make sure support is extra efficient when the change is recent, this is when people are trying to adapt and the support required will be higher.

4. Ask for feedback

It’s being done more and more; take the App-store for example and how people can post reviews, and the way it’s considered by the developers afterwards into their applications.

Feedback, assuming it’s constructive, is valuable information guiding to ways to improve given away for free but usually, it won’t be given if you don’t ask.

Create surveys, send mails, go talk to people, but go grab the feedback and avoid waiting for it.

5. Continuous improvement

Deploying a change is one thing, but maintaining it is equally important. This is what will keep it going, and will make people love it more and more.

Using the feedback you’ve gathered (see #4), you can analyze the information given and improve from there. In other words, change the change!

To complement #4 here: if the feedback is ignored, it will create more frustration, make sure you use it!

In conclusion

Changes can be very good, but the way it’s brought to others can be very bad. Assess how you bring changes to your team and identify where you can make it easier for others overall, and it will automatically become easier for you too.

Don’t hesitate to share more tips!

Leave a comment

4 tips to reduce reluctance with change


Source: xenia

Changes are part of life, we live them in our personal life, and in our professional life. If you work in IT, changes are ongoing, and if you don’t adapt quickly, you fall behind within months. Unfortunately, the human nature is to be reluctant to changes, so here are a few tips that will hopefully help you make changes happen:

1. Make it simple for them

No matter the change, whether it’s a new technology, a new process, a new methodology, etc., the steeper the learning curve, the fewer people will be onboard.

So how can you make it simpler? There are a couple of ways:

  • Build tutorials: Any guide whatsoever will simplify the learning curve. It can be very simple to more elaborate depending of the size of the change. Avoid anything long or boring. Go with quick and easy, like cheatsheets, or something interactive.
  • Available help: Let people know that you (or someone else) is available to help them. Obviously, make sure it’s true, and appropriate help is given when needed.
  • Plan the change: If the change is structured and iterative, people will be introduced step-by-step to the change instead of forced into all at once. That will greatly reduce the fact that people are generally scared of changes since it’s not moving too fast.

2. Show how it’s helping THEM

This tip may not apply for all the changes we want to execute, but amongst other types of changes, let’s say you would want to change a tool that a team uses for projects: The initial reaction would be that it’s either “just another tool added with the others” or “why are we doing this?” or something to that effect.

You want to make sure that people are aware of how the changes are good for THEM, not you or management, THEM. In my example above, you could tell them it’s going to make their overall work easier by having a faster tool, or that this tool has a great set of notifications that will greatly reduce the number of things forgotten.

By focusing on that when you brief the others, they will also focus on that while they are juggling their emotions towards the change. As they fight the reluctance, they can remind themselves how it’s helping them, and it will reduce complaining.

3. Ask “why?”

This tip can be applied once reluctance is being detected. It’s easy to insist on something, or even to force it on people, but by simply asking why they are reluctant, you may find out that it’s because of silly reasons, or justified ones. Once that is identified, you can work towards eliminating those reasons. You may even find out that your idea is not as good as you thought and it’s you who may have to change!

By asking why, you’ll receive valuable feedback as long as it’s constructive, which is always something you want to encourage inside your team.

4. Don’t give up

Stay positive, and keep it up. Don’t quit at the first “no” that is thrown at you. If one strategy doesn’t work, try another approach. Only stop once justified reasons have come up, then adjust yourself, and try something else!

In conclusion

Changes everywhere; some like them, some hate them, and some make them happen. No matter what, there will always be reluctance, so do your best to fight it.

Share your tips and stories! I’m certain a lot of you are facing challenges with changes inside your teams.

Leave a comment

The project went well, why bother talking about it?

English: Symbol "thumbs up", great

Photo credit: Wikipedia

Many waste great opportunities to gather very valuable information by taking projects that went well for granted. A typical saying is “The project went well, why bother talking about it?”, which is important to prevent, otherwise you may waste precious lessons you can apply elsewhere.

Projects that went well means that events/actions/etc. occurred which made it go well. So what exactly helped here? Identify all the positive elements of the project and make sure you get to the root of that positivity. By that, I mean, avoid being vague like “we had a great team working on this”. The root of this might be that the team has worked a lot together in the past and communicate greatly.

Once all this is gathered, figure out what can be applied to other projects, and make sure it’s actionnable.

For example, if a project went well because the client supplied everything on time, and you identify that the client was reminded weekly, with a simple list of what to deliver and when, then how about applying this technique with other clients?

Have a lessons learned meeting even for positive projects; they are just as important as any other lessons learned mettings where you can make sure to learn from the project.


Get out of your comfort zone

The comfort zone is a great place to be. For those who ignore the meaning, here is Wikipedia’s definition:

The comfort zone is a behavioural state within which a person operates in an anxiety-neutral condition, using a limited set of behaviours to deliver a steady level of performance, usually without a sense of risk.

Now why would you want to escape this safe little paradise? Simple, it prevents you from evolving by keeping you protected with this nice little routine. Don’t get me wrong, spending a good amount of time in your comfort zone is great, and even strongly suggested, but like everything in life, a good balance is better.

When you are in your comfort zone, that means you are doing what you know or what you are good at, and that is not how you will learn or accomplish something new. Depending of where you work, you may not have that flexibility, but try pushing your role farther than usual. For example, if you are used to having colleagues communicate with clients while you take care of managing the production, try asking your colleague if you could be part of the communication. It might be scary/stressful at first, but you’ll get used to it and get better. Your colleague can even give you some pointers to help.

You may make some mistakes, but that’s just fine because you will learn from them! Read my article on errors if you are not convinced.

You’ll eventually reach a new comfort zone, and then you can try something else to get out of it again! It can become stressful for you so balance the amount of time you spend outside your zone. Avoid trying too many new things at once, you may become overwhelmed and get discouraged/scared. Learn to pay attention on how to react, how you feel, and escape your comfort zone accordingly.

Another great situation is when you have a manager that pushes you outside your zone. A great leader will be able to analyze who can do what and point them in the right direction, helping them along the way. That way, the leader makes its whole team evolve. Note that it can also be other colleagues and not necessarily managers that can get you out of your comfort zone.

So, get out of your comfort zone, become better at what you do, or become good at what you don’t do yet!