How to write an Internet product plan

By Nathan Rohm

Rate: (1 Ratings)

Learn how to write a useful Internet product plan

Instructions

Difficulty: Moderately Challenging

Things You’ll Need:

  • Web Developers
  • Web Designers
  • Database Developers
  • UX (user experience) test team
  • Project managers (this may be you)
  • Testers

Step1
Identify the business need for the product. Everyone needs to know the vision for the product. Who will buy it? How much money will it make for the company? Add this and forecasts to the plan.
Step2
Identify the product requirements. How is the product going to work? Describe the requirements of what it is supposed to accomplish. You can write use cases, scenarios and personas if they help define what is going to be accomplished with the product.
Step3
Describe the product itself. You can do wire frames drawings of what the product will look like, how it will act, and how users will accomplish tasks. Add this information to the plan.
Step4
Work with the developers, designers, and managers to understand the scale and scope of the project. Identify the underlying technical tasks that need to be accomplished. Add this information to the plan.
Step5
Work with the marketing, support, and sales team to identify what is required to sell, document, and support the product. Talk to legal, accounting, and billing teams to make sure all the bases are covered. Include any localization teams as well in the discussion. Add all the action items, time requirements, and resource needs to the plan.
Step6
Break the project up into manageable chunks (from 1 to 4 weeks in duration). Decide on milestones for the project, at it to the plan.
Step7
Create a schedule, assign resources, and add it to the plan.
Step8
Launch the project. Adjust the plan as needed.
Step9
After the project is completed run a post-mortem discussion. Figure out what worked, what did not work, and how to improve things in the future.

Tips & Warnings

  • Learn how much detail is needed by letting developers, designers, and managers contribute to the plan
  • Test regularly with real users (at least 5) before you launch.
  • Too much detail in your plan can kill innovation and cause overly complex solutions -- give your developers room to fulfill the requirements with creativity
  • Too little detail in your plan can cause confusion and poor results. Find the right balance.
  • Be willing to adjust your plan. Things change. Get comfortable with some ambiguity.

Post a Comment

POST A COMMENT

Request a New How-To Article

Looking for more How To information? Chances are there’s an eHow member who knows how to do what you’re looking to do. Submit an article request now!

eHow Article:  How to write an Internet product plan

eHow Member: Nathan Rohm

Nathan Rohm

Enthusiast Enthusiast | 400 Points

Category: Business

Articles: See my other articles

Related Ads