I'm a first time founder, right out of college. My friends (and best developers[1]) liked my passion for the idea and joined this journey as early engineers. As a founder I look after the product - what to build and how to build.<p>Everyone told me you need to have a clear vision for the product from day one, so I (just me) sketched the product road map for first version. We're moving very slow according to deadlines for the tasks, not because we are lazy but the tasks we thought would be easy aren't that easy. (<i>data extraction - unstructured data</i>)<p>I wanted to hear from you folks:<p>1. How to set clear/accurate deadlines?<p>2. How do you come up with product roadmap? By talking to your founders or engineers also?<p>Thanks!<p>*
[1] - best among the current 21 yr olds in India
I've found that words, ideas, and plans count very little. Having something working to demo is much more impressive. So I'd suggest setting your first deadline as making a prototype. Then formulate your next steps after that.
About setting clear and accurate deadlines- Try setting smaller goals by allocating time in mins our hours. Have a shared spreadsheet where you can list down your names and the things you'll are working on. update it with reasons as to why it didn't take as much time or less. Do this once every day. This will help you get smaller things done quickly and be accountable to one another.<p>about your product--> talk to your customers and understand their reasons for using your product. Focus on what are the key features that are important and how you can add additional value by leveraging your core strengths
You need to talk to customers to figure out what their most pressing issue(s) are/is.
<a href="http://en.wikipedia.org/wiki/Lean_startup" rel="nofollow">http://en.wikipedia.org/wiki/Lean_startup</a><p>Second check out this:<p>Check out this wkipedia article on the <a href="http://en.wikipedia.org/wiki/Project_management_triangle" rel="nofollow">http://en.wikipedia.org/wiki/Project_management_triangle</a>.<p>Also, no one has a good way to estimate tasks you have that aren't similar to stuff you've already done.
First recommendation: read The Lead Startup - it's great for guidance on building a minimum viable product and basing feature releases around what you know about your users.<p>Your roadmap should ultimately be based on what you learn from your users and what will build the product, not what you think will bring in more users.<p>Should if you have any specific questions - @paulnrogers
>1. How to set clear/accurate deadlines?<p>Can you determine within the next 7 days, what is the most important result the business must achieve? Why is that a priority? What are the least number of actions to achieve it?<p>List those out-- that's the road map. Start on item #1.
Here's a good post on this topic: <a href="http://tomtunguz.com/three-minutes" rel="nofollow">http://tomtunguz.com/three-minutes</a>