A Tech Entrepreneur’s Guide to Early Product Development

Successful companies do not build products for themselves, they build products for their customers. Any IT startup that doesn’t bring customers into the product development process early and often is making a strategic, likely fatal, mistake.

Key Roles: Product Owner and Product Manager — A Compass and a Map

In every product development process, there are two distinct roles: Product owner and product manager. The product owner is the client advocate. The product manager is responsible for the solution architecture and product support. The unique challenge with a startup is that many times the CEO wears both hats.

  • User Focus: The goal is to understand and learn from users. The product owner gathers potential users of the product. This is a great opportunity to reach out to users who are in companies that you view as prospects. Exercise your networking skills with local business people, industry contacts, or university or professional organizations; you may compensate them or not. Somehow you want to keep them connected as a group. However, within that group, consider each person as an individual. What are their pains and their desires — pains that your solution might alleviate or desires and goals that your product might help them achieve. Ask questions and listen. All your product decisions should be driven by a user focus and validated with customers/users.
  • Job Stories: Job stories connect the wireframes and personas. A job story is a powerful way to facilitate team conversation and discovery during product design. Job stories give the design process the context in which a real user will use the solution being designed to perform his or her actual job.
  • User Stories: A user story is a tool used in Agile software development to capture a description of a software feature from an end-user perspective. The user story describes the type of user, what they want from the product and why. A user story helps create a simplified description of a product requirement which leads to the features that get built into the product.
  • Epic and Features: An epic is a way to define a large part of the product that can then be broken down into smaller pieces. A feature captures what the user wants to do. An epic is essentially a large part of the product that can be broken down. It’s important to recognize that an epic can span more than one project and more than one version. Inside an epic are features, which capture what a user requires from the product. A feature cluster is a collection of like features that all belong to a single epic.


This overview is written to give entrepreneurs a sense of how to consider and set up effective product development in a startup IT company.

  • Prototypes and minimally viable products (MVP) help users talk about the features they want and will buy.
  • Whether development is in-house or outsourced, the startup owns the result.

An elite team of product creators and data problem solvers.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store