Skip to main content

Join Me at ProductCamp Austin 11

Join me Saturday, July 20th, 2013 for ProductCamp Austin 11.  ProductCamp is an "unconference" where product management and marketing professionals teach, learn, and network.

Two years ago, John Milburn, Scott Sehlhorst, Paul Young, and I led a session on "The Future of Product Management". We noted that the "lean startup" movement was on the rise and would soon become a focus of product management discussion and debate. Sure enough, "lean startup" is all the rage these days, or at least talking about it is.

Yet to the extent product managers have embraced lean startup concepts, most of them have barely put them into practice.  They've done little more than compose a business model canvas or used the "minimum viable product (MVP)" buzzword a few times.  How can product managers move beyond these basics, put lean startup methods into practice, and derive real value from them?

I've proposed a session called "Let's Get Nekkid: Applying Lean Startup Methods":
You've heard about lean startup, and you may have even gone through the exercise of composing a business model canvas. Let's move beyond the theory and hype and examine the practical tips, tools, and guidelines you can use to apply lean startup methods to your company's product management and marketing efforts.

We'll briefly cover business model canvases, but we'll also look at the real-world application of customer development interviews, minimum viable product (MVP), funnel metrics, experiments to test and revise assumptions, instrumenting products to gain insight into what users are actually doing, and the pitfalls of applying lean startup methods.
The full list of proposed sessions is here.

WHAT: ProductCamp Austin 11
WHEN: July 20, 2013 from 8:30 AM to 4:30PM
WHERE: AT&T Conference Center @ 1900 University Ave., Austin, TX 78705
COST: Network, volunteer, pitch a session idea, or just make new folks feel welcome.

You must register (free) to attend.

You can get transit directions to the event by visiting the Capital Metro trip planner and filling in your starting location. If you choose to drive, parking is available for a fee in the AT&T Center underground parking lot.

Labels:

Comments

Post a Comment

Popular posts from this blog

What Product Managers Can Learn from the Apple iPod

The Story When Apple unveiled its iPod digital music player back in October 2001, I dismissed it as a  parity product . I already owned the Cowon iAUDIO CW100 MP3 player, loaded with my favorite tunes. There was Apple, generating great hype over the iPod as if it were a breakthrough product. The idea of a portable digital music player was nothing new. The first mass-produced MP3 players came out in 1998. In late 2001, the concept may have been new to a lot of Apple customers, but it wasn't new to me. I proudly showed my MP3 player to friends when they gushed about the iPod. Thus Apple's iPod was not an innovative product in and of itself. Years later, however, I realized the significance of ecosystem of which the iPod was a part. Apple had released iTunes (with technology purchased from  SoundJam MP ) and created the iTunes Store for finding and downloading music. Unlike Napster , it was a safe and legal way of distributing and acquiring music. The prior way of playing
2 comments
Read more

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
32 comments
Read more

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
8 comments
Read more