Types of Innovators

by Kristen DeLap


The job of a product team is to solve problems for its users and the business. We might not always think of it in this term, but that problem solving is innovation. Some problems require higher levels of innovation than others, but always that should be a goal of our product teams. A Harvard Business Review article explores the roles we take on during the innovation process, “to identify where specific people are needed and who should work together to generate new breakthrough ideas.”

HBR identified four innovation styles: Generator, Conceptualizer, Optimizer, Implementer

The research found that generally, these innovation styles are not evenly distributed. The most people were found to be implementers, folks who take action to put solutions into work. The least amount of people were found to be generators, those who find new problems and ideate based on their own experiences.

This is problematic for two reasons. One, the product teams you are working on are likely lack a balance of innovation styles to be insufficiently cognitively diverse. To solve the most wicked problems that rise on your product, you’ll need support from all four of the innovation arenas. And two, the style you are most likely missing is generators. If we aren’t identifying the problems, are we best serving our users?

Bringing this framework to your product team can help the team understand where they might have gaps, and which innovation styles they might need to lean into.


STAND-UP EXERCISE

After they learn about the innovator types (have them read the article, or walk them through the above graphic), ask your team which innovation style they lean toward. Is the distribution the same as the general population? Which areas are missing?

Ask them to think about how to encourage an even distribution of styles on the team, as well as how to create more generators within their team and the organization. Remember that innovation styles are cognitive state, not fixed personalities. How best can you use identifying these styles to create more true innovation on your team? How can you use this to smooth the pain points in your problem solving processes?


Negotiation Tactics

by Kristen DeLap


One of a product managers most used, but perhaps most underrated, skills is negotiation. Almost every conversation a product manager has can feel like a request that needs to be weighed and agreed upon in some fashion. While a product manager can (and should) say “no”, the way in which they get to the no, or verbalize the no, is all about negotiation. It is a key pillar of communication, and one that can affect speed, outcomes, and team morale.

Specific negotiations with a pessimistic developer, or an over-promising salesperson, or an impassioned stakeholder will be different. But there are core strategies that remain the same.

When we think about negotiations, we often think of them as positional - where each party stands in opposition and applies pressure in attempt to get the other to yield. This is most often seen in bargaining transactions, or when someone is talking about “holding a hard line.” However, the better approach is often principled negotiations, where all parties come together as a team to find the best outcome and maintain the relationship. The Department of Product wrote up an informative article that summarizes the findings of the Harvard Negotiation Project on principled negotiations well.

According to the study, there are 4 facets which make up principled negotiation:

  1. People - Try to separate the people from the problem, by focusing on the real issue, not who brought it up. Then be sure to bring in empathy for the multiple perspectives involved, participation from those people, and resist the temptation to get emotional.

  2. Interests - Understand the shared interests, which are common to all parties, and the divergent interests, where they disagree. Also keep in mind many interests can be traced back to security, wellbeing, sense of belonging, recognition, or control, and so try to address these root causes first.

  3. Options - Generating options for an outcome should be separate from deciding, and no option is a bad one when you are just at the brainstorming phase. Then compare and contrast within your list.

  4. Criteria - Attempt to use objective criteria wherever possible in your negotiation to move away from emotional influences. Search for criteria like fair market comparisons, professional standards, scientific judgement or raw data to analyze options.

A product manager even tackling one or two of these strategies in their daily interactions can rapidly move them toward more effective communication. Not every negotiation feels like intense conflict, it can simply be a question of priorities or slightly different goals. Negotiation isn’t inherently a good or bad thing, but getting to the best answer makes a difference for speed, morale, and outcomes. And, importantly, the best answer isn’t winning - it is a result that is good for all involved, takes the appropriate amount of time to get to, and preserves or even strengthens relationships.


STAND-UP EXERCISE

Give a prompt to product managers to ask them about a negotiation conversation they had this week / sprint / cycle. Examples might include - an executive wanted a new feature added to an MVP; do we prioritize working through this technical debt or getting started on this new initiative; the designer wants more time to iterate and the engineers just want to get going; our lead candidate just got another offer for $10K over our budget; do I really need to attend this meeting or can I send another team member…

What went right? What went wrong? Using investigation of the four facets of principled negotiation, where could they have dug in deeper? Be sure to share yourself, as negotiation is not a once-and-done skill, but a learning path for all of us.

A following stand-up could come back to this topic and ask if anyone was able to use these techniques to find a desired or beneficial outcome.

BONUS:
The Prisoner’s Dilemma is a famous game theory problem that shows that single event negotiation is very different from multiple event negotiation. On any given product team, you’ll need to negotiate often, so it is best to stay focused on the long term relationship. Have your team play though this interactive game “The Evolution of Trust” to learn and enact the theory.


New Year Maxim

by Kristen DeLap


Calendar New Year is fraught with folks setting goals and resolutions. As we know, so many times this type of thing fails out of the gate - research says the failure rate for New Year’s resolutions is about 80%. And a dichotomy is created in the workplace, as often times a fiscal calendar or fiscal quarter professional goal setting doesn’t correspond to the standard Gregorian calendar.

While my organization’s fiscal half falls this time of year, it isn’t a major time of resetting goals. However, these types of calendar milestones are places where people reassess and perhaps are motivated to shift behaviors. Because of that, I think it is important to address as a group. (Note, another good time for this is the start of a school year - while not everyone is a student, or has students, this type of cultural milestone exists in many places.)

Instead of setting resolutions, I ask my team to think about how they are feeling heading into the new calendar year. It’s a bit of taking stock of their energy level and their mentality - a general check-in. And then, steering clear of specific goals or things they want to change, I ask for a word or maxim as they look ahead. The time period of a coherent 12 months can also be hard conceptually, so a general forward outlook may be preferable to a specific time frame. The idea of choosing a “word of the year” has almost a cult following at this point, but even a less rigorous process can still yield thoughtful responses. Additionally, it allows us to see our teams and colleagues wishes and hopes (or struggles and roadblocks) a bit more clearly.


STAND-UP EXERCISE

Once the dust of the holidays settle, prepare a whiteboarding session with a “emotion wheel” or something similar. Ask folks to identify their current state. (I ask that they name two adjectives, as you can have someone who is excited AND anxious or enthusiastic AND confused - it is good to know both.) I leave this part anonymous, so that folks can be honest, but ask them to share their responses if they wish.

Then ask them to add stickies for a maxim / word / wish as they look forward. Ideally sharing with the group provides insight and camaraderie.


Frameworks and Mental Models

by Kristen DeLap


One way product managers can be most effective is by having a process to get to the answers they need quickly and consistently. To find organization in the chaos of a new project or initiative, product managers can use framework thinking.

Framework thinkers are able to find clarity in complex situations. Further, good frameworks can bring focus to everyone's thinking, allowing the team to prioritize the questions that really matter. Framework thinkers make more progress because they remove the clutter and roadblocks for their teams.

Frameworks and mental models are abundant. There are some that are too specific in other areas to apply directly to product management, but almost all of them have something useful to take away. You can find much written about them, as companies and institutions who develop them have a strong incentive to promote them. The specific model becomes part of their brand, their unique selling proposition, and eventually recruitment tools. Some become whole books or treatise, which may or may not actually be the point of a framework. It should be easy to remember and simple to employ.

PMs can start researching specific frameworks for product management to provide structure. You want to build a personal catalog of these that you can lean on when faced with a problem or complex initiative. But looking widely at general business or thinking frameworks can also make you a better product manager (and more well-rounded person). Any of these require a bit more research into the methodology, as well as some trial and error in the application of it.


STAND-UP EXERCISE

Ask the team to read (or listen to) Product Management Mental Models for Everyone, which highlights frameworks in the categories of Investment, Design/Scope, and Shipping/Iterating. I asked my team specifically to reference models 5-12 in the designing and scoping section.

For stand-up discuss if anyone sees where these frameworks might have been useful to have in past projects. Ask if anyone has additional frameworks they use regularly, or have seen used at other employers. Do any of these contradict each other? Are there some that seem better suited for the culture or content of your team than others? Which can you immediately begin using, or using elements of?