What are processes without people to follow them?

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

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.

 

 

Losing ourselves in the moment….

or maybe it’s just on conference calls. I believe strongly in remote work, and by extension I believe in asynchronous communication like email and chat apps, but also believe we need real-time communication like phone calls, conference calls or web sharing sessions. However, I am still amazed by how people behave on conference calls. It seems as if people just lose a little bit of themselves, and forget common courtesies. Today I’m going to use my soapbox to discuss some of my bigger pet peaves.conference-call-meme

  1. Remember everyone on the conference call, not just those in the room. As a project manager, I try to be conscious of everyone on the call. This includes multiple people that might be in the same room or that person sitting alone. There have been times where I’ve been the only decision maker participating by conference call. During these times, I feIt I had to time my opportunity to speak up just right. I had to do this by jumping in on any pause, regardless of where the discussion was at the time.  Alternatively, I will often have side conversations via text to facilitate progress. For people in the same room, or for the conference call organizer, it is important to remember to intentionally include all participates. You invited them for a reason.
  2. Someone needs to lead the call. The belief that conference calls aren’t effective speaks more to the organization of the call, than anything else. There is always a reason a conference call gets scheduled. Someone needs to facilitate the call. What are you trying to accomplish? What is the take away? And most helpful, if something needs to be prepared or investigated beforehand, make sure that expectation was set when the call was scheduled. Otherwise you are wasting everyone’s time.
  3. Don’t forget your manners. I guess all my frustration really boils down to this. I want to believe that we are all passionate human beings and sometimes tempers flair. I know that’s happened to me. We can only control our own behavior so let’s try to reign in our tempers and remember we are all there, in that moment, for a common good.

 

Semi-homemade is better than bespoke for data analytics

I read a product review this week where the company referred to themselves as a provider of “bespoke” data analytics. I had never heard that term used in the context of data analytics, or software specifically. However, when I googled the term, I found many companies using it in their marketing language, but no reference to it by the people who write about data analytics or software. This led me to start thinking about my experiences managing data integration software projects and how my customers view the solutions.

The projects that I’ve worked on in the last couple of years have primarily been data integration projects where we are combining multiple datasources into a single data warehouse and then leveraging that data to deliver data insights. The platform has some standard integration components that you can leverage, but there is also room for quite a bit of custom development. In every implementation, I have had conversations about what “standard” tools are available and what capabilities can be developed custom. On one hand, once these customers start reviewing the available tools, the first questions asked are usually about how we can customize those tools to their business. Each customer self-identifies as a unique even though most are within the same overall industry. There are always unique scenarios for each customer that needs to be accounted for.

bespoke-suit-pattern

http://www.giandecaro.com/img/background-bespoke.jpg

On the other hand, customization takes time and effort, regardless of whether the work is done in house or by external consultants. Where does that leave us if our customers want/need something specific to their business but don’t want or can’t invest the time and money to do so?

I think as integration partners, we are probably looking at the entire product management and implementation process incorrectly. Our customers need a balance of standard tools that they can quickly customize to their specific needs along with partners who will work with them to develop custom solutions for new or innovative work. This is similar to the idea of leveraging a template to develop your website, but then be able to customize your experience by changing colors or adding widgets that extend the template capabilities. We can think of these types of products as “semi-homemade.”

Semi-homemade is a term used heavily by Sandra Lee regarding her cooking style. She leverages pantry staples and other ingredients and creates amazing dishes. By not having everything made from scratch, Sandra Lee reduces the cooking & prep time but is still able to deliver tasty dishes people want to eat. If we apply the same principles to data analytics, I think we can definitely leverage some basic tools that we allow people to extend or meld, which result in delivering data insights without the pain of everything being a custom solution.

It’s time to shift our mindset away from solely developing out of the box solutions, or solely developing custom solutions. Product and services should be working together to build base tools that are easily extended to meet the changing needs of our customers. We won’t totally eliminate the need for custom solutions, or new products for that matter. But we will more quickly be able to meet the changing needs of our customers.

 

Make room to be messy!

I attended the SmartBrief STEM Pathways event on Thursday, October 20th. The format at the event was speakers, followed by smaller group discussions on STEM versus STEAM, student motivation, teacher retention & pathways. As we were recapping the event and having final questions & answer, I was thinking about how far we have come in education & business from early childhood learning. Learning new things is inherently messy. Learning to ride a bike often involves falling, as does climbing trees, or the monkey bars. Cooking or baking involves making messes and even making things that don’t taste good. Even earlier activities like attempting to put shapes in the correct shaped holes, or stacking blocks result in “stuck” toys or toppling towers. But learning in our classrooms as children, or our work environment as adults are expected to be orderly. We are expected to sit quietly, raise our hands & follow the established systems.

https://www.buzzfeed.com/rachelysanders/epic-pinterest-food-fails-2013?utm_term=.tu4o91nxW#.ylaPX3aY2

baking-fail

Are we doing ourselves and the next generation a disadvantage by limiting the time we have to get messy? Conversations in education reform are heavily focused around “STEM education”, but what does that really mean? If you consider STEM as a mindset, and our path to critical thinking and active curiosity, then it is more about giving our teachers the resources they need to target every kid, leveraging whatever it is that helps them engage in the process. Our focus on standardized testing and grades dampers the desire to try new things. The fear of any sort of failing, or movement away from the orderly, causes a discomfort. At the end of last year, my younger daughter was recommended fro Algebra 1 for her 8th grade math class. She also set herself a goal of making the all A honor roll all 4 quarters. Unfortunately, this was cause for a bit of a meltdown this week as her current math grade was a C, and she had a math test, and the end of the semester is approaching. She was putting so much pressure on herself for this next test, because she wanted to meet her goal. She was neglecting the fact that she was taking an advanced class, that was bound to be harder but she would not have been referred into the class, had her former teacher (and her parents) not believed she could do it.

In the same vane, there a quite a few conversations going on in organizational behavior about the fear of failure. The recent news about Wells Fargo and falsified accounts being created by sales people as a result of the unrealistic, intense goals set out by the organization is just another manifestation of the same stories behind Enron, wall street banks, etc. We have put such constraints around our employees and ourselves, that we lose that desire to challenge and be messy. We reinforce that sense of order initiated when we are told we need to start coloring inside the line, or it’s too old for you to still play with dolls.

There is a role for organization & cleanliness, but I encourage you all to make room for some messiness. It doesn’t matter whether it’s in the form of learning to cook something new, or taking on a new hobby or pushing the limits professionally. Give yourself that leeway, and make sure you give that same leeway to your employees.

 

Don’t Apologize…

for being anyone other than yourself!!!! I’ve participated in multiple conversations over the last week that reminded me of this.

Apologies-dot-mean-anything-if-you-keep-doing-what-youre-sorry-forOn Sunday, I got to represent STEM for HER at the She’s the First American University Chapter “Day of the Girl Summit” on their Women in STEM panel. During the event, one of the other speakers shared their experience with convincing themselves to speak up in meetings and make sure their voice was heard. Another panelist identified the problem as one of keeping women in STEM, rather than focus on it as a pipeline problem. Throughout my career, I’ve made it a point of always speak up. Even at my shyest I felt it was important to have my voice heard. This might not have always won me any favors, but it’s part of my principles. I pride myself on my honesty and loyalty. This means that the people I work with and for can trust me to tell them the truth as I see it. If I’m granted respect and trust in return, I can be very loyal. This same comfortableness has guided my decisions to find my own way when I wasn’t getting what I needed from different jobs.

A second conversation occurred with a former employee of mine. He is still at the company where I left him, and is doing quite well as a technical operations manager. He was expressing his thoughts and considerations about bailing out of technology to do something manual like build fences. When he asked how things were going and whether I enjoyed what I’m doing, I talked about consulting being a place where I fit in well. People hire me because they know me and know what I will accomplish. This gives me the forum and format for sharing my expertise, giving my opinions and getting the job done.

I don’t apologize for who I am. Years ago my brother said that “I needed to learn to play office politics and get along with people.” The implication was that if I didn’t do those things, I would be un-hireable. It took me many years, but in some ways he was right. If playing office politics and getting along with people means that I’m trying to withhold my opinions or manipulate the situation to get what I need, then I’d rather not participate. I want to work with places and people who encourage and support me for what I bring to the table…my honesty, loyalty and ability to get the job done.

Each of us needs to look critically at ourselves and figure out who we want to be and what we need to be successful. Once you’ve determined that, it’s a lot easier to figure out if your current situation fulfills you. If not, it’s your responsibility to fix what’s broken or find something else.

 

Whose job is QA?

not-my-problem-meme

Tribute to Gene Wilder as Willy Wonka – it’s not my problem meme

developer.com defines the QA (quality assurance) role as “the role responsible for guaranteeing a level of quality for the end client. It’s about contributing to the quality of the final product.” I really like this definition as it does 3 critical things. First, it highlights the importance of the client. A product that works as designs, but doesn’t solve the customer problem fails to address the crux of software development, giving people an application they need or want. Second, it directly states that the QA role contributes to the quality of the final product. Just as developers contribute to the building of the product, and project managers contribute to getting the project done. Last, this definition removes the perception that QA is the responsibility of a single person. And this, my friends, is the topic of today’s post.

Our job as the project team is to build a solution that solves a customer problem or need. I agree that sometimes you are building a solution that customers don’t know they need yet, but unless that need or problem exists, there’s no point in building it. From the very beginning of development, we should all be working with this goal in mind. And if everyone is focused on the same goal, are we then inherently focused on QA? I think so.

My role as project manager puts me directly in front of the customer. This means that I need to be familiar with the solution, in order to speak intelligibly to customers. I tend to do the “final test” of replicating the steps provided by the customer and using the output as proof that the issue is resolved. Unfortunately, there have been too many times where I’m delivered a solution that doesn’t solve the problem or clearly doesn’t yield the “correct” results. Or, if I report a more general issue about performance, I get very tactical response, rather than considering the customer experience.

So what happens? Why does the solution I’m provided not solve the customer problem? Is it because the developer didn’t understand? didn’t care? More likely, it is the developer did some initial investigation and solved what they thought was the problem but didn’t walk through the steps to see it from the customer perspective and therefore missed a critical step.

I’m not advocating for or implying that I wouldn’t or shouldn’t still have the final sign off not the solution, before delivering it to the customer. I’m suggesting that each person who has touched the solution before getting to me should understand the problem we are trying to solve, and be focused on delivering a quality solution. Each developer should be incorporating regular quality checks into their own development. I never want to hear that “my team doesn’t have a QA person” or “it passed my acceptance test.” If the team members understand the goal, and view QA as a part of their job, the customer solution is bound to be better.

 

All hope is not lost..3 reminders regarding the human side of project management

folly-beach-shoreline

Folly Beach SC shoreline

I just returned from a friendcation in Charleston, SC. This was a much needed vacation after a few really stressful weeks. This vacation was filled with good food, good friends and perfect weather. More than the relaxation and rejuvenation, this vacation reminded me of some key pieces to the human side of project management. Yes, fundamentally, all project management is human, but many times we forget the basic courtesies as projects get challenging.

These three reminders have been playing through my head today as I have returned to my project work.

Don’t forget the generosity of strangers

On the first day of our travels, we were taken under Mary’s wing. Mary was a new acquaintance of one of the group members, who happened to be from the Charleston area. Mary went above and beyond, picking us up, showing us around her town, chauffeuring us to the drugstore, grocery store, and finally depositing us several hours later at our beach house. She provided us with a list of places to go and things to do. We were four friends with a lot of luggage, and a lot of “asks” but Mary extended her southern hospitality and made our lives a whole lot easier. We hadn’t realized how much until about a day or so later when we realized that there were no available Ubers in the area we stayed during the off-season.

In project management, you are usually so focused on your immediate team members and milestones that you can lose sight of the periphery. You might be missing out on just the thing you need to deliver more effectively.

If you’re all aligned to the same goals, you can make anything work

This particular vacation had 4 friends, traveling from 4 different areas, with 4 different budgets. There wasn’t a single spat or disagreement of any kind. Nobody complained about people’s choices to sleep, or golf, or not drink, or even to work a little. We each respected the boundaries the others set and made arrangements for food or checks or whatever we needed.

During challenging projects, it can sometimes get contentious. It’s important to realize that everyone should be aligned to the same goals, and therefore should be able to work together to make it happen. If you truly start to see and feel stakeholders pulling away from the central goal, you need to explore that. Sometimes goals have changed, or other times it’s the pressure they are feeling approaching a looming deadline, or something else entirely. It’s your job to figure out what it is, and how to work through it.

Beware of the driftwood in the corner

Driftwood & Sea Glass

Driftwood & Sea Glass

The beach house we stayed in was very cute. As we were lounging in the front room chatting on the first day, I noticed this driftwood and sea glass art piece in the corner. As I looked more closely at it, it manifested itself as a dead, jumping rabbit carcass. It was all a bit morbid and creepy, but this became the consensus of the group.

Unfortunately, projects often end up with a similar situation. Something seemingly “artistic” morphs into its not so pretty reality. As the project manager, it’s your job to identify these instances before they escalate. Just like the driftwood rabbit, once all the stakeholders start to “see” these in the project, it’s very hard to un-see them.

I’m really glad I took this time away. Yes, I did a bit of work. But mostly, I didn’t. We relaxed in the sun under an umbrella on Folly Beach. We laughed. We explored. I’m back at work, taking my projects to the finish line and reminding myself of all that I learned.

Thanks friends.

Whose side am I on?

http://www.kappit.com/img/122260/whooo-what-a-week-im-so-glad-its-tgif/

http://www.kappit.com/img/122260/whooo-what-a-week-im-so-glad-its-tgif/

This has been a tough week. Not only was it busy, it felt like I was spending a lot of time chasing my tail. Unfortunately, it wasn’t isolated to a single client or project. It seemed across the board, I struggled to keep a handle on what was going on. The one consistent point is that neither the client nor the internal project team felt “I was on there side.”

A project manager or customer success manager for technical products are usually smack in the middle between the demanding customer and the product or project team. So, why then did this week bother me so much? I think it was because I am seemingly able to do a better job balancing everyone’s interests. I’m using today’s post to try and figure out what happened and what I can do better next time.

  • Don’t take it personal – First, I really do need to remind myself not to take it personal. As I tell my kids, “I am only responsible for my own behavior.” On the side of the customer, I am the representative of the company. It is my job to hear their issues and feel their pain. Sometimes that escalates if resolutions aren’t found quickly enough for their liking. On the side of the company, it’s my job to be the advocate for the customer. As a company, we need to realize that it’s not personal. We are each doing our job.
  • It’s all about the communication – This leads me to the second critical point. Everybody needs to communicate. The adage “no news is good news” doesn’t apply in project management. No news usually means that nothing has been done. As the advocate for the customer, it’s my job to follow up and get resolutions. At a minimum, at least tell when I can expect a response. This gives me something to tell the customer.
  • We are all on the same team – Lastly, we all need to realize we are on the same team. No matter how well a company “eats their own dog food”, the customers will always be the experts of the products. Just because they are using the system in a way that we didn’t anticipate doesn’t make what they are doing wrong. They are giving us feedback and making it better. Every time they uncover an issue or ask for something, they are driving us forward. Let’s embrace that. Let’s not assume that the customer is doing something wrong. The onus is on us to understand the use case and solve the customer problem.

I think this week’s lesson is pretty clear. I’m glad it’s friday as I need to regroup this weekend to tackle the open issues head on next week. Hopefully I will be able align everyone towards solving the problems. But as for the question I posed, we are all on the same team: product, services, and customers. 

How do you Counter the “Hurry Up and Wait” Game?

You can get so confused

that you start in to race

down long wiggled roads at a break-necking pace

and grind on for miles across weirdish wild space,

headed, I fear toward a most useless place.

The Waiting Place…

-Dr. Seuss “Oh, the Places You’ll Go

As a project manager who works on complex implementation projects, I find that I spend a lot of time waiting…

  • waiting for developers to finish their work
  • waiting for approval or feedback
  • waiting for resource availability
  • etc

It isn’t the inherent waiting associated with regular project management that’s frustrating, it’s the “hurry up and wait” syndrome that bogs me down.  These are scenarios where you have completed some component of work, are have been waiting for some time for feedback. When the feedback is finally provided, the expectation is that you will turn around a response or resolution immediately. If not managed correctly, this becomes an ugly cycle.

I have to remind myself that this isn’t happening to make my life difficult. There are underlying motivations that I don’t necessarily understand. Ron Ashkenas’s 2014 article in the Harvard Business Review “Two Ways to Reduce “Hurry Up and Wait” Syndrome” suggests that this is a byproduct of the “dramatic acceleration of today’s business culture.” Mr. Ashkenas provides two suggestions for how to minimize the impact by 1) putting a premium on removing low value work so there is more bandwidth for handling urgent issues and 2) do a better job prioritizing new requests as they come in, specifically making decisions on urgency.

I’m a huge supporter of both of these suggestions, but I think the minimize the partnership aspect of working with clients. As a value added partner you should remember these 3 things when faced with the “hurry up and wait” syndrome:

  1. You don’t know what the other person is going through – Yes, you are feeling the stress of the other person’s action, but who knows what they are going through. Maybe this is worse for them.
  2. It is critical you communicate – You need to be able to have a conversation. Tell your customer when you are going to deliver (within reason of course) and deliver. This may not be the requested tomorrow or noon today deadline, but people will generally be reasonable if you set and meet expectations.
  3. Don’t let yourself fall into the “hurry up and wait” syndrome – If you aren’t careful you can find yourself in a situation where you are constantly fighting fires and always reacting to situations. You need to be able to look at all you have to do, across all clients and make legitimate decisions about priority and urgency. By introducing process, you can bring peace to the chaos. It’s this step of building system and process that will allow you to grow and develop smarter as an organization.