Unknown taxonomy term requested ()

How Privacy Legislation Will Change The Ad Network/Exchange Paradigm -- Pulling Back The Curtain Of Oz

Blog post info and actions

Blog post body

In my recent paper titled Privacy Laws Force Rich Dialogue with Customers I outlined some of the looming legal directives that will change the targeting dialogue between brands and consumers and how the industry should respond. 

The ad network ecosystem will ultimately be forced the pull back the curtain of Oz to reveal to customers the machines and levers behind targeting technology. As illustrated in my paper, the predominant approaches are full targeting vesus opt out, but this is not enough choice. Segmentation strategies and targeting techniques used by ad tools are hidden within engines and will need to be surfaced to customers so that they may verify, modify, and importantly play with them.

This isn’t easy, however, as the mathematical vernacular of targeting technology with confusing terms such as graphs, nodes, and vectors are unintelligible to most. Metaphors will be needed to distill the complexity for customers. One of the approaches to take will be similar to how optometrists work by showing the customer different "lenses" (perceptions) held about them and subsequently allowing them to choose. These "lenses" may not just be rich segmentation concepts but will include social and individual assumptions too.

Where does this transparency and explanation rationale take us?

Read more

Product Management: You Get What You Pay For

Blog post info and actions

Blog post body

Tom Grant

Another excellent post from Scott Sehlhorst, this time pointing out that, even without product managers, product management still happens. Scott’s post is a response to Jason Calcanis, the founder of Mahalo, who wrote the following:

In under 30 days, we completely overhauled our product-development process, removing everything between the developer and iterating on the product. We eliminated positions and process. We made it clear the developers were to make the decisions even if those decisions resulted in a developer being 50 percent slower because they were busy *thinking* about the product (as opposed to just transcribing features from the product manager wireframes).

If Calcanis is arguing that his company doesn’t need product managers, because they just are in the way, Scott makes the obvious counterargument:

When I was still writing software and leading teams that were writing software, I would occasionally point out that all software is designed – even if someone sits down and just starts typing code. There is, at the minimum, implicit design happening in the mind of the programmer. It might not be “good” design, but there is always design. There is always a method to the madness, just not always a considered method. The same is true of product management...Eliminating product managers does not eliminate product management.

Read more

Please yell at me for doing my job badly

Blog post info and actions

Blog post body

Tom Grant

Last Saturday, at the Silicon Valley Product Camp, I was part of a panel on PM metrics. Any topic that's at the same time important and unsettled keeps you thinking long after the panel, so not surprisingly, almost a week later, I'm still chewing on it. Here's an observation I'll make today, after further pondering:

You know when you're doing well as a PM when someone yells at you for getting a persona, user story, use case, or task analysis wrong.

Understanding the world from the standpoint of the individual buyer or user is one of the primary responsibility of PM. According to some schools of thought, it's the core responsibility, especially since no one else in a technology company is responsible for collecting, analyzing, and distributing these deep customer insights. (There are other core responsibilities, too, related to the company's business and the technology itself.)

That information may look academic, but it should be immediately pertinent in very important ways. Understanding the way in which people in a variety of roles assess, purchase, and adopt technology is critical for making smart decisions about everything from product design to the product roadmap, from crafting messaging to choosing marketing channels. Unless you live in a Soviet-style command economy, in which manufacturing 3,000 left shoes is a problem for the consumer, not the producer, customer insights need to inform both strategic and tactical decisions.

Read more

How demographics matter in B2B tech adoption

Blog post info and actions

Blog post body

Tom Grant

In case you wanted to attend tonight's open house on the demographics of B2B technology adoption, here's a pertinent diagram from a recent publication on the subject. As you can see, when they look for information, two people in the same department—an application developer and an enterprise architect—go to very different sources.

  • Conclusion 1: Demographics matter. A lot.
  • Conclusion 2: If you say that your target customer is developers, you need to take a big product marketing time-out. Not all development professionals are the same. Now march up to your room and think about that.

As important as conclusion 1 may be, it's not exactly profound. Sure, we all know that people are different, but what are the significant differences? And how should these variations affect the way we market our technology to rank-and-file developers versus the fancy-pants enterprise architects?

Many efforts at persona development break down at the very beginning, with the question, How many different personas do I need? There's no obviously correct answer to that question, especially when you haven't seen the data that indicates which demographic differences are significant, and which aren't. (Leaving aside the practical question of how many personas you can actually produce.)

Read more