Showing posts with label Product Management. Show all posts
Showing posts with label Product Management. Show all posts

Sunday, January 24, 2021

Digital Marketing and User Experience Design

 


All companies organize themselves into separate buckets to best focus expertise on business needs. The bigger the companies, the more these buckets are usually distinct from one another. Marketing is often a function of sales. Engineering and product development are often separate. This is a reasonable distinction. Historically, marketing and sales relied upon designers, but in different ways. Today, this is rapidly changing, and the evolution of digital products requires a different approach.

Since the 19th century, designers did not design products. Rather their job was only to make things visually appealing. They did this by adding ornamentation or through marketing. Marketing was important to differentiate products between companies that were otherwise the same. If we look at Nicholas Felton's graph below, we can see that for over 100 years, it was sufficient for a company to make a raw product - such as a radio, or a clothes washer - before having to compete. The job of a designer was to make the package appealing, to draw up posters, and assemble advertisements. 



Today the competition between products is very steep. Everyone has a clothes dryer. It is not enough for a company to produce the object. They must design special variations of the product to appeal to specific groups of people. They must import new features. Some features are engineering problems - like drying the clothes faster. Other features are industrial design problems, like the ambiguous question, "if your dryer connected to your phone, what would be different, and what would that do?" For physical products, the separation of marketing and product design might continue to make sense. But what about digital products?  

If we examine the digital marketing funnel, we see a seamless journey across multiple digital experiences to engage and pull consumers into the business. Visual images, videos, white papers, and previews are used to get people's attention and pull them toward trying the product. Ideally, the product is good enough that they want to use it and tell others about it.  Nested within this flow is the work of the product team, wherein the team is seeking to understand and satisfy customer needs. During and after product use, the team seeks input on how to improve the product for repeat use. 

Perhaps it is time to change this. 

Digital marketing should not be a completely distinct domain from the product design. If we consider the funnel, at large, the funnel is a viable part of the user experience. Digital ads pull the user to a website, and through the website one directly utilizes a web application. The outputs of the web application are typically reports and dashboards that other people will see and use. The outputs should also be considered as part of the marketing funnel, as these artifacts directly inform the successful adoption of the product into a business. The feedback forms, customer support tools, are obviously important to product reuse but this information can drive new marketing tactics and campaigns.

By creating a deeper blend between digital marketing and digital product teams, one can more quickly accelerate audience discovery, engagement,  customer satisfaction, and growth. This does not require people to give up their responsibilities. Rather, the implication is a change in team configuration.  Product teams may not want to merely consist of engineers and designers. Marketing is no longer merely the domain of business. The supply of market expertise and product expertise is fundamental in driving success within marketing teams and product teams. 

This also implies that designers need to learn and think through the broader marketing funnel as much as marketing people need to better understand the workings of product design. If all stakeholders do the work, they will discover great opportunities to accelerate their missions and achieve the outcomes they want. 

Thursday, July 30, 2020

Product management models of despair and awakening

 

How do you build a good product strategy?  A rather classic, default formula is described above. You analyze the competition, you study the market, talk to some experts and persona some customers. Then build and test and role out and pivot and all that tiresome stuff. This is horrible.

Why is it horrible? Because it is the same as a high school essay. You get a prompt, reflect on your life, maybe read a couple books for inspiration, and then cobble together an essay with 5 paragraphs. You probably start writing a terrible paragraph in the beginning, get more succinct as you go along, then rewrite the intro to align with everything else.  In the end you have a coherent product. The downside is that you wasted a lot of time reinventing the "why." 

There is nothing wrong with this approach. But is standard across the industry because for two reasons - it tends to work - and of equal importance, almost anyone can do it. Most universities are not training students to be product managers. It is a generalist discipline. They are trained in business, or computer science, marketing, social science, or humanities. They become product managers because they see an opportunity to supply their broad knowledge with a specific process. They have some level of authority within an organization. I would argue that most people who are product managers do it because they love the idea of the job, and they might also like the product, but probably not as much as the job itself. 

There are other ways to do this. One should indulge in divergent research.  While the image below is amorphous to interpret, it captures the same details as the standard product management model (above) though with a focus on materiality. This element is key. Products are not ideas. They are things. Digital software is a product. Products are intentionally crafted materials that function as a point of change for the user(s). An insurance policy can be a product, because the specific language of that policy was carefully crafted to determine how a person's life will function in relation to a catastrophic event. The distinction between 20 paid physical therapy sessions or 30 can have a major impact on the person's future. A piece of software is no different - if you must spend time searching for features, are uncertain when you need the tool, or ignore half of the software components - the product might not be well designed for you. 

The questions of product development go far beyond immediate usability. They are questions of market fit, acquisitions, and adaptation. How will demand for this product change over time, and who will have that demand? Under what conditions will the product be successful, and when will it not be successful. How much should it cost to build? How and where do people physically acquire it and at what price?

The answers are not easily distilled, nor should the answers be determined lightly. While a simple conversation might inspire a range of insights - everything should be treated as a hypothesis.  But the constant focus on documents fails to capture the material future of the product, and the only way to reconcile the gap, is to immerse oneself into the environments, the populations, and the materials wherein the prospective product will reside. 

So do the work. Immerse yourself. Make things physical. Quit waving your hands. Stop trying to talk to everyone and spend more time identifying the conversations that matter. Stop trying to be clever, and get personal, become a part of the problem you are hoping to solve. Do you have this problem in your life? Do you actively benefit from this product? If your answer is no, then you are probably the wrong person for the job, or you aren't doing your job right.

Product management that matters is a matter of ingress and egress. Like a good anthropologist, you need one foot in the world of the customer and one foot out. How do you know when you made it? Usually because you broke something "in the system" - you crossed a line of distinction, and are no longer an outsider in the eyes of the stakeholders. You are part of the problem. It is uncomfortable. You might be in jail. You might be injured. You might even just be bored, but now you it the line and it is time to pull back one step. 

Do not wave your hands and apply a generic formula for generic people to generic customers. Embrace the magic that flows through the world, dig into the the problem, become the world's greatest expert on the problem from all points of view, and let the solution realize itself through you. Let it awaken.