Category Archives: Project Management

The impact of sales context on project management

by

domino-effectData or software projects are usually purchased in one of two ways: as a part of a large, enterprise level deal that impacts multiple teams and has overarching corporate goals or as a stand alone purchase for a specific purpose for a specific team. This sales context can make for very interesting project management moments.

If we take the scenario where an organization makes an enterprise level implementation decision, you could have some additional levels of complexity. For example:

  • The project team may have to “sell” the project to the individual teams of users within the organization. The teams will likely have different levels of familiarity and maturity with the business process or solution.
  • Where there are varying levels of maturity, you have to be careful to effectively set expectations and cater differently to teams based on their desired engagement.

In another scenario, one part of the organization makes a purchasing decision with dependencies on other parts of the organization. This will often result is some interesting yet awkward project conversations. For example:

  • If you need to engage with another part of the organization to make the project be successful, it’s important to lay out all the facts and deciding factors. Too often project conversations must occur to relieve stakeholder concerns without those stakeholders having all the facts. Those seemingly minute details can totally shift the tone of conversations, making or breaking success.

And last, let’s consider the scenario where a specific team is looking at a solution. In this case, there can be additional considerations both in the sales process but in the project management as well. For example:

  • Does the team control the purse strings? Or are there other dependent groups or players? Make sure you fully understand the landscape of stakeholders & stakes.
  • Does the pain points being discussed align to what you do best? Just because you can sell your solution, doesn’t mean you should.
  • How does this sale fit into the overall goal of you both organizations? Is this a one-off purchase by a team without any broader organizational support? or are there opportunities for growth for both parties?

Project management in itself is a fairly straightforward undertaking. Your job as project manager is to deliver on the project goals. As the saying goes, “the devil is in the details.” You need to quickly assess the lay of the project land. Who are the key players involved in the project? Who are the key players not involved directly in the project? What are the potential pitfalls or landmines you need keep on your radar (not necessarily on your horizon as you should be working to mitigate these as much as possible)?

The value of user engagement

by

On-boarding customers to enterprise software can be a fairly long & daunting process. There’s usually a standard implementation process including setup, configuration, validation & training. The implied follow up to this occurs when the trained users start actively engaging with the software and embedding it into their business processes. Without this adoption and engagement, there’s a risk of undervaluing the investment.

http://mattshore.co.uk/wp-content/uploads/2015/09/value.jpgEngagement is not passively granted, but rather actively earned. As part of the project implementation, there needs to be special consideration given to figuring out how to keep users involved & engaged. Here are 3 options for continuing the conversation with the user community:

  1. Develop subject matter experts within each crucial team – Working closely with a few key team members to develop their natural curiosity around your software and empowering them as experts can turn them into subject matter experts and advocates throughout the entire organization. Some ways you can do that is collaborating on a few critical business processes to meet a specific business goal. You should result in showing those users the possibility and delivering them a “aha” moment for them to share with others.
  2. Create opportunities for sharing – This applies to within the organization and with the vendor-organization relationship. Leverage the expertise from your vendor/implementation partner to identify best practices that can be applied to your business. Within the organization, it is rarely enough to wait for serendipitous moments to miraculously occur. Everyone is working towards their own goals, often on their own isolated path. Creating “train the trainer”, subject matter expert question time, or brown bag lunch show & tell opportunities can bridge the gap.
  3. Know your path to success – Hopefully, you defined your project success before the implementation. It usually isn’t instantaneous in nature, making it even more critical that you define your path to success as well. Understand where you started from, and develop a plan for moving towards that success. Measure your progress regularly and adjust the plan as needed. You may find that you’re starting point is different than you thought or it will take longer to fulfill your end goal.

User engagement post software implementation is instrumental in the success of your project. Don’t underestimate the importance or complexity of this step.

 

Mislaid project intentions

by

If you managed a few projects, you eventually come upon one with mislaid intentions of some sort. I’m specifically using that word because it comes bearing a sense of temporary-ness, and lacks a sense of malice. Both of which I think are what’s at play in these situations.

misplaced-meme

Sourced https://memegenerator.net/instance/66917865

What do I mean by “mislaid intentions?” For me it’s those situations where things just don’t seem to add up. The actions of the stakeholders or members of the project team don’t align to the published project goals. It might be the subtle (or not so subtle) withholding of information or the constant flux of sidebar conversations or even the lack of follow through.

So, what do you do? Do you put your tail between your legs and run away? Do you whine to the powers that be? I rarely shy away from a chance to show my scrappiness and use this as an opportunity to insert myself into the process. I’m not too concerned about what others think of me. My goal is to execute on a project so I need to use all the resources I have at my disposal and pursue those goals (sometimes quite aggressively, if that’s required).

But, what’s the point? To me this is actually the more interesting question. If we are all working towards the same goal of delivering on the project goals, what’s the point in mislaying intentions? This is where the organizational and personal dynamics come in. Usually the reason for this behavior has nothing to do with you at all. It usually has to do lack of knowledge or understanding (of your role, value, or even the mechanics of the project); or it could relate to broader project issues that originated before you arrives; or it could have to do with personal insecurities.

It’s really not necessary for you to spend too much time speculating on why this is occurring. Remember these are “mislaid” intentions with implications of benevolence and a lack of permanence. Your job is to figure out how introduce your role, and work you way into the dynamics of the project often changing it as you march towards your goal of execution. Don’t stop fighting the good fight.

 

Find your “green flash” in each of your projects

by

A green flash occurs when the conditions are right as the sun rises or sets. Growing up on St. Croix with many weekends spent at the beach at the west end of the island, I’ve seen a few of them. As I sit down to get some work done on this damp, dark, dreary, rainy day Monday I think about this one to two second flash of brilliance on the horizon. Sometimes it is just what you need to refocus your attention on the task or project at hand.

Green flash – www.sandcastleonthebeach.com

So, what then is the equivalent of a green flash moment on a project. It’s that thought, idea or component that drives you forward. It could be the group of people you are working with; or the ability to use a specific skill; or learn something new. It doesn’t really matter what it is, but rather that it motivates you. And this is a more personal endeavor than just being on time, or on budget, or meeting a specific stakeholder KPI. This can and probably should be different across different projects.

Just like a lighthouse beacon, every decision or action you take should be with this point in mind. This means that you need to consciously think through your actions to make sure they align to this particular project goal. While I don’t necessarily think it’s necessary to share your personal green flash moment, but I do think that you need to visualize yourself succeeding in the way you defined. Your mental conversation should be how you get to the end, not questioning whether you can get there.

 

3 reasons to embrace your most vocal customers

by

So, you’re in the middle of a project and your customer spent the last 15 minutes telling you all the ways the are frustrated with how the project is going, and what you need to do to fix it. As a project manager, this can be quite disheartening. Often we put so much of our selves into our work and it’s hard to hear that your falling short. That said, I think we need to view this scenario from another perspective. Here are 3 reasons to embrace this vocal customer:

improvement_construction

  1. Engagement – If your customer is taking the time to vent their frustrations with you they are still engaged. At this point they still want the project to be successful and haven’t given up on you as a vendor. You still have work to do to resolve issues and mend the trust issues, but they are enabling you to do this.
  2. Improvement – Your most vocal customers are the ones that are pushing you to be better. These customers are sharing their intimate business challenges and opportunities and asking for your help in solving them. While it can be frustrating and  the relevancy to the organization may be foggy, this customer has chosen you to help them. Working closely on defining solutions together allows you to do a better job servicing other customers in the same industry.
  3. The alternative is futile – Doing nothing to respond to your customer’s concerns sets you on a very difficult path. This will ultimately drive your customers away. They underlying business requirement doesn’t go away in this situation so if you aren’t helping to solve it, so other vendor will. Additionally, if you aren’t constantly listening to the changing landscape of your customers’ industries, you aren’t able to iterate to solve those challenges.

Next time you are feeling a bit attacked by your customer, take a step back to breath and recover. Once you relax and realize this isn’t a bad thing, then you can identify your plan for exceeding expectations and delivering to the customer.

Do Project Managers still deliver value in 2017?

by

“Between agile and automation, project management is going away. There may be jobs with that title but the work will be very different.” — Kevin Brennan

I saw the above quote today on Twitter. Just like a couple of weeks ago, I was totally taken aback. Agile and automation doesn’t take away what a really good project manager can do. These are methodologies and tools that a project manager can use to deliver projects better. When I asked my husband, a software engineer, what he thought of the quote, he suggested that maybe these would drive the non-technical project managers into extinction.

I guess it all really begs the question of what does or what should a good project manager do? I’ve been asked to help train someone on how I run implementation projects, so I guess I should start putting to paper the criteria around what I do and why it allows me to deliver on implementation projects. I will start by saying that all project managers are not equal. This is a big part of the reason that many technical resources are so critical of the PMO and project managers. They don’t see the value and often feel that the project manager just adds work to the technical resources.

Above anything else, a good project manager should remove obstacles from the team and the project. This might be resource alignment, or a dependency from another department, or almost anything. Status meetings, project documentation and stakeholder management are merely manifestations of this work. The catch here is that the project manager needs to be technical enough to fully understand the nature of technical issues, and work with resources on getting them what they need to resolve them.

Second, a good project manager has the analytics wherewithal to assist business and technical resources. On the business side, the project manager can help bridge that gap between that user story or business requirement to the details of how functionality works, to ultimately helping coordinate the validation efforts further offloading work from the technical project team. On the technical side, the project manager with strong analytic foundations can step in at any point from requirement interpretation to design to validation/QA.

A natural curiosity can also differentiate a good project manager. The ability to ask questions and drill into the details yields a great project management dividends. It shows your stakeholders and project team that your interested in what they have to say, and is instrumental in the trust building required to successfully deliver. Very few projects run without hitches. The desire to ask why can broaden the range of solutions, ultimately resulting in a successful implementation despite the twists and turns.

A good project manager will balance tenacity with adaptation. Too much happens too quickly these days for project managers to stagnate within in a set methodology, toolset or process. We too often see project managers so set in their ways, unfortunately often following the PMI rulebook to its smallest minutia. The moment the project offsets the delicate balance (of the PM), the delivery becomes jeopardized. Come to the table with your preferred methodology and toolkit, but be willing to be flexible during the project implementation. Ultimately, the project manager will be more successful.

At the end of the day, I don’t think being a good project manager is really difficult. I think a shift in mindset and the ability to constantly learn can make you successful. I’ll continue to do what I do and deliver projects. In the meantime, I’ll leave you with this description of a project manager, sent to me by a former coworker. He hadn’t been a fan of project managers until he had the opportunity to work with me on a project. In addition to the several job referrals, he sends me funny project management memes.

pm-meme

 

What did #givingback teach me about team dynamics?

by

My younger daughter and I did some volunteer work yesterday at the Capital Area Food Bank warehouse in Washington, DC. We were part of a group of about 12 people, some parents with kids who needed community service hours and other adults. It was fascinating to watch us evolve from individual or small groups to a graceful machine that just did what needed to get done. I left thinking about how a group of strangers working for a good cause can naturally meld, while we have all been in professional situations where people seem to work against the natural evolution.

team-dysfunction

Our job was to unload several pallets of breakfast and lunch foods in the refrigerator, repacking it all into individual banana boxes. Our group of volunteers started working either individually, or with the people that came together. Fairly quickly, people started stepping into roles that just needed to get done. Instead of fighting for floor or pallet space to load boxes, started opening all the boxes and handing them off to packers. Stronger individuals started collecting the boxes as finished, and others stepped into to funnel empty boxes to those that were packing. As pallets were packaged and left empty, others stepped into to breakdown boxes. And we did all of this, with politeness and instinct. I’m not sure anyone even asked any other person their names. It was awesome to have a bunch of strangers work together so seamlessly, all pursuing the same goals (either the short term one of getting out of the fridge or the more altruistic one of helping a worthy cause.)

Why is it then that I have been in more than one professional situation where the team  doesn’t meld in any capacity, let alone as smoothly as yesterday? I’m not talking about the individual who marches to the beat of their own drum, as I’m pretty sure I fall into that position quite a bit. I’m talking about the person or team that seems to fight against almost every request or initiative to solve our customers problems. Maybe it’s because I’ve grown up around small businesses as a child and for most of my professional career. Small businesses need be customer focused to survive in a way that larger companies some times forget. My professional roles have always been in bridging the gaps between customers and technology, so for me, every decision I make is with the customer in mind. It’s unfortunate then when I’ve been in situations where process or team goals have been misaligned. If I’m working to deliver customer value but all efforts are stymied, does it mean the unhelpful person or team isn’t aligned to delivering value to the customer?

I know that this is a harsh criticism. I also recognize that different people have different motivations, and are provided different team goals within organizations. While I don’t truly believe that these teams intentionally set out to hinder what I’m trying to accomplish, I do think it’s unfortunate that there’s that much misalignment across organizations. Too often, customers see the results of this disfunction and ultimately are the ones that get hurt.

 

Project Managers need agility regardless of methodology

by

My Sunday morning peruse of Twitter led me to a blog post ‘Agile Project Manager’, It’s a Contradiction. Despite being a little taken aback, I did click through and read it. And I whole-heartedly disagree!

I’m going to start my response by first looking at some definitions.

Methodology – Merriam-Webster defined it as “a particular procedure or set of procedures.”

Waterfall – Wikipedia defined it as “a sequential (non-iterative) design process, used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases.”

Agile – Wikipedia defined it as “a set of principles for software development under which requirements and solutions evolve through the collaborative effort of self-organizing cross-functional teams.”

Process – Merriam-Webster defined it as “a series of actions or operations conducing to an end.”

Principles – Merriam-Webster defined it as “a rule or code of conduct.”

In project management, both Agile and Waterfall are considered project management “methodologies” used to deliver projects. They provide a set of guiding principles for getting results, and delivering business value. They both have pros and cons, and each is not right in every situation. Many times, a hybrid approach is needed.

Regardless of approach, a good project manager needs to be incredibly flexible. They need to understand the dynamics of all stakeholders, grasp the complexities of the value proposition and manage the situation throughout the process, adapting to the changing landscape. I would argue that even when using a waterfall methodology, a good project manager must be nimble.

It saddens me that the author of the aforementioned blog post feels that project managers “belong purely to highly planned deliveries where any change is a hinderance and fluidity is frowned upon.” Have they not ever worked with a good project manager that adapted to the movement of the project? Or have I just been incredibly lucky to work in organizations that allowed me to adapt and morph the project, and my role within in it as I see fit? It didn’t matter whether I was using a waterfall approach or were working towards agile.

The author further states that an agile project manager is a hybrid role, comprised of multiple responsibilities on projects not large enough to all the prescribed roles. I prefer to work within small to mid-size organizations, however usually work on projects for very large organizations. I’ve not had the luxury on any project to have a person to fill every role. Additionally, I think there is some level of getting your hands dirty in analysis, value recognition and other aspects of the project that enable me to delivery the projects I work on.

the-best-laid-plans...

http://www.azquotes.com/quote/608738

The one area where we did agree is “The ability to adapt, morph and practically deliver is…the true spirit of agile delivery.” I would also argue that it is the true spirit of a good project manager. If we are not constantly assessing where we are against our goals, and making decisions about how we manage the project (across stakeholders), and making adjustments to our plans, we can’t be successful.

What are processes without people to follow them?

by

The … process is only as great as the people who participate in it. – Jeff Miller

Congressman Jeff Miller is attributed to saying this quote in reference to the democratic process, but I think it applies to most process. A process without people following doesn’t go very far.

If you know me, or have navigated my site at all, you know I love to read. Fiction, non-fiction..books, articles, blogs, pretty much anything I can get my hands on. This also means I look for and want documentation and process. I want to see my starting point, and then figure out where I need to go. This also means that I strive to leave the same for others. I am not afraid to leave behind my knowledge or information for others to benefit.

Too often though it is becoming more common to want to be fed information, rather than seek it. When did we lose our natural curiosity? And further, why are we so quick to stop after the first roadblock? Even more frustrating to me are those that should know where to find the information they are looking for, but still don’t follow through.

Don’t get me wrong, this inclination has yielded plenty of new opportunities for me. Because I know these resources exist, I can leverage them and very quickly expand my knowledge, making me more effective. I guess I will keep doing what I do, and try to leave my knowledge on for the next person. I can hope that someone will take advantage of it.

 

 

 

Project Manage with Intention

by
Some-people-want-it-to-happen-some-wish-it-would-happen-others-make-it-happen

Sue Sotter – https://www.pinterest.com/susoutter/inspiration-to-be-intentional/

In doing my research for today’s blog, I read two separate articles that referenced “accidental project managers” as anyone who leads projects that hasn’t undergone formal project management certification. I’m a bit taken aback by this. While I don’t hold any project management certifications, I have done extensive studying of project management methodologies and am quite successful as a project manager. This isn’t by accident, but rather by intention.

I’m not going to argue the validity or value of having project management certifications, but I will argue that someone taking on the role of project manager isn’t accidental. “Accidental” means that it’s unintentional, unexpected and happens by chance. Is that really the case? Does our corporate leadership randomly pick an employee to lead a project?  Or rather, does the employee demonstrate some set of qualities or interest that results in project leadership? While the timing and recognition may happen at unexpected times; or the size or scope of the project may be larger or smaller than intended (by the management, or the person who solicited the additional responsibility), deliberate steps were taken to initiate this shift.

And my story? I transitioned from an operations role to a technical role when I became pregnant with my first daughter. At the time, it was thought that I would have more flexibility in a technology than in business operations. After a year or two as a database administrator reporting to misogynous boss, I handed in my resignation. I was asked to reconsider with the offer of a project management role. I understood both the business and technology; and had been at the organization long enough to understand how to get stuff done. I developed subsequent leadership (project & team) skills while getting my MBA and managing teams of technical and analytic resources (software developers, project managers, billing specialists, etc.) Every decision made along the way in my career, and when I manage projects are done with thought and intention.

While I don’t think the two articles were using the term “accidental project manager” as an insult, they were definitely on the side of promoting their products. They were trying to target the people who fill project management roles without having received any project management certifications. Maybe it would be better marketing to focus on being “new to project management” or “running your first projects.”

I on the other hand will continue to manage projects, building on my experience and constant reading, researching & self-learning. Practical application and incorporating lessons learned from post mortems supplement my experience and allow me to improve for each project.