4 Changes Affecting Product Managers

 

4 changes affecting pms_4

Today, Product Managers are managing more than products.  Product Managers are responsible for listening to their customers, paying attending to trends and developing products to meet their target audience’s evolving needs.  With the introduction of new management tools and methods, Product Managers are challenged to prioritize and balance their time appropriately.

Increased Social Presence
With continued importance around digital branding, Product Managers reap the benefits of representing and promoting their product in a positive light online.  They are responding to product issues and questions and sharing relevant content about their company and product on social networks. 

Technologists who rock @intuit

A social media presence is mutually beneficial; Product Managers can more deeply understand the end user’s needs, while customers can openly express their product questions and concerns, thus increasing product loyalty and awareness among end-users.  An open and engaging presence is a win-win for everyone.

Increased User Education and Engagement Demands
Gone are the days of simple customer support.  With constant (almost bi-weekly) changes to software, companies are partnering with popular third-party apps Intercom, Pendo and Inline Manual to achieve product and company relevant goals (e.g. increase product engagement or increase client retention, post onboarding). 

“Intercom allows us to ‘scale authenticity’ and foster a passionate community of users.  By A/B testing message format and content, we see open rates above 75% for all of our onboarding emails,” Ben Jordan, VP of Customer Experience, Invision.

Of course, with this demand comes the question of resource management and how to properly balance product and business goals.

New Internal Communication and Management Tools
Real-time responsiveness is key, and with new tools such as AHA! and Slack, Product Managers can quickly and easily communicate with their stakeholders. 

While Jira used to act as the primary platform for adding, editing and prioritizing new features and bugs, the introduction of AHA! provides separate management and communication methods specific to a subset of end-users.

AHA! is great for requirements gathering, prioritizing and roadmap planning, approval and sharing.   The visual heavy aspects are immensely helpful for teams that may not connect with the PM org on a daily basis, such as the sales, marketing, and account management teams; instead of constantly answering one-off questions around what’s on the roadmap and when will it be released, Product Manager’s can easily share a link to the most updated roadmap. 

aha!
While the combination of AHA! and Jira are useful for roadmap communication, Slack combines the most necessary daily communication functionalities into one platform.  Product Managers can create project or team based Channels specific to whom they wish to communicate with (e.g. Engineering, Marketing, Sales, Scrum Team, etc.).   Slack’s integration with Jira is especially beneficial; PM’s can receive ticket updates from Jira simultaneously in a Slack Channel.

Whether it’s through Jira, AHA! or Slack, Product Managers are expected to readily answer product related questions at the drop of a hat.  Dependent on the end-users and the size of the company, multiple communication and management platforms may be the best way to answer those questions in a scalable manner.

Specialization
Product Managers are specializing in multi-disciplinary educations (e.g. technical PM or design-savvy PM) to align with new HR requirements.  This was pulled from a recent Google Product Management job description,

“Minimum Qualifications: BA/BS in Computer Science or related technical field… Preferred Qualifications: Product management or design experience with a focus on software products and technologies.”

Since Product Managers work with the design and engineering teams on a daily basis, it’s helpful to understand how each team functions.  From a startup perspective, Product Managers can more easily market themselves as a technical or design focused Product Manager — the knowledge they have can eliminate previously required resources. 

At the end of the day, Product Manager’s roles, much like products, are constantly changing.  With continued learning and application of design, engineering and communication trends, Product Managers can get ahead of the game and set themselves, their business and their product apart from the crowd.  The question remains that remains is how to properly balance time executing tasks versus learning new management tools and methods. 

5 Ways to Become a More Technically Proficient Product Manager

Get Technical Skills

In a former post, I addressed 7 Skills More Important Than a Technical Degree, and promised to address the skills necessary  to gain a more technical Product Management role.

I too have applied to more Senior Product Management roles only to hear that I lacked  “technical experience.”  When I received this response, I felt frustrated; I’ve already been a successful Product Manager for multiple technical products…

“What do you mean that I don’t have enough ‘technical experience?'”

On a quest to better understand the skills and experience required to manage a more technical product, I found that the experience referred to wasn’t always years of experience, but rather knowledge around more technical subjects (e.g. how to use an API), of which I didn’t have expertise in from my former roles or educational background.

That said, there are five ways a non-technical Product Manager can become more technically proficient, of which include:

1. Ask Your Current Team Questions
If you’re already a Product Manager in a non-technical role, you are surrounded by people working in different technical capacities.  Use them as an educational resource!  Ask questions about the things you don’t quite understand — request that they draw pictures around how things work and don’t be afraid to ask why.  Most people are more than happy to teach their peers, especially if it’s around a topic they enjoy.

2. Read. Read. Read.
I realize this isn’t news to you, but social networks like Twitter, Reddit and Hacker News are great resources for learning about trends in the design and product space.  You’ll tend to see things first show up on Reddit and Twitter then later news outlets.  Get ahead of the curve by reading what (and where) your audience reads.

For learning more tangible skills, read O’Reilly books; there is a large collection of teach yourself books (e.g. learning PHP, HTML, Node, APIs).   

PS: Beyond learning only about the technical aspects of Product Management, read Simon Sinek’s Start With Why and Eric Reis’s The Lean Startup — these are two well known and respected authors and books in the product development space.  Their books educate you around ways to implement innovative product management thinking.

3. Blog About Technical Products, Topics or Trends
The best way to learn is through application, so write about what you want to know!

As a blogger, you’ll naturally perform market and customer research.  Quickly, you’ll get a sense for the general public’s perspective and find other people whom you can gain other perspectives from (e.g. other writers).  The product’s marketing copy and customer perceptions will provide insights around how a product works and why people find it valuable.  

Appear knowledgeable and on-point by using statistical data and related quotes from industry leaders in your writing.  Consist blogging and sharing of relevant content around a product or topic will soon define you as an authority figure. 

4. Network with People in a Technical Role
Connect with people in a more technical Product Management role during an event or through LinkedIn.  Ask to buy them coffee and pick their brain around what they do and how they got there.  You’ll quickly find that people are more than willing to help you — expect great advice and additional introductions.  And yes, this is all accomplished through the tiny price tag of coffee!

5. Take Credible Online Courses
Enroll in free online courses with an option to gain a certificate or degree.  Some of the top-tier colleges like Stanford, MIT and Harvard even offer free courses.  For programming classes, take classes through Codeacademy or Khan Academy.

Remember that you’re aiming to move into another role, so whether it’s within or external to your current company, you want to projects or courses to your resume and portfolio showcasing that you’re working toward gaining the skills you lack.  

A. Get an Agile Certificate
Since the majority of software companies use Agile methodologies, you’ll better understand the software development and resource management process through practicing Agile and obtaining an Agile Certificate.  Additionally, you’ll better foresee and manage potential risks, interact with stakeholders, resolve problems and improve people, processes and the product.

B. Get a Google Analytics Certificate
Analytics succumb all aspects of a business –from the sales and marketing side to the product and design side (percent change in revenue YoY, customer engagement with a new feature, bounce rate,  mobile use percentages, etc.) — and with continued importance on real-time decision making based on data, Product Managers need to understand what the data means and what decisions to make based on that data.

By enrolling in a Google Analytics course(s), you’ll learn how to track data (e.g. marketing campaigns) and evaluate data through in-depth analysis.  With this knowledge, you can successfully provide advice and reasoning around product related decisions.  As we know, storytelling through data is the most persuasive narrative.

Product Management is hard work, and moving into another role — vertical or horizontal — is an exciting challenge.  If you can show progress toward learning a skill in an area you’re interested in, your passion and determination will shine through.  Stay positive if you hear you need to work on a few technical skills.  As John C. Maxwell once said, “dreams don’t work unless you do,” so stay positive, work hard and you’ll get to where you want to go! 


Related article from 
Loudprogrammer.net: Which Programming Language Should I Learn First

7 Skills More Important Than A Technical Degree

While I don’t formally have an engineering or technical degree, I’ve held a product management role for the past few years.  I’ve worked for corporate companies, as well as start-ups and found it to be true that,

“Not all Product Managers need a technical degree.”

As a Product Manager, you’re responsible for managing the product through each stage of the Product Life Cycle (PLC): strategy, roadmap planning, marketing, sales, forecasting, etc.  Each of these stages require a certain skill set, but most important the skill of communication.  When pressed with technical questions in the past, I found that if I asked questions about the things I didn’t understand, that the skills I had superseded the knowledge lacked.*

Overall, there are 7 skills all Product Managers need to succeed.

  1. Customer Love
    Understand and love your customer.  Be empathetic to their pain points and make decisions with the customer in mind.
  2. Think Strategically
    Define and re-define the problem your product solves.  Listen to customers as their problem(s) and factors of influence change.  Investigation into your marketplace and competition will provide insights into the direction and positioning of your product.
  3. Plan and Prioritize Accordingly
    Foresee potential changes in the way your product solves the customers’ problem and how and when your customer makes decisions around the purchasing or use of your product.  Develop your roadmap with those possible challenges and changes in mind, along with proper engineering estimates and product designs.

    “The product manager owns the product roadmap. [S]he is the person responsible for defining, in detail, the ‘why’ and high level ‘what’ of the product that the engineering team will be asked to build.”
    – De Haff, CEO of AHA! (2015)

  4. Influence Others
    You need to explain your product, the reasoning for the direction of your product, as well as why and how your product solves a particular problem better than anyone else’s product.  Since Product Managers work cross-functionally, the ability to build relationships across various teams will ultimately determine the success of your product; if you cannot get other teams to support your product then how can you expect your customer to?
  5. Focus on Details
    Annotate – in detail – the client’s requirements and feedback throughout the Product Life Cycle (PLC).  From color choice to font type, each decision made influences the customer experience and their opinion of the product.  Clarity is important; product decisions need to be explained from the point of view of the customer.

    “Like all forms of design, visual design is about problem solving, not about personal preference or unsupported opinion.”
    – Bob Baxley, Head of Product Design at Pinterest (2003) (Cornett, 2008).
  6. Analyze Data
    Decisions should be made based on data, not gut feeling.  Because data is irrefutable, it’s simple to explain why or why not a product decision was made; it removes opinions from the conversation and leaves only facts.  The analysis of data can additionally provide new insights, which may lead into the development of new features or products.
  7. Execute
    Product Managers need to execute the product goals and roadmap plans outlined.  If you follow through on the commitments and timelines promised, you’ll gain trust, respect and support from your fellow colleagues.

I found that pairing these seven skills with passion and ability to overcome ambiguity in the workplace, that my lack of a technical degree did not affect my level of success as a Product Manager.  As a Product Manager it’s much more important to be fearless — ask questions, be curious and learn from others.

References:

de Haff, B. (2015, July 8). The product manager vs. the engineering manager. Huffington Post. Retrieved from: http://www.huffingtonpost.com/brian-de-haaff/the-product-manager-vs-th_1_b_7733156.html

Cornett, C. (2008, June 2). Visual design is about problem solving. inspireUX. Retrieved from: http://www.inspireux.com/category/bob-baxley/