kenyarmosh

16 yıl öncediscuss

Actually, I specifically bring up beta testing and testing with real world customers/conditions instead of addressing Andrew's question about what's involved in submitting an app. It was that important for me to mention it. Of course, we could spend an entire interview discussing that aspect, so perhaps that is why you perceived me glossing over it. :)

kenyarmosh

17 yıl öncediscuss

Having worked as a startup "product guy" for the last five years, I think there are some good answers to the original question.

Several notes:

1) If you fall into the trap of thinking that engineers, technologists, CEO's, and others can handle this role, you'll just be part of hundreds or startups that don't have their act together. I've sat down with way too many startups who both don't have a handle on the marketplace or customer needs and have poor processes in terms of planning / prioritizing release cycles and roadmaps. While others in the company should have a grasp of both of these elements, the key point is correctly identifying the first part (i.e., customer needs) and then mapping it to the second (i.e., the roadmap).

2) The person who fills this role should be fairly well-rounded and be sort of a weird breed in that they actually are comfortable (and good at) talking with people (customers) and yet can get down into technical details. I wouldn't go as far to say that coding is necessary but surely mocking up initial wireframes and UX should be considered as part of the job.

3) Related to terminology, I'd try to stay away from using labels like "project manager" or "program manager." These are way too broad and make it seem like the role is more focused on logistics and coordination. Above all, this role is strategic...keeping the trains running on time is just one aspect and arguably, not the most important.

comments