As a high school student I had to go through a Philosophy class, even though my curriculum was in sciences. Zeno's paradox, or the negation of movement, was one of the subjects of that class through which I suffered enormously. Years later, my daughter came back one day with some math homework: the subject was to explain why Zeno's paradox was wrong. And I suffered through it again. This familiarity with Zeno, which I really could have done without, lead me to apply it to IT and what I consider to be the ball and chain that slows IT progress. In Zeno's paradox a runner (Achilles) cannot catch a turtle which started a race earlier than him because each time the runner reaches the point where the turtle was, the turtle has of course moved forward. Repeating this reasoning leads to the conclusion that the interval will become very small, but that the runner will never catch the turtle. What's wrong with the reasoning is that it explains a continuous movement variation through a set of discrete events. But this is what we do in IT: we have a continuous progress of IT technology, hardware and software, and IT projects which are discrete events. When we decide to start an IT project, all hardware and software components are frozen for the duration, while technology continue to progress.
On Thursday, November 5th, from 4:00 to 5:30 PM, Forrester Research is hosting an informal discussion about product management and product marketing issues. This session is the first in what we hope will be a series of conversations about these topics, scheduled at Forrester’s Bay Area office in Foster City.
The topic for this kick-off session is how social media is changing the job description for product managers and product marketers. I'll lead the discussion on this topic, since I just did an all-day workshop about "social product management."
The operative word in that last sentence is discussion. If you want to be pummeled with PowerPoints, look elsewhere. We want to host discussions among product managers and product marketers. Our role is to provide insights from our research, and give you a chance to meet and speak with your peers.
Had some great conversations with the workshop attendees on how PM teams are incorporating social media into their customer and market intelligence (including, but not limited to, requirements). Thanks to all who attended.
Interestingly, we spent a good deal of time talking about the type of questions people ask. In trying to make sense of both social media and PM deliverables, I made a distinction between problem-centric questions, which center on the customer, and product-centric questions, which (as the name implies) focus on the vendor's products and services.
In the technology industry, people are far more used to posing product-centric questions. Gradually, companies are learning the importance of the problem-related questions. However, it's easy to slip from one into the other. It reminds me of how I used to struggle with guitar fingering. As a novice player, I would concentrate for a while on keeping my fingers straight on the frets. Inevitably, as I started to think about other things (strumming, rhythm, etc.), I'd start to roll my fingers slightly to the side, which made it harder to hit the notes I was trying to reach.
Val Workman of Ryma technologies talks about the professionalization of product management, by way of a visit to the metaphorical zoo. Oh, and Frank Capra is there, too. (You have to listen to the interview to understand.) Plus, for this week's review, I put my personal agony with a popular application on display for all to see. (c) 2009 Tom Grant
From my grad student years, I know that a lot of mathematical models fall flat on their simulated faces because they don't get the testing they should. In the case of the PM job calculator/department profiler, I had to apply three different tests.
The tasks are many and varied Last year, when I did the survey research on the state of the product management/product marketing job in technology companies, I vetted the list of tasks with a lot of PMs. Using their feedback, I added tasks, rethought others, and even merged a couple. The resulting list represented everything that PMs might be doing, depending on where they work.
The workshop next week, "Using Social Media To Make Smarter Product Decisions," was a good occasion for me to jump into the data we've been collecting about requirements in the technology industry. It's one thing to claim that there are problems that need fixing, and that social media can help fix them. It's another to put that claim to the test.
The requirements survey has produced a lot of interesting results that will see the light of day in a research document to be published later this quarter. The questions we asked build a composite picture of both the content of requirements and the process of creating them. For example, we asked, ""How much time do you dedicate to requirements work at each stage of the development cycle?" Doing a weighted average of the responses, here's the answer:
As discussed in the last post on this topic, I decided to define product management roles through the tasks that those roles perform. The maxim, "You are what you do," made it easy to define different job categories for product managers and product marketers. A task -based approach also helped make a more convincing argument why particular specializations are necessary.