Snowboarding Lessons

As I mentioned a little over a week ago, I went snowboarding in Utah. I stayed with my friend, Chris, and his wife during my visit. I snowboarded for six straight days at the Brighton resort. It was my first time, so I took lessons the first day. The instructors taught me the basics and, by the end of the day, I was able to do 'S turns'. An S turn is where you go down the hill, turn in an arc towards one side, then go down the hill and turn in an arc towards the other side. It keeps your speed under control. Once I knew how to do S turns, I felt it was time to practice rather than take more lessons. So the next five days I spent perfecting my S turns, while progressively subjecting myself to more difficult courses (blues and even some segments of blacks). For anyone, including experienced skiers who haven't snowboarded, I have the following observations:

Take lessons. Practice is very important, but you have to know what to practice.
The frustration of the first day or two learning to snowboard is well worth it. Be prepared for a lot of falling down and a lot of minor aches and pains.
Don't skimp out on the protective gear. I fully decked myself out with a helmet, wrist guards, knee and elbow pads, and goggles.
Keep your speed under control. Slower speeds reduce the likelihood of injury.

Between snowboarding and visiting my friend Chris, I couldn't have asked for a better trip.

Comments

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

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problem

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

Cauvin

Search This Blog