Skip to main content

Product Talks #4: Balancing Commercial Initiatives with User Experience Concerns

I will be in Sydney, Australia in early November to facilitate the fourth installment of brainmates' Product Talks. The conversations will focus on the challenges of balancing commercial initiatives with user experience concerns. A copy of the media release follows:

Raising the Bar on Product Management Excellence

brainmates is inviting Product Management specialist, Roger L. Cauvin, to Australia this November to lead public and client events in Sydney, offering his expertise and fresh perspectives in Product Management to local corporations.

Cauvin will be facilitating brainmates fourth Product Talks session, a free quarterly forum that brings together product and marketing professionals to network and discuss issues in contemporary Product Management. Cauvin will lead conversations on ‘Balancing Commercial Initiatives with User Experience Concerns’ on November 5th at brainmates’ office. Registration is required to attend Product Talks events.

A selection of brainmates clients will also be hosting special roundtable events with Cauvin. Product teams will have the opportunity to broach specific Product Management concerns they want to resolve and gain sound advice and new solutions from his Product Management experience and work in the United States.

The series of events are a part of brainmates corporate initiative to build a solid foundation for the Product Management profession in Australia.

In addition to being the principal consultant of his own company, Roger L. Cauvin is the owner and operator of Dadnab, a successful text messaging service for transit planning in the United States. Cauvin also helps manage ProductCamp in Austin, Texas, the American version of brainmates Product Talks.

brainmates continues to invest and promote Product Management excellence and innovation in Australia through their services, events and resources.

For more information contact Adrienne Tan on (02) 9232-8147.

Comments

Unknown said…
Sounds pretty cool, congrats and enjoy!

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