Skip to main content

Join Me at ProductCamp Austin 12

Join me Saturday, February 15th, 2014 for ProductCamp Austin 12.

By now, if you're a product management, marketing, or technology professional, you've probably heard of ProductCamp. ProductCamp is an "unconference" where product management and marketing professionals teach, learn, and network.

ProductCamp depends on volunteers to organize it, propose and lead sessions, provide lively conversation and debate, set up and tear down the day of the event, and recruit sponsors to keep it free. Participants can propose sessions prior to the event, and participants vote the morning of the event to determine which sessions they will have the opportunity to attend throughout the day.

As I write this blog entry, registration for ProductCamp Austin 12 is open. If you're ready to commit to participating in the product management and marketing conversation, I suggest you register now. The slots usually fill up quickly. If you'd like to present or lead a conversation at the event, propose a session.

I've proposed a session called "5 Ways Companies Make Product Decisions".

Is your company making ad hoc or informed, deliberate product decisions?

In the session, we'll look at five ways companies make strategic and ongoing tactical decisions about how they develop, market, and sell products and solutions. How do they decide what features to include in their products, what messages they will use to articulate the value of their products, what marketing tactics they will use, what prospective customers they will target, and other day-to-day choices?

We'll discuss the pros and cons of each method and explore other methods that may be more likely to result in product success.

I'd love to hear your perspective and see you at ProductCamp Austin 12.

Comments

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio