How would I start developing a product? Are freelance sites such as oDesk or eLance the way to go? Or is a private company a better route? Thanks

Don't Outsource. Period. While there are big drawbacks with outsourcing related to building internal expertise the real reason I would never outsource at your stage is the need for speed and flexibility. Per your description, you are an early stage start-up with a MVP that is gathering data. Congratulations as that is a big accomplishment! However, you inevitably have a ton to learn about what your prospective customers need most and what customers deserve your attention most. The means you will be tweaking your product constantly for the foreseeable future and having to submit ideas to an outsourced team, make sure they understand what you want, wait for the new feature to be scheduled, etc is just too slow and too expensive. You should have your developers literally sitting next to you and (if you have one besides yourself) your product person so you can quickly and constantly share information. Good luck! You are in for a fun ride...

Hello Aidan. I was recently featured on a panel at General Assembly for an audience looking to make a career shift towards product management. In 2014 I moved from a marketing / user engagement role at a software startup to product management. The transition is still fresh in my mind. Based on the experience on your LinkedIn profile, it seems like you would be well-equipped to make the switch. You have a technical background, experience with generating team outcomes and strategic direction. I think the challenge you face is not whether you have the right skills and resources, but rather how you would like to apply them. Product management is broad and so is your choice of employers. It would be great to jump on a call to get a better context of your situation so I can give you specific tips on how to put your best foot forward.

I read your story and I feel your pain, but I have bad news. The problem is not your people, the problem is you. You have a responsibility that goes way beyond developing great products that wow customers; you have the responsibility of leading! Leadership is one of those subjects that most people feel they have covered, I thought I had it covered too until I found myself in exactly the same shoes as you are wearing right now, and boy did it pinch. It took a while for me to realize I was the problem but three things clued me in: 1. I found out that I kept firing and hiring new people and it did not make a difference 2. I met a friend who was building a great company with what I would consider average people and he was really getting things done. The difference was that leading people came natural to him while building products came natural to me 3. I finally came to terms with the fact that I enjoyed being the solution point and the center of the product development universe. Clients loved me, me people stood in awe of me and I loved it and hated it at the same time You need to get into a leadership coaching program. I'm sure you will find some very capable people on clarity but trust me, the sooner you start, the better. Your organization will not change until you change, and there is no better way to say it. Like I said, I know your pain and you are not alone in this my friend.

I am assuming your question is more pertaining to empowering and motivating (rather than hiring). I can outline some of the practices I have seen really result in high motivation and sense of ownership among engineering teams: * Empathize - Your engineering team will work well and be more motivated if they see you as one of them rather than a person who doesn't understand their function. Show your geeky side to them, and show that you understand their thought process and drivers. * Pick their brain on big and small decisions (roadmap, usability, whatever it is) - Product teams value being heard. The more you position yourself as someone who is WANTS to listen, is keen to have their inputs, you will be surprised at how involved they can get, and also how you can actually tap into a lot of smart ideas/thoughts from them that you can develop on. * Take care to explain - show how you arrive at decisions. Share your research, competitive analysis, and even your thought process on arriving at a feature set or list of things for a release. Its stuff you would have worked on anyway - so no harm sharing with more eyes! * Share customer feedback - nothing motivates your engineers than a positive interaction with a customer. Get them to see customer feedback. Have them sit in and observe some of the usability studies. (B2B - have them see you do some demos or do a successful sales pitch) * Send out interesting articles, insights, business and tech articles with your comments/highlights to them on a regular basis (maybe twice a week?) - maybe even some analysis you did on competition or customer feedback * Engineers like working with people they feel are competent and complement the work they are doing to build a great product. So make sure they see how everyone else around them is also doing a good job and adding value and contributing to the success of the product. * Be transparent about the product/business - Make them feel they are responsible and involved in the business, not just technology. I've seen engineering teams happy about their annual goals having components relating to making revenues, keeping customers happy, or reducing costs. If they are enthused about the business as a whole, they will be more motivated with their engineering efforts * Have a mix of little experiments, R&D, attending to engineering debt, in addition to bug fixes and new features that each engineer gets to spend some time on (based on their interest) * Finally get to know each of your engineers personally, and be aware of what their priorities are. Each of us has different motivations in life, so there is no silver bullet to motivate people. When they know you care for them, they are more motivated :).

If you're talking about an app-store launch, then it's important to have the core mechanics of the product (from a user interaction perspective) figured out such that the majority of your users are doing the things you want them to do in order to drive continual engagement with the app. Design polish can come later and often slows down whomever is implementing the development of the app. I don't think anything should ever be "ugly" but lacking polish is often the right way to go to get speed to market. That said, to be sure of the core interactions, you want to do as much testing and observing real users use your app prior to launch. Happy to talk through any of this in a call with you.