Skip to content

Month: August 2016

Please Speak Up…

Let’s face it, providing feedback can be a tricky wicket.  While we all have opinions on just about everything in the world around us, we tend to put a voice to very few of them.  And, ironically, we tend to express most loudly the opinions that impact us the least.

Think about it:

  • When was the last time you vocally questioned a sports coach’s decision?  Or criticized the inability of your favorite artist to live up to their quintessential albums?
  • When was the last time you gave your employer feedback about the quality of their healthcare offerings?  Or let them know if the tools provided were sufficient to most effectively perform your job?

As a Product Manager, I often consider myself one of the “Great Consolidators of Information”; it’s my job to filter through all the data, business cases, and feedback to help determine the best path forward for the product.  Often there are a lot of factors at play, but bringing additional benefit to our customers is the ultimate goal.

However, one of the limitations is that if I never get feedback about a feature or process, I’ll never know that it’s something that needs to be addressed.

So, I’ll ask of you: Please speak up…

Your feedback does matter, and it does play into the decisions being made.  Some feedback will have visible results, while others won’t.  However, that doesn’t mean that the latter was any less meaningful or valuable.

You might think that this is limited to customers, but interestingly, it isn’t.

In most organizations, there are also a number of internal “customers” of a software product; we Product Managers need to make sure support has the tools needed to assist with customer problems and that we are in tune with the market that our sales teams our encountering.  However, many people in these groups are often used to the status quo, or see that a vision or initiative is in place, and go along with it.  So instead of speaking up with insight they may have garnered in years on the job, or from previous roles, they fall silent.  Yet, again, we Product Managers are working to do the best with the information we have at hand…and additional insight helps provide a clearer picture of what that looks like.

I understand that providing feedback isn’t always fun, fulfilling, or fruitful.  However, know that in every organization, somebody is listening.  And your feedback might just give them the insight they need to deliver you a better solution.

So, I’ll ask you one more time: Please speak up…

How Is Secondary

evPmdi1471311822Having been a software developer for the first 7 years of my career, the natural approach to work was to receive a task (a new feature, bug or performance issue) and asking “How do I make this happen?”.  And, honestly, how was the fun part.  It was applying all the algorithms and best practices I had learned throughout getting my Bachelor’s and Master’s in Computer Science, mixing it with the capabilities of the servers I had access to, and making something new that helped solve a problem.

However, as I grew more senior in my profession, had more exposure to the business problems at hand, and began interacting with the people that had to use my solutions, that approach evolved.  Sure, I had made applications that were usable, but not always very intuitive.  As I grew into a Developer/Quasi-Product Manager role, I did start interacting with a handful of key contacts with our customers, and the seed of thoughts around “What is the user trying to accomplish?” had been planted.

I then attempted a transition into Project Management for the next step of my career.  I quickly transitioned from coding with occasional customer interaction to a role that was fully customer-facing.  It was a bit of a shock to the system for a natural introvert like myself, but even more of a shock was no longer having accountability for the answers.  Focused on software implementations, life as a project manager was about “How do we get new customers using our system?”.  And when customers asked for functionality that our application didn’t have, my job wasn’t about addressing that, but figuring out “How can we work around that problem for now?”.

Admittedly, it was difficult, mostly because my job was more about solving our company’s problems than it was about solving our customer’s problems.  That “What?” seed had been planted and continued to grow, and it was anguish to not have any control over addressing those problems.  I knew that I needed to get back to Product Management.

Now back in a Product Management role, I’m back to that “What?”-first mindset, and continually refining it to identify the many levels of “What?” within our customers organization:

  • What are users trying to accomplish?
  • What do users need to do their jobs more effectively?
  • What does management need from our software to see the big picture?
  • What are the key values that purchasers see in our software?
  • What can we do to improve the ROI for our customers?

After we can paint a clear picture of what our customers need, only then can we effectively begin asking “How do we help our customers?”, start putting those plans into action, and then completing UX testing to make sure we haven’t missed the mark.

And it’s not just a one-time exploration.  We must continually repeat this process as our markets change, customers evolve, roles change, and new needs and capabilities arise.  But even in that iteration, the order remains the same: We must first understand what our customers problems are before we can provide effective answers on how to address them.