Menu

Create awareness of reality through bottom-up strategy

Tim Casasola’s post Create awareness of reality through bottom-up strategy points to an issue that we often see in teams—the work that they are doing is disconnected from the company’s core strategy:

There is often a difference between what an organization says its strategy is and what customer/project teams do on a day-to-day. When this dissonance is present, customer/project teams share with the org that their reality isn’t aligned with the organization’s vision. “It’s great that we want to pursue this new customer segment, but most of our engineers are focused on improving the experience of our current customer segment… and we’re far from where we want to be there.”

And yet, the org still says they have a “strategy.” The org turns a blind eye when customer/project teams describe their reality and relies on its existing narrative when feeling challenged.

The organization needs to be aware of when this dissonance takes place. So that they can learn from it, and come up with an actionable strategy.

Tim points to John Cutler’s “Bet Up” activity as a useful exercise to make this disconnect clear:

This seems like a really useful exercise for teams to undertake. It might also be really interesting to ask the executive team to fill out row 4 of the above, and see how their answers differ from what the teams come up with. Exposing a big strategy mismatch in such a clear way could be a really powerful tool to move the organization in a direction where a team’s day-to-day work is reflected in the overall product strategy.

Leadership and product strategy lessons from Reid Hoffman

Ben Casnocha has a long, excellent piece entitled 10,000 Hours with Reid Hoffman: What I Learned, in which he shares a bunch of lessons he learned from then LinkedIn founder:

A lot of strategists (and CEOs) think that their job is to conceive a strategy and then hand it off to the underlings to execute. They might concede that delegation matters, but usually as a matter of execution more than strategy.

Reid disagrees. He once told me, “Whoever is actually immersed in the actual execution of a strategy should always think of ways to tweak the strategy for the better.” It’s a litmus test for talent: How do you know if you have A-players on your project team? You know it if they don’t just accept the strategy you hand them. They should suggest modifications to the plan based on their closeness to the details. And as they execute, they should continue to tweak the strategy, and you (the owner) should not feel a need to micromanage or second guess—if you do, you’ve got the wrong person.

The whole piece is full of wonderful gems like that. Highly recommended read.

Simple product design is about removing the forces that block users

Kate Clayton wrote an excellent essay on simplicity in design that goes way beyond the usual platitudes. From Be an Elegant Simplifier:

When I saw Danny Kahneman speak at a meeting last year, he shared a similar principle to the Crystal Goblet he took from psychologist Kurt Lewin, who, like Beatrice Warde, was active in the 1930s. Imagine, Lewin said, you have an object with forces pushing against it from opposite sides. Human nature would say if you want it to move one way, add more force to one side. But Lewin advised against this. A much stronger solution, Kahneman said, is to remove the force blocking the user’s way. Eliminate some of the muck.

This principle is very close to the product forces concept of Jobs-to-be-Done, and it’s great to see it framed from a slightly different perspective.

Turn customers into a coalition of defenders

I love this sentiment from Rich Ziade in the post The New MVP: The Minimum Valuable Product. He talks about what happens when customers become a coalition that shares your mission. This is written from an agency perspective, but it applies just as much to product companies:

There is no more powerful political tool than releasing good software into people’s hands. You’ll find that the burden of consensus-building and campaigning is far lighter because the thing speaks for itself. It’s something you can draft behind to keep going.

Rinse and repeat. Done right and you’ll bank some political capital. You’ll need it along the way. Mistakes will be made and you will be blindsided by who-knows-what. Ideally you’ll string together a few wins that continuously impress people. Trust increases, anxiety decreases the temperature has gone down. What were once your customers will become part of your coalition, defending your product and mission because it is now their product and mission.

“…it is now their product and mission.” That is an excellent goal we can all aspire to.

It’s not about the clicks

Page Laubheimer explains that The 3-Click Rule for Navigation Is False:

The 3-click rule is a persistent, unofficial heuristic that says that no page should take more than 3 clicks (or taps on a touchscreen) to access. A variation pronounces that the most important information should take no more than 3 clicks to get to. […]

The big problem with the 3-click rule is that it has not been supported by data in any published studies to date. In fact, a study by Joshua Porter has debunked it; the study showed that user drop-off does not increase when the task involves more than 3 clicks, nor does satisfaction decrease. Limiting interaction cost is indeed important, but the picture is more complicated than simply counting clicks and having a rule of thumb for the maximum number allowed.

YES. I’ve been on this bandwagon for a long time. In 2013 I wrote in Don’t optimize for the fewest number of clicks:

Let’s get away from this idea that we should optimize for the fewest number of clicks and taps. Instead, we should optimize for an information architecture and visual hierarchy that makes the next step as obvious as possible.

Education as customer research for product development

I enjoyed this interview with Todd Curtis, Chief Product Officer at You Need a Budget. They cover a lot of ground in From spreadsheet to digital product: You Need a Budget’s Product Excellence evolution, but I especially like the discussion about the many different customer touchpoints they maintain:

As ideas move into discovery and validation, Todd and his team go to customers directly. Todd tries to have hour-long sessions with two customers every week to learn about their budgeting story. Through the company’s frequent online workshops, YNAB is able to engage with hundreds of customers each day and hear their questions and concerns.

All these efforts help YNAB gain a deep understanding of what their customers really need and informs product strategy with actionable intelligence.

The use of workshops (or in our case, webinars) to engage and get feedback from customers is a great practice. It provides tons of value to customers while also helping companies to understand their needs better.

Use asynchronous standups to improve team communication

Ted Bauer and Michael Boykin take on daily, synchronous standups in their article The Daily Standup is Broken, What Should You Do Now?

Asynchronous daily standups or check-ins help to put an end to boundless, traditional standup meetings and get the whole team on the same page with fewer meetings. And corresponding written status updates within a team coordination tool or platform — something that allows every team member to share and review updates from today, yesterday, or even last week — allow everyone to consume updates easily and on their own time.

We landed in a similar (asynchronous) place with our standups, and I wrote about it a while back in Useful daily standup meetings for remote teams:

The issue is always the same: How do we have standups that are useful and that don’t feel like busywork that just takes us away from the jobs we’re supposed to be doing? By using an asynchronous bot and adapting the questions to our needs, we accomplished a few important things:

  • Every member on the team takes a few minutes every morning to plan out their day, and troubleshoot anything that might have gone wrong the previous day.
  • Instead of weekly meetings of an hour long where we discuss what everyone’s working on, we now have focused 30-minute meetings every Monday where we solve problems and discuss issues that came up during the week.
  • I am much more equipped to fulfill my role as Product Manager because our updates are more frequent and the signal to noise ratio is extremely high.

Product managers are responsible for team safety

Matt LeMay’s post on how to build safety into team communication might not immediately seem that relevant to product management, but Why is Psychological Safety at Odds With the way we Work? is an excellent reminder for all of us:

Now let’s talk about the product managers who are willing to take on the individual risk that comes with creating psychological safety for their teams. These product leaders often don’t have the opportunity to step into those big “visionary” roles – not because they lack vision, but because they are so busy doing the emotional labor of cleaning up after the other product leaders who are making those big, lofty promises. These are the product leaders who earn the trust and respect of their teams by helping leadership understand the real-world trade-offs that go into actually delivering products, even when leadership doesn’t want to hear about it. And here’s the thing: over time, they actually train company leadership to be better! They sharpen their organization’s focus by saying, “You can have this OR you can have that. Which is more important given our goals and constraints?” These product leaders deliver so much value to the companies they work for, and the truth is, they don’t always get rewarded for it.

Over the years I have become more and more convinced that team safety is the most important job a product manager has.

More

  1. 1
  2. ...
  3. 33
  4. 34
  5. 35
  6. 36
  7. 37
  8. ...
  9. 201